Thanks guys,
Infact when I l looked at the rest endpoint it seemed the logical an
minimalist place to fix was in the CaptureAgentStateService. All that
was required was changing the map to agent state is stored in to a TreeMap.
I'll attach a patch to the Jira ...
D
On 10/05/2011 07:33 PM, Christopher Brooks wrote:
I think either would work imo, so whichever way you would prefer to
patch is fine...
Chris
On Wed, 05 Oct 2011 16:29:47 +0200
David Horwitz<[email protected]> wrote:
Hi All,
Looking to fix a small but annoying bug:
http://opencast.jira.com/browse/MH-8176
That the list of capture agents in the "schedule recording" form are
randomly ordered. There seem to be two possible points where this
could be fixed and was wondering which would be the best and fit with
Matterhorn practices.
1) make the rest endpoint capture-admin/agents.xml/json return a list
ordered by capture name
2) make oc.scheduler.js sched.handleAgentList sort the returned list
I lean towards 1 as it will also mean that by default the capture
agents list will be alpha ordered (and my java skills are better than
my js ones!), but am unsure if that may have implications elsewhere.
thanks
D
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
