cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Per-Olof Norén <pe...@alma.nu>
Subject Re: TR: [doc] volunteer, grouping topics
Date Wed, 15 May 2002 13:31:35 GMT
I personally would like something like a component refererence (similar to
the one that exists today, extended/rewised).
This would include the "Cocoon Internals" that carlos suggests below. I´m a
litte fed up with looking at the code just to remember the
attributes/elements/namespaces for a given component.
I consider myself being on a firstname basis with cocoon and most of the
times its enough with component reference and a simple usage example.

/Per-Olof Noren


----- Original Message -----
From: "Carlos" <carlos@cvc.edu>
To: <cocoon-dev@xml.apache.org>
Sent: Wednesday, May 15, 2002 2:54 PM
Subject: Re: TR: [doc] volunteer, grouping topics


> How about...
>
> * Cocoon Fundamentals (What you must absolutelty know to get Cocoon
running)
> * Advanced configuration (Now that I got it running, let's give Cocoon
> something to do, a first project type of thing)
> * Introduction to Cocoon App Development (I've written my first pipeline,
I
> want to develop my first application, which doesn't necessarily include
> Avalon components just yet)
> * Advanced Development with Cocoon (How to integrate Avalon directly into
a
> Cocoon project, stuff that is needed for more advanceed application
> development. how do I change a component if I need to? The question then
> becomes, where do we draw the line between beginning and advanced
> development application)
> * Cocoon internals (What are the available commands for the esql
> transformer)
>
>
> On 05/15/02 4:10, "TREGAN Fabien" <fabien.tregan@airbus.com> wrote:
>
> >
> > One of the main problem I hade when I started using "web documented"
project
> > (it was CSS docs, XML/DOM, XSL, tomcat, I was young :) was to find a doc
I
> > can understand.
> > Later, my problem was to find a doc without all that newbies blabla.
> >
> > So I think that best topics grouping is the
intended-audience-groumpings.
> >
> >
> > Another problem with cocoon is that you must learn three differents
things :
> > 1- cocoon concepts (pipelines, sourceHandlers, ...)
> > 2- Avalon concepts (pools, roles, parameters, ...)
> > 3- realworld practice (ok, i know what's a pipeline, but how do I
getthis
> > to works)
> > Of course, everyone is able to understand the following sentence :
"Since
> > the cinclude transformer use urls that are handled by the cocoon
> > SourceHandler component, if you have an avalon source that is XMLizable,
you
> > can use it with cocoon cinclude transformer provided that you registered
the
> > sourcefacotry of your source with the sourceHandler in the sitemap, and
then
> > cocoon will benefit from your source being (avalon)cacheable, and use
avalon
> > pooling system if your source is not threadsafe. [1]"
> >
> > But /understand/ a sentence does not mean /learn/ from it.
> >
> >
> > So, in my opinion, actual docs should be grouped like this :
> >
> > ---Discover Cocoon---
> >
> > -Basic cocoon feature
> >  -sitemap
> >  -matchers & selectors
> >  -generators (file)
> >  -transformers (xslt)
> > -Basic "avalon" feature
> >  -caching
> >  -parameters
> > -Advanced cocoon features
> >  -views
> >  -persistence
> >
> >
> > ---RealWorld Cocoon---
> >
> > -other generators
> >  -request
> >  -...
> > -other tranformers
> >  -I18N
> >  -...
> > -Databases
> > -...
> >
> >
> > ---Cocoon Extensions---
> >
> > -Sunshine
> > -scratchpade things
> > -...
> >
> >
> > ---Extending Cocoon---
> >
> > -How to code Cocoon Component
> > -How to deploy Cocoon Component
> > -tutorial (with separated infos about Cocoon concepts and Avalon
concepts)
> >
> >
> > Hope this help. Maybe a lot of mistake, but main idea is there :)
> >
> > fabien.
> >
> >
> >
> > [1] quote from the tutorial i'm working on... wip :)
> >
> >> -----Message d'origine-----
> >> De: Diana Shannon [mailto:terracare@mac.com]
> >> Date: mercredi 15 mai 2002 12:26
> >> À: cocoon-dev@xml.apache.org
> >> Objet: [doc] volunteer, grouping topics
> >>
> >>
> >> Would someone like to help decide meaningful grouping topics for
> >> Cocoon-related documents? I started to do this for the revised FAQ
> >> documents, based on existing FAQ content. It needs to be expanded and
> >> revised. Perhaps someone could expand/edit what I've started
> >> and post to
> >> this list for comments/revisions. I'd like to use it for all
> >> documents,
> >> including snippets, tutorials, and how-tos.
> >>
> >> Thanks a lot.
> >>
> >> Diana
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> >> For additional commands, email: cocoon-dev-help@xml.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > For additional commands, email: cocoon-dev-help@xml.apache.org
> >
>
> --
> Carlos E. Araya
> ---+ WebCT Administrator/Trainer
>  P | California Virtual Campus
>  - | C/O De Anza College
>  G | 21250 Stevens Creek Blvd
> ---+ Cupertino, CA 95014
>
> email               carlos@cvc.edu
> web                 http://www.cvc1.org/ (work)
>                     http://www.silverwolf-net.net (personal)
> phone               408 257 0420 (work)
> PGP Fingerprint:    E629 5DFD 7EAE 4995 E9D7  3D2F 5A9F 0CE7 DFE7 1756
>
> "If there is artificial intelligence, doesn't that imply there is also
> artificial stupidity!"
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message