I guess I'll toss my 2 cents in to the ring on this issue. I fully support auto/easy/web updating of dabo. Now I do think that this should be handled by the applications using dabo, and not ask for user input. The reason for this is end users of an application are rarely going to know if they should be updating dabo or not, the developer of said application will. I also think that it should not auto Exit when it is done updating, maybe make an UpdateComplete event that the Developers can catch and do something with (like running though sys.modules and removing everything that dabo and their app imported, then reimport it, thus getting the new version without restarting the app)
Since I have not looked closely at the code I am not sure if when it upgrade it just grabs 'release' or it grabs a specific build number. If it grabbs a specific build number then you should allow developers to specify a maximum build number for their app, and thus allow dabo to upgrade/downgrade itself for each end user application that uses it. (This coupled with the event idea should allow each application developer to guarantee a working version of dabo for their app, without having to rely on end users upgrading or NOT upgrading when an upgrade happens to break you app) _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/dabo-dev/[EMAIL PROTECTED]
