Hi Olaf, I think the topic is no more "Jewel Refactoring", since many of the refactors I think where ok, but "UI sets dependency on actual Basic", and if we want to make that grid, the points to evaluate should be "Processing of non used CSS " (or "non CSS default" as you posted, "have lots of unused TLCs in class path for nothing", and many other points I put on other emails. Since other like Less code duplication will not apply if we have all beads and supportClasses in Core and/or Foundation.
Maybe other that want Jewel to depend on Basic should put the lines of why we they want to depend on TLCs and CSS that will never be use on Jewel as well to complete the matrix. Thanks 2018-07-05 21:23 GMT+02:00 Olaf Krueger <[email protected]>: > Hi Carlos, > I just saw post after posting the matrix example. > > I don't want to trigger another discussion but I am not sure if all others > know about all the details which were discussed in the past. > I am also not sure if it is possible to find a consensus by going the > current path. > So, having such a matrix would make it easy for anybody to understand the > different goals and the pros and cons of different approaches. > Moreover, I think it would be good if such an important decision would be > documented. > It also could help to convince others that the alternative which will be > found (whatever it is) makes sense. > > However, just an idea ;-) > > Thanks, > Olaf > > > > -- > Sent from: http://apache-royale-development.20373.n8.nabble.com/ > > -- > Carlos Rovira > http://about.me/carlosrovira > > <http://apache-royale-development.20373.n8.nabble.com/> > >
