AltME groups: search

I think this is the best introduction to REBOL that I can come up 
with.  Many dozens of tiny application examples that should turn 
some heads, especially for newbies, kids, and the non-programmer 
crowd:  http://easiestprogramminglanguage.com

The R2/Forward project has been moved to Github, including an import 
of the DevBase change history by Andreas.
Go here: https://github.com/BrianHawley/r2-forward


No issues or wiki yet, and it needs a lot of work. Still, it's a 
start! Discuss stuff in !REBOL2 here until we have something better. 
I have some improvements to make right away, not the least of which 
is making sure that the license is compatible with R3 and Red.

At a request, I upgraded R3 on Try REBOL from 2.99.111, the last 
official RT version, to Andreas' current build, the ongoing 2.101 
series. Not many changes, but some bug fixes.

http://tryrebol.esperconsultancy.nl


Graham programmed a nice bot for Stack Overflow chat that is able 
to call the Try REBOL web service to execute code examples and post 
the result.

Yes it is nice, and you're avoiding trying it out. I thought you 
were going to drop by the SO chat at some point. Or have you been 
in there under a different name?

I fixed the bug that was breaking cURL networking on Windows:

http://red.esperconsultancy.nl/Red-cURL/dir?ci=tip


I've updated the binaries. This fixes READ in common/input-output, 
console-pro, GTK-text-editor, GTK-browser and RedSystem/read-web-page:

http://red.esperconsultancy.nl/Red-test/dir?ci=tip&name=MSDOS


The binaries for all platforms include the latest Red enhancements, 
particularly support in the interpreter for function creation at 
runtime and execution of those functions that are not compiled and 
thus only have source available. This enhances console-pro, GTK-IDE 
and GTK-browser:

http://red.esperconsultancy.nl/Red-test/dir?ci=tip

I missed making a donation to Red last month, so I will make up for 
it by doing a matching challenge this month. I will match donations 
to Red, up to USD$200, for donations made between now and the end 
of the month.

The audio example is now forced to open a small borderless window 
on Windows. It shouldn't be visible, but there will be an icon on 
the task bar now, and it will probably appear in the window switcher

I've updated the Red test binaries with the latest Red features, 
including the new support for the file! type:

http://red.esperconsultancy.nl/Red-test/dir?ci=tip


As a reminder, here are instructions for downloading them in one 
go:


http://web.syllable.org/news/2012-11-18-20-47-Red-high-level-programming-language-first-alpha.html


All programs for Syllable, Linux and Windows are supposed to work 
now. If you want to help improve the quality of the upcoming Red 
release, please test them and report bugs you find.

I updated our Redsite for the latest Red features, specifically runtime 
function creation in the interpreter (which executes the Redpages):

http://red.esperconsultancy.nl/index.red

I added a simple IDE example to the list of apps:

http://red.esperconsultancy.nl/examples/IDE.red


It's a cross between the standalone GTK-IDE example and Try REBOL; 
basically Try Red written in Red itself. There are two main areas: 
one for editing your code and one for showing the result. Since it 
runs on your computer, unlike Try REBOL, it keeps state between execution 
of code snippets.


To browse the site and the apps you need the latest binary version 
of the GTK-browser. See above.

Just donated 50 EUR to Red, so that Gregg might match the donation. 
Hopefully you don't mind using this channel, it has low noise ratio 
and might inspire others to follow :-)

Some people have wanted to do timing with Red. That was already possible 
with wall clock time, but I've added a new function get-process-seconds 
to both Red and Red/System to get the CPU time used by the process. 
Be aware that on Windows, this still uses wall clock time:

http://red.esperconsultancy.nl/Red-C-library/dir?ci=tip

I've included examples in the Red Fibonacci examples.

To support the OpenCV binding, I've split the C library binding for 
Red into an ANSI standard base and a BSD extensions part:

http://red.esperconsultancy.nl/Red-C-library/dir?ci=tip


Instead of %C-library/C-library.red and %C-library/C-library.reds 
you should now #include %C-library/ANSI.red and %C-library/ANSI.reds.


%C-library/BSD.reds includes %C-library/ANSI.reds automatically and 
provides new functions NaN?, finite?, infinite? and infinity-sign-of. 
It can only be used on platforms that have them.

Because the Red compiler doesn't support preprocessor conditionals, 
I have split console-pro into red, red-core and red-base, to be able 
to supply different functionality per platform:


http://red.esperconsultancy.nl/Red-common/dir?ci=tip&name=examples

They each include different extra bindings:
red-base: ANSI C library, cURL
red-core: red-base + SQLite
red: red-core + GTK+


I've updated the test binaries. Different versions of the red console 
are supplied for different platforms:

http://red.esperconsultancy.nl/Red-test/dir?ci=tip


I rewrote the multi-line parsing in the console to be more accurate 
and straightforward.

In the new red consoles, I implemented ABOUT and LICENSE.

The ReadLine library is available for Android, but hard to install, 
so I made an attempt to build a red console for Android that doesn't 
use it. I have no idea if it works, so I would really like someone 
to test it:


http://red.esperconsultancy.nl/Red-test/doc/trunk/Android/Red/red-core


There may also be issues with the paths to the cURL and SQLite libraries. 
They should be included in Android, but if the paths are different, 
I would like to know that, too. Remember Doc's blog about how to 
start Red executables on Android:

http://www.red-lang.org/2011/12/arm-support-released.html

Now that */Red/GTK-browser in the test executables has been updated 
for the Red 0.3.2 release (and the features and fixes since then), 
I have updated our Redsite to match:

http://red.esperconsultancy.nl/index.red


All listed Redpages and apps work now, and several details have been 
smoothened out.

An interesting thing to try is to enter "stats" and then press the 
Compare button. It will report memory usage for each language.

Announcing INCLUDE update, changelog:

/LINK now uses MOLD/FLAT on Henrik's and Robert's request

Tomorrow, Wednesday 10, our Internet connection will be down for 
scheduled network maintenance. During most of the European daytime, 
our Red and REBOL web sites will be down. This includes Try REBOL 
and our source code repositories. Our static web sites will be partly 
served by CloudFlare.

I've temporarily rerouted our most important domains to our current 
IP address, so they work again, but they will break again when our 
network provider changes the address back.


Try REBOL works again, but it being half down allowed Graham and 
Andreas to find a bug in R3's HTTP handler. :-)

Here is first *alpha* of Rebol3 with graphics on Android: http://development.saphirion.com/experimental/r3-droid-view.apk

Current features:
- AGG based compositor
- Basic windowing support
- Working DRAW dialect
- Very basic input event handling (DOWN, UP, MOVE, CLOSE events)

- "Menu" button now sends "escape" to the interpreter so loops etc. 
can be easily interrupted

- "Back" button closes opened windows, if no window is open it quits 
interpreter

- Embedded simple "demo game", just type DEMO in the console and 
have fun


Note this release is very early alpha so expect unstable situations 
or even crashes. Feel free to report bugs or any other feedback.


This gets us one step closer to be able to create Android apps with 
Rebol. Simple, small, fast. :-)

Carl has mentioned that he is willing to discuss handing over control 
of the Rebol websites, likely to a Rebol community working group. 
 AdrianS (I believe) requested this, and I passed it on to Carl. 
 Just FYI.

I implemented UTF-8 output support for Red. I ended up writing optimised 
versions based more on the Red print backend. I integrated them in 
my I/O routines and made heavy performance optimisations. Thanks 
to Peter for leading the way. There are the following Red/System 
encoders embedded in %common.red:

http://red.esperconsultancy.nl/Red-common/dir?ci=tip


to-UTF8: encodes a Red string into UTF-8 Red/System c-string! format.

to-local-file: encodes a Red string into Latin-1 Red/System c-string! 
format on Windows, and into UTF-8 on other systems. This yields a 
string suitable for the local file name APIs. Latin-1 can be output 
as long as it was input into Red via UTF-8. Non-Latin-1 code points 
cannot be encoded in Latin-1 and yield a NULL for the entire result.


These encoders make use of the Latin1-to-UTF8, UCS2-to-UTF8 and UCS4-to-UTF8 
encoding functions. An example of their use in the Red READ and WRITE 
functions is in %input-output.red

I used the new encoding functions in all my Red bindings: those for 
the C library, input/output via files and cURL, 0MQ, SQLite and GTK+. 
In as many places as possible, data marshalled to the external libraries 
now supports UTF-8. File names on Windows support Latin-1. Files 
and URLs are always read and written as UTF-8, including on Windows. 
Red does not support loading Latin-1 strings.

I've updated the binary downloads. The red console interpreters and 
all the Red examples include the above encoding support now, and 
all the latest Red features:

http://red.esperconsultancy.nl/Red-test/dir?ci=tip


For example, the Red/GTK-text-editor now supports writing UTF-8 files 
with UTF-8 or Latin-1 names.


I've added an MSDOS\Red\red-core.exe for Windows 2000, because the 
GTK+ libraries in red.exe require Windows XP+.

I've also improved the multi-line parsing in the consoles again. 
They now recognise literal strings in double quotes, literal characters 
and comments.

Cross-Post from Android group:


New release of Rebol3 with graphics on Android: http://development.saphirion.com/experimental/r3-droid.apk

Changes:
-enable CTO and OTC functions
-fix window offset
-fix image! / loaders pixelformat color order
-fixed close button action (RL_Init failed?)
-improved WAIT
-added clipping(slow atm but works)
-added RESIZE/ROTATE events
-improved JNI calls synchronization
-added native keyboard input
-updated built-in R3-GUI version



Note this release is very early alpha so expect unstable situations 
or even crashes. Feel free to report bugs or any other feedback.


This gets us again one step closer to be able to create Android apps 
with Rebol. Simple, small, fast. :-)

Following in the footsteps of Red ( https://trello.com/board/red-programming-language/51387ada4e1ba9b86b001141
) 


we have also started a Trello page for R3 ( https://trello.com/board/main-board/518dd9128fbdf0fc6a0004cf
)


to track who is doing what ... Feel free to join Trello and let any 
of the current members know if you wish to be added to the project

I finally got my OpenGL binding for Red/System in a form suitable 
for publishing:

http://red.esperconsultancy.nl/Red-OpenGL/dir?ci=tip


Currently, the only available backend is for PicoGL, which does software 
rendering with the TinyGL library and shows it through SDL.

I ported two of the PicoGL examples to Red/System: GL-spin and GL-textures. 
I've updated the binary downloads and added them, but they're currently 
mostly usable on Linux:


http://red.esperconsultancy.nl/Red-test/dir?ci=tip&name=Linux/RedSystem

Not sure if this is useful for Android, but the JVM JNI interface 
can be loaded as a library from a normal executable:


http://docs.oracle.com/javase/6/docs/technotes/guides/jni/spec/invocation.html


I've added a static JVM binding to my JNI binding for Red/System, 
so Java can be loaded and controlled from regular Red executables:

http://red.esperconsultancy.nl/Red-Java/dir?ci=tip

I made an SDL backend for my Red/System OpenGL binding:

http://red.esperconsultancy.nl/Red-OpenGL/dir?ci=tip


SDL with OpenGL is available on most platforms, and depending on 
your system, it supports hardware acceleration. So you can now choose 
between software rendering with the TinyGL engine through PicoGL, 
and hardware acceleration or software rendering with the Mesa3D engine 
through SDL. The two example programs can be compiled with either 
backend.

I made an OS-Mesa backend on SDL for my Red/System OpenGL binding:

http://red.esperconsultancy.nl/Red-OpenGL/dir?ci=tip


This does off-screen rendering in a memory buffer using the Mesa3D 
engine and then displays the result using SDL. Somehow I can't get 
it to work on Linux, but it's the first time I can use Red/System 
for OpenGL on Syllable. It circumvents two problems: the PicoGL library 
expects application functions that Red doesn't export, and Syllable's 
SDL port doesn't support the official OpenGL backend, so those routes 
both don't work. For most other targets than Syllable, the official 
SDL backend can be used.


It's also the first time that I have used my Mesa3D port to Syllable. 
I couldn't display the output before, because there is no display 
driver for the current Mesa3D versions for Syllable, just the standard 
off-screen rendering. It works great, even though it does only software 
rendering. PicoGL is a bit faster, but Mesa3D is a much more modern 
and complete OpenGL implementation.

I've added binary downloads for all Red platforms to the test repository 
of the two OpenGL examples for the Red/System binding: GL-spin and 
GL-textures.

http://red.esperconsultancy.nl/Red-test/dir?ci=tip


Test reports welcome. All platforms should work in theory, but so 
far I have tested Syllable and Linux x86. You need to have SDL and 
OpenGL installed (in 32 bit versions). SDL is included in the repository 
for Windows, and OpenGL should be included in Windows.

If you use the download.r from the repository (with Fossil), you 
will now get the source code for the OpenGL and Java JNI bindings, 
together with all my other bindings

I added a similar workaround for ELF libraries as in Doc's JNI bridge 
to my R3 and JNI bindings:

http://red.esperconsultancy.nl/Red-REBOL-3/dir?ci=tip
http://red.esperconsultancy.nl/Red-Java/dir?ci=tip


R3 extensions written in Red/System and Red now work on ELF platforms 
such as Syllable and Linux. Should work on Android, too, at least 
when Doc has tested libraries there.

https://github.com/saphirion


We are going to push some of our stuff to Github. This is intended 
so that peple from the community can use and enhance our stuff and 
submit pull-requests to us. Those pull-requests will be reviewed 
by the Saphirion team, and if accepted, the changes are merged into 
our main line. So, it will be included in our next offical release 
and published via our web-site.

The structure for documentation is:
documentation/ 	= stuff that works on R2 and R3
documentation/r2	= stuff for R2
documentation/r3	= stuff for R3

So, feel free to do whatevery you want with this stuff and help to 
improve it.

I fixed the calling convention for the OpenGL library that's included 
in Windows, so the Red/System binding works there now:

http://red.esperconsultancy.nl/Red-OpenGL/dir?ci=tip

I also fixed the binary downloads GL-spin and GL-textures:

http://red.esperconsultancy.nl/Red-test/dir?ci=tip

Another "batch" of doc files committed. See e.g.:


https://github.com/saphirion/documentation/blob/master/r3/whatsnew.mdp

, which tries to compare R2 and R3, which was a popular request.

I dropped the cURL dependency from my red-base distribution. This 
means that it now only depends on a few libraries that can be expected 
to be included in all platforms. This version of the Red interpreter 
can now be used on Windows as a single executable, without any extra 
libraries. The Windows version red-base.exe is here:

http://red.esperconsultancy.nl/Red-test/dir?ci=tip&name=MSDOS/Red


It has versions of READ and WRITE for local file I/O, but no network 
I/O. It also has the other functionality from the C library, such 
as INPUT, ASK, GET-ENV, CALL, NOW and RANDOM, but for more functionality 
you still have to use red-core and red, and download the extra libraries 
for Windows.

Ok, Carl is now on Stackoverflow chat .. just need to upvote him 
somehow so he can actually talk!
http://chat.stackoverflow.com/rooms/291/rebol-and-red

I'm happy to announce that we reached a major milestone and can release 
a bunch of new things. All the different versions have been merged 
into one code base which makes things easier for us. This was possible 
because the new 'retargetable' graphics subsystem was finished. This 
allows us to port R3 to other platforms much easier. Next target 
Linux. The release in detail:


R3-GUI: Quite a lot of fixes and enhancements. Thanks for all the 
feedback. The main milestone we achieved was to switch to a resolution 
independent sizing system. This will scale your app widgets to look 
the same on different display densities. It's a must have for mobile 
apps. Next for R3-GUI is to create a simple mobile style set. Fruther, 
we are going to push the source code to GitHub. We need to setup 
a bridge to our internal SVN repository, so expect some back and 
forth on Github before we are stable.	Anway feel free to help making 
R3-GUI better and better.


Android: This release is now mostly the same as the windows release. 
So, yes, it's now possible to do R3-GUI apps on Android. I'm going 
to try to run Treemapper on it. Type DEMO to see the new R3-GUI version 
and widget scaling feature. Post as much screenshots / pictures of 
your phone as you can :-)


R3/Saphir: New version for windows with bug-fixes are released as 
well. Please see the change-log on our web-site for details.


Thanks to all the team for the great work! I really think we are 
close to have a very good and stable base with R3 and R3-GUI. Looking 
forward to see more and more people joining and becoming part of 
it.

Links:
http://development.saphirion.com			(Change Logs, Downloads, etc.)
http://development.saphirion.com/experimental	(Android)
https://github.com/organizations/saphirion		(Documentations)

Hi,

 I paste the link: https://github.com/organizations/saphirionin Firefox 
 and the main page of GitHub open. I see no Saphirion repository.

Announcing changes to Saphirion doc:


Function arity documentation and Argument passing styles documentation 
now adjusted to document both R2 and R3 versions. See

https://github.com/saphirion/documentation

Robert, thank you for the improvements and progress with Android 
(sorry, I've been away from AltMe for a while)

I'm happy to announce that we made good progress regarding the Android 
R3 encapper.


A major breakthru in the multiple-app generation has been made (thanks 
to Andreas for ELF format hints). Now it is possible to create encapped 
apps with unique app-id. Such apps can be recognized properly by 
the Android OS and also accepted on the Google Play market.


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 ;-)


There are some glitches we are going to fix and than the encapper 
is ready for production.

My Redis scheme was updated heavily and I hope it's ready for use 
by others. You can find it here: https://github.com/rebolek/prot-redis

I changed the Red 0MQ interface to optimise the memory use during 
receiving of messages:

http://red.esperconsultancy.nl/Red-ZeroMQ-binding/info/2a1541af57


SEND and RECEIVE have been renamed to send-string and receive-string, 
because they currently handle messages as UTF-8 text. When Red gets 
a binary! type, versions for binary messages will be added, and there 
will probably be type agnostic SEND and RECEIVE wrappers again. Previously, 
you used

message: receive socket


to receive a string message. Now you pass a premade string! (similar 
to call/output in R2):

message: ""
receive-string socket message


This means that you can choose between creating new strings for each 
message (with COPY) or reusing the same string. In the latter case, 
some Red/System code in receive-string makes sure that no extra Red 
memory is used, and that all used system and 0MQ memory is freed 
again. By optimising memory use, this also improves performance of 
message throughput.

This work will be paid for by Respectech as part of an assignment 
I'm doing for them. As far as we know, this is the first commercial 
assignment done with Red.


I'm implementing a network server that needs to run for long periods 
and handle relatively large numbers of requests. This is tricky because 
Red has no garbage collector yet, and the memory allocator doesn't 
handle large series yet. We have been testing the memory system to 
scale it, and Doc has fixed an allocator bug so that series can now 
be twice as large. I've also found and reported seven other bugs 
so far.


The results are very encouraging. The memory system is reliable in 
my stress testing. It can use all the memory available in a machine 
for the contents of series. In the default configuration, one series 
can have a maximum content of 2 MB, or 131070 values for a block!. 
This can be enlarged, basically at will, by compiling your program 
with customised allocator settings.


To reduce the amount of memory that currently cannot be reclaimed 
by garbage collection, I am reducing the number of series generated 
during the handling of each server request. This can be done within 
the same Red program, because low level optimised Red/System code 
can be inserted anywhere. I am down to only a few hundred bytes per 
handled request, and the memory budget of the server is a GB, so 
the Red 0MQ server will be able to handle several million requests.

For relevant platforms, I added extra versions of my Red interpreter 
console distributions to my downloads:

http://red.esperconsultancy.nl/Red-test/dir?ci=tip


They provide versions that include my 0MQ binding for messaging. 
Previous interpreter distributions didn't include it, because on 
most platforms, you have to install the 0MQ library as an extra. 
Further, people may need 0MQ with the GTK+ GUI binding, or without 
it on servers and embedded systems. So there are two new distributions 
in each platform folder:

*/Red/red-core-message
*/Red/red-message


red-core-message is meant for servers and includes bindings for the 
C library, cURL, SQLite and 0MQ. In addition, red-message also includes 
the GTK binding and is meant for GUI programs. For Windows, most 
of these interpreters are in the MSDOS/Red/ folder, but I also added 
a version that is meant to start scripts for GUI programs, so it 
doesn't open an extra console window:

Windows/Red/red-message.exe

In addition to these added programs, the existing interpreters and 
other programs have been rebuilt with the latest Red enhancements, 
including the doubled maximum size for series.


These new Red interpreters are candidates to be used in filming and 
streaming the presentations on the DevCon in Montreal.

https://github.com/saphirion/includerepository created, containing 
the %include.r and %include.mdp files

Added 2 more video's to the RedRebols channel http://www.youtube.com/channel/UC4UikCida6olTyowsi5JyyA

I forgot to tell about not requiring a specific return, not needed 
to declare types and use of normal naming is encouraged and the automatic 
casting of the return value. Need to make a [3.5] too someday..

I'm happy to announce that Doc and I got the first Red/System kernel 
driver working, for Windows. This is Doc's second kernel driver, 
and my first, and also my first real Windows program, so it took 
a few weeks to figure it out. This new ability of Red is sponsored 
by Respectech. Our test driver just loads and prints a Hello World 
style message that a kernel debugger can view, but I will be developing 
the driver into the functionality we need for our Respectech project. 
I will post the code of the test driver in the Red group.

You will get a driver.sys file that you can install, start, query 
and remove like this, from a Windows account with administrative 
rights:


sc create hello-Red type= kernel binPath= C:\full\path\to\driver.sys
sc qc hello-Red
sc start hello-Red
sc query hello-Red
sc delete hello-Red

To view the debug message generated by sc start, you need to install 
a (kernel) debug tool such as DebugView, and enable kernel debugging 
in the Windows boot options.


Other than that, you should see sc query showing the driver as running.

Red has a new platform, Android for x86 processors, so I added it 
to the downloads of example programs:

http://red.esperconsultancy.nl/Red-test/dir?ci=tip


The Android programs for both ARM and x86 include the recent fixes 
to the Red Android port, so they have a better chance of working 
now. I would still like someone to test them.


All example programs for other platforms have also been rebuilt with 
the latest Red enhancements and fixes.

Now that generation of shared libraries and drivers is available 
in Red's mainline, I have extended my build script to build libraries 
and drivers. I have added examples of a Windows kernel driver and 
libraries for R3 extensions in both Red/System and Red to the downloads 
repository mentioned above. The R3 extensions are available for all 
platforms to test, but the Windows kernel driver is here, as hello-kernel-driver.sys:


http://red.esperconsultancy.nl/Red-test/dir?ci=tip&name=MSDOS/RedSystem


See above how to start the driver. Instructions for using the R3 
extensions are in the headers of the source code:


http://red.esperconsultancy.nl/Red-REBOL-3/dir?ci=tip&name=examples

I have extended the Red/System null driver for the Windows kernel 
into a null mini-filter driver. It now registers itself as a mini-filter 
and imports functions not only from the kernel, but also from the 
FilterManager driver, so it is now in a hierarchy of drivers. It 
now responds to a stop command, so you can stop running the driver 
like this:

sc stop hello-Red


I will set up a new repository later to publish the Windows kernel 
and FilterManager bindings and examples.

We did a new Saphir / R3 Andoid release.

Changes:
-fixed input text renderin bug

-reworked misc internal threads synchronisation issues to fix possible 
dead locks
-added ACTIVE, INACTIVE events
-added horizontal native scrolling for layouts wider than screen
-fixed screen rotation
-updated demo script (just type DEMO in the console)
-fixed BROWSE bug

-added .r3 suffix to be able open this type of R3 scripts automatically
-other smaller internal fixes


If you want to test it on your phone just run the console and type:

do http://development.saphirion.com/experimental/demo.r


ATTENTION: We changed the directory layout a bit. You find the Andoid 
release here:

http://development.saphirion.com/experimental/builds/android

We added other platforms as well:
http://development.saphirion.com/experimental/builds/

And the root is still:
http://development.saphirion.com/experimental/


Next Wednesday I will give a short talk about our porting efforts 
here via Web-Cast:  http://www.vksi.de/sneak-preview/17072013-android-qs.htm
(German)

Some additional notes:

-you can run the demo on Saphir / R3 Andoid just by typing DEMO in 
the console

-the Linux, OSX-PPC and OSX-Intel "View" binaries needs 32-bit version 
of freetype2 library (also included in the specific build folders)

-the Linux, OSX-PPC and OSX-Intel "View" binaries are currently able 
to render DRAW dialect to image! (using the DRAW command). We'll 
be working to get full graphics support on the metioned platforms 
in the near future.

I upgraded the 0MQ library for Windows that is included in my Red 
downloads from version 2.0.10 to 2.2.0:

http://red.esperconsultancy.nl/Red-test/dir?ci=tip


Timeouts are now available for sending and receiving messages, and 
the OpenPGM library is included for multicast networking. Thanks 
to MikeL for noting the newer binary builds for Windows.

New World alpha release at
https://github.com/Geomol/World


- Added better networking using cURL library, libcurl (OS X and Linux)
- Added tasks incl.:
	- task! datatype
	- task-id! datatype
	- TASKS native function
	- task? and task-id? mezzanines

 - Task support for many functions incl. HELP, SOURCE, FIRST, SECOND, 
 PICK, COMPILED? and DISASM
	- KILL mezzanine to call TASKS/KILL

- Added inter-task communication using SEND and RECEIVE native functions
- Added support for messages to WAIT as: wait 'message

- Added preemptive multitasking using TASKS/TICKS to specify number 
of Virtual Machine instructions per task run (default is 200)

- Added timers for tasks triggered by WAIT native and READ native, 
when reading from url
- Task yield can be achieved by: wait 0
- Changed ;{ } comment syntax to ;( )
- Parens can now span several lines at the prompt
- Added system/console/paren
- Added support for pressing <Esc> to stop execution of main task

- Sending input via pipe to World started with a script will activate 
input without echo and without <tab>-completion etc.. (Not sure how 
and if this works under Windows.)
- Added support for picking 'Re and 'Im of complex numbers
- Better implementation of TRY

- New test versions of IF and EITHER, that can take other than block! 
arguments
- Added more tests

We have pushed our R3-GUI sources to Github. The project was cleaned 
up, old stuff removed etc. So it should be in pretty good shape. 
We keep the GibHub repository in sync with our internal SVN repository. 
We will further take a look at pull requests and take your feedback 
into our main line. You can find the repository here:

https://github.com/saphirion/r3-gui

Thank you very much Robert and your team members for all of your 
efforts. I'll also contribute to your advancement by sending some 
contributions to you very soon. Just waiting for my next pay cheque 
in about 15 days.

using a scheme is a good idea.  then we can add various options to 
how to build them including things like auto naming, manual naming, 
prefixed naming, numbered, and the way it reports if a tmp file already 
exists.

yes link, unlink and lstat are included too.

ok, will include this and CPU_SET ;-)

After the current build streamlining work, I plan to look into better 
stdio and a more versatile "call" next.

Still should be an extension though, since not everyone is running 
R3 on a server. And definitely if it is limited to server platforms, 
or any platform limits.

yes, call is migthy when proper designed. using os.execute and io.popen 
all the times with lua. highly underestimated for it's capabillities 
but not easy to built.

Brian, the posix extension is also to refresh my lost C skills (heck, 
I lost half of rebol in only 6 month I was buys with Lua) and I have 
no claim this extension need to run everywhere nor do I want to pollute 
the rebol way. it's just a component to fill some gaps for serverbased 
processing on linux machines.

>> file-type? %mi.txt
== text
>> file-type? %mi.r
== none


Text is considered a file type in R3, like .jpg and such. I think 
it was intentional, though I'm not sure whether we should continue 
to intend this. We should check with Carl.

Anyone know how to use PUT in http?  And how to use write ?

Hmm.  Will this fail if your locale is not english, and the web server 
is giving dates in enlish?

And nearly 6 years ago

This is a periodic posting of community links along with activity 
levels for discussion dedicated to Rebol and Rebol-like languages. 
The intent is to bring a dispersed community together by providing 
the current list of places where the community gathers along with 
reasonably accurate activity indicators for each place. This list 
will be posted in each location weekly or bi-weekly so that anyone 
dropping by will not have to look far in order to learn where else 
things are happening.


Currently the activity stats are gathered manually and postings are 
also not automated. This will hopefully change as the requisite scripts 
to scrape and post automatically are developed. This updated list 
will eventually be available at http://rebol.comas the site is cleaned 
up post Rebol open sourcing. 


# Chats

## R3 Chat

This is the primary forum for Rebol 3.0. It runs from any Rebol console 
in a text mode, but a GUI version is planned.
- Run R3, type chat and follow the instructions (all platforms.)

- Type "help" for more information or visit R3 DevBase Chat Forum 
(http://www.rebol.com/r3/devbase/index.html).

- To view public messages from any web browser go to RebDev mobile/phone 
interface (http://www.rebol.net/cgi-bin/rebdev-web.r).

- Problems? Please contact Rebol Technologies at (http://www.rebol.com/cgi-bin/feedback/post2.r).
Activity: 4 messages this month


## Rebol chat on Stack Overflow (http://chat.stackoverflow.com/rooms/291/rebol)

- Note that you will need a reputation of 20 in order to be able 
to post in the chat. 

- You can gain this minimal reputation (essentially a spam filter) 
by participating in the Stack Overflow group of sites. 
Activity: 380 messages this week


## AltME Worlds

A private instant messaging system where rebolers hang out 24/7. 
The current world dedicated to Rebol and Rebol-like language discussion 
is called REBOL4
- Get client at http://www.altme.com/download.html
- connect to the 'rebol-gate' world with user/pass, guest/guest
- request account on REBOL4 world in the REBOL4 request group

Web archives of public groups, first to last in the most active world, 
REBOL4, as well as the dormant world, REBOL3:
REBOL4 (http://www.rebol.org/aga-groups-index.r?world=r4wp)
Activity: 286 posts last 6 days
REBOL3 (http://www.rebol.org/aga-groups-index.r?world=r3wp)


# Forums

## Rebol Facebook group (http://www.facebook.com/groups/rebol)
A new special interest group for Facebook users.
Activity: 26 messages this month



## Rebol Google+ community (https://plus.google.com/communities/100845931109002755204)
Activity: 4 messages this month



## Rebol Google Group (https://groups.google.com/forum/?fromgroups#!forum/rebol)
Activity: 43 messages this month



## Synapse EHR Rebol Forum (http://synapse-ehr.com/community/forums/rebol.5)
A web-based forum for R2 and R3, provided by Synapse EHR
Activity: 13 messages this month



## RebelBB France (http://www.digicamsoft.com/cgi-bin/rebelBB.cgi)
A simple forum, written in Rebol, for French speakers.
Activity: 140 messages this month


## Nick's Rebol Forum (http://rebolforum.com/index.cgi)

A micro-forum (just a few lines of Rebol) hosted by Nick Antonaccio. 
(Note: the captcha question is first.)
Activity: 79 messages this month


# Q&A (Question & Answer)

## Stack Overflow questions on Rebol
http://stackoverflow.com/questions/tagged/rebol
Activity: 219 questions tagged
http://stackoverflow.com/questions/tagged/rebol3
Activity: 2 questions tagged

Of course this should be on rebol.com, but that's currently not up-to-date 
and doesn't include activity levels. Any comments, additions, etc?

I've seen this kind of periodic, summary messages being posted on 
several mailing lists and find them helpful and not overly intrusive 
or spammy - thoughts?

the AltME numbers are bogus though - I got those from the web archive 
which shows only the web-public activity (and a non-constant one 
at that, if you hit F5 repeatedly)

I took the liberty of taking AdrianS's posting, reformatted it to 
Markdown (only minimal changes necessary), added IRC, reordered things 
slightly, and updated two few counts.

Here's a rendering of this updated Markdown document to HTML:
http://bolka.at/2012/rebol3/pages/community-radar.html

Here's the Markdown source of the updated document:
http://bolka.at/2012/rebol3/pages/community-radar.mkd

Yes, got a message there saying my browser was not supported and 
I should upgrade my bosses computer.

Same reason I do not develop for Red, because Github does not support 
Snow Leopard any more, and my Mac cannot go further and I do not 
buy a new mac for  github. And the command line I consider too much 
trouble to learn.

Github has a program for Mac for Lion and up

Github p*ssed me off, for when I was on Leopard, there was a program 
for Snow Leopard and I did upgrade then and then demands had been 
pushed up.

and enemy

Some people holds to the saying "if it works for you well, dont try 
to fix it"...I belong to them and don't update apps just because 
'update is available'. I got bitten by updating to 'newer and better' 
version many times.

I think, I'm two OS versions behind on my iPhone, and it says, it 
has 26 app updates for me.

I'm one OS X version behind on my MacBook and found out the other 
day, my Xcode is 'old' too. So what? It works.

I haven't updated my Windows and Linux 'machines' in VirtualBox for 
years.


I just can't waste my time on all this updating to "now even more, 
newer, better". It's rubbish! :)

Writing the NLPP program, one of the very biggest challenges was 
to make a no-hassle upgrade procedure. This was one of the hardest 
things to do and also one of the parts that took up most time to 
code and test.

Something is wrong in all this.


I try to see software as tiny bits and pieces, each doing a certain 
task. Like very simple Lego building blocks. So each piece takes 
some input (like a function does) and produces an output. If that 
piece needs to be updated, then it's because it has some error, or 
that there is a faster way to do, what it already does. If new building 
blocks arrive, because new software needs them, then they're just 
added to the system.


If that is done right, then updating should be very simple and only 
include very little data to be transfered to my system.

Following this thought, maybe all the mezzanine functions in %cortex.w 
(in World) should be separate files in a directory? And the shell 
commands should be separate files in a %libs/shell/ directory.


Reminds me, that I should pick up my database again. It has records 
as separate files.

Can't we make them? :)

some-func: func [input1 input2] [...]	; -> produces some output.


That's isolated, and it should work, even if other functions, it 
depends on, get updated. The task is to define each function/object 
as doing one simple thing.

And then implement a system like Erlang, where every piece can be 
hot-swapped.

We seem to have a somewhat limited dev pool to start with, and most 
of the people capable and willing to work on R3 are also tied up 
elsewhere (to make a living).

Yes, but say I'd poor in $1,000,000 today (hypothetically, I'm trying 
to understand what is needed to accelerate), compared to nothing. 
Assuming Android is  the first step (including encap and device access), 
when woud this be done with and without "unlimited money".

Given money, one of the best uses for it would be to give core developers 
stability to commit, and then build the community, which, to me, 
means providing platforms and toolsets that people see as viable 
alternatives to other languages.

Yes, I'm trying to get a handle on "quite a bit capacity available". 
And then attach a pricetag to it to make it happen.

I would want R3 on Android with GUI, GPS, Camera support. And R3 
64 bit Linux server side ("Core").