First of all, there are huge technical limitations as to why we only offer two text input methods. This isn’t going to change any time soon. As far as other widgets, we decided to just do the core widgets that are needed (buttons, switches, sliders and so on). If you need a widget we don’t support you can:
-
Build it yourself (and of course share it with the community if you want)
-
Put in a feature request at http://feedback.coronalabs.com
-
If you want to change how one of our widgets works, you can download the Lua source from them from our GitHub repo at: https://github.com/coronalabs/framework-widget and modify them to your needs.
If you want to change how one of our widgets works like a slider, they are completely skinable. Instead of a circular slider, make it a shield or a fireball.
The native.newTextField() has plenty of control too. It still has to sit on top of everything, but it can be inserted into groups for easy moving around. It can be made invisible and you can put it on top of any design that you want. We did a tutorial on making a widget.newTextField() that takes you through this skinning process. This is basically what the widget library above does. It wraps their skinning around native.newTextField().
I don’t believe it’s being maintained, but the code was in pretty good shape I think. We of course can’t provide support for it.
Rob