Am Fr, 10.10.2008, 10:56, schrieb Francois Armand: > Ok, so we reach the point where T5.0 final is imminent, and we are all > (I think) really happy of that. > As we also want that T5 really makes its way in the Java Web ecosystem, > I think it always miss some really little things that are really > important for a .0 release. > > I purpose to start this discussion in the ml, and when some major gap > emerge, to post them in the issue tracker, and vote for them. > > So, for me, what I expect for 5.0 : > 1/ - full and complete and rather simple internationalization : I really > believe that a web framework can ignore other language and culture > (date, number) today ; > that include validator translation and stuff like that.
I believe you meant "can't" ;-) https://issues.apache.org/jira/browse/TAP5-211 This is the thing I care the most about as there is no workaround without breaking other things. > 2/ - valid XHTML, even for IE, by default. The workaround is here for > some time, but why it's not default ? See > http://wiki.apache.org/tapestry/Tapestry5HowToXhtml > 3/ - something around AJAX documentation and Zone update inside a form > (that includes update of part of a form on change from a select : > https://issues.apache.org/jira/browse/TAP5-138) That seems to be a very frequent use case and should really be implemented soon. > 4/- a property symbol provider, also simple and in use almost always > @see > http://wiki.apache.org/tapestry/Tapestry5HowToReadSymbolsFromPropertiesFile I think this is not that important to have. There is a simple solution in the wiki that people can refactor into a module, put it in a jar file and drop it into their projects as needed. On the other hand this wouldn't be too complicated to integrate into the core distribution, given that the code already exists. > > Without 1, T5 just can't get is path easely outside English contries ; > Without 2, T5 can hardly be considered top-level (even if on the > technical point of vue, it's completly rigth and it's IE fault), without > 3, AJAX seems not so well integrated, and it's hot stuff todays, and 4 > is so much common in a application, why do we have to bother with that > each time ? > > Other simple stuff that should be corrected before 5.0 (in my opinion) : > - why hidden field is still missing ? It's so easy to add, a new user > should not even have to search for that ! > - https://issues.apache.org/jira/browse/TAP5-257, that seems to bring > other pb with decorator and the like ; Personally, I can live with all of those points except the localization issues. On the other hand I think that most of your points can be solved without much effort and therefore should be considered for the final release. Cheers, Uli --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
