AltME: Announce

Messages

Gregg
The big day has finally arrived. We just launched our Kickstarter campaign for The Future Soon, our Broadway style sci-fi musical. You can find it at http://kck.st/15vWOjA.
This is what has taken me away from things here so much lately. Getting the campaign up doesn't mean I'll have more time yet, but it's a step in that direction. If it succeeds, then I'll be busy mounting the show, but have made other adjustments that I hope will give me more time for Red and REBOL.

NickA
I made a 1/2 hour video introduction for the Merchants' Village Consignment software:   http://youtu.be/-HF45N_W5bI

Kaj
More improvements to the 0MQ binding for Red and Red/System, to support multi-part messages, from our Respectech project.
http://red.esperconsultancy.nl/Red-ZeroMQ-binding/dir?ci=tip
SEND & RECEIVE are back, as simplified Red wrappers over the more efficient send-string & receive-string Red/System ROUTINEs. 0MQ often creates multi-part messages under the hood, but they can now be handled manually when needed. There is now send/part which sends a message part. SEND sends the last (or only) part. To handle the other end of the transmission, both Red and Red/System now have a message-tail? function, which determines whether the last part of a message has been received, or whether more parts are still to follow.
Kaj
To demo Red and 0MQ tomorrow for systems development and networking students, I enhanced the ventilator example for distributed supercomputing to allow the ventilator to send arbitrary Red code to the worker processes:
http://red.esperconsultancy.nl/Red-ZeroMQ-binding/dir?ci=tip&name=examples
A Red expression can be passed on the command line. If the results from the worker processes are numbers, the sink process will total them up:
0MQ-ventilator "random 100"
Kaj
I've updated my binary Red(/System) downloads for the latest 0MQ binding and examples, so that the interpreter consoles can run the examples from the source code:
http://red.esperconsultancy.nl/Red-test/dir?ci=tip
As always, here's the guide to get all files with Fossil:
http://rebol.esperconsultancy.nl/documentation/how-to-use-Fossil.html
and here's the link to get a Zip package, where you have to wait two minutes for the server to create the package:
http://red.esperconsultancy.nl/Red-test/zip/Red(System)%20Testing.zip

Ladislav
Endo, and all, I just put Saphirion's RebGUI fork to GitHub:
https://github.com/saphirion/RebGUI
GiuseppeC
Robert, nice to have your REBOL3 version on GitHub.
I have 2 question:
1) is there an "History" text for fixes and improvements ?
2) Is REBOL3 curecore being updated in some way ?

Robert
1) We can extract this from our SVN log. The latest release on our web-site has a change log that's cleaned. And yes, I need to upload a new version and update it. I just don't find the time doing it.
2) The team might answer this better. IIRC Ladislav is quite active in maintaining CC.

Kaj
I upgraded Try REBOL to Red 0.4.0:
http://tryrebol.esperconsultancy.nl
Kaj
I've updated my binary Red(/System) downloads for Red 0.4.0:
http://red.esperconsultancy.nl/Red-test/dir?ci=tip
As always, here's the guide to get all files with Fossil:
http://rebol.esperconsultancy.nl/documentation/how-to-use-Fossil.html
and here's the link to get a Zip package, where you have to wait two minutes for the server to create the package:
http://red.esperconsultancy.nl/Red-test/zip/Red(System)%20Testing.zip
DocKimbel

Kaj
More improvements to the 0MQ binding for Red and Red/System, to support binary messages, from our Respectech project.
http://red.esperconsultancy.nl/Red-ZeroMQ-binding/dir?ci=tip
Binary messages were already supported in the Red/System binding, of course, because Red string! messages are based on them, but now they can also be handled at the Red level when necessary. Red doesn't have a binary! type yet, so they are handled as the original 0MQ messages. Notwithstanding that, the life cycle management of a message is automated. RECEIVE creates a new message. The message can be consumed and cleaned up either by passing it to SEND to route it to another destination, or by using the new function message-to-string to handle the content yourself. To receive a string message immediately, instead of a binary message, you now need to use receive/string. The more efficient receive-string is also still available. Further, both Red and Red/System now have a function empty-message? that tests for a message of zero length. Empty messages are used by 0MQ as markers in multi-part messages. Binary messages can be combined with multi-part messages.

Kaj
More improvements to the 0MQ binding for Red and Red/System, to support polling for incoming messages, from our Respectech project.
http://red.esperconsultancy.nl/Red-ZeroMQ-binding/dir?ci=tip
Polling was already possible, but not directly supported. There is now an interface for a simple form of polling for incoming messages, without blocking to wait for messages to arrive. RECEIVE has a new refinement receive/no-wait that returns immediately when no messages are available. In that case, it returns NONE. RECEIVE now returns FALSE on other errors. There is also a new refinement receive/into that takes the place of receive-string. Both Red and Red/System have a new function empty-socket? that can be used to test if receive/no-wait found no messages, but its use is probably only needed in Red/System. There's also a new function send-empty that creates and sends an empty message, as a marker.
Kaj
The Red binding now also has an end-message function to manually clean up unused messages. These can result from receiving unexpected messages or message parts, for example with the new receive polling.
Kaj
In Red, SEND NONE has the same effect as using send-empty.

NickA
I started converting some of my R2 tutorial materials for R3 Saphir. It's nowhere near done, but at this point should be enough to get absolute beginners using R3:    
    
http://learnrebol.com
    
For anyone with some experience, the code examples at http://re-bol.com/examples.r3 are a quicker way to get up to speed, without the extra prose.
    
I'll try to keep both documents updated together.

Kaj
I added Nick's new R3 tutorial and Arnold's Red video tutorials to Try REBOL in the links section:
http://tryrebol.esperconsultancy.nl

Ladislav
I just updated rebol.org/… to describe how to contribute new tests to the core-tests suite.
Kaj
I've updated my binary Red downloads with the Red objects branch:
http://red.esperconsultancy.nl/Red-test/dir?ci=tip
object!s are now implemented in the interpreter. You can try them with one of the */Red/red* interpreter consoles for your platform. The latest 0MQ enhancements are also in there. You can run the example programs in the interpreter:
http://red.esperconsultancy.nl/Red-ZeroMQ-binding/dir?ci=tip&name=examples
As always, here's the guide to get all files with Fossil:
http://rebol.esperconsultancy.nl/documentation/how-to-use-Fossil.html
and here's the link to get a Zip package, where you have to wait two minutes for the server to create the package:
http://red.esperconsultancy.nl/Red-test/zip/Red(System)%20Testing.zip

Kaj
I upgraded Red on Try REBOL to the objects branch, so you can try objects there, too:
http://tryrebol.esperconsultancy.nl

Last message posted 110 weeks ago.