The thing to remember is that Grid and BeanEditForm are intended as scaffolding to get you up and running quick. As your application gets refined, you may start to pull apart the scaffolding components to build something more precisely tuned to your specific requirements. It is not my intention that we should keep layering on more parameters and models and such to make BeanEditForm and Grid the be-all and end-all of editting and display components; they're really about keeping momentum going, especially during the early, frustrating parts of writing an application: those first few steps.
On Fri, Mar 6, 2009 at 2:25 PM, leechj <lee...@gmail.com> wrote: > > Hello, > I was wondering if there was an easy way to add properties to fields in a > BeanEditForm. > Our application needs "tabindex" and "accesskey" in all fields in order to > comply with federal rules dealing with accessibility. Is there a way to add > these 2 properties to the fields in the form or should I just create the > form by hand instead of using BeanEditForm? > > Thanks for any help! > > > -- > View this message in context: > http://www.nabble.com/Tabindex-and-accesskey-in-BeanEditForm--tp22380749p22380749.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
