OK, so a little sum up with the matching bug reference, so that at least
everybody can vote for this easaly. It would be quite simple afterward
to bring the T5 dev attention to bugs with tens of vote for them.
Note: some bugs are in the Tapestry project, not the TAP5 one. I thing
there owners should reopen them in the new TAP5 project.
So ! Go and vote for your bugs and features !!
(notice 2 : I really believe that T5 is a WONDERFUL framework, and it's
just that the 5.0 is so much important in people (I mean, non tech)
spirit that it deserve to reflect the beauty of T5. I would be a mass
that people stop after only some trying ours because they it one of the
these bugs).
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.
It's a point that seems to drove a lot of attention, and which is really
important for the success of T5 outside English-speaking countries.
So, there is the validator already opened bug :
https://issues.apache.org/jira/browse/TAP5-211
UTF-8 in autocomplete, with the one-line patch :
https://issues.apache.org/jira/browse/TAPESTRY-2433
"There is no data to display." is hardcoded in Grid.tml :
https://issues.apache.org/jira/browse/TAP5-262
If other specific issue with i18n appears, please open other bugs and
linked them here.
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
It appears that it's important that things will "just work" on IE, even
if this browser suck. Perhaps a configuration value ?
So, the bug :
https://issues.apache.org/jira/browse/TAP5-263
Others queries was raised :
* Javascript at top or bottom of the page, what seems to be a really hot
topic, and does not required a lot of modification in T5 code base :
https://issues.apache.org/jira/browse/TAPESTRY-2364
The bug is closed, so perhaps it will be good to open a new one for
5.0.16 and post the link ?
* ApplicationStateObject, "mileading name". The fact here is that after
5.0 released, the named will be write in the stone forever. Personnaly,
I have no opinion on that topic, but it appears that several members in
my team don't feel at ease with this name.
Related bug :
https://issues.apache.org/jira/browse/TAPESTRY-2703
* T5 lacks queries with named parameters, especially for search and this
kind of queries.
I'm fear that this one may require a lot of modification in the T5 code
base. Some solution are purposed, like having a map in the query :
http://foo/myT5app/mypage/normalcontext/mycontextmap=[key1:value1,key2:value2]/othercontextparam
will match a onActivate(String normalcontext, Map<String,String>
mycontextmap, String othercontextparam).
The map would contains the different key/values.
The bug is here :
https://issues.apache.org/jira/browse/TAP5-264
* Missing "hidden" field component : a rather simple thing to do, and a
strange missing :
https://issues.apache.org/jira/browse/TAP5-265
The next queries seems to be less important, so for now I didn't opened
other bugs.
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)
4/- a property symbol provider, also simple and in use almost always
@see
http://wiki.apache.org/tapestry/Tapestry5HowToReadSymbolsFromPropertiesFile
[...]
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 ;
Enloy !
--
Francois Armand
Etudes & Développements J2EE
Groupe Linagora - http://www.linagora.com
Tél.: +33 (0)1 58 18 68 28
-----------
InterLDAP - http://interldap.org
FederID - http://www.federid.org/
Open Source identities management and federation
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
