RE: Additional change to DefaultViewHandler proposal. ..

> I have to fully agree to you. However, not using xmlc means not
> to use the bcomponents at all, as these heavily rely on a DOM.

Well, just to be clear, it doesn't mean we can't use the Barracuda component
model. It just means we need to write replacement pieces to handle the items
outlined in my previous response (loading, caching, rendering). Those are
NOT that difficult to do, but they will take a good block of focused effort.
Wish I had a month to spend on this... ;-)

Christian

----------------------------------------------
Christian Cryder [[email protected]]
Internet Architect, ATMReports.com
Barracuda - http://barracudamvc.org
----------------------------------------------
"Coffee? I could quit anytime, just not today"

> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Diez B. Roggisch
> Sent: Thursday, March 06, 2003 4:37 AM
> To: [email protected]
> Subject: Re: [Barracuda] Additional change to DefaultViewHandler
> proposal. ..
>
>
> hI,
>
> > Although... I'd still like Barracuda to support multiple presentation
> > technologies.
> > It's easier to sell Barracuda if it supports JSP, XSLT, ~append relevant
> > technology here~, etc etc
> > Alot of developers I've spoken to won't touch Barracuda because they
> > consider XMLC to be a third party technology/tool
> > that can disappear and leave them stranded.
>
> I have to fully agree to you. However, not using xmlc means not
> to use the
> bcomponents at all, as these heavily rely on a DOM. And I don't know any
> other (convenient!) way to create and manipulate the DOM. So I
> think we can
> easily add jacobs propsition to DefaultViewHandler, as it is only
> used in the
> rendering phase. And if someone wants to drop xmlc, he'll barely use the
> DefaultViewHandler.
>
> So +1 from me :)
>
> Diez
> _______________________________________________
> Barracuda mailing list
> [email protected]
> http://barracudamvc.org/lists/listinfo/barracuda