norman wrote: > Carl Karsten wrote: > >> There are 2x2=4 groups of people: those that do/don't want to override dabo >> framework code and those that do/don't understand the i-layer idea. >> >> 1 do, do = easy to manage changes. >> 2 do, don't = change the code in the dabo classes and have to merge updates. >> 3 don't, do = i-layer is useless. >> 4 don't, don't = spend a bit of time and at some point realize they don't >> care > > This looks like you are trying to make the case that you and those who would > like the changes you want are in the majority.
Not at all. I have no idea of the distribution. > In fact, the majority just want to use Dabo to make their desktop apps. How do you know that is the case now and in the relevant future? > It is already clear from the discussion alone that this addition would be a > time consuming process. Minimal. To add this pattern now, they would need to create the empty classes (i-layer) and add an "i" to the beginning of all the places where they reference a class. The class creation can be automated (which is what I am trying to figure out how to do - so that part will be 'done' regardless of who does it.) > My opinion is that Ed and Paul should be left to spend their time catering > for the majority. That is an easy position to take when you are in the majority. :) I like the "minimize the average time developers spend" model, which is kinda the point of a framework. there is a group of developers - give them a tool that makes them able to code apps more efficiently. If a feature saves one developer 10 hours, but costs 10 developers 30 minutes (time spent investigating new feature) I think it is a good feature, > If you want to change Dabo then go ahead and do it. If, as you seem to > suggest, the changes would be transparent to ordinary users, then submit your > changes to be included as Dabo, I need to know if Ed/Paul want to use the pattern. Ed has done it, so I don't need to implement it for him to understand it. I think Paul gets it, but doesn't understand the value of it. If they do want to use the pattern, I will be happy to make the changes. Actually, one of the reasons I want this pattern is so I can make changes and submit* them, and if they are rejected, I can keep using them for my apps. (*submit as in show and discuss, not submit a patch. once the change is approved,then there would be a 'move' step to integrate the change in the dabo base classes.) Some key parts of the VFE framework lived in my i-layer for over a year. Carl K _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
