Open Evizero opened 8 years ago
Not sure. It might be good to keep it as a catch-all for JuliaML plotting. Or maybe everything has a better home?
On Tuesday, August 23, 2016, Christof Stocker notifications@github.com wrote:
A lot of recipes have now moved to their respective packages.
What do we want to do with this?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/JuliaML/MLPlots.jl/issues/13, or mute the thread https://github.com/notifications/unsubscribe-auth/AA492qISyLEaGqu9NT3HG3m8NLSuoEpzks5qizmUgaJpZM4JrOsJ .
Well one thing we could do here is test the recipes in our JuliaML packages. As it is currently I avoid testing those in the main packages because of travis inconveniences.
Either way, this package would need some cleanup. For example subplot
is still used here, while I think that doesn't exist anymore in Plots
Agreed. This needs cleanup. I like your idea to do all the testing here! (I really need to improve VRT)
On Wednesday, August 24, 2016, Christof Stocker notifications@github.com wrote:
Either way, this package would need some cleanup. For example subplot is still used here, while I think that doesn't exist anymore in Plots
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/JuliaML/MLPlots.jl/issues/13#issuecomment-241957072, or mute the thread https://github.com/notifications/unsubscribe-auth/AA492mBJb5Gr_NKzDm0jQ06sa0WrChNmks5qi85fgaJpZM4JrOsJ .
A lot of recipes have now moved to their respective packages.
What do we want to do with this?