Perhaps a slight fork of issue 20, but we should enforce a system where
modules have the following high level methods:
* constructor/load() - load module and do any initial work that doesn't
require any outside dependencies
* init() - finish any initial work that DOES require external dependencies
(on crop plans, say, or databases)
* reinit() - _maybe_, this would push through any changes in settings and
such, perhaps reload w/ a new datamodel
* shutdown() - close connections, save settings, save state, etc
The rudiments of this are in place already in the basic API data structures
and interfaces, but modules will need to be retrofitted and the driver
module (CropPlanning) and ModuleManager will need some minor reworking to
make it work.
Original issue reported on code.google.com by cropplan...@gmail.com on 11 Dec 2008 at 2:44
Original issue reported on code.google.com by
cropplan...@gmail.com
on 11 Dec 2008 at 2:44