[Tickets #6293] By client 'submit all' multiple checkbox selection.
bugs at horde.org
bugs at horde.org
Tue Feb 19 20:12:47 UTC 2008
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/?id=6293
-----------------------------------------------------------------------
Ticket | 6293
Created By | kyrian at ore.org
Summary | By client 'submit all' multiple checkbox selection.
Queue | Hermes
Type | Enhancement
State | New
Priority | 2. Medium
Milestone |
Patch |
Owners |
-----------------------------------------------------------------------
kyrian at ore.org (2008-02-19 15:12) wrote:
Hi,
I've spent so long scrolling through the timeslice list in Hermes that I
thought I would try and fix it myself, but I couldn't work out where to
look/edit when I did. It looks like a Horde_UI function generates these
things, though...?
Anyways, the gist is that when submitting timeslices, I find that I more
often than not want to submit all timeslices for client X, but none from
the others, and in those cases where there are many clients and 10's of
checkboxes per-client, it gets very time consuming.
That leads in the direction of having an 'X' or other icon that uses
javascript/DHTML to select/unselect all timeslices by a given client to
speed this process up significantly, and reduce strain on the eyes/brain.
It would be cool if this could be implemented. I'll do it myself and
submit a patch if I can get some pointers as to where to look in the code
for what generates that menu.
Either way, the gist would be to get each checkbox assigned as eg.
id="check_[clientid]_[itemsequence]" (where 'itemsequence' is incrememented
from 0 or 1 for each one in the sequence for that client) and loop through
them with javascript with an 'onclick' for the new button and check/uncheck
all that begin with "check_[clientid]_"...
Apologies if that's teaching the proverbial grandmother to suck eggs, of
course.
K.
More information about the bugs
mailing list