Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 77969 invoked by uid 500); 15 May 2002 12:54:10 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 77933 invoked from network); 15 May 2002 12:54:10 -0000 User-Agent: Microsoft-Entourage/10.0.0.1331 Date: Wed, 15 May 2002 05:54:07 -0700 Subject: Re: TR: [doc] volunteer, grouping topics From: carlos@cvc.edu (Carlos) To: Message-ID: In-Reply-To: <3997D874A598D51190A70002A56BC995023685A7@TOCOMEXC17> Mime-version: 1.0 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N 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" wrote: >=20 > One of the main problem I hade when I started using "web documented" proj= ect > (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. >=20 > So I think that best topics grouping is the intended-audience-groumpings. >=20 >=20 > Another problem with cocoon is that you must learn three differents thing= s : > 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 t= hen > cocoon will benefit from your source being (avalon)cacheable, and use ava= lon > pooling system if your source is not threadsafe. [1]" >=20 > But /understand/ a sentence does not mean /learn/ from it. >=20 >=20 > So, in my opinion, actual docs should be grouped like this : >=20 > ---Discover Cocoon--- >=20 > -Basic cocoon feature > -sitemap > -matchers & selectors > -generators (file) > -transformers (xslt) > -Basic "avalon" feature > -caching > -parameters > -Advanced cocoon features > -views > -persistence >=20 >=20 > ---RealWorld Cocoon--- >=20 > -other generators > -request > -... > -other tranformers > -I18N > -... > -Databases > -... >=20 >=20 > ---Cocoon Extensions--- >=20 > -Sunshine > -scratchpade things > -... >=20 >=20 > ---Extending Cocoon--- >=20 > -How to code Cocoon Component > -How to deploy Cocoon Component > -tutorial (with separated infos about Cocoon concepts and Avalon concepts= ) >=20 >=20 > Hope this help. Maybe a lot of mistake, but main idea is there :) >=20 > fabien. >=20 >=20 >=20 > [1] quote from the tutorial i'm working on... wip :) >=20 >> -----Message d'origine----- >> De: Diana Shannon [mailto:terracare@mac.com] >> Date: mercredi 15 mai 2002 12:26 >> =C0: cocoon-dev@xml.apache.org >> Objet: [doc] volunteer, grouping topics >>=20 >>=20 >> 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=20 >> this list for comments/revisions. I'd like to use it for all >> documents,=20 >> including snippets, tutorials, and how-tos. >>=20 >> Thanks a lot. >>=20 >> Diana >>=20 >>=20 >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org >> For additional commands, email: cocoon-dev-help@xml.apache.org >>=20 >=20 > --------------------------------------------------------------------- > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org > For additional commands, email: cocoon-dev-help@xml.apache.org >=20 --=20 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