Hi, considering making Jewel dependent on Basic. I'm trying to put my mind in that place. Since this is a huge effort for me, hope you all try to do the same as me and considering some thoughts, so we can plan something that works for all:
Since Basic will be the middle point between Core and Jewel, can we consider to move Basic CSS and TLCS to a BasicUI swc? So Basic could be really the common basic library and CSS doesn't mess Jewel things? If so, we can go that router and test and discuss that integration in a separate branch and deal with all of that. this will inevitably delay the release, but maybe is time to solve this first. One of the things to do in the final result is to compile Jewel (debug and release) and comparte results on develop and results on integration branch Then we can decide what's better and release that Thoughts? El lun., 3 sept. 2018 a las 4:53, Alex Harui (<aha...@adobe.com.invalid>) escribió: > FWIW, I agree with Harbs. Enough time has passed and changes have been > made that it is time to try making Jewel dependent on Basic so we can see > in code (not words) what the problems are with doing that. > > My 2 cents, > -Alex > -- Carlos Rovira http://about.me/carlosrovira
