When this discussion first came up in this list, I was really against
having default binding prefixes at all. However, I didn't have the time
to test
Tap4 back then so I kept my mouth shut.
Well, for the last 2 weeks I'm really testing v4 and I found out that
default bindings
are very natural to use (at least in HTMLs, I haven't seen what goes in
in XMLs). Perhaps it
has to do with the experience I already have with v3, but I NEVER (not
even a single time)
did I have to consult the documentation for checking the default bindings.
It always is the one I try!
So, I'm currently in favor of having default bindings, and using #1
Kevin Menard wrote:
On Jul 20, 2005, at 11:35 AM, Howard Lewis Ship wrote:
What are people finding now that they are (hopefully) playing with
Tapestry?
I prefer #1. What I am not a big fan of, however, is how the default
binding prefix is different for HTML and XML files. Since the two
contexts have two different defaults, components can't rely on a
single default and thus component parameters that may only be ognl
expressions must provide a default-binding. If both the HTML & XML
files defaulted to ognl, then it would simplify components. Second,
I find I tend to move components back & forth from my HTML to XML
files. This doesn't happen a lot, but it would be nice if I could
rely on the same default semantics.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
