Dj Gilcrease wrote: > 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)
I guess this brings up another concern I have about it: the dilution of the point of it. There have been several points of view expressed so far about what should be updated and who should be responsible for it. Ed made it for the people using dabo to develop apps to keep updated with the most "stable" trunk revision. I think it should be for this same class of users but us the most recent stable branch. You, Dj appear to think it is for the end user of a dabo application. And I believe there have been other variations as well. Concern in summary: The point of web update isn't concisely stated, leading to potential confusion by our users as well as ourselves. -- pkm ~ http://paulmcnett.com _______________________________________________ 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]
