Hi Greg, I looked into the links the mentioned by you in the previous mail and tried to understand all the parameters related to it. And I have an opinion of the following UI design for capture agents.
> > Hrm, not quite sure what was going on with [1], but it should be up > now... I know we don't have a lot of time before the application > deadline, so why don't you come back with some ideas of how you think > the UI should work. It needs to be able to display the agent's state, > start and stop the capture, list the media that the CA has on disk, and > adjust the parameters listed in the configuration you'll see at [1]. > Ideally the UI should be able to display confidence monitoring > streams/images as well, however I'm not sure of the state of the > confidence monitoring code at the moment; this may not actually work yet :) > > The [1] is working perfectly fine now. According to me, 1. The top of the page should mention about the "Agent Status", whether it is currently streaming or idle (with appropriate font colors or maybe images). 2. As mentioned in [2] section 2, there should be some input box of type 'range' + non-zero constraints + some limit value (limits to browser supporting HTML5 but can be done in jQuery too) frame-rate and bit-rate, depending on the user input, it can start capturing. 3. I'm sorry but I am unable to understand the importance of [3] on the ../capture/ page. If in case it is important to show the logs, we can have a table kind of structure having the important parameters with corresponding green-ticks or red-cross or maybe the some value. 4. As mentioned in [2] section 2, the three parameters number of nanoseconds of data that can be held before frames are dropped ( capture.device.NAME.buffer.time), the number of frames that can be held ( capture.device.NAME.buffer.size), and the size in bytes that should be reserved for holding frames (capture.device.NAME.buffer.bytes) should have input type of range, for user to enter the values. 5. A Start Capture button which starts the capture. and a stop capture button. After hitting the start capture button, the values of previous bit-rates and frame-rates should become only in read-only mode and cannot be altered. 6. The start button should be replaced with some pause button in case one has to pause the video along with a confirmation about one's action. 7. Alerts in case, if the number increases from the parameter given above, then an alert box to say "You have exceeded the limit" type. 8. Also, alerts in case the 'capture agent tries to start a capture but is receiving no signal', or 'if during the video capture the video signal changes'. 9. At the end of the page, a list of media that CA has on the disk in some table like structure listing it. 10. About confidence monitoring, it is different page, right? Or have to integrate in the same page itself? Something like [4] ? Eventually we want to have a user friendly way of adjusting most of the > parameters on the CA's inputs (see > > http://opencast.jira.com/wiki/display/MH/Capture+Agent+Configuration+%28Trunk%29 > , > section 2 for an example and don't worry about what the values actually > mean just yet), so keep that in mind when working on your initial ideas. > Another eventual feature is a embedded version of the page inside the > admin tools (i.e. [2]), although this is very definitely a component > that you don't need to do unless you have lots of extra time. > > We can have an embed HTML code part on the right side of the actual video or an extra column in the table while listing the videos saying "Embed", when as soon as one clicks it, the HTML code get copied on his clipboard using http://code.google.com/p/zeroclipboard/ perhaps. Once you have some ideas then I think you need to put in a formal > application through GSoC. I can help proofread and whatnot for that so > feel free to send things to me if you want help. Don't put too much > time into thinking about your designs yet: You aren't guaranteed to be > accepted! A strong idea of what you want to do will, however, help when > you write the 500 word 'Why are you perfect for this project' essay :) > > G > > Please let me know, if I'm going on the right track with this. What would be my next step? Should I go about documenting a formal application for this project? Please let me know. Thanks for your kind support. [1]: http://testca.usask.ca:8080/welcome.html [2]: http://opencast.jira.com/wiki/display/MH/Capture+Agent+Configuration+%28Trunk%29 , [3]: http://paste.ubuntu.com/902558/ [4]: http://opencast.jira.com/wiki/display/MH/Confidence+Monitoring -- Regards, Chitesh T.
_______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
