Hi Pier, On 7 July 2015 at 16:56, Garino Pierangelo < 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: > > > > Second picture: > > > 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 > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-robotics/attachments/20150715/869ab2bd/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 158123 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-robotics/attachments/20150715/869ab2bd/attachment.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 161806 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-robotics/attachments/20150715/869ab2bd/attachment-0001.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 68500 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-robotics/attachments/20150715/869ab2bd/attachment-0002.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image012.png Type: image/png Size: 85361 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-robotics/attachments/20150715/869ab2bd/attachment-0003.png>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy