[drupal-devel] [feature] Check All | None on Content List Page (admin/node)

[factoryjoe]

Issue status update for http://drupal.org/node/20641

 Project:      Drupal
 Version:      cvs
 Component:    node.module
 Category:     feature requests
 Priority:     normal
 Assigned to:  Anonymous
 Reported by:  jjeff
 Updated by:   factoryjoe
 Status:       patch

Bookmarklets are not a viable solution when viewing a site on
kiosk/school web browser. +1 for this functionality, but I really think
that these scripts belong in a drupal utility.js file, similar to Rails'
prototype.js [1] file.


It also seems to me that there needs to be a bit more logic about where
this kind of "check all" | "deselect all" link shows up. As it is, I
couldn't tell if it gets added to the table header, footer, or shows up
after... I think tossing it in the admin UI makes good sense for now,
but I imagine that this would also be useful in more user-facing UIs.
[1]
http://dev.rubyonrails.com/file/trunk/actionpack/lib/action_view/helpers/javascripts/prototype.js




factoryjoe



Previous comments:
------------------------------------------------------------------------

April 16, 2005 - 17:53 : jjeff

Attachment: http://drupal.org/files/issues/node_module_check_all.patch (1.23 KB)

>From the "what a great time-saver" department:


Here is a short patch to node.module that adds a "Check all | none"
javascript link to the bottom of the content listing table on
admin/node. By clicking "all" or "none" you can select or deselect all
of the check boxes in the table at once.


The javascript is very non-invasive, should work older (non-DOM)
browsers, and non-javascript browsers will simply lose this function.


The patch also adds the attribute [name = "node-admin"] to the [form]
tag. I don't know if there is a form naming convention, but this was
the best guess I could come up with by looking at the page source. And
incidentally, if Drupal is going to move toward javascript/ajax
functioning, all forms are going to need 'name' and 'id' tags. Most
don't have these now.


-Jeff




------------------------------------------------------------------------

April 21, 2005 - 18:49 : Bèr Kessels

-1. Its up to the client to provide such interface tricks. Most clients
can do this with bookmarklets already.




------------------------------------------------------------------------

April 22, 2005 - 12:02 : Junyor

How would you propose that a client implement this?  As of now, there's
no common attribute that the client could use to determine that the
checkboxes are related.  Theoretically, it could be done if the
checkboxes shared a common name.  But what would the UI look like?


My point is, no UA has implemented this and there's a working solution
used throughout the Web.  Let's use that solution.




------------------------------------------------------------------------

April 22, 2005 - 13:00 : Bèr Kessels

http://www.squarefree.com/bookmarklets/forms.html is the one you are
looking for. See "Toggle checkboxes".




------------------------------------------------------------------------

April 22, 2005 - 13:05 : Junyor

Checking all checkboxes on a page is not a viable solution for most
cases (though it may work here).




------------------------------------------------------------------------

April 22, 2005 - 13:29 : moshe weitzman

It is silly to require users to install bookmarklets from 3rd party web
sites in order to easily use our pages. Every web mail application I've
used provides a 'check all' feature. This is not a "client hack". It is
ECMAscript, which is a web standard.  +1