-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Richard Lewis-Shell wrote: | Richard Lewis-Shell: -1 (binding) | | It is not clear to me that we have exhausted other possibilities to | reduce confusion. Removing the feature seems pretty heavy handed. If | it was deemed that defaults were not so good for the framework, then an | alternative idea would be to make all framework parameters use OGNL but | allow other people/components to use defaults if they want to. (this | might actually be what the vote was for - that is also not clear to me) This is what I view as the best proposal. There will always be a "default" even if it's not specified that it's a default (literal). My thoughts on 'best path' were to have that default be "literal" (ala specify a prefix if you want, otherwise we treat it as a literal) while allowing that default to be changed in the application's config. For that, I'm still +1 as any confusion would be relegated to the project personnel, not tapestry itself. (never going to remove all confusion) | | eg. why not make template bindings always use literal unless otherwise | specified. This is backwards compatible with 3.0 which is where this | original problem came from - pain+confusion when upgrading to 4.0. |
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) iD8DBQFCmmnaaCoPKRow/gARAjUSAKDTFGmHEZ7eGQ4e5RB0ae296iDqyACgyWEP EL9XM64o5PhVXr6ZbCMZ6J4= =fFgM -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
