If some code use global variables like $layout then it should be replaced in all placed to global $aiki->layout, if we use this global $variable to expose API then internal code should use it. For instance this CreateLayout class inside widgets.php should be renamed to widgets or file renamed to CreateLayout and then use via $aiki like $aiki->CreateLayout->??? or $aiki->widgets->??? maybe it would be good to create in all those classes/files only methods that will be uses like static once and all logic put into index.php. So you could actually read whole Aiki looking at index.php file that use various API functions.
On Sun, 12 Feb 2012 19:32:23 +0100 Roger Martín <rg1...@gmail.com> wrote: > thanks for coments! > > one collateral effects of aiki engine is that some libraries need to > be "cleaned", as they need to work with other engines (basically work > without global $layout). Aiki architecture and components will be > improved. > > In this line, i change libs/Output.php and index.php, and redefine > some plugin action (see http://www.aikiframework.org/wiki/Actions). > This changes assure plugin compatibility between engines. -- Jakub Jankiewicz twitter: @jcubic www: http://jcubic.pl _______________________________________________ Mailing list: https://launchpad.net/~aikiframework-devel Post to : aikiframework-devel@lists.launchpad.net Unsubscribe : https://launchpad.net/~aikiframework-devel More help : https://help.launchpad.net/ListHelp
