Hi again! This is mainly to Reinhard and Sylvain, I guess. Who else is a CForms guru here? :)
I have a question about the inheritance and namespace/inclusion semantics which are not really discussed in the wiki. 1. What about nested libraries? In the wiki it says it forms a flat namespace. Would that be like this: include library 1 as "lib1" and library 2 (from library 1) as "lib2", then all macros of lib2 will still be accessible as lib2:name in a definition which includes lib1? It also mentions a tree like model (I guess like java packages?), which would result in "lib1:lib2:name" to resolve to a macro in lib2? I guess both would be sort of easy to implement. 2. Can any widget type be macro-ized or only fields? I guess any would make sense... Can macros be extended in the form definition? 3. Extension/Inheritance of widgets may be a problem as currently the validation of configs is done within the builders' buildWidgetDefinition() method. May need to implement "extendWidgetDefinition(Element, WidgetDefinition)" for each of the builders. Default may be to just return the given definition. Could be called in AbstractWidgetDefinitionBuilder.buildAnotherWidgetDefinition(). Do you think that would that solve it? 4. What exactly is the NewDefinition for? For dynamic form generation? In that case, I guess, I can reuse some of it's parts for the MacroDefinition(Builder), yes? 5. What about caching or reloading libraries if they changed? How is that handled right now? Sorry if I am rambling a bit... Once I get this straightened out, I will post my ideas for a solution on the wiki, like requested. Good night! max On 6/9/05, Max Pfingsthorn <[EMAIL PROTECTED]> wrote: > Hi Reinhard, > > Good. Err, should I put my SoC application there then? Seems to me > more like a problem statement (for CocoonRefDocProject) than a > proposal for a solution... > > Thanks and bye! > max > > On 6/9/05, Reinhard Poetz <[EMAIL PROTECTED]> wrote: > > Max Pfingsthorn wrote: > > > Hi! > > > > > > I have a question. There are two, somewhat conflicting descriptions of > > > the CForms project on the wiki: > > > > > > http://wiki.apache.org/cocoon/CocoonFormsScratchpad > > > http://wiki.apache.org/cocoon/WhiteBoardCocoonForms > > > > > > I guess the most recently edited one (WhiteBoard...) is the most > > > preferred one... is that so? I just would like to make sure. > > > > > > Oh, I am finalizing my proposal now, should I send it here first for a > > > quick glance over? > > > > yes to both questions. I propose that you add your proposal to the wiki > > (http://wiki.apache.org/cocoon/GoogleSummerOfCode2005) > > > > -- > > Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach > > > > {Software Engineering, Open Source, Web Applications, Apache Cocoon} > > > > web(log): http://www.poetz.cc > > -------------------------------------------------------------------- > > > > > > > > > > > > ___________________________________________________________ > > Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier > > anmelden: http://mail.yahoo.de > > > > >
