World: r3wp

also "local" does not work for me. I would change it to "Connect", 
"Disconnet", which is much more obvious for me ...

upon my request Carl extended latest Doc chapter regarding console 
about Rebol/Core mention, and auto-completion feature :-)

the button should be more visible as well. New users won't notice 
it until after a while.

yes, that is true ...

this is so important to Desktop, that it could be main menu option, 
or left panel icon?

there should also be an option to let users double click rather than 
single click. I've encountered many users who doubleclick on items 
in the viewtop, starting programs twice.

Yes, people are so used to double-click, that they've lost the understandig 
of the difference between single- and double-click. Is it the masses, 
that just don't get it, or is it the designers, who doesn't design 
the user interfaces good enough?

AFAICT its MS who convinced the world.  MY desktop is single click.. 
and its obvious Window was not designed for this.

AFAICT Vista is much better in this regard.

btw, I have successfull had Carl add a nav bar at the bottom of the 
quickstart tutorial...  he will propagate it to the other pages as 
well...

My first double-click experience was on Macs (the original Macs, 
with a 400kb floppy)

I believe it was the Mac interface which influenced MS to most in 
this regard.

Anyway, the option single/double-click would be good.

Something like this would be good:

view layout [across space 0 b: box 80x24 leaf "offline" btn 70x24 
"Connect" [b/text: "online" show b face/text: "Disconnect" show face]]

or maybe this, so it fits nicely in the existing left pane.

view layout [space 0 b: box 100x24 leaf "offline" btn 100x24 "Connect" 
[b/text: "online" show b face/text: "Disconnect" show face]]

Pekr, what is the link to the Doc chapter that changed ?

Well, I guess I keep putting this one off. Today, I am going to see 
how LAYOUT works from the inside.

Well, it seems easy to patch layout. Just bind the body to system/view/vid

I am shocked how easy it is. I put this off for years for fear of 
complication.

I've always just inspected layout's body to figure out how it works.

Anton - why? :-) The doc is new doc in the line of new docs - console 
:-) http://www.rebol.com/docs/quick-start4.html.... I just suggested 
point 6), that simply to get Console you can download /Core, and 
the docl also initially  missed one good feature - auto completion 
...

I really like how new docs are done - very good for real newcomers 
...

Thanks, just wanted to see.

I've pretty much finished commenting LAYOUT. (Of course there is 
always more that can be done to explain the workings of this high-use 
function, but 24 hours later......)
http://anton.wildit.net.au/rebol/doc/investigate-layout.r

If anyone has any questions about how LAYOUT works, now is a good 
time to ask me, because my head is full of it right now.

is it possible to prevent the creation of the Public folder when 
running a rebol/view that isn't installed, but just run on a windows 
PC?

I am not sure it is - well, it is - just don't run desktop!

run view.exe -i, to prevent install process ....

well, I'm not. I'm running View from a dos script, using all the 
options to keep it as quiet as possible.

just throwing ideas around, dunno if it really works ...

using all that already, so...

PATH-THRU specifies the directory in its source. READ-THRU creates 
public cache directories to store the files in. Maybe if you remove 
or replace the "public" in PATH-THRU you will see different behaviour.

The problem might be that the directory is created before user.r 
is done. In that case, you would have to resort to other tactics.

oh well, no biggie. it's just not "pretty"

It should be easy to just try patching path-thru in user.r. I'd like 
to know if that works for you.

I just tried it. The public dir is always created (empty) despite 
patching path-thru in the user.r file.

I suppose that rebol simply requires it always.

I don't see any technical reason why it should be hardcoded.

well, the public dir is solely for cache use, isn't it?

Yes, everything that comes from the net *thru* the cache :  path-thru 
, read-thru, load-thru, do-thru

then it would be nice with a global option to turn it off for these 
cases.

...and exists-thru?   They all hang off path-thru, which specifies 
the cache directory, and the way the path is constructed.

Turn what off ?

caching and thereby the public folder.

You mean, use the current directory instead of looking in the public 
dir ?

not using caching at all

Ok, that's just a matter of temporarily patching path-thru to your 
taste. I've done this before.

I patched path-thru to allow urls with query strings (from a particular 
website). The urls were mapped to the filesystem in a particular 
way. But your case sounds really easy.