On 7/10/07, Paul McNett <[EMAIL PROTECTED]> wrote: > 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.
Actually I think it could/should be used to allow developers to ensure their end users are running the proper version of dabo for their application. Kinda like wxPythons version selections allows me as a developer to ensure that my end users are running a version of wx that I know my application works on (eg not wx2.6 and lower in my case). But without the end user having to install multiple versions of dabo for different applications. eg. Developer A write application A Developer B writes application B End User A uses both application A & B Say we start on dabo build 3000(Just a random number) and both applications work as intended, time goes on and both developers are fixing their own bugs and pushing their own releases. During this time dabo gets build number 4000, and something between 3000 and 4000 broke the way application A & B worked. As it so happens Developer A is on vacation so cant get around to fixing whatever broke, but Developer B is around and fixes his application to work with dabo build 4000. End User A gets the new version of application B, which now requires dabo build 4000. Now in this situation the end user is either stuck using an older version of Application B, or stuck with a broken version of application A, but with a webupdate system that is controlled by the developers of dabo applications, all the Developer has to do is add the new dabo build number requirement to his application and when the end user runs his application it will auto update dabo and be on its way, then when the same user runs application A again, it will downgrade dabo to build 3000 and be on its way and the user does not have to worry about dabo, nor do the developers need to worry about which version of dabo their users happened to download since they can just tell dabo to upgrade or downgrade to the version that they know their application works with, _______________________________________________ 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]
