Hi Alvaro, thank you for your description and proposal for the widget. I agree with your suggestions. Let me try to summarize your suggestions in a table. I also made some proposals (blue text). Phase Robot List Camera Box Robot Button Button Tooltip or Text box Joystick Start Display All Robots in plain text. Optionally, at start the first Robot is selected, thus this state is the same as next row. Use colour too (Robot status, same as button)? Empty Hidden Hidden Hidden User click a Robot in the list (not yet controlled) The Robot name text becomes bold (means: Video selected). Use colour too (Robot status, same as button)? Show Video from selected Robot Visible, with text "Take Control" and set a color meaning "Robot Available". Show "Not controlled" Hidden User click the Robot button to control it Robot name is still Bold. Use colour too (Robot status, same as button)? Show Video from selected Robot Visible, redirect to a login (if needed) then text change to "Release Control". Colour change meaning "Robot Controlled". Show "Controlled by <user>" Visible User click the Robot button to release it Robot name is still Bold. Use colour too (Robot status, same as button)? Show Video from selected Robot Visible, text change again to "Take Control" and a color change to mean "Robot Available". Show "Not controlled" Hidden User click on another element in the list The selected Robot name text becomes bold (means: Video selected), the previously selected name become plain. Use colour too (Robot status, same as button)? Show Video from newly selected Robot Visible, text and colour depends on current Robot status. Show text depending on robot status Hidden ROBOT LIST and BUTTON COLOUR (Robot Status): Having clickable list or buttons is a choice of interface design but I like the idea of a list to better explain that robots can be N, not just two. My proposal is to apply (optionally) the colour meaning the Robot Status to the elements in the Robot List. This would allow a user to see the status of all robots at a glance, before clicking on them. KURENTO / VIDEO DISPLAY: In this setting, the action of clicking a list also activates the video from that robot and display the robot Button. This avoid having two (or more) camera widgets, and it’s good for me. I guess the simplest solution is having always streams enabled from the two robots, and simply switching between them on the one to display. This implies more traffic from Kurento Media Server (always receiving two streams) but seems more practical for the demo. Another solution might be having only one Robot controlled and transmitting a video at the same time, but I do not like such setting because it will not show the main capability of the platform, e.g. to manage and control multiple robots simultaneously. Moreover, in that case we need to change the video transmission endpoint every time we change the robot controlled. Other solutions, for instance controlling two robots but having only one video at any time, seem even more complex… Please let us know if these proposals are fine for you, if you have different insight or if you need further information from the team. Thank you in advance, Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Álvaro Arranz Inviato: mercoledì 15 luglio 2015 14:44 A: Garino Pierangelo Cc: amagan at conwet.com; fiware-robotics at lists.fi-ware.org; Javier Soriano; Luis López Fernández; fdelavega at fi.upm.es Oggetto: Re: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi Pier, On 7 July 2015 at 16:56, Garino Pierangelo <pierangelo.garino at telecomitalia.it<mailto:pierangelo.garino at telecomitalia.it>> wrote: Dear Alvaro, I have some questions about the widgets and the robotics demo, after the call we had last week, your feedback will surely help me clarifying the related issues. - Is the ‘Joystick’ widget in the pictures above composed of the joystick itself, i.e. is the ‘Spy wiring’ a second widget? The spy wiring widgets is a testing widget ;-). It's not going to be part of the demo :-). - When you propose to put together the camera view, the joystick and the robot buttons, do you mean to have the three of them in the same widget (see first picture below), or are they separate widgets superimposed? In the latter case, I believe that a better layout would be having them separate as layout (see second picture below). First picture: [cid:image001.png at 01D0BFB6.79DD3E40] Second picture: [cid:image002.png at 01D0BFB6.79DD3E40] I was thinking about providing a mockup version of the dashboard, but finally I din't find time. I will try to provide it next week from Mexico (jointly with the document about the interactions user/dashboard/cb). They are going to be separated widgets, although the can be placed overlapped, we can configure them as you wish, it's not a problem. Anyway, My idea is to provide a widget with the list of the robots (and probably an icon with the status of the robot: still, moving, ...) as I think that the idea to promote is that you can have N robots (in the first phase we have 2 real robots) and not two buttons. This list widget will connect to the context broker though a subscription, so if a robot is registered or remove this list will be updated (as well as the status icons of the robots). Regarding the joystick widget, my idea is to hide it until the user clicks on a "Take control" button. This button is the one I was thinking about to place inside the camera widget (and probably also in the robot list widget). Also, this button should be updated taking into account if the current user is anonymous (proposal | label: "Take control", label on hover: "Sign-up"), if the robot is already controlled by another user (proposal: button disabled, label: "Busy", tooltip: "Controlled by <user>" ), and if currently the user is controlling the robot (proposal: label: "Release control"). If the user clicks the "Take control" button, the widget will try to get the lock over the robot and will show the joystick (I think that in this case the widget will be floating over the other widgets, but the user will be able to move it). If the user clicks on the "Release control" or closes the joystick widget, the dashboard will release the lock over the robot and will show again the "Take control" button. What do you think? Thanks in advance for your feedback. BR Pier Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non è necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-robotics/attachments/20150716/a94ba6f7/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 161806 bytes Desc: image001.png URL: <https://lists.fiware.org/private/fiware-robotics/attachments/20150716/a94ba6f7/attachment.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 158123 bytes Desc: image002.png URL: <https://lists.fiware.org/private/fiware-robotics/attachments/20150716/a94ba6f7/attachment-0001.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: <https://lists.fiware.org/private/fiware-robotics/attachments/20150716/a94ba6f7/attachment.jpg>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy