[WIKI-UPDATE] GT2003Usability GT2003FlowHandling GT2003Configuration GT2003Hackathon Fri Oct 3 11:00:04 2003

[st...@outerthought.org]

Page: http://wiki.cocoondev.org/Wiki.jsp?page=GT2003Usability , version: 1 on Fri Oct  3 08:41:10 2003 by MarcPortier

New page created:
+ !Topics of MiniTalk 
+ by Matthew
+ 
+ A major part of the Cocoon community are the users and the people that actually try and build applications on top of Cocoon. I often find that users are overwehelmed by Cocoon and make common mistakes or find it difficult to jump start using the platform. The aim of this talk/discussion is to identify areas that would help increase the usability.
+ * Cocoon itself
+ ** configuration (see also extended discussion below)
+ ** installation
+ ** documentation
+ ** distributions
+ ** "wizards"
+ 
+ * Tools
+ ** Can we envision tools that would help
+ ** Looking at [sunBow|http://radio.weblogs.com/0108489/] as an example - what sort of features should a tool have
+ 
+ * Other areas
+ 
+ 
+ 
+ !Additional comments:
+ * (sylvain) Cocoon itself should provide 'Sitemap-level' stacktraces
+ * (sylvain) Adding Woody forms to each component to automatically build an xconf editor
+ * (mpo) Enhance the 'out of the box' experience with some setup-explore-guidance-selftraining-trail. (very much like Forrest is doing) would be great to have it hook up with above mentioned editors... 
+ * (mpo) Discuss timing: maybe lots of this needs to be reviewed in the scope of 'real blocks' still makes sense to do now what we can do now?
+ 
+ 
+ !Outcome of the hackathon discussion:
+ (check back after monday 6th October)
+ 


Page: http://wiki.cocoondev.org/Wiki.jsp?page=GT2003FlowHandling , version: 1 on Fri Oct  3 08:48:54 2003 by MarcPortier

New page created:
+ !Outcome of the hackathon discussion:
+ (check back after monday 6th October)
+ 


Page: http://wiki.cocoondev.org/Wiki.jsp?page=GT2003Configuration , version: 1 on Fri Oct  3 08:41:07 2003 by MarcPortier

New page created:
+ !Topics of MiniTalk 
+ by Sylvain
+ 
+ The cocoon.xconf is really frightening, because it lists every component with every possible option. The result is that average (or even advanced) users don't even dare to touch it, except adding datasources. Here are a few ideas that could make it easier:
+ 
+ * Having sensible builtin defaults in every component (maybe it's already the case)
+ * Autopopulating selectors by "scanning" implementations existing in the classpath (natively provided by Fortress?)
+ * Expanding {...} expressions with a set of bootstrap input-modules to move away some deployment-time parameters in web.xml, external configuration files or system properties.
+ * Running modes: have conditional sections depending on a running mode (dev, debug, deployed, etc).
+ 
+ 
+ !Additional comments:
+ * (yours here)
+ 
+ 
+ !Outcome of the hackathon discussion:
+ (check back after monday 6th October)
+ 


Page: http://wiki.cocoondev.org/Wiki.jsp?page=GT2003Hackathon , version: 83 on Fri Oct  3 08:48:06 2003 by MarcPortier

- ! Flow Handling (Carsten)
- Flowscript, apples, dywel.
+ ! [Flow Handling|GT2003FlowHandling] (Carsten)
+ MiniTalks:
- * WebContinuation Management (lessons learned from doing Apples) - mpo
+ * [WebContinuation Management (lessons learned from doing Apples)|GT2003WebContinuationManagement] - mpo
?   +                                                              +++++++++++++++++++++++++++++++++