I've been thinking in terms of @Type("foo"). Right now, it is deducing the
type exclusively from the Java type: so String and Number -> text, etc.
Allowing @Type would provide an easy way to reference additional, or custom,
types such as "password" or "textarea", etc.
On 10/27/07, Christoph Jaeger <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I like using the BeanEditForm, but I think there should be some
> additional annotations to make it even easier to use.
>
> There is already an annotation called "NonVisual" to mark properties you
> do not want to display on your page.
>
> How about
>
> @Display(type=password)
>
> so you do not have to use
>
> <t:parameter name="password">
> <t:label for="password"/>
> <t:passwordfield t:id="password" value="person.password"/>
> </t:parameter>
>
> or
>
> @Display(type=multiline)
>
> instead of
>
> <t:parameter name="address">
> <t:label for="address"/>
> <t:textarea t:id="address" value="person.address"/>
> </t:parameter>
>
> or
>
> @Display(type=text, length=30)
>
> for
>
> <t:parameter name="email">
> <t:label for="email"/>
> <t:textfield t:id="email" value="person.email" size="30"/>
> </t:parameter>
>
> I think this would increase the chances of using just
>
> <t:beaneditform object="person"/>
>
> in your .tml files. Or is something like this already implemented, and I
> just overlooked it?
>
> Thanks,
>
> Christoph Jäger
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Howard M. Lewis Ship
Partner and Senior Architect at Feature50
Creator Apache Tapestry and Apache HiveMind
