Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 21069 invoked from network); 26 Jul 2000 13:06:39 -0000 Received: from benjamin.webslingerz.com (206.66.49.217) by locus.apache.org with SMTP; 26 Jul 2000 13:06:39 -0000 Received: from snorlax2.webslingerz.com (snorlax2.webslingerz.com [216.27.31.68]) by benjamin.webslingerZ.com (Postfix) with ESMTP id ECE84C0A7; Wed, 26 Jul 2000 09:19:18 -0400 (EDT) Date: Wed, 26 Jul 2000 09:02:19 -0400 (EDT) From: Kevin Sonney To: cocoon-dev@xml.apache.org Cc: matt@sergeant.org Subject: Re: idea for documenting xsp logicsheets In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On Wed, 26 Jul 2000, Donald Ball wrote: > assuming we could configure the xsp processor to ignore the xspdoc > elements (either by stripping them when doing the XSLT transform or adding > "strip xspdoc elements" rules to the xsp to java stylesheet), all we'd > need to generate concise docs is a simple stylesheet like this: Why strip them? I would rather somrthing like : Here's the JDBC Driver be placed in the java code as a *REAL* comment : /* Here's the JDBC Driver */ This would make it a little more debug freindly when I'm gutting the auto-generated java files tracking down an error. > obviously we could elaborate a bit on the elements and attributes of the > xspdoc namespace, but that's the gist. any thoughts from other logicsheet > authors? worthwhile to pursue? +1 from this end. I'd also make things a bit more client freindly, when I hand projects off to their final maintainers. -- - Kevin Sonney kevin@webslingerZ.com