I think for T5 as default:
Tapestry's binding language might be extended to do some simple
evaluation at best, and nothing more! .... the simpler the better in my
view, isn't this the general idea of using components and moving away
from embedded scripting? I think, in general, support for pulggable
views for different devices, platforms and resolutions is becoming more
and more important, and is served best through using components.
OGNL is now super fast and powerful, good in many respects... but I am
glad it's no longer in the picture (no offence intended Jessie).
Expression binding is not something I want to even think about ever, nor
do I want to do wonderful things with it, Java is best for this in my
view... besides OGNL has caused me some pain in the past.
I think for a T5 as optional:
Some people require stuff like true recursion with fine grained control
and complex evaluation of templates (there was a post on this a while back)
Components can be too inflexible for this type of thing, wheras
scripting makes sense and almost effortlessly can do it. So there is a
very valid argument, which I support, for some real scripting support in
the framework and not just a more powerful expression binding
language... as important as this is, it serves a niche so is best made
optional in my view.
If you say that scripting support can be pluggable or language agnostic,
then this is a MUST HAVE feature for Tapestry... is it a 'bad idea'? as
you have correctly said, having an expression binding language to do the
job of a scripting language is the only bad idea IMHO.
Peter
Jesse Kuhnert wrote:
Oh well....it wouldn't hurt my feelings if anyone used MVEL. I'm
only as loyal to the best technology and hope everyone else would be
too.
On Nov 16, 2007 4:35 PM, Davor Hrg <[EMAIL PROTECTED]> wrote:
thanks,
I've played with it only a bit...
It was that time that MVEL was said to be much faster than OGNL
and very long flame on serverside.
I've just wanted try both, and made a small project that adds
both binding prefixes..
(I was not testing speeds .. just integration...)
after playing with it I was more satisfied with OGNL,
and MVEL crashed on some simple examples when
byte code optimizer was turned on for it.
Davor Hrg
On Nov 16, 2007 10:06 PM, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
You can know the type in advance by calling
OgnlContext.getCurrentType() after evaluating an expression (or
getPreviousType() / getFirstType() / the type and accessor types are
all pushed on to a stack now)..
It also supports generics / enums / varargs / etc now..
On Nov 16, 2007 2:42 PM, Davor Hrg <[EMAIL PROTECTED]> wrote:
ognl can be easily added as a binding prefix,
however expect some features to not work
because tapestry in some occasions needs to
know in advance type that the expression will return
<snipped>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
