| Summary | By client 'submit all' multiple checkbox selection. |
| Queue | Hermes |
| Type | Enhancement |
| State | Rejected |
| Priority | 2. Medium |
| Owners | |
| Requester | kyrian (at) ore (dot) org |
| Created | 02/19/2008 (6300 days ago) |
| Due | |
| Updated | 02/21/2008 (6298 days ago) |
| Assigned | |
| Resolved | 02/20/2008 (6299 days ago) |
| Milestone | |
| Patch | No |
New Attachment: hermes-help.xml
on adding some docs to Hermes in order to show my appreciation for
the system? :-)
start on this with a few topics I thought were important which I've
attached.
State ⇒ Rejected
on adding some docs to Hermes in order to show my appreciation for
the system? :-)
then submit all?
little more 'clunky' than I imagined, but it'll certainly do the job.
Please excuse my laziness and/or stupidity.
Perhaps this ticket should be closed, and I should focus my attention
on adding some docs to Hermes in order to show my appreciation for the
system? :-)
Having a quick look at IMP's docs, the XML format looks simple enough,
all I need to do is find an XML editor.
State ⇒ Feedback
then submit all?
Priority ⇒ 2. Medium
Type ⇒ Enhancement
Summary ⇒ By client 'submit all' multiple checkbox selection.
Queue ⇒ Hermes
State ⇒ New
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.