Changes between Version 30 and Version 31 of frontend/features

Show
Ignore:
Author:
robertc (IP: 192.168.0.1)
Timestamp:
01/08/08 11:33:04 (10 years ago)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • frontend/features

    v30 v31  
    3333 
    3434[[Image(form.gif, nolink, align="left")]] 
     35{{{ 
     36#!html 
     37<div class="feature"> 
     38}}} 
    3539== Form controls and input == 
    3640But 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. 
    3943{{{ 
    4044#!html 
     45</div> 
    4146<div class="clear">&nbsp;</div> 
    4247}}} 
    4348 
    4449[[Image(datagrids.gif, nolink, align="left")]] 
     50{{{ 
     51#!html 
     52<div class="feature"> 
     53}}} 
    4554== Dynamic data representation (model, view, controller) == 
    4655One 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]] 
    4756{{{ 
    4857#!html 
     58</div> 
    4959<div class="clear">&nbsp;</div> 
    5060}}} 
    5161 
    5262[[Image(scripting.gif, nolink, align="left")]] 
     63{{{ 
     64#!html 
     65<div class="feature"> 
     66}}} 
    5367== Tight scripting integration == 
    5468The 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. 
    5771{{{ 
    5872#!html 
     73</div> 
    5974<div class="clear">&nbsp;</div> 
    6075}}} 
    6176 
    6277[[Image(extensible.gif, nolink, align="left")]] 
     78{{{ 
     79#!html 
     80<div class="feature"> 
     81}}} 
    6382== Extensibility == 
    6483libRocket 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: 
    6988{{{ 
    7089#!html 
     90</div> 
    7191<div class="clear">&nbsp;</div> 
    7292}}} 
    7393 
    7494[[Image(debugger.gif, nolink, align="left")]] 
     95{{{ 
     96#!html 
     97<div class="feature"> 
     98}}} 
    7599== Debugger == 
    76100libRocket 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. 
    77101{{{ 
    78102#!html 
     103</div> 
    79104<div class="clear">&nbsp;</div> 
    80105}}}