-
Notifications
You must be signed in to change notification settings - Fork 780
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
UI Picker / Text Field Updates #244
Comments
That would be a huge feature, but an awesome one! An We just have to do it starting now 😬 Before going with the real deal (custom picker), we can start bt abstracting the native picker (support for designable, and animatable). We can take inspiration from ActionSheetPicker-3.0. We can also directly start with a custom one, both are worth it 👊 |
Once I get some free time this weekend I will do the generic Animatable / Designable Picker and make a PR unless someone beats me to it. I already have a base skeleton for something I was calling UIPicker that effectively serves the exact same purpose. |
Here's one article regarding clock input:
http://uxmovement.com/forms/why-a-clock-widget-is-easier-for-picking-time/
I would love to see this as an alternative to date picker. I'm thinking since it depends on a base clock graph, a generic graphing library base (bar, line, pie chart, etc) might be necessary to round out a pull request for it. Furthermore, it then becomes a question of how we display the clock in an iPhone vs iPad-type scenario. As well as localization settings for 12 vs 24 hour clock with optional user settings to always show Date Picker versus Clock.
Another regarding text fields:
http://uxmovement.com/forms/a-stronger-visual-cue-for-text-fields/
If we did the text field addition for general "focused" element/view effects, this could be combined with a blur or #243 potentially.
Also, while are talking about pickers: https://github.com/ipraba/EPContactsPicker
That should be an addition as well. But this starts opening up a can of worms since an image picker is next (or first).
Just some thoughts.
The text was updated successfully, but these errors were encountered: