cocoon-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From stev...@outerthought.org
Subject [WIKI-UPDATE] SandBox WoodyScratchpad Mon Mar 29 21:00:04 2004
Date Mon, 29 Mar 2004 19:00:05 GMT
Page: http://wiki.cocoondev.org/Wiki.jsp?page=SandBox , version: 283 on Sun Mar 29 19:22:49
2004 by 204.28.3.51

- Play here until you are confident; it is easy.
+ Play here until you are confident; it is easy and fun.
?                                              ++++++++



Page: http://wiki.cocoondev.org/Wiki.jsp?page=WoodyScratchpad , version: 12 on Sun Mar 29
19:17:58 2004 by 65.116.199.19

+ (tim: +1 to this alternative; nice syntax, and conveys the right ideas more clearly.)
+ 
- 
- 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.
+ 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. (tim: +1 the pre-built definition caching is one of the reasons for importing
instead of just using (x|c)include)
?                                                                                        
                                                                                         
             ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

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

- *Where should imported types be registered (affects namespace)? (mpo: I don't get this question)
+ *Where should imported types be registered (affects namespace)? (mpo: I don't get this question)
(tim: let's ignore it, I don't think it makes sense anymore.)
?                                                                                        
        ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

- **Widget definitions that will have instances created.
+ **Widget definitions that will have instances created. (tim: Does this have any usecases?)
?                                                       ++++++++++++++++++++++++++++++++++++

+ (''tim: I was thinking of offering both forms, not just one-or-the-other, because I have
usecases for both.'')
- *What should we do if the expression evaluates to the default anyway? (mpo: seems more logic
in the when@test/otherwise filosophy?)
+ *What should we do if the expression evaluates to the default anyway? (mpo: seems more logic
in the when@test/otherwise filosophy?) (tim: I do not understand; could you clarify you comment?)
?                                                                                        
                                           +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

- *What namespace should the widget id's be in? (''mpo: supposing you refer to namespacing
with respect to generated request-parameter names, right?'')
+ *What namespace should the widget id's be in? (''mpo: supposing you refer to namespacing
with respect to generated request-parameter names, right?'') (''tim: yes'')
?                                                                                        
                                                             +++++++++++++++

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

+ ''tim comments: when/@test would be fine with me; should we also copy the word 'choose'
from xslt, instead of using 'choice'? 'choice' seems more declarative, but I would be ok with
either word.''



Mime
View raw message