Hi Piotr, I think Core or Core + Foundation should have all the reusable pieces for the rest of UI sets (Basic, Jewel, Express, and more) and those combine regarding their objectives.
Basicaly core classes, interfaces, supportClasses and beads. For example almost all *Base.as classes should be common, and then final and TLC implementations must go to the UI Set. For example Group and Container start to evolve differently in Jewel that Basic as I told it will happen Initially that was a copy/paste, but just to part from a working state, then I'm changing it to become what Jewel requires. For me is just to start working on that instead of writing more emails about this. Carlos 2018-07-05 11:46 GMT+02:00 Piotr Zarzycki <[email protected]>: > I remember that Harbs asked your for list of files which should be part of > Core yes ? You said that you will do this and discussion died in that > place. > > > czw., 5 lip 2018 o 11:39 Carlos Rovira <[email protected]> > napisał(a): > > > I think the discussion was mainly done and that we agree in almost all > > things but one: Should Jewel link Basic? For me it's clear that no. > > Should Jewel use code in basic, clearly yes. So that left us with only 3 > > options: > > > > 1.- Make Jewel link Basic. But I against this solution due to many > points I > > exposed in lots of emails before. > > > > 2.- Separate Basic in two: Foundation (that's beads, supportClasses, and > so > > on, no CSS here) and Basic (TLCs, CSS,...). I think this is the middle > > point where we should go as a community that wants to hear all voices and > > respect all visions. For DG case, Jewel will end taking the needed common > > pieces from Foundation. > > > > 3.- Duplicate code. I think the worst solution since no body wants it. > > > > For me this discussion can't give us more, since we all know how others > > think and is not about one think is better that the other, is clear as > well > > that all are valid solutions, but we need to take a path to continue our > > way. The path should not be one fixed solution 100%, but a mixture of > > various since we are community and fixed things could make people not be > > happy at all with the solution, and end leaving. We have a huge historial > > of leaves to make this happen again and some community things to talk > about > > yet that we said will do after closing this discussion. > > > > IMHO, point 2 is the middle solution and for me the recommended to take. > > > > Just my 2ctns > > > > Carlos > > > > > > 2018-07-05 11:14 GMT+02:00 Piotr Zarzycki <[email protected]>: > > > > > Hi, > > > > > > Someone could start work on DataGrid, but the discussion about not > using > > > Basic/Express in Jewel has not been finished. I don't see how actually > is > > > create that sophisticated component without inheriting those one from > > > Express. > > > > > > Piotr > > > > > > -- > > Carlos Rovira > > http://about.me/carlosrovira > > > > > -- > > Piotr Zarzycki > > Patreon: *https://www.patreon.com/piotrzarzycki > <https://www.patreon.com/piotrzarzycki>* > -- Carlos Rovira http://about.me/carlosrovira
