There is a JIRA issue about this:
https://issues.apache.org/jira/browse/TAP5-119
Please vote, so we get it higher on priority list.
Fernando Padilla wrote:
alright, so we just upgraded from 5.0.11 to 5.0.16-SNAPSHOT, so sorry I
was not able to complain earlier.. Please help:
but tapestry
I agree with all the points.
And, for point #4, there is also a JIRA issue you can vote on:
https://issues.apache.org/jira/browse/TAP5-223
As it is a simple addition and commonly used, I do not see why it should
not be included in 5.0. Then the wiki page can just describe how to
enable it
Ulrich Stärk wrote:
Russell Brown schrieb:
What 'it'? You mean symbol names?
Well the 'it' was the class, or moreover the approach but that does
result in specifically the
symbol names in this instance, so: Yes that it, or they.
Indeed. I think I could just load everything into a Map,
wrote:
Neeme Praks schrieb:
PS. Sorry about the curly braces style in the refactored class - my
eclipse autoformatted it to my coding style and I was too lazy to
change it back
Please don't be too lazy next time... I revised it a bit because I
personally don't like to have several
Added:
https://issues.apache.org/jira/browse/TAPESTRY-2684
Rgds,
Neeme
9902468 wrote:
+1, I've encountered this annoyance too... I'd say add Jira issue.
Neeme Praks wrote:
Hi,
While debugging with Tapestry5, I noticed one not-so-nice issue. But
first, a bit of background.
I usually
I'm not sure if it is the same, but I'm also interested if there is a
way to centralize ALL i18n strings into a single messages file. By ALL
i18n strings I mean all texts from components, pages and layouts combined.
So when I need to add a new language to my T5-based webapp, I can take
that
Nice, thanks for that one.
I would suggest to add that PropertiesFileSymbolProvider class also to
main Tapestry5 distribution. And I took the liberty to refactor the
symbol provider implementation in wiki to be more generic: it now
accepts also URL and InputStream as possible places to load
Hi,
While debugging with Tapestry5, I noticed one not-so-nice issue. But
first, a bit of background.
I usually configure my logging framework (log4j) to log all statements
for my application at debug level during development. E.g. all log
records logged to com.mycompany.myapp logging
