> This could be a new repo for Royale that hosts that library and other extra things that are not so core but could be needed in some apps.
I think that when anyone creates a library (or externs) for Royale, we should encourage the creation of external repos that aren't managed by Apache. Not everything needs to be bundled with Royale. Even committers/PMC should consider this. In my opinion, something like html2pdf feels like one of those things that should be managed externally. I'll add that one sign of a healthy ecosystem for a framework/SDK is a variety of external community projects. Royale doesn't have enough of those, I think. -- Josh Tynjala Bowler Hat LLC <https://bowlerhat.dev> On Wed, Jul 22, 2020 at 3:33 AM Carlos Rovira <[email protected]> wrote: > Hi, > > Piotr talked about moving the html2pdf lib I created and to some external > repo. > > This could be a new repo for Royale that hosts that library and other extra > things that are not so core but could be needed in some apps. > I think we could even segment and take this opportunity to clean a bit of > what we have, since I think we have many experiments that seem to not reach > a final usable point (i.e: createjs or flat), but have a cost currently in > our daily builds. Only people that need this one will need to build it. > > For example some segmentation could be: > > * extern libraries (html2pdf one will fall into this category, if create an > ECharts lib, that could be done here,...I expect this one will most needed > for royale developers) > * new royale libs that are create from scratch, but doesn't fit into some > core functionality (i.e: MDL UI Set) > * experiments (we could move here unfinished libs like createjs or flat > from asjs, so asjs one will benefit from building faster by moving things > not used to that one) > > I must say that probably I don't have the time to work on that now, since I > have other tasks for Royale in the near horizon, but we can see if this > makes sense and even see if others can take over. > > Thoughts? > > > > El mié., 22 jul. 2020 a las 11:48, Piotr Zarzycki (< > [email protected]>) escribió: > > > Yeah it is, but I need to checkout your whole website in order to get > that > > library. It would be great to checkout only that and have it. - That was > my > > point. ;) > > > > śr., 22 lip 2020 o 11:39 Carlos Rovira <[email protected]> > > napisał(a): > > > >> Thanks folks :) > >> > >> @Piotr Zarzycki <[email protected]> the library is opened in > the > >> Codeoscopic repository, so it's available for all. But I'm open to > moving > >> to another place. Even we can host here in Royale since html2pdf is > MIT. Or > >> host royale-extras, if we consider it is not core but an "extra" that > could > >> be needed. So we can create a directory of external libraries that > royale > >> users can need at some point. The problem I see in royale-extras is that > >> maybe will need some maven setup in order to release libs like this. > >> > >> [1] https://ekoopmans.github.io/html2pdf.js/#license > >> > > > > -- > Carlos Rovira > http://about.me/carlosrovira >
