You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by "F. Da Costa Gomez" <dc...@fixed.com> on 2003/11/26 13:28:26 UTC
[onClick capture] Immediate checkbox processing
Hi,
What would be the best way to immediately process the onClick / select
action on a checkbox so that it goes to the server right away to be
processed.
Looking at the @Checkbox html code there is no href to use (or at least
not on my page).
Do I 'manually create a href through js or am I missing something obvious?
TIA,
Fermin DCG
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [onClick capture] Immediate checkbox processing
Posted by "Kevin C. Dorff" <kd...@dorffweb.com>.
I would say, in general, doing a submit after every change, text field,
any input is a bad idea. You application performance will go right into
the toilet even on a fast network.
Train your users to fill in the form and click "Save Changes" or "Cancel
Changes".
Kevin
F. Da Costa Gomez wrote:
> Forgot about that, thx.
>
> However, I was/ am looking for a more direct approach to dealing with
> the checkbox or any other <input tag> for that matter.
> The form is encapsulating a TreeTable with an unknown number of
> branches & leafs. So a submit could be quite large.
> Basically I have a choice to make:
> immediate auto-submit or do a multiple submit update using a button.
>
> Assuming the avg user doesn't want to think and its always the pc's
> fault (for they are infallible) I thought it might be an idea to have
> an automatic 'submit' on a changed cell.
> Could also be a textfield (the principle remains the same). Having
> changed it on the client would imply an underwater delta on the server
> (only bothering the user if something went wrong). This is probably
> food for discussion but also OT ;-) .
>
> I'm not sure though whether this is proper Tapestry behaviour.
> Any suggestions are still very welcome.
>
> Fermin DCG
>
> John Meredith wrote:
>
>> Hi,
>>
>> You'd have to use javascript, so that the form is submitted immediately
>> the checkbox changes state ie. onClick or onChange (can't remember off
>> the top of my head).
>>
>> The submitOnChange from PropertySelection would be a good starting point
>> for your new Checkbox component.
>>
>> - John
>>
>> On Wed, 2003-11-26 at 13:28, F. Da Costa Gomez wrote:
>>
>>
>>> Hi,
>>>
>>> What would be the best way to immediately process the onClick /
>>> select action on a checkbox so that it goes to the server right away
>>> to be processed.
>>> Looking at the @Checkbox html code there is no href to use (or at
>>> least not on my page).
>>> Do I 'manually create a href through js or am I missing something
>>> obvious?
>>>
>>> TIA,
>>> Fermin DCG
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [onClick capture] Immediate checkbox processing
Posted by John Meredith <ps...@t-online.de>.
Possibly related, but something I've always thought would make web-apps
more user-friendly would be to persist forms if a user partially or
fully fills in a form (without submission), then side-tracks to another
page before returning to the form (filled in with the previously entered
data). I'm not quite certain how one would go about implementing it
though :-)
- John
On Wed, 2003-11-26 at 15:17, F. Da Costa Gomez wrote:
> Forgot about that, thx.
>
> However, I was/ am looking for a more direct approach to dealing with
> the checkbox or any other <input tag> for that matter.
> The form is encapsulating a TreeTable with an unknown number of branches
> & leafs. So a submit could be quite large.
> Basically I have a choice to make:
> immediate auto-submit or do a multiple submit update using a button.
>
> Assuming the avg user doesn't want to think and its always the pc's
> fault (for they are infallible) I thought it might be an idea to have an
> automatic 'submit' on a changed cell.
> Could also be a textfield (the principle remains the same). Having
> changed it on the client would imply an underwater delta on the server
> (only bothering the user if something went wrong). This is probably food
> for discussion but also OT ;-) .
>
> I'm not sure though whether this is proper Tapestry behaviour.
> Any suggestions are still very welcome.
>
> Fermin DCG
>
> John Meredith wrote:
>
> >Hi,
> >
> >You'd have to use javascript, so that the form is submitted immediately
> >the checkbox changes state ie. onClick or onChange (can't remember off
> >the top of my head).
> >
> >The submitOnChange from PropertySelection would be a good starting point
> >for your new Checkbox component.
> >
> > - John
> >
> >On Wed, 2003-11-26 at 13:28, F. Da Costa Gomez wrote:
> >
> >
> >>Hi,
> >>
> >>What would be the best way to immediately process the onClick / select
> >>action on a checkbox so that it goes to the server right away to be
> >>processed.
> >>Looking at the @Checkbox html code there is no href to use (or at least
> >>not on my page).
> >>Do I 'manually create a href through js or am I missing something obvious?
> >>
> >>TIA,
> >>Fermin DCG
> >>
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> >>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> >>
> >>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
--
John Meredith <ps...@t-online.de>
Re: [onClick capture] Immediate checkbox processing
Posted by "F. Da Costa Gomez" <da...@xsall.nl>.
Forgot about that, thx.
However, I was/ am looking for a more direct approach to dealing with
the checkbox or any other <input tag> for that matter.
The form is encapsulating a TreeTable with an unknown number of branches
& leafs. So a submit could be quite large.
Basically I have a choice to make:
immediate auto-submit or do a multiple submit update using a button.
Assuming the avg user doesn't want to think and its always the pc's
fault (for they are infallible) I thought it might be an idea to have an
automatic 'submit' on a changed cell.
Could also be a textfield (the principle remains the same). Having
changed it on the client would imply an underwater delta on the server
(only bothering the user if something went wrong). This is probably food
for discussion but also OT ;-) .
I'm not sure though whether this is proper Tapestry behaviour.
Any suggestions are still very welcome.
Fermin DCG
John Meredith wrote:
>Hi,
>
>You'd have to use javascript, so that the form is submitted immediately
>the checkbox changes state ie. onClick or onChange (can't remember off
>the top of my head).
>
>The submitOnChange from PropertySelection would be a good starting point
>for your new Checkbox component.
>
> - John
>
>On Wed, 2003-11-26 at 13:28, F. Da Costa Gomez wrote:
>
>
>>Hi,
>>
>>What would be the best way to immediately process the onClick / select
>>action on a checkbox so that it goes to the server right away to be
>>processed.
>>Looking at the @Checkbox html code there is no href to use (or at least
>>not on my page).
>>Do I 'manually create a href through js or am I missing something obvious?
>>
>>TIA,
>>Fermin DCG
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [onClick capture] Immediate checkbox processing
Posted by John Meredith <ps...@t-online.de>.
Hi,
You'd have to use javascript, so that the form is submitted immediately
the checkbox changes state ie. onClick or onChange (can't remember off
the top of my head).
The submitOnChange from PropertySelection would be a good starting point
for your new Checkbox component.
- John
On Wed, 2003-11-26 at 13:28, F. Da Costa Gomez wrote:
> Hi,
>
> What would be the best way to immediately process the onClick / select
> action on a checkbox so that it goes to the server right away to be
> processed.
> Looking at the @Checkbox html code there is no href to use (or at least
> not on my page).
> Do I 'manually create a href through js or am I missing something obvious?
>
> TIA,
> Fermin DCG
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
--
John Meredith <ps...@t-online.de>