Hi Olaf, you're right. But what I'm trying to say is that we discussed long over various things. That was very positive since we found many bugs and problems, so discussion brings many positive things. Not the final thing where I think we are stuck is in something that technically I think is better (and I refer to lots of emails of points and thoughts), for me this is important and spend many time to make all understand why I don't want a UI set depends on another and depends on CSS and have TLCs that you normaly would not use and can make people end taking the easy way just because you have some code in your class path, and making problems more difficult to detect. as I said we had a community problem still undiscussed and unsolved, since we still didn't close this one. And other leave the project because of that problem. So it's normal in this case talk about leave, just because is something implied in the discussion. I think in other projects things are managed more easily and discussed and things are not taken so strictly giving way to the participation of all. We should get to that place if we want to evolve as a community.
About the matrix you proposed I think we discussed way to long over it, and for me that will be started it over again. I think we have all data in the table and if I can recall right, the only point to go forward is if we want UI sets depends on actual Basic or separate Basic TLCs and CSS to it's own library, what I highly recommend, since I don't see coding Jewel with actual Basic dependency. thanks 2018-07-05 18:18 GMT+02:00 Olaf Krueger <[email protected]>: > Hi, > > >fixed things could make people not be happy at all with the solution, and > end leaving > > I prefer to don't speak all the time about leaving. > Anybody is free to leave at any time, same as in the real world. > But leaving because of technical decisions is completely incomprehensible > for me... as long as decisions are made in favor of the project and not to > suit someones personal taste. > > However, this is a technical project here and I think it should be possible > to find a decision based on technical facts. > > One way to get a decision could be to build something like an evaluation > matrix. > Criteria have to be listed and weighted and particular alternatives have to > be evaluated. > The goal is to get the best alternative/solution. > > I'll try to prepare an example tonight. > > HTH, > Olaf > > > > -- > Sent from: http://apache-royale-development.20373.n8.nabble.com/ > -- Carlos Rovira http://about.me/carlosrovira
