Ok... dunno if anyone else will be this psyched about it, but I had to share... in my quest to find a replacement for prism/webrunner, I finally made some time to tinker with luakit... and I can't beleive how easy it was. a) aside from a small glitch on my end with java plugin install - it works perfectly out of the box and b) it only took an hour or so to find the right snippet of code to add to get external links opening in the system default browser. I even upgraded from 2.6.4 to 2.6.5 without any hiccups! You could have knocked me over with a feather when that ran.
For anyone interested - my rc.lua (tiddlywiki.lua actually, with a wrapper script to run 'luakit -c ~/.config/luakit/tiddlywiki.lua "$@"') is here: http://dl.dropbox.com/u/45371072/tiddlywiki.lua I stripped our persistent cookie support from the .lua file, since I had already disabled use of cookies in my tw, and quite a few other things... if you just want the external link behavior with stock luakit/TW, copy the block of code with 'xdg-open' to the default rc.lua, in the "user scripts" section. The only glitch I ran into, which wasn't luakit or tw at fault, was that I had previously copied the java plugin libnpjp2.so to .mozilla/ plugins, manually. It was working fine under firefox - but I guess not because of my manual copy. It appears, the durn thing is smart enough to know it's been symlinked, and follow that link to find the rest of java... so when you follow the actual directions to install the plugin (http://www.oracle.com/technetwork/java/javase/manual-plugin-install- linux-136395.html) the saver.jar works perfectly under luakit (possibly any webkit based browser?). Plain luakit works out of the box just fine - but the stripped down, and slightly tweaked .lua above makes it behave more like an SSB, and if you have "open links in external window" turned on in TW, then my tweak uses xdg-open to launch the appropriate program for that link. Plus... luakit is super lightweight, and extremely customizable - more in function that looks - my whole goal has been to only have TW as the chrome, with the browser out of sight. Now to dig into the keyboard bindings, and see what interesting features are hiding out there. As easy as everything else has been with it - I'm thinking it might not be too much work to provide local file access as well (without requiring tiddlysaver.jar). Cheers! --Jim -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
