World: r4wp

On the other hand, the main Do button has always been first, on its 
own

Ah, now that I click them--and remember--I get it. My gut said that 
Available Words would give me a matrix with the languages at the 
top and a list of words available in each.

e.g. col 1 would be a union of all available words, and each row 
would have a check if lang-x supports it.

That would be very hard to accomplish, over all the different languages

Well, I thought if anyone could do it... :-)

I'll be pleased when we get it just for Red

Just need a masert WORDS-OF reflector for each language. :-)

masert = master

My objective is to move forward and spend as little effort as possible 
to be able to fight another day. So I must try to ignore the legacy 
languages as much as possible

Understood. Keep fighting.

Will do

Well worth the wait. Excellent work Doc & contributors!!

Thanks Arnold!

Doc, you're doing something very important.  Please keep up the great 
work!

Thanks Nick. The good thing is that I'm not alone on this journey. 
:-)

This is fantastic Doc. I know it's still very early days, but you 
are making great progress and it's very exciting to see it come to 
life. When I copied the commands from the new blog entry, to build 
the console, and it worked the first time, perfectly, it made my 
day. Then, even doing just simple things in the console was fun.

Of course, then I tried pasting the routine example from the blog, 
which didn't work. :-)

The most painful part of the whole thing? GitHub/Win.

Routine are basically Red/System code which require a compilation 
step, so it can't run as-is in the interpreter.

But if you define a routine in a Red script, and then DO it, it will 
work. You can also build a custom console by writing a Red script 
and adding at the end an %include %<path-to>/console.red.

Yes, I will read more carefully. Just too excited. :-)

if you define a routine in a Red script, and then DO it, it will 
work.
 => the script needs to be compiled for that to work.

About the "painful" part, I would like to provide ready-made Red 
consoles for each platforms. If Andreas (or anyone else) could make 
a redsource site as he did for R3, providing automatic builds, that 
would be great.

I will do it myself if nobody else steps in, once we get the target 
console implemented (Unicode LOAD, EXIT and RETURN supported,...)

I'm working on console downloads

They're basically already in the test repository, but still with 
some flaws

Nice work Graham! Is r3gui.com your site?

Yes :)

I set it up to hold r3gui docs I had corrected but looks like it 
is going to hold anything related to r3 ( or red !   )

And it's just a S3 bucket confiured as a website which keeps my costs 
down.

Very nice Graham.

I am expecting that everyone wil now start to scheme!  ( not in the 
Jaime way though )

Andreas has pointed out that the http scheme uses several async handlers, 
and tcp level handler can create events to send to the outer http 
handler :(

So, it gets pretty complicated

Anyone know what Jaime is up to these days? In any case this is great 
stuff Graham.

Just checked LinkedIn, he's working for some company called homeland 
security

Yikes! :-)

Are we talking about Jaime Vargas?

Yes

I still have a couple of his WhyWire wireless units operating on 
a ranch here north of Ukiah.

Have you upgraded the version of rebol running in them?

Great work GrahamC, added to http://rebol.informe.com/wiki/view/R3_network_scheme
 so the community may contribute! :-)

@GrahamC: No, they are still running stock.  Seem to be quite reliable, 
much more so than most access points and wireless bridges out there. 
 They've been running for almost 6 years with no maintenance, and 
both units are outdoors.

That's pretty impressive.  I always wondered what exactly the embedded 
Rebol did in those boxes.

The WhyWire boxes ran OpenBSD off a CF card with Rebol installed. 
 I know Rebol was used at least for configuring the units.  I don't 
know if Rebol actually handled any of the wireless communication 
parts.

It's great to see we've decided to stop "Waiting for Godot". Thanks, 
Ladislav!

I think someone else also had this problem, but I'm getting this 
when building this source on Linux:

undefined reference to `dtoa'

I guess that you did not do make make and make prep?

(that is necessary to include the new source code file)