Re: message catalog and generated labels from property name
If it is boolean, better way is to define the label in properties. propertyname.true=Yes propertyname.false=No DH - Original Message - From: "Thiago H. de Paula Figueiredo" To: "Tapestry users" Sent: Tuesday, January 26, 2010 11:07 PM Subject: Re: message catalog and generated labels from property name On Tue, 26 Jan 2010 12:07:13 -0200, kamiseq wrote: > oh, one more thing > can I map values in components like grid to some other names. > so if in cell I have "false" or "true", can I map this to something like > yes / no Not out of the box, but you can use blocks (formerly blocks) to override how a property will be output. This is documented at the Grid componente reference: http://tapestry.apache.org/tapestry5.1/tapestry-core/ref/org/apache/tapestry5/corelib/components/Grid.html. -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, software architect and developer, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: message catalog and generated labels from property name
On Tue, 26 Jan 2010 12:07:13 -0200, kamiseq wrote: oh, one more thing can I map values in components like grid to some other names. so if in cell I have "false" or "true", can I map this to something like yes / no Not out of the box, but you can use blocks (formerly name=""> blocks) to override how a property will be output. This is documented at the Grid componente reference: http://tapestry.apache.org/tapestry5.1/tapestry-core/ref/org/apache/tapestry5/corelib/components/Grid.html. -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, software architect and developer, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Res: message catalog and generated labels from property name
I'm sorry... Because of the email subject i though you knew about the properties label name changing... De: kamiseq Para: Tapestry users Enviadas: Terça-feira, 26 de Janeiro de 2010 12:03:17 Assunto: Re: message catalog and generated labels from property name I think I missed that somehow as you can write a name of the property in mypage.properties file and the new label will be applied as well. but of course that doesn't work when there is a space in label. ok I will check that out. thanks! pozdrawiam Paweł Kamiński kami...@gmail.com pkaminski@gmail.com __ Veja quais são os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.com
Re: message catalog and generated labels from property name
oh, one more thing can I map values in components like grid to some other names. so if in cell I have "false" or "true", can I map this to something like yes / no pozdrawiam Paweł Kamiński kami...@gmail.com pkaminski@gmail.com __
Re: message catalog and generated labels from property name
I think I missed that somehow as you can write a name of the property in mypage.properties file and the new label will be applied as well. but of course that doesn't work when there is a space in label. ok I will check that out. thanks! pozdrawiam Paweł Kamiński kami...@gmail.com pkaminski@gmail.com __
Re: message catalog and generated labels from property name
On Tue, 26 Jan 2010 11:17:07 -0200, kamiseq wrote: hi, Hi! my problem is that tapestry in components generates labels as two words (with space between) from property name when camel notation is used so property name like rtobjectDescr will be changed to 'Rtobject Descr' and then I cant change this in my message catalog to something that makes more sense to a user. You *can* change this: add rtobjectDescr-label=Nice label to your app.properties. -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, software architect and developer, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Res: message catalog and generated labels from property name
Hi, Is changing the property label (on the page's properties file) on Grids/BeanDisplays/BeanEditForms so bad? I believe this auto-naming just do the majority work... And when you need to support another languages also, it's more usual to change it... Usually, if you name your Objects/Properties well, the auto naming would be better... That would be a problem only if you were working on infra-structure classes that couldn't be changed... But i'm curious to know if i can define the property's name in another way than properties/beanmodel De: kamiseq Para: Tapestry users Enviadas: Terça-feira, 26 de Janeiro de 2010 11:17:07 Assunto: message catalog and generated labels from property name hi, my problem is that tapestry in components generates labels as two words (with space between) from property name when camel notation is used so property name like rtobjectDescr will be changed to 'Rtobject Descr' and then I cant change this in my message catalog to something that makes more sense to a user. and I can really find a solution to that other then add another getter and setter with other name and exclude original name in component thanks pozdrawiam Paweł Kamiński kami...@gmail.com pkaminski@gmail.com __ Veja quais são os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.com
message catalog and generated labels from property name
hi, my problem is that tapestry in components generates labels as two words (with space between) from property name when camel notation is used so property name like rtobjectDescr will be changed to 'Rtobject Descr' and then I cant change this in my message catalog to something that makes more sense to a user. and I can really find a solution to that other then add another getter and setter with other name and exclude original name in component thanks pozdrawiam Paweł Kamiński kami...@gmail.com pkaminski@gmail.com __
