You have to compare Roger's example of what an extension is vs what a plugin is. I need to look at more too...Roger?
On Tue, Oct 4, 2011 at 7:53 PM, Bassel Safadi <bassel.saf...@gmail.com> wrote: > Loading on demand reduce system resources needed to render a page. And once > a package is needed and loaded it stay loaded until session end. Also on > aiki.php libs can be added to be loaded on system start. We should always > try to minimize the amount of queries so adding one more table for > extensions is not needed. > > What others think? > On Oct 3, 2011 12:35 AM, "rg1024" <792...@bugs.launchpad.net> wrote: >> We can use a similar technique used in plugin: >> - Create a table for all extension, with name, description,version (in > future url to upgrade) , file, class, status (active, deactive, missing) >> and selectors (list selectors) >> Example: >> webdate. >> file: webdate.php >> class: webdate >> status: active >> selector: * /*/* >> - onload aiksi search extension active, and if extension selector matches > current site/view/language, load it. >> >> - if each extension need configurations, we need add another table to >> stored it. >> >> -- >> You received this bug notification because you are subscribed to >> aikiframework. >> https://bugs.launchpad.net/bugs/792681 >> >> Title: >> aiki only loads extensions on-demand and no simple way to load them >> upon system load >> >> Status in Aiki Framework: >> Confirmed >> >> Bug description: >> Well there are ways to do, but need to be able to set in the >> config.php file a setting for extensions to load. >> >> One thing we can do is only load extensions that inherit from a new >> Extensions superclass. >> >> The idea here is that there are some operations that would need to be >> tested for aikiframework core, and they might need to be run on every >> instance of aiki. Also, this gives a nice migration plan if an >> extension becomes useful enough to move into the core...which we are >> trying to keep lean. >> >> >> My thought is to add: >> >> $config['extensions-preload'] = array('myExtensionClassName', >> 'AnotherCrazyExtension'); >> >> Then in aiki.php we add after all the default extensions, this: >> >> foreach ( $config['extensions-preload'] as $ext ) { >> $aiki->load($ext); >> } >> >> ### >> >> Other things we could do, is add a priority to extensions, so that the >> loading can happen in a weighted way, rather than file order. Or, we >> could add an option to have pre-extensions and post-extensions for >> when to load those extensions orrrr, we could add an event/hook system >> and fire an event like 'pre_extension_load' and allow for code to hook >> in and load extensions pre, and then do the same like >> 'post_extension_load' and let developers load in whatever extensions >> they want. >> >> Simpler is better though IMO. >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/aikiframework/+bug/792681/+subscriptions > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/792681 > > Title: > aiki only loads extensions on-demand and no simple way to load them > upon system load > > To manage notifications about this bug go to: > https://bugs.launchpad.net/aikiframework/+bug/792681/+subscriptions > -- Jon Phillips http://rejon.org/ | http://fabricatorz.com/ chat/skype: kidproto | irc: rejon +1.415.830.3884 (global) | +1-510-499-0894 (sf) +86-187-1003-9974 (beijing) -- You received this bug notification because you are a member of Aiki Framework Developers, which is subscribed to aikiframework. https://bugs.launchpad.net/bugs/792681 Title: aiki only loads extensions on-demand and no simple way to load them upon system load Status in Aiki Framework: Confirmed Bug description: Well there are ways to do, but need to be able to set in the config.php file a setting for extensions to load. One thing we can do is only load extensions that inherit from a new Extensions superclass. The idea here is that there are some operations that would need to be tested for aikiframework core, and they might need to be run on every instance of aiki. Also, this gives a nice migration plan if an extension becomes useful enough to move into the core...which we are trying to keep lean. My thought is to add: $config['extensions-preload'] = array('myExtensionClassName', 'AnotherCrazyExtension'); Then in aiki.php we add after all the default extensions, this: foreach ( $config['extensions-preload'] as $ext ) { $aiki->load($ext); } ### Other things we could do, is add a priority to extensions, so that the loading can happen in a weighted way, rather than file order. Or, we could add an option to have pre-extensions and post-extensions for when to load those extensions orrrr, we could add an event/hook system and fire an event like 'pre_extension_load' and allow for code to hook in and load extensions pre, and then do the same like 'post_extension_load' and let developers load in whatever extensions they want. Simpler is better though IMO. To manage notifications about this bug go to: https://bugs.launchpad.net/aikiframework/+bug/792681/+subscriptions _______________________________________________ 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
