On Thu, 2008-01-31 at 06:45 +0100, Matthias Wessendorf wrote: > > > The only direct alternative I can see is Matthias' view that components > > > should not be edited at all, and all custom logic should be in renderer > > > classes. However like Mario I am rather skeptical about that; it just > > > does not sound right to me. And in any case, that still qualifies for a > > > number of the above categories. > > > > Matthias view sucks, cause component logic should be right where the data > > is, according to object-oriented principles - and not in the renderer. The > > renderer is only there for RENDERING logic, as the name says. > > Please show me the lines, where I said "no component logic inside the > components"....
Sorry, looks like we have all misunderstood what you meant. So you also recommend that a uicomponent should contain any "business logic" specific to that component, and that the renderer just contain the "presentation logic"? But in that case, many uicomponent classes will have code in them that differs from other uicomponent classes and cannot be auto-generated, so this also means that a "template" will have more stuff in it, and need to be more often debugged, ie that the suckiness level of generating uicomponent classes again goes up. I had thought you were recommending simple "dumb" uicomponent classes - which would indeed be better candidates for code-generation. What point were you originally wanting to make about the Trinidad approach? Regards, Simon
