Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 26515 invoked by uid 500); 29 Mar 2001 02:52:03 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 26504 invoked from network); 29 Mar 2001 02:52:02 -0000 Date: Thu, 29 Mar 2001 12:54:27 +1000 From: Jeff Turner To: cocoon-users@xml.apache.org Subject: Re: Central repository for taglibs Message-ID: <20010329125427.D21438@socialchange.net.au> Mail-Followup-To: cocoon-users@xml.apache.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.15i In-Reply-To: ; from YannC@Symtrax.com on Wed, Mar 28, 2001 at 12:32:24PM -0800 X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Hooray, someone agrees ;) On Wed, Mar 28, 2001 at 12:32:24PM -0800, Yann Camenen wrote: > Hello all, > [..] > Also, where is that logicsheet/taglib documentation that everybody is asking > for ? I know there are resources, they're just not easily accessible to new > users. Taglib documentation is one of the biggest areas a taglibs project could address. It's an "overhead" cost that, individually, taglib developers are reluctant to meet. Donald's xspdoc (used in esql) looks like a good start. For taglib development (as opposed to use), a taglib tutorial would be nice. David Parry started one (http://www.suranyami.com/XSPtutorial/), but evidently ran out of steam. Again, collective ownership of such a document could potentially ensure it's long-term survival. > What about the taglib schema validation idea that came up a few weeks ago ? > There probably could also be some kind of taglib schema for logicsheet > authors to extend. That all requires someone to make it happen ;) If every taglib provided a uniform way of accessing it's schema, that would aid the development of schema-based validation. > I believe that some sort of organisation would allow for a higher degree of > coordination on such projects. If a structure existed, it probably would > induce some additional overhead for existing taglib authors but would > definitely facilitate entry for new contributors. It doesn't necessarily > mean a new mailing list and web site, just a few pages on the Cocoon site > and a [Taglib] subject line. Yep, initially that would be fine. However, assuming the rapid growth that C2 is sure to induce, this probably be scaleable in the long term. > Finally, how many people here have modified/improved versions of the esql or > fp taglibs that they don't know what to do with ? Who should these > modifications be submitted to (especially for those taglibs that don't have > a well-known maintainer) and how ? Are patches to taglibs to be treated the > same way as cocoon contrib patches are ? Are the same people supposed to > handle both ? Exactly :) I wonder how many people have useful variants of taglibs that they don't publicize, simply because they don't want to support it. --Jeff > > Just my opinion. > > Regards, > Yann Camenen --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: