AltME: Announce

Messages

Robert
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

NickA
I've made numerous updates to http://learnrebol.com
james_nak
Thanks Nick. You've really created a helpful way to learn R3.

Marco
I have updated my latest script:
http://www.rebol.org/view-script.r?script=vid1r3.r3
As of v.0.3.1 I have reached a good degree of compatibility but it is becoming increasingly difficult to add features and correct bugs, especially those regarding "bindological" problems. Please help me.

Kaj
I made fixes to the 0MQ binding for Red(/System) to fully support 0MQ 3. In particular, handling of multi-part messages was broken. It was awkward to find and abstract the differences between 0MQ 2 and 3. The binding still uses 0MQ 2 on other platforms than Windows until common Linux distributions have upgraded:
http://red.esperconsultancy.nl/Red-ZeroMQ-binding/dir?ci=tip
0MQ 4 was recently released. The binding works with it, but doesn't explicitly support the new security capabilities yet.

Marco
I have updated my latest script:
http://www.rebol.org/view-script.r?script=vid1r3.r3
and also files-renamer.r, parse-aid.r and visual-sorting.r that now work on R3 (with vid1r3.r3)

Maxim
started to Add a bit of documentation to Steel applications:
https://github.com/moliad/steel/wiki/Header-box
https://github.com/moliad/steel/wiki/hammer
you should really try out header-box it allowed me to update 30 scripts with very complete headers in a matter of hours with no possibility of errors.  usually, you try to cleanup the headers and every script has some little thing you forgot to do (like put the date, update the license text, or author)
Maxim
Note that I have done a LOT of updates in my various libs in the last week, so if you are using them, now might be a good time to update.

Maxim
just thought I'd share that I did 65 commits to my various Github projects in the last month a record... one I aim to beat next month  :-)

Last message posted 110 weeks ago.