Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-users@xml.apache.org
From: "Upayavira" <uv@upaya.co.uk>
To: cocoon-users@xml.apache.org
Date: Mon, 27 Jan 2003 21:46:26 -0000
MIME-Version: 1.0
Subject: Re: proposal: "The Newbies Competence Center"
Message-ID: <3E35A8B2.22743.657BDF2@localhost>
Priority: normal
In-reply-to: <3E358DEB.8050108@saxess.com>
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body

> user:      *uses*    the given infrastructure as is
> developer: *creates* his own add ons to given infrastructure
> 
> I get troubles when it comes to xsp programming, which clearly
> sits between the chairs. But even there i see a bunch of prepacked
> ready to use logicsheets ready made  for the "users" and the self made
> extra logicsheets from the developers... maybe this is a little
> simplistic, but it may hold as a first approach towards separating
> user concerns from developer concerns.

How about this as a distinction:

You switch from being a user to a developer when you consciously invoke a Java 
compiler.

XSP to my mind is still in the user space. You are using functionality provided to you 
by cocoon, even if that is programming functionality. But if you write your own 
generator, then you're moving into the developer space, because, depending upon 
exactly what you choose to do with your generator, you might start to need to know 
more about Cocoon internals, Avalon, etc.

Regards, Upayavira


---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <cocoon-users-unsubscribe@xml.apache.org>
For additional commands, e-mail:   <cocoon-users-help@xml.apache.org>