Anti-kludge kludge as a uBrowser replacement

Since uBrowser is probably going to take as long to implement as llHTTPRequest has taken, would anyone be up for a suitable replacement... It is quite possible to screw around with the HTML help files that appear in the new help floaty when you hit F1 (instructions available upon request), which means the only thing missing to give us an in-world wiki is some kind of feedback mechanism for editing those HTML files.

Would people be willing to install a 3rd party application on their system to update and syncronize those HTML help files with a wiki or even to act as a manual for in-world products?

I ask this not because it's a product or service I'm working on, but it occurs to me if SL developers could agree on an XML schema, then this kind of application would allow people access to product information in a way that (a) wouldn't require more inventory items, (b) would be equally and automatically accessible from the web, and (c) would bypass in-world, kludged message systems like InfoNet. Does this sound like something that's logistically viable for Second Life users?

(*Note: I have no qualms with InfoNet paticularly, it's the inefficient object passing methodology that bugs me. My Pear laptop does the same thing.)

Okay wait a minute in our circles in our circles in our circles and breath

We have an inworld browser, yes, but we don't know it's capabilities. Is it feasible to add an option to the llLoadURL() command so that it will post the page to the inworld browser rather than open the client's default?

Here's what I am aware of:

1. It uses C:\Program Files\SecondLife\help\ as its root directory, and will only open files from that and child directories.

2. It cannot make HTTP requests; you can't link outside of the root directory.

3. It only supports the html, head, title, body, p, br, b, and a tags.

4. Loading large files in the HTML help floaty can cause your client to crash.

5. You cannot type in locations of files; launching the browser loads index.html, and every other files gets loaded by links. (It seems to remember pages, so if you close it three links in, when you re-open the browser it'll still be three links in.)

Aside from that, it's pretty much a text-based browser, ala Lynx.

Er, I'm not quite getting the advantage of this over... using a proper web browser. So you get a little floating window in SL, with a text-only browser in it. What's wrong with llLoadURL as it is? The only thing I can think of is that it's annoying if you're running SL fullscreen, but is that really a major problem?

There may not be one, except for people who want to "live inside" the SL client, without using external applications.