25 | | == Form Controls and Input == |
---|
26 | | But wait, there's more: you also get access to a full form controls widget set - input fields, text areas, slider bars, drop down lists, as well as the new dynamic data displays, datagrids. All with full source! We've also taken care of all your Drag and Drop needs with element dragging built right into the core. |
---|
| 25 | == Form controls and input == |
---|
| 26 | But wait, there's more: you also get access to a full form controls widget set - input fields, text areas, slider bars, drop down lists, as well as the new dynamic data displays, data grids. All with full source! |
---|
33 | | == Dynamic Data Representation (Model, View, Controller) == |
---|
34 | | One of the key parts of any UI is displaying dynamic data - main menus are all well enough but the real test of a UI is how well it can handle the lobby screens, the inventory screens, and the level select screens. libRocket comes with a powerful collection of classes to detach the data from the output. Data is fetched from a data source, passed through a data formatter, then finally displayed in a datagrid which includes full support for tree-like structures, like Windows Explorer.[[br]] |
---|
| 33 | == Dynamic data representation (model, view, controller) == |
---|
| 34 | One of the key parts of any UI is displaying dynamic data - main menus are all well enough, but the real test of a UI is how well it can handle the lobby screens, the inventory screens, and the level select screens. libRocket comes with a powerful collection of classes to detach the data from the output. Data is fetched from a data source, passed through a data formatter, then finally displayed in a data grid which includes full support for tree-like structures, like Windows Explorer.[[br]] |
---|
50 | | libRocket doesn't do exactly what you want it to do? No problem! We've bent over backwards to open it up to modification by adding own custom interfaces to it. You can: |
---|
51 | | - set your own log, file, render and system interfaces. |
---|
52 | | - define custom decorators, to display anything you like. For example, the starfield in the demo application, Rocket Invaders from Mars, was a custom decorator. |
---|
53 | | - define custom elements, with their own behaviour, events and display. |
---|
54 | | - add extra features to the XML parser, to make it do whatever you want it do. |
---|
| 50 | libRocket doesn't do exactly what you want it to do? No problem! We've bent over backwards to open it up to modification by adding customisable interfaces to it. You can: |
---|
| 51 | - Set your own log, file, render and system interfaces. |
---|
| 52 | - Define custom decorators to display anything you like. For example, the starfield in the demo application, Rocket Invaders from Mars, is a custom decorator. |
---|
| 53 | - Define custom elements with their own behaviour, events and display. |
---|
| 54 | - Add extra features to the XML parser to make it do whatever you want it do. |
---|