-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide Thymio-specific connection dialogue #694
Comments
The idea of using categories is interesting, but complicates too much the generic Aseba GUI, as there might be a lot of different categories of robots. If the combination of the current generic GUI and the single connection to the first Thymio is not enough, I suggest to make a Thymio-specific dialogue within the Thymio launcher. That would also filter out things such as Bluetooth ports, etc. |
I like the idea. It might also be more clever to do that in a more specific Thymio part such as the Thymio launcher instead of the generic Aseba launcher. |
I've changed the title to reflect our discussion. |
Just to come back at the original discussion two generic categories could be "local" (local robot connected), and "on network", and put alos robot of local simulator in first category |
It is indeed a good idea to resolve the hostname and see if it is on the machine. I implemented this feature in commit c010fd9. |
I'm closing this in favour of #728, a launcher-specific issue. |
I find this new connection interface pretty neat! :))
I am just afraid it might be a bit technical for teachers in terms of which is which. Differentiate the local simulated robots from the USB or Wireless ones is easy when technical data such as "local serial port" doesn't scare you

My only criticism would be that we could have a more user friendly GUI like with buttons or anything.
I made a quick drawing, more explicit than words. It's ugly, but you will get the jizz.
What do you think? This could become a wish.
The text was updated successfully, but these errors were encountered: