World: r3wp

Volker: That's interesting regarding wait. I will raise that with 
Carl. It may have to do with the plugin's more complicated event 
loop.

Will the doc address only rebol security in regards to browser, or 
also rebol's  security in general?

Volker: If you uninstall via DPF, that should disable it (although, 
like I said, I have noticed a few bugs lately).

JoshhM: don't worry, R3 will have faster event system, or not? :-)

What is DPF *blush*

Pekr: We will be releasing a document soon for a feature called "Trusted 
Scripts" that will lock down security and enable licensing and safe 
loosening of the security settings.

Volker: Sorry, Downloaded Program Files.

Josh - but "trusted scripts" concept does not address the limitiation 
of "normal" plug-in, or eventual extension of rebol security scheme 
itself ....

I hope I am wrong :-)

Pekr: Yes, TS will include a major lockdown of default security settings, 
b/c we will have a way to loosen them.

Ok, that should be enough.

Pekr: TS will not include a change to REBOL's security scheme itself....as 
I have said a few times, changes to REBOL itself are out-of-sync 
with the plugin.

and that was my point - that is a pity ... as folks here had good 
ideas in that regards iirc ...

Pekr: Please raise them with whoever is working on R3.0.

so the whole security concept will be solved by plug-in itself, completly 
unrelated to rebol?

Pekr: If there's something critical for the plugin (I.e. get-net-info), 
we will look at that now.

Pekr: We will make a few, minor changes to REBOL to support changing 
security settings with a valid license key, but that's it. We operate 
on a philosophy of "destablize REBOL as little as possible".

ok, now I understand - you want to get plug-in working with pre 3.0 
rebol, so you have to solve it within plug-in itself, right?

We want to make as little changes to the 1.3 codebase as possible.

Just so you all know, I live in the world of "get the plugin as great 
as possible". Carl owns REBOL itself and whoever he delegates that 
work to.

get-net-info is imo critical - imo majority of corporate users are 
behind the proxy. Imo to get those users on-board, we have to 1) 
provide ability to do some settings (control panel icon, right mouse 
context menu, whatever), or to make proxy detection better ....

Pekr: Yes, I am looking at that code.

ok, I got it ...

hopefull my earlier points towards where windows stores proxy settings 
will help you ...

Pekr: K, I am checking into this now.

Josh - I can help you - I will look into Opera this evening/tomorrow 
and FF and Mozilla, to see where in registry those are stored - you 
know, Mozilla/FF does NOT use Windows control panel settings ... 
so users not using IE will have those settings elsewhere ...

but maybe we don't need to solve it that way, simply suggesting in 
docs, that users should set their proxy in control panel, that would 
be the easier way ....

BTW, Pekr -- if you or anyone else wants to re-write get-net-info, 
it is a REBOL function and you already haev the source. Feel free 
to code away :). If not, we'll put this on the task list, but no 
promises on when it will get done :)

Graham: Regarding launch URL -- the problem is that we currently 
don't have support for relative or root relative paths in FF. This 
is a bug that we should have fixed for the next release.

What about Linux & OSX support?

Terry, good question. Nothing is planned at the moment.

Well, that makes the whole plugin a moot point for anything less 
than a vertical market.. which might as well download and install 
an encapped script.

the thing is that it probably takes a bit more man power to support 
more platforms and browsers, won't it?

if i could go back to linux then.. I guess Jaime would spend some 
effort too.

Having to set the proxy on the control panel may not be enough. There 
are lots of people out there, who don't know what a proxy is.

Henrik - why should it? There is no IE to support on other platforms. 
And imo other browsers on Linux/OS-X use NS compatible plug-in. And 
imo it should be even compatible API wise.

Ingo - I don't understand - most of the time, you don't care of proxy, 
if you don' know what it is ;-)

... but if you want to get to the internet, and you are behind one, 
someone has to set it - you, or your admin :-)

In my world a browser plugin that only works on windows is worthless. 
And this is the REBOL plugin. Think about that bold statement about 
those 40+ systems REBOL works on. But the plugin is windows only 
???

ditto

Pekr, right. So I set it the internet up for Ma Dalton. Then she 
finds that interesting website, but the plugin just doesn't work.

... and in a company, do you want the admin to walk to all boxes 
just to set up Rebol/plugin?

Ingo, sorry, but you either don't know what you are talking about 
or it is kind of big misunderstanding .....

if you want to get yourself to the internet, and you are behind the 
proxy, either you know how to set it, or you don't have access to 
the internet. Or your ISP gives you adice of how to fill-in proxy 
settings ...

Maybe a bit of both .. I don't know :-)

I do agree about cross platform issues. I hope it will come. Josh 
is doing great job here  ....

I think it's about RT claiming support for many platforms where it 
would only turn out to be a half truth. Windows is already by far 
the best supported REBOL platform. A windows only plugin only skews 
the support even more.

To me Ingo makes sense. HE is around the first time, makes browser 
working, a while later she downloads this pluginin without him aorund. 
says things like control-panel.

Remember older plug-in? There was no chance of getting plug-in for 
Mozilla/FF, Opera. No chance for multiple instances. Now we have 
them, in beta, auto installation. Last thing to be fixed is the proxy 
thing and fixing some bugs. Then Josh can look at compiling to other 
platforms ...

Volker - how is that? Our idea is to set-up proxy automatically ...