World: r4wp

I had to refer to the ReactOS source code for some insights

I saw the discussion about windows path names.  If you need to convert 
a path to not have spaces then windows uses a tilde ~ for truncating. 
 To see your path converted just open a command prompt and type dir/x

that gives the path names with conversion.

Thanks, but the WDK apparently doesn't do that, because it simply 
doesn't work

Cost me quite some time to figure that out

And using quotes doesn't work also?

such as "c:\my documents\Some nerdy dudes folder\"

You'd have to modify the WDK to do that. The use case is simply to 
develop a driver in your user directory

You don't give the WDK full paths, just relative ones, without spaces

yeah I thought it would still recognize the tilde formatted paths.

I don't doubt that, but you can't solve the problem that way

Ok, not a problem.  I'm not aware of all the details.

Thanks for your help, anyway. The debugging tools were worth trying

Sure no problem.

The spaces problem is probably in the 12,000 lines build script I 
mentioned. I didn't feel like modifying that to make it space-proof

Thanks Kaj.  Saw the Rebol boys this weekend and you, of course, 
were part of the key topics.

So I heard :-)

You have a lot of fans.

Good to hear

Did you have a good time?

I thought it would be OK. When I got there at 11 PM Thursday and 
the hotel clerk said "I don't have a reservation for you" I wasn't 
so sure.   He found one for Michael Michael who had not shown up 
but had the same dates booked as I wanted.    He gave me that room 
because me and Michael Michael have the same home phone number... 
   But it went straight up when I met Gregg at breakfast and I enjoyed 
my whole time there.

:-)

Identity theft!

Yes after you commit to an online booking site they morph your information 
to other systems which eventually ended up at the hotel to be re-keyed. 
  If you think green screens are dead you should look over the counter 
as they are searching....  Data is probably faxed to them..... so 
it is a bit of a miracle that the world holds together as well as 
it does with this stuff.      .... ahhhh ... opportunity knocking....

Always prefer amber screens to green ones :)

Thank you Robert and Cyphre for the new Android release!

Yes, thank you for the Android release.

Robert, Thanks for the R3-gui release.  Do you have a date for Rebol 
and view engine also being part of a source release?  


These where one of the most frequently recurring discussions at the 
devcon.

r3-gui.r3 is exactly as long as the MS build script for a Windows 
driver :-)

Good move Robert ... now we need to tell aso SO guys, which are not 
visiting here :-)

Maxim, we are gaining experience with the git-svn bridget now. I 
think we will use it for a couple of weeks. Than the next move will 
be R3 and the View engine.

Thanks, Robert. Could you briefly describe somewhere (in just a few 
sentences) the workflow you use when working on/debugging r3-gui? 
i.e is it possible to stay in the same R3 instance and rebuild (do 
you even need to be using the monolithic r3-gui script when debugging?), 
reload the script safely, etc.

Robert, why not just dump the svn and create your own git server?

Is it just do %loader.r3 after a change?

yes

or you can use the build.r3 do get on-file version

(note Ladislav's INCLUDE is needed https://github.com/saphirion/include)

why not just dump the svn
 - not trivial :-)

our whole workflows etc. are based on SVN, so we need to change our 
toolchains etc.

step-by-step

So to work on / debug R3-GUI (Cyphre please correct me, if I'm wrong):

;; Load INCLUDE (once)
>>  do https://raw.github.com/saphirion/include/master/include.r


;; (Re-)load R3-GUI (multiple times; assumes you are in the R3-GUI 
toplevel directory)
>> include %loader/loader.r3

Include tips and tricks:


I run r3 with include and loader, the include.mdp documentation describes 
how it can be done.

Yes, the most efficient way(in Windows) is to setup INCLUDE+R3-GUI 
loader to be executed everytime you click on *.r3 script. I'm using 
that and every change to the R3GUI sources is then automatically 
"propagated" once I run any R3GUI script again.

Yes, the strategy Cyphre describes is ideal for immediate testing 
of any changes made to R3-GUI sources.

Thanks guys - maybe these brief notes could be added to the readme 
on GitHub.

Adrian, check the new wroding of README, and, eventually, submit 
a request, please.