er natively, not naively. On Mon, Nov 21, 2011 at 3:51 PM, Ray Nicholus <rnicho...@widen.com> wrote:
> Looks interesting, and I do think a mixin is a good way to go here. > However, I'm trying to think of a case where multiple submits would be > permissible. If there is no such case, perhaps it would be ideal for this > to be handled naively by Tapestry. Has there been any discussion along > these lines? > > > 2011/11/21 François Facon <francois.fa...@atos.net> > >> Nice Work Lenny. >> >> I just discovered your mixin >> >> http://code.google.com/p/flowlogix/source/browse/services/src/main/java/com/flowlogix/web/mixins/DisableAfterSubmit.java >> >> And his related prototype file >> >> http://code.google.com/p/flowlogix/source/browse/services/src/main/resources/com/flowlogix/web/mixins/DisableAfterSubmit.js >> >> >> >> 2011/11/21 Lenny Primak <lpri...@hope.nyc.ny.us>: >> > Perhaps there are better solutions, but I solved it via >> DisableAfterSubmit mixin in my FlowLogix utility module >> http://code.google.com/p/flowlogix/ >> > >> > On Nov 21, 2011, at 4:07 PM, Ray Nicholus <rnicho...@widen.com> wrote: >> > >> >> I'm sure I am not the first one to encounter this problem, and before >> I go >> >> about re-inventing the wheel, I wanted to see if this is something >> that has >> >> already been elegantly solved in the tapestry circle. Anyone? >> > >> > >> > --------------------------------------------------------------------- >> > 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 >> >> >
