Issues, pull requests, etc of course remain unaffected. Redirects from the previous location (rebol/r3) are in place (both HTTP/S and Git). Forks on Github originally created from rebol/r3 automatically reflect the new upstream location.
Andreas
(Just to clarify: that rename was Carl's decision. I'm just the messenger :)
Marco
I have uploaded another new script to rebol.org but this time I want to make an announcement
It is a quite complex script and I desperatly need your help as bug hunters but mainly also to "fill in the gaps" since there are a lot of things to add and try. Please help me by sending me an email or posting your additions and enhancements on AltMe.
To be able to use this script you must have the Rebol SDK http://www.rebol.net/builds/#section-2 and change the sdk-dir variable. If you want to stop dumping events go to ;view-funcs/view/; Window handler/handle-events/handler.
Bo
I just got the specifications and pricing pages done for the Rebol3/Red HD surveillance cameras I've been developing: http://respectech.com/smoothcam.html
Kaj
I upgraded my 0MQ binding for Red and Red/System to support and require 0MQ 3 when used on Windows:
Therefore, Red/System now has its own encapsulated interface to program arguments here in ANSI.reds (because it uses string copying functions from the C library):
get-args-count: Returns the number of arguments, but not including the program path. get-argument: Returns a string argument by number. On Windows, the argument is copied and double quoted arguments are stripped. Number 0 gets the program path. end-argument: Frees the memory of the copied argument. This does nothing on other platforms than Windows.
It now builds on the Red/System interface to provide the following functions:
get-args-count: Returns the number of arguments, but not including the program path. get-argument: Returns a string argument by number. On Windows, double quoted arguments are stripped. Number 0 gets the program path. get-arguments: Returns a block of strings of all arguments, but not including the program path.
This is in sync with our internal code line and we will maintain the repository. Pull-Requests are welcome and will be reviewed by us.
I hope with this step, the whole fuzz about Saphir and if it can be used is solved. As we promised, we will publish the code for it. Now I'm looking forward if the community is picking it up and if we see some pull-requests soon.
Bas
Kaj will give a presentation about Red wednesday 18th next week during Software Freedom Day at te CWI (Center for Math and Informatics), Science Park Amsterdam:
"Broad new Programming Language: From Systems Programming to Declarative GIU Scripting" From scalable network servers to small mobile platforms such as Android and Raspberry Pi. Kaj will present a declarative GIU binding for GTK, and will touch some bindings for ZeroMQ and SQLite.
Amongst others, we expect students doing a master education in System and Network Engineering at the University of Amsterdam, as part of their colloquium.
Kaj
I've updated my binary Red(/System) downloads. In particular, I upgraded the included 0MQ for Windows to version 3.2.3. This is only the second stable 0MQ 3 release. Before 3.2.2, 0MQ 3 versions were only compatible with themselves. This latest version can communicate over the network with 0MQ 2 versions, so I can finally use it cross-platform, for example with my 0MQ bindings for R3 and R2. The minimum requirements for 0MQ have likely gone up a bit, from Windows XP to Windows XP SP3. Further, all the latest Red fixes are in the new downloads:
More Red updates, to make my interpreter console versions more correct. I updated the binary downloads: see the links above. I added a new function for both Red and Red/System: TAKE-ARGUMENT that gets the next command line argument, but hides it for subsequent code. I'm using this in the console to consume the script file parameter. You could already run a script file with my consoles like this:
red file.red
But scripts that take parameters would see "file.red" instead of the intended first argument that the compiled script would get. Now you can run scripts with arguments unchanged between the compiler and my consoles. For example, if you want to use 0MQ directly from the Red interpreter, without compiling your programs, you can use the */Red/red-core-message and */Red/red-message (with GUI) interpreters for your platform from my binary downloads. Then you can start the 0MQ examples directly:
Also, after the execution of the script, you would remain in the console to inspect the result of execution. This is not what you want for CGI or shell scripting, so the console now exits after the script. You'd have to use HALT like in REBOL to remain in the console, but HALT currently QUITs the console altogether. I can't override HALT because it's a keyword, so for now I have implemented a STOP function to remain in the console. It only sets a flag: it can't stop the script execution, so it only behaves exactly like HALT when used at the end of a script.
Lastly, I have overridden LOAD and DO to support reading from a file by passing a file! type, here in input-output.red:
My DO is quite inefficient because I can't use the original DO, but it will do until Doc implements it in core Red.
Kaj
Doc allowed to override HALT, so I updated my downloads again with STOP renamed to HALT. Note that it still doesn't actually stop script execution. I suppose that will become possible when Red gets error! exceptions.
Maxim
Just thought I do a little annouce about the fact that I've been cleaning up and putting my stuff on github all week...
It should now start to actually be useful. I still need to put up Glass (a lot of work ahead) and some of the projects which tie it all up together, but at least the files are now starting to appear and you can start collaborating with me more easily if you want to.