jon * wrote:
>
> on 12/16/99 9:11 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> wrote:
>
> > jon, Aren't WebMacro and FreeMarker proprietary solutions for generating html
> > content from templates? I think your right that jsp isn't a good solution.
>
> Oh gawd...don't get me started with this "proprietary" argument. ;-)
>
> JSP is a hell of a lot more "proprietary" than anything else out there
> considering the fact that the ONLY people who have final design decisions on
> the specification is Sun. On top of it, Sun's *main* motivation for
> developing JSP is simply to compete against M$ ASP. Talk about proprietary.
>
> The same argument could be made about Turbine as WebMacro or Freemarker. If
> you think that W/F is proprietary, then why don't you think that Turbine is?
>
> Let me end this with this statement:
>
> All truly Open Source software is NOT proprietary in any way. Period. End of
> discussion.
>
> > Wouldn't developers be better advised to use the XSL/XML combination, as does
> > Cocoon, to generate html from templates?
>
> The subject of this message is communication about integrating Cocoon into
> Turbine. Yes, we want to offer that as a solution as well.
>
> But, for those of us, like myself, who do not believe (yet...ie: prove me
> wrong) that XSL is the right way to go, we want alternative solutions, ie:
> freemarker and webmacro.
>
> > I'm currently using Turbine with an XSL processor to generate html. I'm using
> > ECS to compose the html from 1 to many XSL transformations. I'm looking
> > forward
> > to the Turbine samples using Cocoon.
>
> Cool! How about contributing your code to do this back to the project?
>
> > For intranet applications, I think that most will want to return XML to the
> > browser and implement the transformations in the browser. Can anybody point
> > me
> > to some information on doing this job with Mozilla?
Actually, I don't really want this to be part of Turbine - it depends on
the browser, which goes against everything Turbine is, which is a
_server-based_ framework. Now you start having to make Turbine
(screens) figure out what browser is being used, and adjust the XML
based on compliance - this is the whole point of XSLT on the server. I
really think for web applications (not Intranet) you aren't guaranteed a
certain browser, so don't code to one. No anything in the browser
sounds like a good idea to me. Just give it HTML, which is what it does
well.
-Brett
>
> Try www.mozilla.org. Good luck though, you are trying to be way more cutting
> edge than most Intranets can withstand IMHO.
>
> -jon
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
