cocoon-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From stev...@outerthought.org
Subject [WIKI-UPDATE] WoodyScratchpad LenyaEditors ConnectionPooling Mon Mar 29 16:00:05 2004
Date Mon, 29 Mar 2004 14:00:05 GMT
Page: http://wiki.cocoondev.org/Wiki.jsp?page=WoodyScratchpad , version: 11 on Sun Mar 29 13:35:57
2004 by 195.144.88.29

+ 
+ 
+ ! Alternative suggestion (''added 20040329 by mpo''):
+ 
+ Given the fact that this starts looking like namespaces a lot, why not also adopt the syntax
of namespaces?
+ {{{
+   <wd:any-scope wdns:my-types="cocoon://MyOwnTypes.xml"
+                 wdns:other-types="cocoon://OtherTypes.xml"/>
+ }}}
+ 
+ and reference some definition in there with: (preferig the colon over the dot)
+ {{{
+   <wd:widget id="my-widget" extends="my-types:some-type-definition"/>
+ }}}
+ 
+ 
+ 
+ IMHO having the prefix-to-source binding declared as attributes makes the scoping a lot
more transparant. (otherwise the lookup for resolving would not only be about looking in the
ancestor axis, but also into the preceding-sibling which IMHO 'blurs' the relation between
containment and scope?) 
+ 
+ This would also stress nicely that prefixes only have local scope, that the sources are
the real important things, and that the form-manger could cache these repositories based on
the source.
+ 
+ Additionally we could have the form-manager entry in the xconf kind of pre-load repositories
like this by adding the sources (without prefixes since those have only local meaning) to
the configuration?
+ 
+ 
+ 
- **Top of the form definition.
+ **Top of the form definition. 
?                              +

- **Anywhere a widget definition is allowed.
+ **Anywhere a widget definition is allowed. (+1 mpo)
?                                           +++++++++

- *Where should imported types be registered (affects namespace)?
+ *Where should imported types be registered (affects namespace)? (mpo: I don't get this question)
?                                                                +++++++++++++++++++++++++++++++++

- **Widget definition prototypes.
+ **Widget definition prototypes. (+1 mpo)
?                                +++++++++

+ (''mpo: I like the latter most, reads like <xsl:choose><xsl:when test="..">..<xsl:otherwise>..'')
- *Instead of using an empty "id" attribute should we use <wd:default/> as the default
case? (+1 tim)
+ *Instead of using an empty "id" attribute should we use <wd:default/> as the default
case? (+1 tim, +1 mpo)
?                                                                                        
          ++++++++

- *How should we indicate when we do not want to allow a default selection?
+ *How should we indicate when we do not want to allow a default selection? 
?                                                                          +

- **Do not supply a default case.
+ **Do not supply a default case. (+1 mpo)
?                                +++++++++

- *What should we do if the expression evaluates to the default anyway?
- *What namespace should the widget id's be in?
+ *What should we do if the expression evaluates to the default anyway? (mpo: seems more logic
in the when@test/otherwise filosophy?)
+ *What namespace should the widget id's be in? (''mpo: supposing you refer to namespacing
with respect to generated request-parameter names, right?'')
- **widget-id -- Same as widgets outside the choice. (+1 tim)
+ **widget-id -- Same as widgets outside the choice. (+1 tim, +1 mpo)
?                                                           ++++++++

- **case-id.widget-id -- wrapped by th case's namespace. (-0 tim)
+ **case-id.widget-id -- wrapped by th case's namespace. (-0 tim, -1 mpo, see below)
?                                                               +++++++++++++++++++

- **choice-id.case-id.widget-id -- wrapped by the choice's and the case's namespaces. (-1
tim)
+ **choice-id.case-id.widget-id -- wrapped by the choice's and the case's namespaces. (-1
tim, -1 mpo since the cases are exclusive)
?                                                                                        
   ++++++++++++++++++++++++++++++++++++++

+ ''mpo comments: I would prefer the case/@expr and default to become when/@test and otherwise''
+ 


Page: http://wiki.cocoondev.org/Wiki.jsp?page=LenyaEditors , version: 16 on Sun Mar 29 13:38:37
2004 by 195.138.42.67

- ||||HTML Form Editor||HTML One Form Editor||[Bitflux Editor|http://www.bitfluxeditor.org/]||Epoz||Xopus||
+ ||||HTML Form Editor||HTML One Form Editor||[Bitflux Editor|http://www.bitfluxeditor.org/]||[Epoz|http://epoz.sourceforge.net/]||Xopus||
?                                                                                        
    +    ++++++++++++++++++++++++++++++



Page: http://wiki.cocoondev.org/Wiki.jsp?page=ConnectionPooling , version: 8 on Sun Mar 29
13:31:53 2004 by 82.161.98.62

+ If you wish to see the source code for this database connection script, you should have
the sources of
+ cocoon. You can find the imported Database.js (and the files it calls) at:
+ {{cocoon-2.1.4/src/blocks/petstore/java/org/apache/cocoon/components/flow/javascript}}
+ 
+ 



Mime
View raw message