World: r4wp

Kaj: good idea, I'll make a montenegrin version of that page, with 
*only* Red! ;-)

AdrianS: thanks, it's reverse-engineered, so, maybe not fully accurate 
and complete, but it  looks like a good start.

Doc - not sure about debugging driver priority, but bear in mind, 
that ppl are waiting for networking and other IO ... e.g. Maarten 
was asking today, when it comes. I think that we need more feature 
complete Red ASAP ...

debugging driver priority

 Not sure if you're mixing things here or not. First PDB has nothing 
 to do with drivers, it's a general-debugging help for Red and Red/System. 
 Second, I never said that drivers or PDB support was prioritary. 
 If I worked on adding driver support for Windows, it was just to 
 help Kaj and Bo use Red in their project, nothing else. The priorities 
 are clear, but I won't be able to resume on them until I get back 
 from Montréal.

I'll add the /deep to %build-arm-tests.r Pekr (Runnable dir is required 
and built by quick-test.r)

I'll also suspend the function tests from the Arm build.

Yes, I mixed it incorrectly. Priorities are surely your call, I am 
just reporting what I can anticipate from ppl asking question here 
or there, and the message is - more complete Red. So - looking forward 
to resumed Red development ...

I've just lost a long post I was typing here because my finger ripped 
on the small laptop keyboard from a CTRL-S to CTRL-Q...who the hell 
got the bright idea to put the app killing (no confirm prompt) key 
close to the post sending key?...Will have a few words with Carl 
about ergonomy in AltME. ;-)

Peter: no need to disable function tests, I've already commented 
the few tests related to #420 that were causing the crashings.

Sorry Doc on the pdb thing.  I don't think your going to find a pdb 
file format.  Closest I seen was this that someone may have been 
trying to reverse engineer https://www.informit.com/articles/article.aspx?p=22685.

Paul: thanks, AdrianS posted a similar link above. Yes, it seems 
that it's not documented.

Well, MS not wanting people to debug their software explains a lot

With Red, you'll be able to debug your programs on the other platforms, 
before running them on Windows

I see the WinDLL and DarwinSO targets in config.r are now uncommented, 
but LinSO is stil commented out. How do they relate to the -dlib 
compiler parameter now?

Wouldn't it be possible to add MSDOS-ARM and Darwin-ARM targets right 
now, to start testing on Windows Phone and iOS?

The red APK builder script build.r attempt to download some files 
i.e. http://static.red-lang.org/droid-tools/jli.dll.But only gets 
404 Page not found...

For which platform are you building?

Android

Sorry, I mean on which operating system

On Windows

That should be supported. Have you retried?

Yes, you can make clicl on my example

click ..

How can you click? You said it didn't work

here:  http://static.red-lang.org/droid-tools/jli.dll

OK, Doc will have to look if something is wrong with the script or 
with his server

Oops, old build.r version. Thanks Kaj.

Always update to the latest Red code for new features

Yes as build.r  with multi OS support  !!

@Doc What a nice syntax for poiinter dereferencing in Red/System! 
Well done.

Encapped Red on Windows preview: http://static.red-lang.org/encapped.png

Arie: thanks!

Woohoo! But...does it run? ;-)

It does, but does not blend! ;-)

That's really excitiing Doc.

I was thinking you would be happy with that move. As the newcomers 
keep showing up on Red, it's time to make it closer to the final 
form.

Also, once the encapped version will be done for all supported platforms, 
we need to set up a continuous integration chain, with tests and 
builds automated. That will take some time to get done properly, 
so better start now.

Yes, it's a great step. I think the console is important as well, 
so once I get some other things done, we will talk about doc extraction 
and mezzanines in support of that.

Right, we'll work on those tasks as planned during August.

Encapped Red seems cool, if it's what I think, it is. To have a script 
included and executed at launch, so it's all in one file?


I wonder, what it takes to do that in World. Probably easy enough, 
just need to figure it out.

Geomol: I think encapped Red means that you can compile Red programs 
from the command prompt instead of having to launch Rebol2 and then 
compile the Red program.

Geomol, what is encapped is the Red toolchain, it adds no new features 
to the toolchain itself except removing the need to run it from a 
Rebol2 console.

It is possible right now to include an external file in the executable.

Oh, Bo was faster. :-)

Only by 44 seconds according to my AltME. :-)

I'd be interested to know how Doc got around the problems I was seeing 
him have with the Rebol2 encapper.  He is a digital magician!

Bo: The issue I had to fight with in my hotel room was just that 
my own prebol replacement lib was adding  an extra layer of MOLDing 
to the input source, because of the workarounds to avoid the #include 
(and others) directive collisions. This resulted in disabling some 
parts of the code leading to  odd runtime errors. I couldn't focus 
enough on it to see it that night because I was too exhausted and 
wanted to listen to the discussion at the same time. :-) (For others: 
my room was a kind of meeting point in the hotel ;-)).


To debug that, I reproduced the preprocessing changes step by step 
in a console until I located the "disabled" parts of the code, once 
I PROBEd those parts in the console, the cause was clear and the 
fix easy.

This is the encap script I'm using:

Rebol [ ]

#include %encap-paths.r
#include %red-system/utils/encap-fs.r
do #include-string %.cache.efs
do #include-string %red-encap.r

Also, to be able to see any output in DOS console from an encapped 
Rebol app, I needed to change a flag in the executable file (sub-system: 
`console` instead of `GUI`).

you can also set an attribute in the header for it to be generated 
as a console app.

Really? I missed that in the docs.