I don't think there is much confusion here. The issue is that with a small change we can enable people to implement the template part of the UI tags in their own favorite tecnology. Currently if you want to use the nice UI tag framework you are forced to use velocity based templates. The only actual dependency on velocity in the UI tags is located in AbstractUITag. By refactoring this functionality by delegating to a TemplateHandler that could be implemented either as today with mergeTemplate using velocity, with JSP includes using JSP based templates or some other templating based technology of your own choice we would get a more powerful UI tag library.
The problem is not that the current solution forces you to use velocity. The problem is that it prevents you from using something else. (while taking advantage of the tags)
I'll try to provide some code to back this up. Hopefully before the end of this weekend.
Fredrik Lindgren
On Fri, 12 Dec 2003 05:47:00 -0800, Drew McAuliffe <[EMAIL PROTECTED]> wrote:
Unfortunately, that's like saying if I don't like commons-logging, I
shouldn't be forced to use it. Or if I don't like ognl, I shouldn't be
forced to use it. You can't make every dependency in the library pluggable.
The only reason I could see velocity becoming a barrier to your work with
webwork would be if the dependency forced you to write velocity templates.
It does not. If you never want to touch a velocity template ever with
webwork, you don't have to. But you need the jar file because it is used
behind the scenes for some work. If you're not being forced to use velocity
templates, then webwork shouldn't be forced to remove the dependency on
something it uses for its internals just because you don't happen to like
it.
It sounds to me like you're confused about what the velocity dependency
means. It doesn't mean you don't have a choice in presentation methods,
because you do (Freemarker, JSP, velocity). If you want to use the ui tags,
then you may want to know about velocity to understand the templates or
provide your own. If you don't want to use them, then fine, don't, and
you'll never be forced to even look at a velocity template.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of remigijus Sent: Friday, December 12, 2003 4:02 AM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] WebWorks without velocity how to
----- Original Message ----- From: "Tracy Snell" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, December 12, 2003 1:49 PM Subject: Re: [OS-webwork] WebWorks without velocity how to
On Dec 11, 2003, at 1:22 PM, Jason Carreira wrote:
> WW1 you can use without velocity, WW2 uses velocity for its UI tag > templates. If you don't plan to use the UI tags, you can remove it.
You can use WW2 and just use JSPs and never have to write any Velocity templates. However, Velocity is still there lurking in the dark helping you out.
Ok I'm happy to get velocity in help when I need it, but I don't want to be
forced to do that. You can say siple don't use it. Ok I already doing that.
But we are tolking about ww2 design issues. It has to be clear and if it's
addition, evryone should now that is not ww2 but just another additional
feature. And as I see some people also rising some questions about use of
freemaker instead of velocity. I think I'm not only one person who think in
this way.
Forget about what is already, done, think again is it better to have it as
option or let's say in the core of ww. Try to be objective, don't be inertic
(inertia - I don't know how to write it in english in correct way, I hope
you eill undertand).
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
-- Fredrik Lindgren Software Architect, Appear Networks AB
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
