[
http://opencast.jira.com/browse/MH-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=29233#comment-29233
]
Judy Stern edited comment on MH-8469 at 2/7/12 6:43 PM:
--------------------------------------------------------
Hi, Kenneth.
> Can you please clarify what you meant by "follow style used elsewhere in the
> UI (i.e. don't use heads for each selection element, instead just label it)
> "?
Compare "Video Input Type" as in my mockup vs. the way it appears in
Screenshot-3.2.png. If you go to any form (e.g. click the Schedule Recording
or Upload Recording buttons on the Recordings tab) you'll see how all user
inputs have right-aligned labels (with colons); the corresponding input field
or selection element(s) is directly to the right (not below) of the label. I
realize we don't have other stacked sets of elements (e.g. radio buttons each
on their own line) but the pattern still applies (again, refer to my mockup)
>Also, where do you want gstreamer Command and Temporary Output Files Paths to
>show up when you click on the "Show Command" and "Show Paths" links?
In my mockup (second screen), I put the field for Show Command directly below
it. I realize that I forgot to show the "Show Paths" link below the Command
field (i.e. it gets pushed down). I'll try to add that soon.
> point me to other pages where similar UI elements have been used so that my
> change will be consistent! Thanks a lot!
And thank you for being sensitive to issues of consistency!
Schedule, Upload, Review/Trim hold state, Edit Series are the other places
(forms) where user input is required. You're breaking new ground here, though,
in that we don't have other forms with editable fields we want to hide and
show on the page itself, and I'm not wedded to the way I've done it (was just
one idea) so I welcome alternative ideas on this. The important thing here is
that we need an "Extras on Demand" type of interaction (see
http://www.designinginterfaces.com/firstedition/index.php?page=Extras_On_Demand)
was (Author: judy):
Hi, Kenneth.
> Can you please clarify what you meant by "follow style used elsewhere in the
> UI (i.e. don't use heads for each selection element, instead just label it)
> "?
Compare "Video Input Type" as in my mockup vs. the way it appears in
Screenshot-3.2.png. If you go to any form (e.g. click the Schedule Recording
or Upload Recording buttons on the Recordings tab) you'll see how all user
inputs have right-aligned labels (with colons); the corresponding input field
or selection element(s) is directly to the right (not below) of the label. I
realize we don't have other stacked sets of elements (e.g. radio buttons each
on their own line) but the pattern still applies (again, refer to my mockup)
>Also, where do you want gstreamer Command and Temporary Output Files Paths to
>show up when you click on the "Show Command" and "Show Paths" links?
In my mockup (second screen), I put the field for Show Command directly below
it. I realize that I forgot to show the "Show Paths" link below the Command
field (i.e. it gets pushed down). I'll try to add that soon.
> point me to other pages where similar UI elements have been used so that my
> change will be consistent! Thanks a lot!
And thank you for being sensitive to issues of consistency!
Schedule, Upload, Review/Trim hold state, Edit Series are the other places
(forms) where user input is required. You're breaking new ground here, though,
in that we don't have other forms with editable fields we want to hide and
show on the page itself, and I'm not wedded to the way I've done it (was just
one idea) so I welcome alternative ideas on this. The important thing here is
that we need an "Extras on Demand" type of interaction (see
http://quince.infragistics.com/Patterns/Extras on Demand.aspx)
> Review of UI
> ------------
>
> Key: MH-8469
> URL: http://opencast.jira.com/browse/MH-8469
> Project: Matterhorn Project
> Issue Type: Sub-Task
> Components: Administrative Tools
> Affects Versions: 1.4
> Reporter: Christopher Brooks
> Assignee: Judy Stern
> Fix For: 1.4
>
> Attachments: Screenshot-1.2.png, Screenshot-2.2.png,
> Screenshot-3.2.png, Screenshot-4.2.png
>
>
> Here are some screenshots of the current ui. The first screen shows the drop
> down box where you choose a workflow. So "export to downloadable media" can
> be done on either files that are uploaded or on the inbox. (Ignore the new
> radio button "Archived media package", that's going away).
> The second screen shows the admin console, note that the status is "on hold"
> and that there is an action to "Configure Export"
> The third screen is technical. The top three radio groups identify different
> input parameters, sources, and output resolutions that can be dealt with. As
> these are manipulated, the actual command that is run on the server is shown
> in the text box below. This command can be modified by the admin if they
> feel knowledgeable enough to do so. The text box at the bottom is a list of
> where files will be processed on the drive. (This might not be necessary?
> Can't we just configure this in the workflow file and leave it out of the
> admin ui?)
> The fourth screen shows that the pipeline has started processing. (Bug: why
> does it say "On hold" at the beginning still?)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://opencast.jira.com/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
