On Thursday, November 7, 2002, at 03:47 AM, Erik Beeson wrote:
Erik, the property tag will never undergo a major change in behavior. The amount of code that this would break would be huge. Everyone who ever used the Taglibs would have to have a development iteration just to recode their Views to handle the new behavior.
One of two things NEEDS to happen here. Either property tag NEEDS to be
broken up, before 1.3. OR one of you people who is set on not breaking it
up needs to document the beegeebers out of it, put your money where your
mouth is so new users at least stand a chance at using this thing.
Telling your existing users "if you don't like use something else", is immoral. They have trusted us and many have large applications built on the framework. Just packing up and going somewhere else is too cost prohibitive for them. These guys also *need*, not want, 1.3. The 1.2.x series was extremely buggy and they need to get those bugfixes. There is simply no way we can tell them that they have to rewrite their View layers just to get bugfixes.
-Maurice
-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
