> Any pointers to examples, tutorials or real-world apps built
> with Turbine? Is a template language (Webmacro, etc.) REQUIRED
> in order to use Turbine? If yes, what seems to be the preferred
> choice? Are there any licensing issues with these languages?
Not required, no. The "default" way to create "screens" is with ECS, which
is a programmatic way to generate HTML or even XML pages (see ECS project at
ASF). This "default" is currently being moved to WebMacro though - it's very
well integrated into Turbine.
> I meant that, from the documentation, I gathered I had to follow
> a "top navigation bar, bottom navigation bar, middle content
> area, etc." layout in my pages. Jeff Brekke pointed out this is
> not correct, through the use of a templating language (Webmacro).
> Do you concur?
You don't HAVE to do anything - the top, bottom, etc. navigations is an
EXAMPLE layout. Your layout could have any number and organization of
navigations, e.g. left menu navigation, etc.
> I guess this is the crux of the issue to me. I can see my apps
> will require user authentication, session management, etc., so
> it looks like Turbine would be a good fit. But we have also
> made the decision to provide all content with XML, and use XSL
> for presentation; even more, we would really like to separate
> the groups working on the logic, content (data) and presentation,
> and Cocoon looks like a very good fit for this. How could I mix
> both alternatives?
We find Cocoon overkill for our simple XML ---XSLT---> HTML/WML/whatever
needs, so we've built a very simple mechanism on top of Turbine that uses
XML+WebMacro ---XSLT(Xalan)---> HTML/WML/whatever. Turbine gives you the
power to select the components you want and code your own as needed.
> Interesting. You have mentioned Cocoon 2's taglibs and sitemaps
> a couple of times. I don't know what a sitemap is, but it seems
> to me that using taglibs and sitemaps you could offer the equivalent
> of Turbine's functionality in a pure Cocoon(2) environment; therefore,
> you COULD have a Jetspeed based on Cocoon only, and with all the
> functionality offered today by Turbine ported to Cocoon. Am I
> totally wrong here?
Quite correct - although providing some of the more advanced Turbine
back-end featurs as taglibs will be hairy, to say the least.
Frank
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
