Opening URL in SL Browser

I've scripted my media screen to automatically open the displayed page in a browser using llLoadURL() when touched. Despite the fact that my defaults are to use the in-viewer browser, and clicking on links in chat opens the in-viewer browser, llLoadURL() always uses the external browser. Have I missed something?

Don't ask me why but it is designed to do that.

Edit:
Found this on Sloodle:

For SLClient 1.20, the llLoadURL function is being changed to only support the external browser. (See VWR-7034). Apparently, the internal browser has been breaking too many webpages (e.g. involving JavaScript, Flash, or multiple windows), so the decision was made to reduce its use. This is a shame, because the Sloodle configuration worked almost perfectly (except for a couple of minor form glitches on Linux).

So what can we do? Well, if we wait, then LL might make a new version of the llLoadURL function which lets you select which browser to use (in code or in the UI, see VWR-4843). However, I'm not holding my breath for that! It is still possible to open the internal browser by using a URL clicked in the chat/IM window though, so we could make objects awaiting configuration llOwnerSay the URL either just before, or instead of, launching a llLoadURL dialog.

This approach has the advantage of eliminating script delay (llLoadURL delays the script by at least a couple of seconds). However, it is less obvious, as people will have to open their chat history window to see a clickable link, because the regular chat displays links as plain text.

about that delay

i just send it to another script using linked message as it`s only purpose is to avoid delaying the main script as messages are queued, all url`s are loaded after each delay (untill they break that...)

Thanks Ron. I'll stop trying to puzzle it out then I already output the URL in chat to be clicked on, so I'll stick with. The internal browser does admittedly have all sorts of foibles, but it does work with a fair bit of javascript, and for content-management type things, (which I guess is what Sloodle are using it for too), it's much nicer to stay inside SL. Let's hope that the ability for the HTML-on-a-prim to capture keyboard and mouse input comes along soon! Isn't it moving to webkit too at some point?

As an addicted User of Goggle Chrome, which has been open sourced and uses webkit, I hope they follow that route, especially as they already use Goggle code for the search functionality.

Ditto

Holy Crap! It was going through my mind that the only thing that keeps Chrome from being the perfect browser was the inability to use GreaseMonkey. Well guess what? I just searched one more time and someone has come out with GreaseMetal!!! WOOHOO!

http://asiajin.com/blog/2008/09/10/greasemetal-google-chrome-greasemonkey/

Thanks Jesse, great find, installing now

We've got a very basic version of that as a SLOODLE side-project (free and GPL, as always):

http://www.sloodle.org/browser


It's not been updated to use the lovely new "llDetectedTouch*()" functions yet... but hopefully will be at some point. At the moment, there's a prim-mouse that you drag about, then touch it to click on links and form elements etc.. You type chat messages on channel 3 to enter form data, and when you've done so, the page refreshes to show what you've entered. To visit a specific URL, you type it on channel 2. Alas the browser breaks on complex pages, or any page with JavaScript errors (which accounts for more than half the web!)... but as you can see from our demo screenshots on the above site, you can do stuff like Google searches with it.

That's very cool Pedro. And of course with llDetectedTouch things will get more interesting too. Thanks