"default-binding-prefix" is a lovely thing, I like it. it is very useful "somewhere", and maybe not "otherwhere", why not we use it partly in the framework (when it do need)? such as <form listener="doClick"> not <form listener="listener:doClick"> we don't need to remove it entirety.
IMO, to keep "default-binding-prefix" partly exist, we can add another parameter to all components, "use-default-binding", which default to False. and we can encourage the tapestry users not to use the "default-binding-prefix", to avoid somethings. liigo, thanks 在 Wed, 27 Jul 2005 04:29:18 +0800，Howard Lewis Ship <[EMAIL PROTECTED]> 写 道:
Now, we don't want to make the same mistake as Sun did with Generics; how do we reach concensus on wether to include or strip out default-binding? Another vote? I tending towards leaving it as is, but there are some good ideas on how to processed if we strip default-binding out. For example, changing the various link components to take a "onclick" parameter (as a rename of "listener"), i.e. <a listener="listener:doClick">...</a> vs. <a onclick="listener:doClick"> ... </a> The lack of repetition in the second example is desirable. I'm also tending towards default of literal: in a template, default of ognl: in XML. But there's that consistency issue again; perhaps is should be literal: everywhere for best efficiency?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
