> 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.
I believe there was a bit of a miscommunication here. The reason Erik said that the property tags needs to be broken up before 1.3 (a opinion I do not share) is because the current property tag behavior does pretty much everything it can to confuse new users. If we want to attract new users with 1.3 it would be a good idea to simplify the taglib (but keeping property tag as a deprecated tag of course) so that we can attract new users by saying "see how stable, easy and logical it is" and not just "it's stable". Easy to learn is a BIG argument, especially for those who want their web designers to edit the JSP code. A full page of complicated documentation for the property tag is not very polite to the non-coders that need to use webwork imho. // Anders Hovmöller PS. I hope I didn't put words in your mouth Erik. DS. ------------------------------------------------------- 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
