World: r3wp

Cool. :-)

The gtk-widgets.exe demo is really cool, it shows both the quality 
of the binding and the dialecting possibilities of Red/System (kudos 
for Kaj for inventing it!). Kaj really pushed it very far...and this 
is only v0.2.2 of Red. ;-)

Agreed. I tried to combine a GTK with a ZMQ.... I start to get collisions 
on #includes.      Is there an #include/check option that I didnot 
see in Section 10  http://static.red-lang.org/red-system-specs-light.html#section-10.2

No /check option (is that an option from Ladislav's #include?).

Collisions: we are currently lacking modules in Red/System, I plan 
to introduce them at some point, I'm waiting to go deeper in Red 
runtime implementation first to figure out the adequate approach 
for modules support.

Yes Ladislav's gem ...  include/check prevents scripts from being 
re-included (included more than once).   http://www.rebol.net/wiki/INCLUDE_documentation

IIRC, there's already such feature built in Red/System preprocessor, 
but it's based on absolute paths of included files.

I will try your example of including both GTK and ZMQ to see if something 
is going wrong in the preprocessor.

Harking back to the discussion of Red strings, it might interest 
you to know that the SMS character set uses the 0 position for the 
@ character. Just one of many character sets that won't work with 
C strings. C string support is good for Red/System apps that have 
to access C string library functions, but is a bit too limiting for 
Red itself.

I never planned to base the Red string! type on the Red/System c-string! 
type. All Red datatypes will have their own specific implementation. 
In some cases, for the sake of optimization, we should be able to 
substitute some Red scalar values to Red/System scalar values (mainly 
integer! in fact).

to => with

The current Red memory allocator is already providing the low-level 
layer for storing those Red values, but the datatypes constructors 
are not  implemented yet.

That should be my next step once I finish the ARM port.

I was just going through the SMS character set standards to see what 
characters were supported. It's interesting that you can send REBOL 
or C-like code, though you might need to escape some characters; 
to send Lisp code you need to not use macros since the ` character 
isn't supported. One of the surprises is that there is an additional 
standard where you can send UCS-2 (for those Lisp macros, or Perl), 
but you are limited to 70 characters and not all phones and SMS gateways 
support that type of thing.

I wonder if Twitter's character set is similarly limited, since it 
was originally an overlay service on SMS, IIRC.

Interesting, but I guess that a specific data encoding would be more 
appropriate than plain REBOL or C? Something like the Golf dialect 
(wrote by hostilefork?).

I was mostly interested in code sharing over text messages, but something 
like AltME or a code editor on my phone would be invaluable. A code 
editor that can send code snippets over SMS or other sharing services 
sounds interesting. I only mention this in this group because Red 
looks like it will end up on my phone before R3, barring a miracle.

Though, technically, I might be able to get Topaz running on the 
phone even quicker...

I guess that Topaz should already run on it, have you tried the Topaz 
demo URL?

Not on the phone yet, but I'll try that today :)

In case you've missed it, you can already run this simple Red/System 
HelloWorld app on your Android phone: http://static.red-lang.org/android-hello.jpg

And full Red/System apps very soon.

Nice :)

What program did you use to run the remote app?

This one: http://gimite.net/en/index.php?Runnative executable in Android App

Do you want to make a QNX port as well?

Thanks for fixing that bug in the Windows version, Doc. I'm developing 
on Linux, so I seldomly test such things

It was a bug occurring only in rare cases, I'm glad I had the occasion 
to spot it.

QNX: if you're thinking about BlackBerry support, why not. But as 
BlackBerry has a decreasing market share, I am not sure that would 
be a relevant target to support in a year. Anyway, iOS is second 
on my list of mobile OSes to support (if we can find our way through 
that "fortress").

Thank you for all your continued work!

Thank you for your kind support Nick.

red/system running on another phone:
http://twitter.com/xearl/status/138413355126886400/photo/1/large


that's a hello world binary (using libc) compiled with red/system 
running on a nokia n9.

(inside a terminal. for those not so familiar with linux: the first 
two lines are the call of the binary and the resulting output. the 
rest is just platform porn.)

Cool. Is that an unmodified Linux target?

I mean, would it run on other Linux ARM machines?

Yes :)

That's Red/System's vanilla Linux-ARM target, for which we now have 
basic library imports working.

That's great

Is there still GTK on MeeGo, or did they drop it completely for Qt?

purely qt. i didn't yet look if the gtk libs are even available at 
all.

makes ui bindings extremely annoying, unfortunately. but a simple 
wrapper that bootstraps you into GL might be an option.

Bummer. I'd hate to do all bindings double

http://en.wikipedia.org/wiki/MeeGo#Handset

The Handset UX is based on Qt, but GTK+ and Clutter will be included 
to provide compatibility for Moblin applications.

meego is dead in the water anyway, i fear

intel and nokia split up. intel's way forward is now called "tizen"

GTK support seems to depend on the device, and not include the N9

the n9 is not really "full" meego

it's a maemo/meego mix nokia dubs "meego/harmattan"

but the nokia side of things is unfortunately all rather dead now 
:)