aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "zoe slattery (JIRA)" <>
Subject [jira] Assigned: (ARIES-303) Improvements to prototype graphical console
Date Mon, 10 May 2010 07:11:48 GMT


zoe slattery reassigned ARIES-303:

    Assignee: zoe slattery

> Improvements to prototype graphical console
> -------------------------------------------
>                 Key: ARIES-303
>                 URL:
>             Project: Aries
>          Issue Type: Improvement
>          Components: Samples
>            Reporter: Holly Cummins
>            Assignee: zoe slattery
>            Priority: Minor
>         Attachments: aries303-1.txt
> Ultimately there are two use cases for the console; the first is as a dynamic replacement
for the power point pictures we use in demos to illustrate the architecture of the blog sample,
and the second is as a management console. We'll want different things in the two scenarios
- in general, we'll want a lot of abstraction when we're using the console to illustrate what's
happening in a demo, but using the console to debug or manage a proper system would need much
more detail. For example, we may not want to show the bundle IDs for a demo, and we may want
to programatically filter out bundles which aren't part of the blog sample. I think a good
way to achieve these two modes is to provide a customisable set of preferences, and we can
ship with two default modes, 'abstract' and 'diagnosis' (say). We could use a different URL
pattern to swap between the modes, and also allow users to customise the preferences files
to create hybrid modes.
> I've taken a step towards this by allowing some of what's shown to be turned off and
moving the control for that switch into a separate javascript file. The next steps will be
to externalise it to a user-editable file, possibly in combination with a set of controls
in the GUI and cookie persistence. 
> I've also added a visual representation of the bundle state, so that bundles which aren't
active are greyed out. At the moment they go a slightly bilious yellow when they're not active,
but we can fine tune the colours as we go. :)
>  (Depending on the preferences setting, we can show the state as a text string, use the
visualization, or do both.)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message