Skip to content
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

Next-generation version of NumberDisplay is needed. #828

Open
pixelzoom opened this issue Dec 18, 2023 · 1 comment
Open

Next-generation version of NumberDisplay is needed. #828

pixelzoom opened this issue Dec 18, 2023 · 1 comment

Comments

@pixelzoom
Copy link
Contributor

pixelzoom commented Dec 18, 2023

NumberDisplay has reached its end of life. It is not a good fit for the current PhET feature set, especially dynamic strings.

As I commented in #824:

What is really needed is a next-generation NumberDisplay, with an API that is better suited to displaying a string that is derived from a TReadOnlyProperty<number | null> and other dependencies (like translated strings, preferences, etc.)

NumberDisplay is a widely-used UI component (43 imports across the PhET code base), so it seems like this should be relatively high priority.

@pixelzoom
Copy link
Contributor Author

1/4/24 dev meeting summary:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant