Howard Lewis Ship <hlship <at> gmail.com> writes: > > OK ... this discussion has gone on long enough. I'm willing to strip > out the default-binding stuff and replace it with a simpler approach. > Attributes will be intepreted as literals (unless prefixed) in the > template, and as OGNL expressions (unless prefixed) elsewhere. > > This is a potentially de-stabilizing change; I am willing to do the > work, but will expect others to pitch in and test (that is, pull down > code and build apps against it), to help track down any latent errors. > > Howard M. Lewis Ship: +1 >
-1 (non-binding) Reasoning: This feature allows for component parameters to be defined with the most likely use pattern which is very good and reduces clutter in our forthcoming Tapestry 4.0 application somewhat (especially omitting the "message:"-prefix in our own components, where the parameter names have meaningful names like "label" or "listener"). For new users a mandatory "literal:" default binding will do nothing but produce lots of exceptions and unreadable specifications, while an "ognl:" default binding will produce unexpected results for newbies and lots of extra typing for developers working with rich components. However, if support has to be removed (looks like it from my preliminary vote count), use literal:, as it's most likely to produce exceptions instead of unexpected results. Best regards, Jonas Maurus --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
