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 component, but it looks like what I need to attach to with the
BeanEditForm is several layers deep of components within components
and I'm not sure the best approach for that.
Is there a way to inject functionality into the bean editor? Is it
better to try to just extend the bean editor?
Any suggestions would be helpful--particularly if there are any
examples even remotely similar that I may have overlooked.
Mark
On Tue, Feb 8, 2011 at 3:10 PM, Thiago H. de Paula Figueiredo
<thiag...@gmail.com> wrote:
> Please file a JIRA asking for an additional parameter (<p:xxxDescription>,
> 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 mixin that adds the descriptions after BeanEditor/BeanEditForm is
> rendered.
>
> On Tue, 08 Feb 2011 18:03:08 -0200, Mark <mark-li...@xeric.net> wrote:
>
>> On Tue, Feb 8, 2011 at 12:53 PM, LLTYK <ll...@mailinator.com> 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, but my goal is to be able to create this without needing to
>> customize the .tml file.
>>
>> Ideally what I want is something like this:
>>
>> class Person {
>> @ToolTip("The first name of the person being edited")
>> String firstName;
>> @ToolTip("The last name of the person being edited")
>> String lastName;
>>
>> //getters and setters
>>
>> }
>>
>> Assuming I can figure out how to setup the annotation, what is the
>> best way to change the filed names on the the bean edit form, without
>> resorting to creating a parameter for each attribute?
>>
>> I looked at some of the custom decorator documentation, but it seems
>> designed for modifying services rather than components.
>>
>> Mark
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>> For additional commands, e-mail: users-h...@tapestry.apache.org
>>
>
>
> --
> Thiago H. de Paula Figueiredo
> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and
> instructor
> Owner, Ars Machina Tecnologia da Informação Ltda.
> Consultor, desenvolvedor e instrutor em Java, Tapestry e Hibernate
> Coordenador e professor da Especialização em Engenharia de Software com
> Ênfase em Java da Faculdade Pitágoras
> http://www.arsmachina.com.br
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
