World: r4wp

@Arie, wrong group Announce. Bas already pointed this out. (Softwarefreedomday 
is his channel). I do not want to steal viewers from Bas' channel.

The point is I want to use this new channel as a dedicated channel 
for Red (and REBOL) specific video's. I imagine this being used by 
this community to post self-made tutorial video's on. The softwarefreedom 
channel is much broader than this. One does not exclude the other.

Why not use separate channels for Red, Red/System and Rebol respectively 
or conversely using a family name like "Rebol-like languages" or 
"Rebolish" or something similar ? Personally I prefer using separate 
names, even splitting furthermore amongst Rebol2 and Rebol3 ... but 
this is a suggestion only. In the end I also see some specific place 
for Boron, World, and Topaz but then everyone should point to the 
others or to a single "entry point portail" which points and summarizes 
the évolution and differences while it could alos only point to each 
of the specific related websites, as they appear  !!!

May be "Rebol inspired languages"  would be enough ...

We do have #notREBOL for general chat on REBOL alternatives.

@Gregg : I was thinking the group was in search for a new name on 
Youtube, not here, isn't it ?

Bas' existing playlist is a Red playlist. It's just one of the SoftwareFreedomDay 
account playlists

Robert it is a GREAT news! Thank you!

Gerard, maybe I'm confused. I just meant the group here.

Robert, that sounds great. Congratulations to you and the team.

Guess I'll have to consider an Android device at some point now. 
:-)

Robert: "The cool thing with this approach is one really don't need 
anything more than the Android encapper to produce the apk file. 
No need for android NDK, SDK or even JAVA to be installed ;-)"


Do I understand you reimplemented jarsigner, zipalign and the java 
XML binary compiler in Rebol?

The R3Demo1 apk works great on my Motorola running Android 4.1.  
The only minor complaint is that the text doesn't all fit inside 
the window (the "n" in "been").

Doc: basically yes. Currently only the zipalign is used in the encapppign 
process since it is small cli based exe but we might get rid of it 
eventually as well if there is any license collision (but I guess 
not)

Very Cool Robert!

Fantastic!  This gives R3 some basis for commercial use.

@Bo: yes, the text related issues are not yet solved in the current 
R3/R3GUI versions(which also the ecapper uses). But are next on my 
"Android todo list" so you can expect them to be fixed in upcoming 
release.

Good to see you got the redis:// working!

I hope so :) Now I'm going to use it in one web, so I can test it 
in real life.

Cool work Rebolek!

Thanks, Endo!

Awesome. And then some.

Can't wait to free some time and start working with this.

Thanks, Maarten!I hope it will be usable :)

nice work Rebolek.

R3GUI + async http...Nice demo Andreas!

If you don't mind I've added some more 'bells' to your script. Try 
this version: http://rebol.atwebpages.com/tests/r3gui-httpget.r3

To se that the asyncs works nicely, just hit the "download" button 
few more times ;)

Nice addition, Cyphre :)

Can any of this be posted on facebook?

Typo: "sice"

Great work Kaj!

Great work Kaj and Doc!

Thanks for the explanation Kaj, that is most helpful.

A year ago this was beyond expectations. Congratulations Kaj!!

Congrats to all parties! Kaj for the hard-work, and Bo for the courage 
to go with Red/System solution. I would like to know the motivation 
to use Red/System instead of e.g. R3 (my understanding is, that R3 
has 0MQ available too?)

When I saw the opportunity, I had already thought that that might 
be something for Kaj, and now it even turns out he turned it in to 
a Red project too.

@Pekr: Part of the problem was that we needed to hook into the Windows 
kernel and also perform very fast operations because we're monitoring 
tens of thousands of files in real-time.  Plus, Kaj wanted to use 
the project to help Red mature, and I am completely in favor of helping 
in that manner.

In addition, Red has a "lead developer" (aka Doc) so any changes 
that needed to be made to the core language could be made quickly 
by him.  R3 has a strong lead in Saphirion, but they have their own 
priorities to consider.  I haven't been able to discern if there 
is a person outside of Saphirion that could do the same for R3.

(and Red has a Red/System part designed to operate on the same level 
as C, it is compiled)

It is in line with what your site says.

Note that the project is done in Red so far. Only a small piece of 
Red/System was added to the pre-existing 0MQ binding to optimise 
it. I'm compiling the three programs of the project, but because 
they're in Red, they could also run in the interpreter. On the other 
hand, I would expect that to use more memory, so the compiler is 
probably essential to this project, not for speed but for memory 
performance. Also, a custom Red needs to be compiled to scale the 
memory system, so I could compile a special interpreter, but I might 
as well compile the entire program

Next we will try to implement the Windows kernel driver in Red/System, 
but I may still have to use a C version of that

R3 is not practical for me to use, because the target systems are 
Windows. I can test on Windows, but I develop on Linux. I could write 
an R3 script there, but my 0MQ extension for R3 is written in C, 
so I would have to set up and maintain a complete Windows development 
environment to compile it for Windows. Red and Red/System are much 
easier to deal with

R3 is not practical for me to use, because the target systems are 
Windows.
 - this is obviously not true

I develop on Linux when I do for R3

I must have morphed into Ladislav overnight, then

Try rereading my explanation

Thanks to all who helped to get the new version out on github.

Congratulations Kaj!

Thanks. Doc, too; he made room in a tight schedule

Guys, this is great news! My first reaction was to get it posted 
on the MSDN site, but I'm not sure that reducing the need for Microsoft 
tools would be viewed as a positive thing from their point of view. 
It should be, though, since simplifying Windows driver development 
leads to more peripherals/accessories being integrated with the OS. 
It's a win for everyone (well, I guess not for the rabid anti-MS 
crowd). Between this and the similarly simple mobile dev that's coming, 
Red and R/S will be unbeatable.