14
Quote:
trabis wrote:
First we need to:
- Finish this 2.4 bug hunter
- Move our focus to 2.5 (go php5 movement), build a XOOPS module framework 'XMF'. XMF will be a module itself and it will provide alternative libraries. XMF will be an interface between modules and core.
Build comments, notification, imagemanager modules using XMF.
Implement a hooking system(observer pattern) so modules using XMF can extend other modules using XMF with plugins (listen and respond to events such as: onUserDelete, onModuleInstall, onSearch, etc).
- 2.5.5 : Make new system module with XMF (the hooking system will be heavily used here)
- 2.5.9: Have every possible module using XMF
- 2.6 : Move XMF to core
- 2.7 : Feature request go here :)
I agree except on one point, either you make your 'XMF' a module either you make it part of the core but not first a module then a core "feature".
This will only drive to problems.
You must measure the PROS and CONS.
CONS:
If it's a module, we will have problems because you will need the correct version for your module
PROS:
If it's a module, you are not dependant of the core's version...
What else PROS and CONS ?
