You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Jacek Wiślicki <ja...@gmail.com> on 2006/04/30 23:24:15 UTC
why Velocity?
Hi,
I do apologize for this post, but Velocity seems to me an extremely
useless solution. It does not have any calculational power, iterrates
only over lists available in the context, does not support conditional
returns from macros, objects and their methods available in macros are
known only to their programmers (unless one inspects a source code where
a Velocity context is created)...
What are advantages of using Velocity instead of any other templating
engine, e.g. JSP (<sarcasm>even JavaScript at client side seems a better
one</sarcasm>)? The technology becomes more and more popular among
programmers while in my case in causes only problems.
Please, correct me if I am wrong, maybe there are bright sides of
Velocity, but I just cannot see them :)
--
pozdrawiam,
Jacek Wislicki
jacek.wislicki@gmail.com
tel.: +48 502 408 444
gg: 2540358
skype: jacek_wislicki
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: why Velocity?
Posted by Jacek Wiślicki <ja...@gmail.com>.
Wiadomosc od Aaron Evans z 2006-04-30 23:42 brzmiala:
> Jacek,
> I think you're gonna get flamed by the velocity die-hards. ;-)
I don't feel like a martyr for decorators ;) Thanks for the warning.
> I too would prefer JSP, and one of these days when I get some time (I
> know I keep saying this) I'll try my hand at implementing some JSP
> decorators.
I think it would be really great, at least some simple alternative to
Velocity.
--
pozdrawiam,
Jacek Wislicki
jacek.wislicki@gmail.com
tel.: +48 502 408 444
gg: 2540358
skype: jacek_wislicki
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: why Velocity?
Posted by Aaron Evans <aa...@gmail.com>.
Jacek,
I think you're gonna get flamed by the velocity die-hards. ;-)
I too would prefer JSP, and one of these days when I get some time (I
know I keep saying this) I'll try my hand at implementing some JSP
decorators.
On 4/30/06, Jacek Wiślicki <ja...@gmail.com> wrote:
> Hi,
> I do apologize for this post, but Velocity seems to me an extremely
> useless solution. It does not have any calculational power, iterrates
> only over lists available in the context, does not support conditional
> returns from macros, objects and their methods available in macros are
> known only to their programmers (unless one inspects a source code where
> a Velocity context is created)...
> What are advantages of using Velocity instead of any other templating
> engine, e.g. JSP (<sarcasm>even JavaScript at client side seems a better
> one</sarcasm>)? The technology becomes more and more popular among
> programmers while in my case in causes only problems.
> Please, correct me if I am wrong, maybe there are bright sides of
> Velocity, but I just cannot see them :)
>
> --
> pozdrawiam,
> Jacek Wislicki
>
> jacek.wislicki@gmail.com
> tel.: +48 502 408 444
> gg: 2540358
> skype: jacek_wislicki
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
Re: AW: AW: why Velocity?
Posted by Jacek Wiślicki <ja...@gmail.com>.
Wiadomosc od apache@salesfactory.org z 2006-04-30 23:47 brzmiala:
> i know polish very well ;)
So do all the other subscribers now :P
> i*m glad to use velocity. my frontend-designer (photographer) can use it
> by knowing #if #else #foreach - not more not less.
And what is the difference in using these structures in Velocity and
JSP, for example?
Anyway, my post was not about Velocity itself (I don't care about it),
but basing portal decorators on it. I just cannot see any advantages :/
--
pozdrawiam,
Jacek Wislicki
jacek.wislicki@gmail.com
tel.: +48 502 408 444
gg: 2540358
skype: jacek_wislicki
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
AW: AW: why Velocity?
Posted by ap...@salesfactory.org.
i know polish very well ;)
i*m glad to use velocity. my frontend-designer (photographer) can use it
by knowing #if #else #foreach - not more not less.
-----Ursprüngliche Nachricht-----
Von: Jacek Wiœlicki [mailto:jacek.wislicki@gmail.com]
Gesendet: Sonntag, 30. April 2006 23:45
An: Jetspeed Users List
Betreff: Re: AW: why Velocity?
Wiadomosc od apache@salesfactory.org z 2006-04-30 23:33 brzmiala:
> o kurwa.
Do you know what "o kurwa" means in Polish? If not, check some
dictionaries or see this link:
http://www.urbandictionary.com/define.php?term=Kurwa&defid=385624. Here
are some more if you wish to lear Polish:
http://www.insultmonger.com/swearing/polish.htm.
> because velocity is designed to be used by frontend-only-designers
> (non-programmers) too.
Is this the reason for Velocity limitations or why adding any extension
to a decorator must be followed by Jetspeed rebuild and redeployment (at
least one JAR)? I don't get your point.
--
pozdrawiam,
Jacek Wislicki
jacek.wislicki@gmail.com
tel.: +48 502 408 444
gg: 2540358
skype: jacek_wislicki
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: AW: why Velocity?
Posted by Jacek Wiślicki <ja...@gmail.com>.
Wiadomosc od apache@salesfactory.org z 2006-04-30 23:33 brzmiala:
> o kurwa.
Do you know what "o kurwa" means in Polish? If not, check some
dictionaries or see this link:
http://www.urbandictionary.com/define.php?term=Kurwa&defid=385624. Here
are some more if you wish to lear Polish:
http://www.insultmonger.com/swearing/polish.htm.
> because velocity is designed to be used by frontend-only-designers
> (non-programmers) too.
Is this the reason for Velocity limitations or why adding any extension
to a decorator must be followed by Jetspeed rebuild and redeployment (at
least one JAR)? I don't get your point.
--
pozdrawiam,
Jacek Wislicki
jacek.wislicki@gmail.com
tel.: +48 502 408 444
gg: 2540358
skype: jacek_wislicki
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
AW: why Velocity?
Posted by ap...@salesfactory.org.
o kurwa.
because velocity is designed to be used by frontend-only-designers
(non-programmers) too.
-----Ursprüngliche Nachricht-----
Von: Jacek Wiœlicki [mailto:jacek.wislicki@gmail.com]
Gesendet: Sonntag, 30. April 2006 23:24
An: Jetspeed Users List
Betreff: why Velocity?
Hi,
I do apologize for this post, but Velocity seems to me an
extremely
useless solution. It does not have any calculational power, iterrates
only over lists available in the context, does not support conditional
returns from macros, objects and their methods available in macros are
known only to their programmers (unless one inspects a source code where
a Velocity context is created)...
What are advantages of using Velocity instead of any other
templating
engine, e.g. JSP (<sarcasm>even JavaScript at client side seems a better
one</sarcasm>)? The technology becomes more and more popular among
programmers while in my case in causes only problems.
Please, correct me if I am wrong, maybe there are bright sides
of
Velocity, but I just cannot see them :)
--
pozdrawiam,
Jacek Wislicki
jacek.wislicki@gmail.com
tel.: +48 502 408 444
gg: 2540358
skype: jacek_wislicki
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org