[Proto-Scripty] Tactical Advice: Many rows, one checkbox per row

2012-04-25 Thread Phil Petree
Hey All, My need is to create a easy approval process for what could be a handful of subscribers up to 1000's of subscribers. The idea thus far is to create a table that has (and needs) only a few columns of information: RecordID (hidden) | Approved [checkbox] | Subscriber Name (read_only

RE: [Proto-Scripty] Tactical Advice: Many rows, one checkbox per row

2012-04-25 Thread Brian Marquis
Why not get rid of the hidden field and assign the record id as the value of the checkboxes. When you submit the form (or serialize it) only the checked items will be passed to the server. For example: input name=ApprovedSubscribers value=123 type=checkbox checked=checked/ Joe Cool input

Re: [Proto-Scripty] Tactical Advice: Many rows, one checkbox per row

2012-04-25 Thread Phil Petree
Funny, I had just figured out what you had suggested for getting rid of the hidden field and making the record id the value. The problem is that ONLY the checked items get passed... if someone is unchecked their approval is revoked so I need to update the table for that as well. On Wed, Apr 25,

RE: [Proto-Scripty] Tactical Advice: Many rows, one checkbox per row

2012-04-25 Thread Brian Marquis
Yes, that's the nature of checkboxes and radio buttons. If you need the value submitted in all circumstances, then you're back to the hidden field implementation. Problem with that approach is that it won't work if the user has javascript disabled. A few options for event listeners

Re: [Proto-Scripty] Tactical Advice: Many rows, one checkbox per row

2012-04-25 Thread Phil Petree
I'm now wondering if the onchange event will allow me to set the value of the hidden field BEFORE the form.observer fires the ajax call I'll test that tomorrow... My thinking is that I'll set the value of a hidden field to on/off and the name of the field to the record #. On Wed, Apr 25, 2012