World: r3wp

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

Tizen will probably include Samsung's reference platform, which includes 
GTK

And Clutter, and EFL... What a mess

Just checked, the only parts of GTK that remain on a stock N9 are 
glib and pango.

Thanks

Switching to Cheyenne project until Saturday, I will do a Cheyenne 
presentation at a PHP event in France on friday, so I need to get 
prepared.

Doc, reading a twitter message - congrats to finishing ARM port stage 
:-)

Well, there's still the fun part to do: debugging ;-)

(that's why I've left the progress bar at 90% in the Roadmap: http://www.red-lang.org/p/roadmap.html)

From REBOL School channel discussion: .Net support for Red is planned 
after JVM support, which will be most probably done in 2012.

I'd like to make the JVM port before the rewrite of Red/System in 
Red, as doing so will certainly require some deep adjustments to 
Red/System compiler and linker, so better have it experienced before 
the rewrite.

experienced: experimented

I've tried including two bindings in one program that both include 
the C library binding, and I can't get it to do a single pass over 
the nested include, either with relative or absoltue paths to the 
C library binding

The first thing it bombs out on is a #L marker that it seems to insert 
into the source to mark line numbers (even though I didn't do a debug 
build)

I will a look at it today.

Kaj: I have just pushed a fix for the problem you've reported.

Great, thanks!

I can confirm that including multiple times works now on Linux

Particularly, Mike's case of using both GTK and 0MQ works now

The WebKit binding is now here:

http://red.esperconsultancy.nl/Red-GTK-WebKit

Great news!

Implemented a separate SCROLL widget in the GTK binding, that can 
be used as a container for other suitable widgets to make them scrollable

Red/System can now compile hello.reds (including the Red/System runtime) 
for ARM, and the resulting binary works fine.

That's ARMv5, isn't it, not ARMv7? On what targets does it and does 
it not run?

It should work fine on all ARM9+ CPUs, which is pretty much any ARM 
platform used these days.

ARMv5, yes. Should work on ARMv5+.

For ppl non-familiar with ARM naming conventions: http://en.wikipedia.org/wiki/ARM_architecture#ARM_cores

So on ARM9, ARM11, Cortex A.

Cores, that is.

As Doc said, that covers most ARM systems in use today (except for 
the original StrongARM (historic; for those who happen to own an 
Apple Newton or Compaq iPAQ) and the current Cortex M microcontroller 
cores.

Wow! Exciting news indeed.

Red/System hello.reds now runs also on Android. If you have a rooted 
device, you can get and run the binary from here: http://sidl.fr/tmp/hello

is there any other possibility than using rooted device?

If you use a native exe loader (like "Run Native Exe"), the ANSI 
escape codes won't be interpreted.

Other possibility, yes, just install this app: http://gimite.net/en/index.php?Runnative executable in Android App

as for Cortex MCUs -  are those too low level MCUs, or is it just 
a matter of some work to do?

I haven't check their specs, but I guess that the current ARM backend 
should work for them too.

Isn't it possible to change debug level durring compilation? I would 
like to see the traces for my code, but not for the included runtimes.

It is

[-v <integer!>]

How it's supposed to be used during compilation? When I use:
do/args %rsc.r "-v 3 %tests/hello.reds"


i can see a lot of traces for files like %runtime/common.reds %runtime/lib-C.reds 
%runtime/win32.reds %runtime/utils.reds which I'm not interested 
in.

Not sure what the levels mean. I suspect the runtime can't be excluded

(I'm just trying to jump in and understand what the compiler does 
and in which steps) I know they must be there to create the app runable 
but I don't need such a app at this moment:)

It's probably more easier for me to add some probes here and there:)

You can use -v 6 and echo all output to a file and use a text editor 
to review the output for your code.

Disabling debug output for runtime files sounds like a useful option 
though.

(and it should be the default option)