Changes between Version 15 and Version 16 of frontend/features

Show
Ignore:
Author:
peterc (IP: 192.168.0.1)
Timestamp:
01/07/08 20:55:12 (10 years ago)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • frontend/features

    v15 v16  
    1616[[Image(template.gif, nolink, align="left")]] 
    1717== Templating == 
    18 libRocket comes with a powerful templating tool. You can define key elements, such as windows, then re-use these throughout the project. If you want to make a change to the window, change it in one place and every window will reflect the change. 
     18libRocket comes with a powerful templating tool. You define key elements, such as windows, then re-use these throughout the project. If you want to make a global change to the window, change it in one place and every window will reflect the change. 
    1919{{{ 
    2020#!html 
    2323 
    2424[[Image(form.gif, nolink, align="left")]] 
    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 == 
     26But 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! 
    2727{{{ 
    2828#!html 
    3131 
    3232[[Image(datagrids.gif, nolink, align="left")]] 
    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) == 
     34One 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]] 
    3535{{{ 
    3636#!html 
    3939 
    4040[[Image(scripting.gif, nolink, align="left")]] 
    41 == Tight scripting Integration == 
    42 The lightweight python plugin exposes all of rockets core features and DOM to the python programmer. The python interface has been modeled around javascript for simplicity and can be used to manipulate any part of a document in real time. Whole games can be written in python once the rocket framework is initialised. 
     41== Tight scripting integration == 
     42The lightweight Python plugin exposes all of Rocket's core features and DOM to the Python programmer. The Python interface has been modeled around Javascript for simplicity and familiarity, and can be used to manipulate any part of a document in real time. Whole games can be written in Python once the Rocket framework is initialised. 
    4343{{{ 
    4444#!html 
    4848== Extensibility == 
    4949 
    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. 
     50libRocket 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. 
    5555 
    5656== Debugger == 
    5757 
    5858[[Image(debugger.gif, nolink, align="right")]] 
    59 libRocket also comes with its own visual debugger to allow you to track down any problems you're having with your interfaces. You can click on any part of the screen and see what the element is, why it looks and acts the way it does, exactly where it gets its style information from, and navigate up and down to any of its children or parents. 
     59libRocket also comes with its own open-sourced visual debugger to allow you to track down any problems you're having with your interface development. You can click on any part of the screen and see what the element is, why it looks and acts the way it does, exactly where it gets its style information from, and navigate up and down to any of its children or parents. 
    6060{{{ 
    6161#!html