Loading Profile...
Is there a way to make Coda use a Webkit nightly build?
Like a lot of Mac-wielding web developers, I run Webkit nightlies (which are especially nice now Sparkle has been added), which includes all manner of nice things.
While it's handy to test against current release Safari, it'd be useful if there was a way to make Coda use an installed Webkit nightly instead of the system-wide Webkit installation. A preference for this would be ideal (presumably accomplished by dynamically-loading the framework when needed rather than specifying it at compile time), but a straightforward mechanism of launching Coda so that it binds to the Webkit nightly would do the job.
While it's handy to test against current release Safari, it'd be useful if there was a way to make Coda use an installed Webkit nightly instead of the system-wide Webkit installation. A preference for this would be ideal (presumably accomplished by dynamically-loading the framework when needed rather than specifying it at compile time), but a straightforward mechanism of launching Coda so that it binds to the Webkit nightly would do the job.
I’m optimistic
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Indeed there is a way to do that. It involves setting some environmental variables at launch time for Coda. I have written a little Automator app to do that for you. It assumes that you have WebKit.app in your /Applications folder. Let me know if you run into any troubles.
http://tinyurl.com/codanightly
--
Ian
Panic -
Inappropriate?Thanks for that—it nearly works, but... not quite.
Ah, it turns out that Coda and Webkit's versions of Sparkle disagree—I can think of some workarounds (maybe), but it's Coda expecting Sparkle to provide the symbol SUCheckAtStartupKey and not finding it, because Sparkle is getting loaded from within WebKit.app due to the dyld path.
Forcing Coda's own Frameworks folder to appear before WebKit.app's in DYLD_FRAMEWORK_PATH does the trick, but you need to know where Coda is for it to work. -
Inappropriate?Ah yes... quite right... I was testing with an internal build of Coda that does not use that symbol. Sorry! You could try copying out the WebKit frameworks to another folder, or downloading/building the WebKit source (the source package includes scripts for launching other apps linked to the compiled source). I know neither of these are as easy as a simple script. I will try to whip something up.
--
Ian
Panic Inc.1 Comment
Add a comment
This answers the question
-
No no, you don't need to whip anything up—the fix is just to amend the framework path in the script to force Coda's own Frameworks folder to appear before WebKit's in the list (so Coda's version of Sparkle is used instead of WebKit's). -
Inappropriate?Okay, I just don't get with this means, " amend the framework path in the script to force Coda's own Frameworks folder to appear before WebKit's in the list." Can some kind soul just type out what I need to feed into this script to get it to work with the latest nightlies? Thanks.
EMPLOYEE
