Designers, artists, and/or programmers create your user interface.
Loads output from Quill. Renders graphics and handles input events.
Populate UI data. Listen for changes and events caused by the user.
Composites UI and feeds user input back to the runtime.
Edit your UI and watch changes take effect in real time.
The lightweight runtime doesn't need multithreading. A typical UI will use a small fraction of a single CPU core.
Built in OpenGL, DirectX, and software renderers. Or bring your own.
Design UIs for PC, consoles, and mobile.
Keyframe animations, WYSIWYG, visual data processing, icons fonts, and more.
Avoid performance constraints of dated technologies that weren't meant to be used for modern UX.
Node Based Logic
Use a node system to process data and user input. No coding necessary.
Use a refined system that can drastically reduce development time and code complexity.
Evaluate for Your Game
Something that doesn't take you long to learn when making an application is that gluing together code and UI is tedius, error prone, and incredibly boring. There are a number of common approaches to solving this problem of keeping state synchronized between code and UI: immediate mode architectures, data binding, and good old fashioned spaghetti code to name a few. All these methods come with their with their own sets of pros and cons... »
Creating user interfaces, especially implementing them, is not high on many peoples' list of favorite things to do. Even for designers who enjoy engineering an experience, working with programmers to implement their ideas can be frustrating... »