Okay, will do. I plan using this in my current project, so after some
testing with a more complicated application I'll provide the patch.
-Matej
Juergen Donnerstag wrote:
Ok, I agree on this as well. Matej, are you able to provide a patch
(incl. javadoc, formatting, etc.) to add it to wicket-e
Ok, I agree on this as well. Matej, are you able to provide a patch
(incl. javadoc, formatting, etc.) to add it to wicket-extension?
Juergen
On 7/23/05, Matej Knopp <[EMAIL PROTECTED]> wrote:
> Eelco Hillenius wrote:
> > Juergen Donnerstag wrote:
> >
> >> we've discussed it already and agreed on
Eelco Hillenius wrote:
Juergen Donnerstag wrote:
we've discussed it already and agreed on waiting for Matej to come up
with a first draft to proof that the idea works, and it obviously does
very well.
But I guess I'm the only one, who thinks there must be a better
solution. I guess the reason
Juergen Donnerstag wrote:
we've discussed it already and agreed on waiting for Matej to come up
with a first draft to proof that the idea works, and it obviously does
very well.
But I guess I'm the only one, who thinks there must be a better
solution. I guess the reason why I'm not especially k
Matej Knopp wrote:
Eelco Hillenius wrote:
Looks nice. It doesn't break the API, right?
No, it doesn't break anything. I wanted to make it as transparent as
possible.
Do you think this should be something that Wicket supports
out-of-the-box, or something that you can use as an add-on (in whic
we've discussed it already and agreed on waiting for Matej to come up
with a first draft to proof that the idea works, and it obviously does
very well.
But I guess I'm the only one, who thinks there must be a better
solution. I guess the reason why I'm not especially keen on the idea
is because it
Eelco Hillenius wrote:
Looks nice. It doesn't break the API, right?
No, it doesn't break anything. I wanted to make it as transparent as
possible.
Do you think this should be something that Wicket supports
out-of-the-box, or something that you can use as an add-on (in which
case we could put i
Looks nice. It doesn't break the API, right?
Do you think this should be something that Wicket supports
out-of-the-box, or something that you can use as an add-on (in which
case we could put it in the extensions project).
Eelco
Matej Knopp wrote:
I think the functionality is more important
Johan Compagner wrote:
i also like the idea that you have one html file, X number of property
files and then at load time of the markup file
for a specific locale the property file for that locale is merged in
to the html. And that html is stored for that locale in the cache.
At least i think
i also like the idea that you have one html file, X number of property
files and then at load time of the markup file
for a specific locale the property file for that locale is merged in to
the html. And that html is stored for that locale in the cache.
At least i think tht is the complete idea?
I think the functionality is more important that the actual source code.
This example was supposed to be a simple one.
It certainly can be implemented in a different way than I have done it.
If anyone knows better place where to hook the translation please let me
know.
-Matej
Eelco Hillenius
I like it (haven't look at the source code, but I like the
functionality). What about having a vote whether and where (which
project) this should be integrated?
I'm off to bed soon, but I'll certainly take a look tomorrow!
Eelco
Matej Knopp wrote:
Hi.
I've made a demo showing international
12 matches
Mail list logo
