Why No TextInput Primitive?
See original GitHub issueI’ve seen some light discussion on why TextInput
may or may not make sense as a primitive. Mostly in this issue.
I too believe that text inputs are a core feature of building complex, rich, interactive UIs. I would like to start a more in-depth discussion on what it would take to add such interactive elements to the core API. Or, to see more insight as to the hesitation against such a move.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:4
- Comments:14 (2 by maintainers)
Top Results From Across the Web
Check if input is of Primitive type in Java? - Stack Overflow
An instance of Short (etc) is not primitive: it is an instance of the wrapper type, so input.getClass().isPrimitive() won't ever return true.
Read more >GLSL failed to link and error C6022: No input primitive type
I am a rookie and just trying something randomly. I create an solid wing in solidworks and imported into Hypermesh(11.0).
Read more >Input/Output primitives of TeX - LaTeX Stack Exchange
The \read primitive reads one line at a time (unless braces are not matched) and tokenizes in the normal TeX way.
Read more >Primitive text - WinCC OA
Figure 1 . Primitive text HOW To write primitive text First you have to decide whether the primitive text should have a border...
Read more >Primitive input/output | R Object-oriented Programming
There are a number of primitive commands that offer fine grain control for reading and writing information to and from a file. We...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Perhaps
Touchable
should be generalized toInput
since it is also responding to a form of input.TextInput
implies input from a keyboard. If we had a generalInput
primitive it could be bound to different input types, like mouse, touch, keyboard, gyroscope, location, etc.Might be worth listing it in the Readme alongside
react-primitives
svg`