.
-Original Message-
From: Thiago H de Paula Figueiredo [mailto:thiag...@gmail.com]
Sent: Monday, April 27, 2015 21:30
To: Tapestry users
Subject: Re: Customized display/edit blocks for components other than the grid
On Mon, 27 Apr 2015 12:04:48 -0300, Davide Vecchi d...@amc.dk wrote:
Hi
On Thu, 30 Apr 2015 08:35:05 -0300, Davide Vecchi d...@amc.dk wrote:
Ok, thanks for the explanation. Right now we can't update to 5.4 but
when we do we will explore the possibility you mentioned. For now we
have just slightly changed our requirements and we can use the Tapestry
Translator
Very interesting, I will definitely explore this possibility.
-Original Message-
From: Thiago H de Paula Figueiredo [mailto:thiag...@gmail.com]
Sent: Thursday, April 30, 2015 15:23
To: Tapestry users
Subject: Re: Customized display/edit blocks for components other than the grid
On Thu
Are you aware that BeanEditor, BeanEditForm and BeanDisplay all obey the
BeanBlockSource?
On Mon, 27 Apr 2015 12:04:48 -0300, Davide Vecchi d...@amc.dk wrote:
Hi everybody,
Hi!
Now I'm wondering if there is some similar mechanism in Tapestry that
can be used not only for grids but also for other components, f.ex. a
normal TextField not inside a grid.
Not out-of-the-box.
In
Hi everybody,
I would like to define a custom numeric datatype, f.ex. monetary, for the
purpose of annotating fields and accessor methods with something like
@DataType(monetary)
so that such fields would be rendered and edited according to a custom format.
I actually tried that by contributing
