Closed GoogleCodeExporter closed 9 years ago
Original comment by kkragenb...@gmail.com
on 13 Dec 2010 at 11:22
Looking at doing this there is a need for three or four corresponding lists of
status:
1. What you type when setting status or using +jobs/select status (e.g., HOLD,
25, etc.)
2. What you see when setting status (e.g., ON HOLD, 1/4 COMPLETE, etc.)
(optional, could use #4 below)
3. What is displayed in the 8-char job listing (e.g., --HOLD--, 1/4 DONE)
4. What is displayed in reports (e.g., On Hold, 25%, etc.)
Two ways to implement this, need preferences of users:
1. Attribute lists such as:
&JOBSTATUSLIST VA=HOLD NEW UNDERWAY ....
&JOBSTATUSDISPLAY VA=--HOLD--|NEW|UNDERWAY|1/4 DONE ....
&JOBSTATUSREPORT VA=On Hold|New|Underway ....
or
2. One attribute per status with the 3 names:
&JOBSTATUS_1 VA=HOLD|--HOLD--|On Hold
&JOBSTATUS_2 VA=NEW|NEW|New
etc.
Discuss.
Original comment by widdis@gmail.com
on 13 Jan 2011 at 12:21
Do we really need to maintain all the different versions? That seems a little
wacky, to me. That said, the grouped method (second one) is better, but the
attrnaming gives me a headache. We're already using CMD_ for the attributes on
the JGO, why not use STATUS_ for these attributes. E.g.:
&STATUS_0 VA=--HOLD--|On Hold
&STATUS_1 VA=NEW|New
&STATUS_2 VA=UNDERWAY|Underway
Original comment by kkragenb...@gmail.com
on 26 Jan 2011 at 8:50
Status_# it is. And I'll figure out something to only need 2 entries.
Original comment by widdis@gmail.com
on 26 Jan 2011 at 8:53
Speaking of "a little wacky" look at the interaction between REPORT_STATUS and
MAP_STAT_STATUS. That's getting a complete rewrite.
Original comment by widdis@gmail.com
on 27 Jan 2011 at 7:45
Done in r394.
Original comment by widdis@gmail.com
on 13 Feb 2011 at 7:40
Original issue reported on code.google.com by
kkragenb...@gmail.com
on 13 Dec 2010 at 11:17