Checking for updates as part of the WebKit Launcher (the application which is what you run when you double-click on a nightly build) w/o slowing down startup or modifying Safari.app is non-trivial. All the WebKit Launcher really does is set the DYLD_FRAMEWORK_PATH correctly to the included frameworks and then calls exec() pointing to your installed Safari.app executable. You'd have to spawn a separate updater process or keep the Launcher running after spawning Safari.app in order to to the update check.
Patches are certainly welcome. http://trac.webkit.org/browser/trunk/WebKitTools/WebKitLauncher -eric On Wed, Dec 31, 2008 at 5:14 PM, Maciej Stachowiak <[email protected]> wrote: > > On Dec 31, 2008, at 3:12 PM, Dan Mulroy wrote: > >> Hi All, >> >> Is there a reason the Sparkle (Free self update framework for mac os x >> applications) is not being used to update webkit? Having to download a full >> disk image every day is tedious, and the Sparkle frameworks are fantastic. >> > > NightShift is an application that will automatically update you to the > latest WebKit nightly: > > http://web.mac.com/reinholdpenner/Software/NightShift.html > > I recommend it if you want to track WebKit development via nightly builds. > > Regards, > Maciej > > >> Best, >> >> -Dan >> <Mulroy4.jpg> >> >> _______________________________________________ >> webkit-dev mailing list >> [email protected] >> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > > _______________________________________________ > webkit-dev mailing list > [email protected] > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
