-
Notifications
You must be signed in to change notification settings - Fork 6
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
Can the homescreen & navbar buttons be rewritten using the new Sun.buttons? #159
Comments
Did @jonathanolson do any work on this in scenery/02? I have a vague recollection about something similar. |
This relates somewhat to phetsims/sun#94 (comment) |
Which might have already been merged back? Were the navbar buttons possible to write with Sun.button? |
I asked if the navbar scene selection buttons could be implemented with RadioButtonGroup here: phetsims/sun#127 We still need to address the other joist buttons though. And I thought we backported the ohtwo work you did to joist/01. |
Fixing this issue may help with #160 |
In phetsims/sun#94 @pixelzoom proposed that @pixelzoom work on this. |
Here is @pixelzoom comment from phetsims/sun#94
Note that the Home and PhET buttons are two of the buttons that should be rewritten to use sun. We could also implement the "screen" icons that appear on the homescreen and in the navbar. |
There's no reason to rewrite the home screen and navbar using sun push buttons if RadioButtonGroup is going to handle it (see phetsims/sun#127). Which approach are we taking? |
As a result of #170, PhetButton and HomeButton now use sun.NodesPushButton. The navbar and home screen are still rolling their own buttons: |
Tackling the home screen and navbar screen icons is going to be a lot of work, more than I have time for. And both the home screen and navbar could benefit from a thorough cleanup. So I'm going to unassign this. If someone else wants to tackle this, go for it. |
Duplicate of #183, closing. |
Can the homescreen & navbar buttons be rewritten using the new Sun.buttons?
The text was updated successfully, but these errors were encountered: