Return-Path: Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 62267 invoked from network); 11 Sep 2000 06:42:53 -0000 Received: from elvis.triestram-partner.de (HELO BLAHFASEL.Triestram-Partner.de) (212.185.173.195) by locus.apache.org with SMTP; 11 Sep 2000 06:42:53 -0000 Received: by BLAHFASEL with Internet Mail Service (5.5.2650.21) id ; Mon, 11 Sep 2000 08:42:58 +0200 Message-ID: <906987C05D86D4119F0E0000D1106EC4613F@BLAHFASEL> From: Henning von Bargen To: cocoon-users@xml.apache.org Subject: AW: Examples of Cocoon Date: Mon, 11 Sep 2000 08:42:57 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N > -----Urspr=FCngliche Nachricht----- > Von: Marco Pauck [SMTP:pauck@wmd.de] > Gesendet am: Freitag, 8. September 2000 18:15 > An: cocoon-users@xml.apache.org > Betreff: Re: Examples of Cocoon >=20 > Pratik Machchar wrote: > >=20 > > Dear cocoon Users. > > Where can I have more examples of cocoon. besides samples = direcotry. >=20 > From my own experience trying to dig into Cocoon, I agree that > comprehensive and real-world examples are extremly helpful and > considerably lower the learning barrier. >=20 > The stuff in the samples directory is a starting point but many > even basic aspects of XSP & Co. are left unexposed. >=20 > Speaking for myself, I learned most things by closely following this > mailinglist and studying the samples published by some of you (e.g. > Uli Mayrings' authlib). >=20 > Therefore, I suggest to collect each and every single line of code > that might be helpful as an example or maybe even a real-world > solution to an actual problem, building a public 'library'. >=20 > There are several possiblities of where to put this stuff, e.g. > 1. into the distribution under contrib > 2. on the Cocoon web site > 3. distibuted on the web with links from a central page on the > Cocoon site >=20 > Each contribution should be classified either by application domain, > technical aspects, etc. Such as classification will probably = initially > by very simple but evolve as the library grows. >=20 > Personally, I would suggest to start with approach 3, as it is the > one with the least maintenance effort. Approach 1 might be = appropriate > for some selected and more advanced samples that are also guaranteed > (well, sort of ;-) to work with the corresponding distibution. >=20 > Oh well, CPAN comes to my mind ... ;-) >=20 > Making code available online will also simplify the answering of FAQs > (e.g. Q: "How can I generate WML output?" A: "Have a look at ..."). >=20 > Any comments, especially from the maintainer(s) of the Cocoon web = site? > Any suggestions for links (who will be the first? ;-) >=20 > Marco > --=20 > Marco Pauck -- WMD GmbH Hamburg, Germany -- http://www.wmd.de/ > e-mail: pauck@wmd.de, phone: +49-40-58958-120, fax: +49-40-58958-199 >=20 I think that this is a _VERY_ good idea. The more examples, the better. But you have to cleanly separate them from the basic Cocoon = distribution. I would prefer a contrib directory that you can download separately. The Cocoon distribution could contain an empty contrib directory = containing only a ReadMe file with a link where to download the contributed samples. Henning