Creation of a Router table a unique routerName field in action_settings2 to simplify configuration

[GoogleCodeExporter]

To further ease the configuration of BungeniEditor and to highlight that there 
is no relationship between a router and a dialog class (this relationship is 
only brought out in the code in cases where the router creates a dialog), the 
proposal is to create a separate table ROUTER_CONFIGS with the following schema

ROUTER_NAME  <FOREIGN KEY, PRIMARY KEY>
ROUTER_CLASS [From SUB_ACTION_SETTINGS]
ROUTER_DIALOG [From ACTION_SETTINGS & SUB_ACTION_SETTINGS] 

The ROUTER_NAME field will also be available in the ACTION_SETTINGS2 table. 
Code in BungeniEditor will now check for the variable ROUTER_NAME rather than 
ROUTER_CLASS and use the ROUTER_CONFIGS table to find out the dialog that is 
displayed, where necessary. 

Entries to the ROUTERS_NAME will be created using the following structure 

router_[action]_<doc_type> e.g. router_applyStyle_debaterecord

Original issue reported on code.google.com by reaganmb...@gmail.com on 12 Jan 2012 at 8:32

[GoogleCodeExporter]

router name can just be [action]_<doctype>

router dialog - is perhaps just form action_settings - since the dialog itself 
is registered in selector dialogs - so this should be the parent dialog which 
registers sub dialogs.

Original comment by ashok.ha...@gmail.com on 12 Jan 2012 at 2:32

[GoogleCodeExporter]

Completed, moved routers to xml

Original comment by ashok.ha...@gmail.com on 1 Feb 2012 at 2:33

• Changed state: Fixed