/
Separating installer from a rest of a system
Separating installer from a rest of a system
- Alex
Owned by Alex
Jun 13, 2012
Loading data...
Imported From: http://groups.google.com/group/in-portal-dev/browse_thread/thread/bb0b9c9e16cc5f7c#
Right now In-Portal Install/Upgrade wizard is tightly coupled with rest of
In-Portal code. In some cases (when database tables are renamed) we have
warnings across all of Installer.
I'm proposing to disconnect make Installer script a separate entity, that
doesn't base itself on top of kApplication class and even may use it's own
SQLLite database if there is a need.
Then when Installer need to make changes to underlying In-Portal system
(e.g. rebuild caches), he can create in-portal instance and communicate
with it. This is of course not required at all to do database changes.
--
Best Regards,