Name clash

[BeastyBlacksmith]

We clash names with https://github.com/tkf/Kaleido.jl
Other good name suggestions? @joshday, @sglyon

[BeastyBlacksmith]

PlotlySave.jl exists already, Savefig.jl would still be available, but is maybe a bit too broad.
PlotlyFile.jl or Plotly2File.jl would also be available.

[sglyon]

Maybe we coordinate with @hhaensel to use PlotlySave.jl?

[joshday]

PlotlyKaleido?

It looks like PlotlySave implements FileIO.save, which we would be unable to do since the types we need live in different packages.

[hhaensel]

Hi,
Not sure what the scope of that packages shall be. If it is identical to mine, feel free to take over PlotlySave.
I offered this already some time ago before I registered the Package.
In that case I propose that PlotlySave is migrated to JuliaPlots

[BeastyBlacksmith]

The scope of this package is much narrower than that of the current PlotlySave, it takes a valid plotlyplot json string and creates an output file from it, if you don't intend to develop/maintain it we could move it to JuliaPlots, make a breaking realease and replace it with this version of the package since according to juliahub PlotlySave has 0 Dependents.

Otherwise PlotlyKaleido would also work for me.

[joshday]

My vote would be to register this repo as PlotlyKaleido as the path of least resistance.

[hhaensel]

If you are interested you can migrate the Package to JuliaPlots and publish a new version.
Wouldn't you think that it's interesting to keep the savefig command as is?

I understand that the definition of FileIO.save() is strictly speaking type piracy, although I still find the syntax tempting. Not sure, how a correct way out could look like. Perhaps by defining a format type that resides within PlotlySave and which is mandatory when calling FileIO.save ...?
Let me know what you think.

[BeastyBlacksmith]

I've gone with PlotlyKaleido now, since I do find it awkward to change the scope of a package between major-versions.

[BeastyBlacksmith]

JuliaRegistries/General#67704 🎉