Peter
Thanks for the comments; I am still not sure I
understand or agree with the "proprietary" code part;
my definition (based around ownership) seemingly disagrees
with yours - we will then obviously disagree about the
implications...
I am perfectly happy at present to stick with XSLT and the
various Cocoon logicsheets at present - the added complexity
of my learning Java in depth now (i.e coming from a programming
background I already have sufficient understanding of the basic
constructs; enough to add in logic where required) is not worth
some *potential* portability for some *potential* future ultra-pure
appplication ;-)
I also have enough confidence in the way that Cocoon is
developing to know that none of these choices will constitute
a *significant* barrier to my development, or the future evolution
of the systems I am working on.
I do hope that some of what you are doing will eventually filter
back to the Cocoon in a way that fits in with modular and
component based philosophy of the system, and can be used
by a wider group of developers.
>>> [EMAIL PROTECTED] 29/01/2003 06:12:18 >>>
> Well, you carefully
(or not?) snipped out my point that, in the
> end, the XSPs are converted to
Java
That's irrelevant; you're still writing
proprietary code...
> - and at least one of
the Cocoon books I read
suggests this as a perfectly vaild way
> to start off doing your
own coding for custom generators.
Absolutely, just understand the
tradeoffs you're making in terms of performance and
portability.
> So... I am not sure what you
mean by "loss of portability" -
It may not be an issue for you.
For us, we have some requirements to run our code outside of Cocoon.
They haven't forced us away from Cocoon yet, but they could in the
future.
> All that said, I would be very
happy to "upgrade my skills"
> (and design approach) to learn
how to develop Cocoon-based
> systems that are both complex
and XSP-free.
1st learn Java. 2nd learn
XSLT. :-)
> If you (or anyone else)
would care to share your approach
> and methodology in the form
of tutorials and/or examples,
> I am sure I am not the only one
who would benefit from it.
The way we do things won't make a lot of
sense to you until you have a lot of Java and XSLT
skills.
--
This message has been scanned for viruses and dangerous content by
MailScanner, and is believed to be clean.
"The CSIR exercises no editorial control over E-mail messages and/or
attachments thereto/links referred to therein originating in the
organisation and the views in this message/attachments thereto are
therefore not necessarily those of the CSIR and/or its employees.
The sender of this e-mail is, moreover, in terms of the CSIR's Conditions
of Service, subject to compliance with the CSIR's internal E-mail and
Internet Policy."
