World: r4wp

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.

I updated the Try REBOL site to the latest red-core:

http://tryrebol.esperconsultancy.nl


I've moved the About button behind the Red button, as this function 
is now executed in Red by default.


Also fixed several bugs in the site. Thanks to Graham for reporting.

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.

Pushed the first take of the modular RebolBot into it's own repo.
https://github.com/gchiu/rebolbot

Online Red compiler: http://bircomteknoloji.com:8181/

Runs on Cheyenne on Windows, compiles using rebol.exe (v2.7.6) as 
CGI.

We're online again, but the network company managed to unfix our 
fixed IP address - again. Our domains may well remain unreachable 
for several more days

If you need access to our source repositories or Try REBOL, you can 
temporarily define our hosts locally on your system to our current 
IP address. For example in the /etc/hosts file on Unixy systems:

188.142.58.98 red.esperconsultancy.nl
188.142.58.98 rebol.esperconsultancy.nl
188.142.58.98 tryrebol.esperconsultancy.nl

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. :-)

great

http://www.nlpp.ch/	English web-site for our main product we do with 
R2. Feel free to spread the word.

Feedback regarding typos etc. welcome (the vimeo videos are not working 
at the moment).

@ Robert:  Holy crap!

(about Android release)

(about Android release)

I though you meant nlpp.ch ;-)

Awesome work on R3 Android with graphics!!!

Hello, I started a wiki about only the Rebol 3 source: https://github.com/angerangel/r3bazaar/wiki/Source-explained
, may you help me? ;-)

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.

I can't test the encoding on Mac, so I would be interested to hear 
if it works there, especially UTF-8 file names

https://twitter.com/saphirion_dev/status/328539090167427072/photo/1

Great work everyone!

I'm making another $500 matching donation offer for the Saphirion 
R3 port, till the end of May 2013.  Please help keep up the progress.

NickA: Many thanks for your support!

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. :-)

Welcome back editor:  http://rebol2.blogspot.it/2013/05/r3b-update-welcome-back-editor.html

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

You can now write REBOL 3 extensions in Red. I've added a Red example 
to the existing Red/System example:


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

This currently still requires the dyn-lib-emitter branch of Red.

Here's an example of a session:

r3
>> import %hello-REBOL-3-extension.dll
>> hello
Hello Red REBOL extension!

You have to compile the example with the -dlib parameter to get an 
extension library

Here's a complete JNI binding from Red/System to Java:

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

The example extension library can be compiled similarly to Doc's 
Java bridge

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

PicoGL is included in Syllable Desktop, but there's a symbol loading 
issue that currently prevents the Red/System programs from loading 
the PicoGL library there

If you want to compile PicoGL, on Syllable Server or some other Linux 
system, you can use the Syllable build system. Here's the build recipe:


http://syllable.cvs.sourceforge.net/viewvc/syllable/syllable/system/apps/utils/Builder/packages/PicoGL/

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.