Sample Code needs DataBinding

[najak3d]

Your Sample project (modern style, Toon Style, etc) -- only shows controls, but no Data Binding of any sort.

As such, currently, I'm trying to figure out how to do the following simple action:

1. Pop up a Text Entry prompt (e.g. "Save Scene AS..." with text entry for the scene name, user edited).
2. Know when user has hit "Enter" key - which signifies "Done".

There are several scripts inside "ScrollableTextField" with a "Text" property. I've tried setting events for "OnTextChanged()" on a couple of these, but neither is firing events as I type....

So it leaves me "guessing" on how to do very basic things - like reading a Text Field, because your sample code does none of this.

Please make there be some sort of Data Model behind your Sample UI's, to demonstrate two-way bindings of various sorts.

[najak3d]

As I thought more about this during my sleep (I do that) - I believe the best example code would be in the form of a Mini-App. The current samples are good for showcasing the UI styles/presentations, in various modes. But a Mini-Game/App would then allow you to show more interactions with an app.

Things the mini-app would demo:

1. Main Menu - which launches the game, maybe lets you enter your Name.
2. Settings Menu - lets you set various settings (which should have a backing Model, but otherwise can be fake / unused in the game)
3. Main Game UI - including a HUD/mini-map, action icons, Popup Menu/form, Score/Status bar at top, etc.
4. Health Bars
5. World-space UI labels, that follow a 3D entity. (name, health, status)
6. Wheel Selection menu, perhaps.

The game can suck entirely, but it would still demonstrate various methods for integrating NovaUI into a game.

[najak3d]

Also to note, I got this working fine this morning. The TextInput script seems to be the best entry point.

But my detection of "Enter" key is kludgy. I see other places in NovaUI where a better hook might exist, such as "OnSubmit" for the KeyboardInput script. But it seems to me that "TextInput" should have it's own "OnSubmit" event.

I don't generally like "coming up with what works" when it comes to things like this, as "whatever I figure out" is usually non-optimum, and would much prefer to see a Sample Project where "best practices" are shown from the start, and I just copy the techniques.