I have a lateral suggestion that you might not like. My design “rule of thumb” is to use a paged grid for display only. I find it ambiguous to use for create/update/delete because when you change pages, or click on a column to re-sort the grid, or change the value of a filter field (if you have one), then it is not at all clear that it should remember the changes you’ve made to fields.
Just my two cents worth. Geoff > On 13 Apr 2016, at 9:12 PM, Thiago H de Paula Figueiredo <thiag...@gmail.com> > wrote: > > On Tue, 12 Apr 2016 08:32:29 -0300, Ricardo Veloso > <ricardo.vel...@flowinn.biz> wrote: > >> Obrigado! :) > > De nada! É um prazer ajudar! > > Translating from Portuguese to English: > >> Thanks! > > You're welcome! It's a plasure to help! > >> Issue opened: TAP5-2542 <https://issues.apache.org/jira/browse/TAP5-2542> > > Thanks! > >> Meanwhile I will try to get a workaround for this, simulating a checkbox >> with images and trigger an event when is checked, in order to get things >> done on time. > > You can use an ordinary HTML checkbox (<input type="checkbox">, without a > t:type attribute), so you don't need to use images. Or maybe you could use > some AJAX, keeping the checkbox or changing it to an EventLink. > > -- > Thiago H. de Paula Figueiredo > Tapestry, Java and Hibernate consultant and developer > http://machina.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
