round 1 of refactoring is in. its much more elegant now. feedback please.
-Igor
On 11/8/05, Igor Vaynberg [EMAIL PROTECTED] wrote:
thats pretty much exactly what i was thinking.
-Igor
On 11/8/05, Christian Essl [EMAIL PROTECTED]
wrote:
Very good. I am still playing around with the writeReplace
I'm all for making things easier for the user.
Perhaps Wicket could have something like this:
span wicket:id=message:myLabelHere/span
I'm not sure this makes sense. wicket:id is not a text to be displayed
anywhere. It is a name which identifies a component. It definitely
won't work.
Even
Hello,
On 11/7/05, Steven McNeel [EMAIL PROTECTED] wrote:
I consider this sort of thing as analogous to MVC Front Controller (aka
Dispatcher) logic. I'm basically unclear as to where that logic belongs in
a Wicket app.
The fact is, while I'm still new in the area of Components based web
PageableGridDataView is not GridView in extensions. there are only
minor incompatibilities with the old dataview package so you should
have no problems migrating.
the dataview project is no longer in wicket-stuff cvs btw.
-Igor
On 11/8/05, Eelco Hillenius [EMAIL PROTECTED] wrote:
I don't know
Sorry, you were right.
YES, overriding of validation messages now works as expected.
BUT overring of other messages doesn't work any longer. Example:
APage
- XPanel x
- DropDownChoice y
Now the string resource for a displayValue 0 will be searched in the
following order:
APage.properties:
-
I think you are right. I didn't know it is used in AbstractChoice as
well (and there seems to be no test for it either).
Juergen
On 11/9/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Sorry, you were right.
YES, overriding of validation messages now works as expected.
BUT overring of other
and there are about 5 more source to be modified.
Juergen
On 11/9/05, Juergen Donnerstag [EMAIL PROTECTED] wrote:
I think you are right. I didn't know it is used in AbstractChoice as
well (and there seems to be no test for it either).
Juergen
On 11/9/05, [EMAIL PROTECTED] [EMAIL PROTECTED]
Unfortunately the public cvs is late so I can't see your changes yet.
Anyway before I've read this mail I started on reworking the proxing code
(attached). SerializableLazyProxyCreator is the only thing with content
the others are interfaces and one (basic) test.
There are quite some changes:
I understand. That is why I suggested a url that was more like a typicalurl (no page=) and did not require any special configuration by the developer.
Another possibility would be to override Page2.html to mean bookmarkablePage=wicket.examples.template.Page2 so that url:
Juergen Donnerstag wrote:
I'm all for making things easier for the user.
Perhaps Wicket could have something like this:
span wicket:id=message:myLabelHere/span
I'm not sure this makes sense. wicket:id is not a text to be displayed
anywhere. It is a name which identifies a component.
You mean for tag text, correct? span wicket:message=hello.message /
What do you think about wicket:message key=../. Than it is clear
that the whole label is wicket specific,
span wicket:message=key is a bit dangerous because how would we
handle span wicket:id=myLabel wicket:message=key?
Thanks for the response.
How are your questions related to i18n messages?
Sorry I missunderstood the i18n question. I read the preprocessing of the
tag-body you mentioned and thought - well the wrong thing.
Thanks,
Christian
I think wicket:message key=../ would fit well with our other wicket tags,
e.g wicket:panel.
IMHO such an addition would be very useful.
Sven
You mean for tag text, correct? span wicket:message=hello.message /
What do you think about wicket:message key=../. Than it is clear
that the whole
That worked, thanks :)
Gili
Igor Vaynberg wrote:
oops, not=now.
-Igor
On 11/8/05, *Igor Vaynberg* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
PageableGridDataView is not GridView in extensions. there are only
minor incompatibilities with the old dataview package so
I like wicket:message key=../ as long as it would work how normal JSP tags currently work. In other words, I would be able to do this:input type=button value=wicket:message key='labelKey'//
orscript alert(wicket:message key='labelKey'/);/script--AndrewOn 11/9/05,
[EMAIL PROTECTED] [EMAIL
On 11/9/05, Andrew Berman [EMAIL PROTECTED] wrote:
I like wicket:message key=../ as long as it would work how normal JSP
tags currently work. In other words, I would be able to do this:
input type=button value=wicket:message key='labelKey'//
or
script
alert(wicket:message
Oh and the other nice feature would be that if you do it like this: wicket:message key=..My Text/wicket that the My Text would be the default text if the key is not found.
On 11/9/05, Andrew Berman [EMAIL PROTECTED] wrote:
Well, I guess not being able to do it in _javascript_ would be ok, but I
i can live with:
wicket:message key=..Default Text/wicket:message
and
input type=button value=message:key=my-key/
But i think the second one will be pretty hard.
Because then we have to parse the complete xml and see if in any attribute something starts with message:key
even for non wicket
http://thread.gmane.org/gmane.comp.java.wicket.user/5512On 11/9/05, pepone pepone
[EMAIL PROTECTED] wrote:Hello
Is posible in wicket make validation that´s depend on multiple imputsthe simple use case is password match re-passwordother can be input a need to be biger/lesser that input
wicket:message key=..Default Text/wicket:message
and
input type=button value=message:key=my-key/
But i think the second one will be pretty hard.
Because then we have to parse the complete xml and see if in any attribute
something starts with message:key
even for non wicket tags as
Hmmmwell, I do think it would provide value to have the attribute
way as well. How much slower do you think it is going to make it?
Anyone else have any suggestions?
--AndrewOn 11/9/05, Johan Compagner
[EMAIL PROTECTED] wrote:i can live with:
wicket:message key=..Default
We have different options (as explained in my first mail)
- do the replacement while loading the markup, prior to xml reading
it. The cached version will have the messages replaced
- analyze the attributes while reading xml. The cached version will
have the messages replaced for the attrbutes.
if you do the replacement at parse time.
then every html in the markup cache is specified by a locale?
(even if there is not locale in the name of the html)
To me it looks like that wicket:message can only be executed at runtime because then the locale is know
But we could store one for every
Looks like I've missed the part of where is this work available. Is it a way to
access it?
./alex
--
.w( the_mindstorm )p.
---
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it
Johan Compagner wrote:
i can live with:
wicket:message key=..Default Text/wicket:message
This makes sense.
input type=button value=message:key=my-key/
I don't think this one does. It breaks the previewability of pages
which is one of Wicket's hallmarks.
How about something like
On 11/9/05, Johan Compagner [EMAIL PROTECTED] wrote:
if you do the replacement at parse time.
then every html in the markup cache is specified by a locale?
(even if there is not locale in the name of the html)
Thats already the case. The markup id includes locale style etc. But
multiple
good idea, except I would like to make a =. wicket:i18n=value=my-key
Juergen
On 11/9/05, Scott Sauyet [EMAIL PROTECTED] wrote:
Johan Compagner wrote:
i can live with:
wicket:message key=..Default Text/wicket:message
This makes sense.
input type=button value=message:key=my-key/
I
ok then pre process and do it at markup loading time.
The only problem i see with this then that people will start to complaind that they don't
see changes when they alter there messages
So suddenly we also have to watch those??
johan
On 11/9/05, Juergen Donnerstag [EMAIL PROTECTED] wrote:
On
then call it wicket:message=value=my-key
so that
wicket:message key=..Default Text/wicket:message
and
input type=button value=My Val wicket:message=value=my-key/
uses the same kind of notation.
Als value=My Val can then be seen as the default value if the value is not found for the given
It is in wicket-stuff under wicket-contrib-spring. And there in the
wicket.contrib.spring.injection package.
Christian
On Thu, 10 Nov 2005 00:07:44 +0200, Alexandru Popescu
[EMAIL PROTECTED] wrote:
Looks like I've missed the part of where is this work available. Is it a
way to access
Thats an RFE already. I'm not yet sure what the best approach is. Just thinking.
Juergen
On 11/9/05, Johan Compagner [EMAIL PROTECTED] wrote:
ok then pre process and do it at markup loading time.
The only problem i see with this then that people will start to complaind
that they don't
see
yesm true. do you prefer wicket:mesage or wicket:i18n?
Juergen
On 11/9/05, Johan Compagner [EMAIL PROTECTED] wrote:
then call it wicket:message=value=my-key
so that
wicket:message key=..Default Text/wicket:message
and
input type=button value=My Val wicket:message=value=my-key/
One more idea. How about using some reserved word for wicket:id. Like this:
span wicket:id=$somereservedword$ value=message:key1 alt=message:key2/
This would create an automatic component (with a behaviour) that scans all attributes and does its magic. This could be easily extended to other
can't say i have a real preference.
Somehow wicket:message looks better because i18n looks like capitals
But that is just a feeling.
And i still don't know if it is i18n or should it be l10n? (localisation)
Because you do Localize youre page itself. But the template is maybe i18n
On 11/9/05,
Other way of handle tranlations can be take and aproach simiar to Qt ui tollkit
i try to explain it a bit
whe you localiced and application all string in html are desired to be translate
we can parser html files and assign and unique id to each string to be
translate
provide a singuel file for
There sure is a mismatch; component based frameworks emerged because
of the mismatch Model 2 frameworks with page parts. Requests in Model
2 frameworks map to page wide actions. The controller/ view handler
has to ensure the state of all elements of the page are kept in sync
and rendered
How can i use tomcat instead of Jetty? (is there a 'tomcat-config.xml' somewhere to configure?)
Problem with that is that input type=button value=wicket:message
key='labelKey'// is not valid xml.
Eelco
On 11/9/05, Andrew Berman [EMAIL PROTECTED] wrote:
I like wicket:message key=../ as long as it would work how normal JSP
tags currently work. In other words, I would be able to do this:
Hello,
What about something like that:
Use one of the two forms (both could be allowed):
wicket:label key=my.msg.keyA text to render/wicket:label
or
wicket:labelmy.msg.key/wicket:label
Of course, this introduces a new element in the wicket namespace ...
Or something like that:
span
2005/11/9, Andrew Berman [EMAIL PROTECTED]:
Oh and the other nice feature would be that if you do it like this: wicket:message key=..My Text/wicket that the My Text would be the default text if the key is not found.
How about using the content as the key wicket:messagekeyLabel/wicket:message?
#: Christian Essl changed the world a bit at a time by saying on 11/10/2005
12:29 AM :#
It is in wicket-stuff under wicket-contrib-spring. And there in the
wicket.contrib.spring.injection package.
Christian
Thanks a lot Christian.
./alex
--
.w( the_mindstorm )p.
On Thu, 10 Nov 2005
Sure. You need nothing special for Wicket to work with any servlet
container. Just configure as you like/ use plugins from your IDE.
Eelco
On 11/9/05, Paulo Sérgio Medeiros [EMAIL PROTECTED] wrote:
How can i use tomcat instead of Jetty? (is there a 'tomcat-config.xml'
somewhere to configure?)
After rechecking the whole thread, I couldn't find out if this change got into the 1.1 release. Can
somebdoy put some light onto this?
thanks a lot,
./alex
--
.w( the_mindstorm )p.
#: Johan Compagner changed the world a bit at a time by saying on 10/27/2005
1:41 AM :#
Hi
I have written a
just realized its not going to work in a hierarchy of components never mind
-Igor
On 11/9/05, Igor Vaynberg [EMAIL PROTECTED] wrote:
oh and btw, rendering the same component more then once on a page will
throw HEAD into an infinite loop while it works quiet well in 1.0 and
1.1. Should i write
You cannot really compare wicket to tapestry. Although they are both
component oriented frameworks, they have completely different
approaches. In wicket the focus is on java code not on the template.
Wicket templates are simple and limited (purposefully) where as
tapestry allows for a lot more
see if this thread helps.
http://thread.gmane.org/gmane.comp.java.wicket.user/5512
-Igor
On 11/9/05, pepone pepone [EMAIL PROTECTED] wrote:
HelloIs posible in wicket make validation that´s depend on multiple imputsthe simple use case is password match re-passwordother can be input a need to be
oh and btw, rendering the same component more then once on a page will
throw HEAD into an infinite loop while it works quiet well in 1.0 and
1.1. Should i write up a bug or is this part of someone's work in
progress?
-Igor
On 11/9/05, Igor Vaynberg [EMAIL PROTECTED] wrote:
Hmm
isnt all this
no this is 1.2On 11/10/05, Alexandru Popescu [EMAIL PROTECTED] wrote:
After rechecking the whole thread, I couldn't find out if this change got into the 1.1
release. Cansomebdoy put some light onto this?thanks a lot,./alex--.w( the_mindstorm )p.#: Johan Compagner changed the world a bit at a time
#: Johan Compagner changed the world a bit at a time by saying on 11/10/2005
2:05 AM :#
no this is 1.2
Thanks Johan.
./alex
--
.w( the_mindstorm )p.
On 11/10/05, Alexandru Popescu [EMAIL PROTECTED] wrote:
After rechecking the whole thread, I couldn't find out if this change got
into
Hmm
isnt all this already possible without having to do anything?
public class Message extends WebMarkupContainer
{
public Message(String id)
{
super(id);
}
protected void onComponentTagBody(MarkupStream markupStream, ComponentTag openTag)
{
ValueMap attrs=openTag.getAttributes();
if
Hi,
I am trying to use wicket:extend mechanism to share common
functionality between pages and it seem to work only with one level of
hierarchy. When I add another level, I get error (pasted below). Am I
doing something incorrectly?
Here is code to reproduce the behavior:
Base.html:
html
yes it help a lot is what i looking for
thanks Igor and Johan
On 11/9/05, Igor Vaynberg [EMAIL PROTECTED] wrote:
see if this thread helps.
http://thread.gmane.org/gmane.comp.java.wicket.user/5512
-Igor
On 11/9/05, pepone pepone [EMAIL PROTECTED] wrote:
Hello
Is posible in wicket
On Wed, 2005-11-09 at 11:47 -0800, Igor Vaynberg wrote:
You cannot really compare wicket to tapestry. Although they are both
component oriented frameworks, they have completely different
approaches. In wicket the focus is on java code not on the template.
Wicket templates are simple and
Hello i have a page that same times contains tow feedbackpanels i want
to filter messages that are displayed on each one depending of the
component that reports the error
is IFeedbackMessageFilter designed to make this kind of filters?
must i override getFeedbackMessageFilter() to suply my own
Johan Compagner wrote:
then call it wicket:message=value=my-key
so that
wicket:message key=..Default Text/wicket:message
and
input type=button value=My Val wicket:message=value=my-key/
uses the same kind of notation.
I can't decide if I like this idea or not. I like the idea of having as
I think this is starting to get all out of hand and when I suggested
this whole thing I didn't think it was going to be crazy like
this. Perhaps the attribute thing is best left to doing it the
normal Wicket way. I think the only thing I really need for i18n
in terms of changing attributes is for
Most of em do, though we all have kind of our different 'expertises'.
The currently active developers are yours truly, Juergen, Johan, Igor
and Martijn, though Martijn is mainly doing site/ builds/ promotion
etc. Gwyn is the man for Wiki. Jonathan is not really active, but does
some work in the
This is wrong
...
wicket:extend
span wicket:id=subLabelsub label/span
/wicket:extend
wicket:child/...
must be
wicket:extend
span wicket:id=subLabelsub label/span
wicket:child/
/wicket:extend
Juergen
On 11/10/05, Ramnivas Laddad [EMAIL PROTECTED] wrote:
Hi,
I am
Ah... anything outside wicket:extend.../wicket:extend
gets ignored.
Thanks, Juergen.
-Ramnivas
Juergen Donnerstag wrote:
This is wrong
...
wicket:extend
span wicket:id="subLabel"sub label/span
/wicket:extend
wicket:child/
...
must be
wicket:extend
span
59 matches
Mail list logo
