> 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: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
