NYCPHP Meetup

[Cliff Hirsch]

Actually, I already do this, and use a similar UI to PHPAdmin --
checkboxes for global button actions and individual buttons for single
row actions. Hard to beat it's UI, other than a lot of clutter.

The difference is PHPAdmin uses Hyperlinks and I'm leaning towards
submit buttons. But than again, I'm a bit of a stickler for protocol.
Ok...rigid...

Although, if the Action requires an authenticated user, I'm still not
sure I understand where the risk is.

 
-----Original Message-----
From: talk-bounces at lists.nyphp.org [mailto:talk-bounces at lists.nyphp.org]
On Behalf Of billy reisinger
Sent: Monday, November 21, 2005 5:15 PM
To: NYPHP Talk
Subject: Re: [nycphp-talk] Preferred method for parsing
multi-rowsubmitbuttons


I'm not sure exactly what you are trying to do, so this may not apply to
you.  I'll throw it out there anyway:  If you have many things on one
page that a user could edit or delete, it may be easier for the user if
you provide them with a way of doing them all at once.  In other words,
use a toggle next to each item (a select widget, radio button, whatever)
and have a "Edit Selected" or "Delete Selected' button at the top and
bottom of the list.  PHPMyAdmin does this too, and I agree, it is a
great peice of software.  Just a thought! Cheers

--
Billy Reisinger
billy.reisinger at gmail.com
410.736.0148

On 11/21/05, Daniel Krook <krook at us.ibm.com> wrote:
> > > <input type="submit" name="submit[$row_id]" value="Edit"/> <input 
> > > type="submit" name="submit[$row_id]" value="Del"/>
> >
> > Seems like this would be better as hyperlinks rather than forms.
> >
> > --Dan
> ...
> > I thought of that, and again, it sure would be much
> > easier. But doesn't
> > that violate the W3C recommendation for get versus post. Isn't a 
> > Hyperlink simulating a get submission, which should not be used for 
> > "actions" that modify a database.
>
> Yep, in theory GET requests should be side-effect free, so the 
> instinct is not to use links... If only for one lesson learned the 
> hard way... What if a spider or recursive wget hits this page (and all

> you have to stop the requests for the normal user are JavaScript 
> confirms)?
>
>
>
>
>
>
>
> Daniel Krook, Content Tools Developer
> Global Production Services - Tools, ibm.com
>
> http://bluepages.redirect.webahead.ibm.com/
> http://blogpages.redirect.webahead.ibm.com/
> http://bookmarks.redirect.webahead.ibm.com/
>
> _______________________________________________
> New York PHP Talk Mailing List
> AMP Technology
> Supporting Apache, MySQL and PHP 
> http://lists.nyphp.org/mailman/listinfo/talk
> http://www.nyphp.org
>
_______________________________________________
New York PHP Talk Mailing List
AMP Technology
Supporting Apache, MySQL and PHP
http://lists.nyphp.org/mailman/listinfo/talk
http://www.nyphp.org