I would like to join the discussion with a small example.
Ofcouse listener="listener:..." is obsolete. BUT, not every parameter is so clear.
For me, the Shell's title should be a message, not a literal. For someone else, its a literal. oops - look at the docu. The same with all literals, except for "element" in For. But in the short time I use 4.0 I really got confused, and wished this would be different.
If one keeps an eye on the learning curve, I think #2 is the golden middle. This is also my favourite.
Cheers, Ron ציטוט Howard Lewis Ship:
With the new betas out, I'm thinking that it's become easier to discuss the binding prefixes. I like how succinct the prefixes are but if we can get a consensus, we can change things around. I would suggest that, if we remove explicit default binding prefixes on parameters, we still use a simpler system of defaults: literal: for HTML (or other templates), ognl: for XML and elsewhere (such as annotations). <form jwcid="@Form" listener="doSubmit"> vs. <form jwcid="@Form" listener="listener:doSubmit"> vs. <form jwcid="@Form" listener="ognl:listeners.doSubmit"> I prefer #1, but would be satisified with #2. Either is better than #3 (as it stands in Tapestry 3.0). What are people finding now that they are (hopefully) playing with Tapestry?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
