You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Simon Robins <si...@mac.com> on 2003/02/07 00:05:48 UTC
clearing property-specification properties
Do I need to clear property-specification properties in the initialize
method using setXXX?
Cheers,
Simon
RE: clearing property-specification properties
Posted by "Howard M. Lewis Ship" <hl...@attbi.com>.
The problem is that name was (in that release) already a property on the
page.
I've done some cleanup in alpha-5 that breaks some backwards compatibility
(like renaming the packages didn't), but will fix this. The properties name
and qualifiedName were removed, now there is just pageName.
--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/proposals/tapestry
> -----Original Message-----
> From: Simon Robins [mailto:simonrobins@mac.com]
> Sent: Sunday, February 09, 2003 11:46 AM
> To: Tapestry users
> Subject: Re: clearing property-specification properties
>
>
> My mistake. I should have read the updated User Guide and not
> just the
> Developer Guide.
>
> BTW is there a problem in the new property-specification code. I have
> the following:
>
> <property-specification name="name" type="java.lang.String"/>
>
> and when first displayed the 'name' property has the value
> 'Home' which
> just happens to be the page name.
>
> Cheers,
>
> Simon
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
Re: clearing property-specification properties
Posted by Simon Robins <si...@mac.com>.
My mistake. I should have read the updated User Guide and not just the
Developer Guide.
BTW is there a problem in the new property-specification code. I have
the following:
<property-specification name="name" type="java.lang.String"/>
and when first displayed the 'name' property has the value 'Home' which
just happens to be the page name.
Cheers,
Simon
DatePicker localization
Posted by Per Norrman <pe...@telia.com>.
Hi again,
I just started looking in to this. The DatePicker calendar is
a funny one; not even a hint of the concept of leap year!
While am at it, anyone against making the calender conform
solely to the French Revolution Calendar (12 months, each month with
three 10 day weeks, plus 5 or 6 leap days (could be made holidays!)).
I wonder what locale that should be: rv_FR perhaps?
/pmn
RE: DatePicker localization
Posted by "Howard M. Lewis Ship" <hl...@attbi.com>.
Yes, that's exactly what I'd like to see!
Don't have a solution for testing JavaScript.
--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/proposals/tapestry
> -----Original Message-----
> From: Per Norrman [mailto:pernorrman@telia.com]
> Sent: Friday, February 07, 2003 10:59 AM
> To: 'Tapestry users'
> Subject: SV: DatePicker localization
>
>
>
> Dou you mean replacing just the text field and the button
> with a select tag, but keeping the popup grid?
> And the select tag containing just one option value, the
> selecetd date?
>
> I see no immediate problems with that. My first shot
> would, however, be to fix the localization of
> month and weekday names, plus the first-day-of-week thingy.
>
> BTW, is there a smart and *quick* way for testing JavaScript
> stuff when using tapestry script specifications.
>
> /pmn
>
>
> > -----Ursprungligt meddelande-----
> > Från: Howard M. Lewis Ship [mailto:hlship@attbi.com]
> > Skickat: den 7 februari 2003 15:25
> > Till: 'Tapestry users'
> > Ämne: RE: DatePicker localization
> >
> >
> > Currently, the DatePicker is built using a text field, and a
> > Submit button (plus some hidden fields and a bit of JavaScript).
> >
> > Would it be possible to build it using a <select> tag? It
> > would match the L&F of the page better that way.
> >
> > --
> > Howard M. Lewis Ship
> > Creator, Tapestry: Java Web Components
> > http://jakarta.apache.org/proposals/tapestry
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
SV: DatePicker localization
Posted by Per Norrman <pe...@telia.com>.
Dou you mean replacing just the text field and the button
with a select tag, but keeping the popup grid?
And the select tag containing just one option value, the
selecetd date?
I see no immediate problems with that. My first shot
would, however, be to fix the localization of
month and weekday names, plus the first-day-of-week thingy.
BTW, is there a smart and *quick* way for testing JavaScript
stuff when using tapestry script specifications.
/pmn
> -----Ursprungligt meddelande-----
> Från: Howard M. Lewis Ship [mailto:hlship@attbi.com]
> Skickat: den 7 februari 2003 15:25
> Till: 'Tapestry users'
> Ämne: RE: DatePicker localization
>
>
> Currently, the DatePicker is built using a text field, and a
> Submit button (plus some hidden fields and a bit of JavaScript).
>
> Would it be possible to build it using a <select> tag? It
> would match the L&F of the page better that way.
>
> --
> Howard M. Lewis Ship
> Creator, Tapestry: Java Web Components
> http://jakarta.apache.org/proposals/tapestry
>
RE: DatePicker localization
Posted by "Howard M. Lewis Ship" <hl...@attbi.com>.
Currently, the DatePicker is built using a text field, and a Submit button
(plus some hidden fields and a bit of JavaScript).
Would it be possible to build it using a <select> tag? It would match the
L&F of the page better that way.
--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/proposals/tapestry
-----Original Message-----
From: Per Norrman [mailto:pernorrman@telia.com]
Sent: Friday, February 07, 2003 6:56 AM
To: 'Tapestry users'
Subject: DatePicker localization
Hi,
the DatePicker is nice. However, has anyone done
any work to localize it? Apart from the obvious
difference in day and month names, some locales
start the week on another day than Sunday.
If there is no work done and an interest, I can give it
a try, otherwise I just do quick port to swedish
rules.
/pmn
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
DatePicker localization
Posted by Per Norrman <pe...@telia.com>.
Hi,
the DatePicker is nice. However, has anyone done
any work to localize it? Apart from the obvious
difference in day and month names, some locales
start the week on another day than Sunday.
If there is no work done and an interest, I can give it
a try, otherwise I just do quick port to swedish
rules.
/pmn
RE: clearing property-specification properties
Posted by "Howard M. Lewis Ship" <hl...@attbi.com>.
Nope! That's the great thing about them; they automatically clear at the
end of the request.
You can set initial values for them three ways:
1) As an OGNL expression (the initial-value expression).
2) As an OGNL expression (as the character data for the
property-specification element) (this is not even in CVS yet, though).
3) By overriding finishLoad() and setting the property there.
The property is set to this initial value. In the case of an OGNL
expression, the value is only evaluated once.
--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/proposals/tapestry
-----Original Message-----
From: Simon Robins [mailto:simonrobins@mac.com]
Sent: Thursday, February 06, 2003 6:06 PM
To: Tapestry users
Subject: clearing property-specification properties
Do I need to clear property-specification properties in the initialize
method using setXXX?
Cheers,
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org