Hi,

I think you can use a message: prefix as well (defining it in the
app.properties) - tough a symbol (or similar) binding for properties will
probably be less confusing.

For date field format the message: binding is a perfect match as you get all
the ordinary resource bundle goodness for free ;)
-- 
Chris

On Tue, Sep 27, 2011 at 4:49 PM, Steve Eynon <steve.ey...@alienfactory.co.uk
> wrote:

> To enhance Tapestry, what are people's thoughts about defining default
> component values for some components as Symbols?
>
> For example, the Grid component has the following:
>
> @Parameter("25")
> private int rowsPerPage;
>
> meaning if I wish for a pagination of 50 rows, I have to find all
> instances of the Grid component in my application and manually add a
> "rowsPerPage" parameter.
>
> But if the parameter was defined as:
>
> @Parameter("symbol:tapestry.grid.rowsPerPage")
> private int rowsPerPage;
>
> then all I would need to do is override the symbol contribution and
> voilĂ , it changes everywhere.
>
> While converting developers to T5 a common question I'm asked is,
> "That's cool - but how do I now make that change happen everywhere in
> the app?" At the moment all I can do is shrug and say, "Um, it's
> complicated." (*)
>
> Other specific component defaults I've been asked about are, the
> "update" parameter for Zone et al (because the classic "yellow fade"
> doesn't work for everyone!) and a date format for DateField (I know
> this one is a bit tricky, but the default format for the default
> formatter could be supplied by a symbol).
>
> To me, this why Symbols exist, for extensible configuration - so, err,
> how about it!? Or have I overlooked / missed something really obvious
> here?
>
> Regards,
>
> Steve.
>
> (*) I know workers and mixins can accomplish the same, but a T5 newbie
> isn't going to appreciate that!
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>

Reply via email to