On Tue, 08 Feb 2011 21:55:01 -0200, Mark wrote:
The mixin approach sounds reasonable, but I'm not sure how to approach
changing what gets rendered in each row of the bean editor. I'm not
sure how to go about changing the functionality of an existing
components.
This mixin wouldn't change the
The mixin approach sounds reasonable, but I'm not sure how to approach
changing what gets rendered in each row of the bean editor. I'm not
sure how to go about changing the functionality of an existing
components.
The mixins that I'm familiar with usually add some code to the page or
to the compo
Please file a JIRA asking for an additional parameter (,
for example) in BeanEditor/BeanEditForm that is put inside the field
edition block. Or some other message key convention, such as
xxx-description, to do the same without any markup customization.
Meanwhile, you could try writing a mix
On Tue, Feb 8, 2011 at 12:53 PM, LLTYK wrote:
>
> A more descriptive label would be easy, just add the keys to the properties
> file. More than that will probably delve into custom decorator or property
> block territory.
I need the label to stay the same. I'm familiar with the property
block, bu
A more descriptive label would be easy, just add the keys to the properties
file. More than that will probably delve into custom decorator or property
block territory.
--
View this message in context:
http://tapestry-users.832.n2.nabble.com/Annotation-for-Field-Description-tp6004837p6005098
I am working on a project where the datamodel is being changed
frequently. The bean edit form is a huge timesaver because it changes
automatically and I don't have to go in an edit every form.
However, I'm finding that I need a bit more explanatory information
for my test users. I know I can ove
