|
Type:
|
Enhancement
|
|
Priority:
|
Low
|
|
Severity:
|
Trivial
|
|
Status:
|
Unassigned
|
|
Resolution:
|
Unresolved
|
|
Resources:
|
Nobody
|
|
Reported By:
|
Bob Denny
|
|
Component:
|
Desktop Browser Help Content, RTML 2.3 .NET Assembly, VOEvent Alerter, VOEvent Receiver, Web Schedule Browser
|
|
Versions Affected:
|
3.3
|
|
Start Date:
|
?
|
| Created: |
9/8/2011 12:44:39 PM |
| Revised: |
9/8/2011 12:54:51 PM
|
|
Structural reorganization of RTML. Move constraints down to the Target level, leaving only Priority and TimeRange (not the TimeRange constraint!) where they are under Schedule. There is a work in progress RTML 3 already under RTML23/Schema in the Scheduler project tree. The Krajci TimeRange constraint can be called TimeLimits as an RTML Target level constraint to separate it from the TimeRange that is at the Schedule level. Also provide for the (separate) ACP username (now handled by the [ACP User=xxxx] hack, as well as other hacks currently described in help under RTML Mapping. Remove some unneeded image calibration modes. This will percolate all over the place.
|
|
|
Links |
|
SCHEDULER-379
|
|
Add TimeRange controls to new web forms
|
Grouped
|
|
|
|
|
|
|
|
|
Are you sure that you want to reset the votes?