World: r3wp

BrianH - I am fine with whatever crap windows require. I have my 
most needed stuff on C:, in !mp3, !REBOL, !Foto etc. dirs. I run 
as an admin, so I don't care ...

So, if a program that is being installed needs Rebol ... where should 
it look?

Right. File placement is a matter of chosing the default folders 
of the installer, as it does now. You can change those choices.

Python seems to install to c:\python2n\

As in almost all cases, Python is a bad example.

BrianH: so where can users (not admin) safely put his rebol scripts, 
so that rebol executalbe can write and read from such a directory? 
We can't do it in program files, but can we do in somewhere on C:\REBOL?

The trick is registry usage. The folder locations can be looked up 
in the registry.at runtime, as long as those registry settings are 
in the right location of the registry. I'll have those exact locations 
Tuesday evening.

... or only user profile dirs is the right placement?

c:\rebol is out ... unless you write enable

d:\rebol is fine though :)

Pekr, it's not abot where the user can pt their user scripts, it's 
about the desktop files and such. File associations manage the user 
script issue.

User scripts can go wherever you like.

will the installer be written in rebol?

Or, will you use a standard installer script ?

It is already.

It's in the SDK source.

And how then will it cope with Windows 64?

32 bit programs can't write to the windows 64 bit registry

BrianH - but when user script is run, REBOL changes current dir to 
that of the script placement, no? And the script might require to 
create some file at that destination. I know that temp files will 
go to some deep cache dir, but what if script wants to write to the 
dir of the script placement?

It will go in the WOW64 "Program Files (x86)" directory.

Pekr, that is a runtime issue, not affected by the installer at all.

For R2, all that matters for install is the View desktop and file 
associations.

If you have the installer all sorted out .. we should move on to 
something else!

yes, we should all move onto R3 :-)

I can only SAY WOOOW on this release, I am still a strong R2 user 
and this is much more than appreciated!

Yup Graham. For me that should be a little sleep - I have to wake 
up again in 2 hours to go to a customer site. Pekr, stay on topic 
:)

Graham: thanks a lot for gmail related code, this was big hinge in 
some stuff I was planning

Janko, whooo, yay!

Brian, I would like to see prot-http.r extended ... since googledoc, 
and amazon are big topics for some of us

I wrote some changes .. they just need to be optimized by someone.

By the way, the reason we can consider getting the installer in this 
release at all is because the hard part has already been done. If 
any of the rest of you have tested patches that don't break anything, 
get in touch. If they don't make it into 2.7.7, they might make it 
into 2.7.8 next month :)

BrianH: you have access to sources? Who can do native changes? Only 
Carl? Because if so, I hope there is not much of changes. I wish 
Carl finish R3, not to spend much time on further R2 enhancements 
in native code ....

Here's my patches to http-prot.r .. http://rebol.wik.is/Protocols/Http

I have used it for a while and they do not break anything AFAIK ...

Graham, once we switch to the community development infrastructure 
next month such changes will be more possible. Yes, that means the 
R3 chat vcs too, so get your account and start learning to use it. 
If you think it sucks, write your own client - it's not hard.

I'll look at your patches :)

I also remember some patches to http by Oldes or someone else, I 
just don't remember details ...

BrianH: how can you write your own client to R3 Chat? Can you actually 
use its command set? I mean - create a gui, and "send" command like 
"n", "lm", etc. to console in the background?

Pekr, you'd be surprised how much we can fix in mezzanine. Nonetheless, 
it is our job (well, mine) to minimize the impact that R2 development 
has on Carl's R3 work. We're keeping the native changes to a minimum, 
but the big part is testing and coordination.

The UI should really be split out, if it's not already done in R3 
chat. But don't forget that we already have bots for R3 chat.

Own client to R3 chat: The interface between the client and server 
is simple RPC. The UI is split out already.

I think we're off topic

Yes, thank you.

Henrik ... is that memory leak still present?

Graham, I believe so.

I've avoided creating UIs with too much networking with open ports.

R2/Forward location: R3 chat 837 - Community/Libraries/R2-Forward

Fix memory leak, fix installer, update http, back port some r3 mezzanines 
... and parse improvements, and we're done.

I read also that that Brian's vid resizing scheme works well too 
... does it break any old vid stuff?

No PARSE improvements this release unless Carl has a ready bugfix. 
Fixes to DECODE-URL are fair game though.

Resize doesn't break anything, however it's been re-used in the VID 
extension kit with some modifications, which I don't think are compatible.