• Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search
 

World: r4wp

[Ann-Reply] Reply to Announce group

Maxim
19-Jul-2013
[2271]
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.
Kaj
19-Jul-2013
[2272]
r3-gui.r3 is exactly as long as the MS build script for a Windows 
driver :-)
Pekr
19-Jul-2013
[2273]
Good move Robert ... now we need to tell aso SO guys, which are not 
visiting here :-)
Robert
19-Jul-2013
[2274]
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.
AdrianS
19-Jul-2013
[2275]
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.
Maxim
19-Jul-2013
[2276]
Robert, why not just dump the svn and create your own git server?
AdrianS
19-Jul-2013
[2277]
Is it just do %loader.r3 after a change?
Cyphre
19-Jul-2013
[2278x3]
yes
or you can use the build.r3 do get on-file version
(note Ladislav's INCLUDE is needed https://github.com/saphirion/include)
Henrik
19-Jul-2013
[2281]
why not just dump the svn
 - not trivial :-)
Robert
19-Jul-2013
[2282x2]
our whole workflows etc. are based on SVN, so we need to change our 
toolchains etc.
step-by-step
Andreas
19-Jul-2013
[2284]
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
Ladislav
19-Jul-2013
[2285]
Include tips and tricks:


I run r3 with include and loader, the include.mdp documentation describes 
how it can be done.
Cyphre
19-Jul-2013
[2286]
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.
Ladislav
19-Jul-2013
[2287]
Yes, the strategy Cyphre describes is ideal for immediate testing 
of any changes made to R3-GUI sources.
AdrianS
19-Jul-2013
[2288]
Thanks guys - maybe these brief notes could be added to the readme 
on GitHub.
Ladislav
19-Jul-2013
[2289:last]
Adrian, check the new wroding of README, and, eventually, submit 
a request, please.