Week 1 :

Read the Sahana Agasti code base and Module manager documentation and archives and set up a demo instance on my local pc

Week 2 :

I have separated the admin code and Module manager code from the admin section and created a new module as Module manager which will contain code of all the responsibilities of Module Manager . I have almost finished coding with basic version of Upgrading/Activating/De-activating a module . By the end of this week i will most likely finish the working Module Manager and start work on how the modules must be packaged and the App store (will start after a discussion with mentors).

Week 3:

As discussed with Greg, Glenn Sir (mentors) for this project in the last IRC meeting about the Enabling and Disabling a module has been succesfully completed . Now using the Module manager modules can be enabled and disabled with no issues and also changes are reflected in the admin http://sahana/index.php?mod=admin&act=acl_enable_mods . Upgrade of a module if an upgrade version is available is also finished . This also includes if the module A is dependant on say X,Y,Z modules and then X,Y,Z are updated if not already in the latest version . I have tested this by setting up a demo repository of the upgrade version of modules and fetching the files . So far everything works clean . This week i will document all the work done so far and also Module package guidelines that will be required for packages being recognised by module manager as valid upgrade modules .

foundation/module_manager_documentation.txt · Last modified: 2010/12/18 17:35 (external edit)
Back to top
CC Attribution-Noncommercial-Share Alike 3.0 Unported
chimeric.de = chi`s home Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0