World: r4wp

Pekr: I have set my RPi memory split to 192MB for apps, 64MB for 
video, not memory issues so far.

Pekr: still a lot of details to work on before that, as always before 
a major release.

I think it will take me one or two days for the 0.3.0 release todo-list 
to get done.

That also means, we'll probably postpone floats hardfp ABI support 
for a later release (probably 0.3.1).

Some blog article about what 0.3.0 brings to the table, would be 
nice then, to show ppl what is implemented, what one can do already 
in Red (eventual list of supported dtypes, natives, actions?), and 
what comes next? That would keep ppl motivated ...

Wrinting a new blog entry is part of the todo-list. ;-)

Did not know, that todo-list contains also non-development related 
stuff :-)

Did not know making the to-do list takes two to three days ;)

:-) to do list to get done means, to implement all to-do items :-)

There already was a minimal GTK program with direct GTK calls: goodbye-cruel-GTK-world

That one is crashing.

The issue is probably in 'label related functions.

Yes, so if you strip that down further, you should find the cause

Removing `gtk-append-container` call makes it work.

Elapsed time is reporting a weird number in Fibonacci and Mandelbrot. 
I suppose that's due to running ARMEL code on an ARMHF platform

If floats arguments are involved, yes, most probably.

Yes, in the computation of the time difference. As long as it stays 
within Red/System, float computation is fine, like in Mandelbrot

Good news: all GTK demos now run fine on ARM...finally! :-)

Very good news indeed :-)

I'll find you some more bugs in the bindings that run on top of GTK 
;-)

So, we can now say that Red/System is more advanced than R3, as it 
can make sophisticated GUI apps on ARM devices. ;-P

New bugs: no hurry! ;-)

I am in a hurry, I want to report them before release :-)

I wish we could put Red in the "Programming" menu of the RPi...It 
probably will need to wait for the Red IDE to be ready...

They base themselves on Squeak, the traditional Smalltalk educational 
track, with Scratch on top, and Python thrown in to appease the rest 
of the world

But yes, it's the domain I always wanted to target with REBOL

No worries, though, Red will have that position in the new Syllable 
releases

Let's try to please Raspbian guys then with some cool Red features....but 
will need Red to be self-hosted first anyway, else we're limited 
to cross-compilation only.

The Raspberry forum is full of complaints about the slowness of Scratch

That's a domain we can perfectly address with Red dialect + Red/System 
low-level access abilities.

Like the OLPC, they're now forced to double the memory of the hardware 
- for the second time

Get Cyphre to do a modern View like engine, and we will be kings 
- just believe me :-)

Well, or don't, as I have 6 beers tonight :-)

Is that still on your to-do list Pekr :D

I am in a hurry, I want to report them before release

 drive faster so you will be home before you are out of gas.  "But 
 yes, it's the domain I always wanted to target with REBOL" the domain 
 you want to target is the world isn't it?


I am studying the Red and Red/system sources these days to get more 
of a feeling what is going on.

It looks like there are only function and context definitions. WHere 
does the code start?

Start

 might not be the appropriate term in this context, as the code is 
 modular. What you're probably after are the compilers wrappers:

- for Red: %Red/red.r
- for Red/System: %Red/red-system/rsc.r

Not exactly, I read rsc.r as if system-dialect is not set then start 
with the compiler.r script. (after that or else the rest of the script 
follows) but then is has some do other scripts and a modular part 
and the other scripts are modular too. It look all very sound bu 
somewhere <there must be/I expect> a first action or function call.

rsc: context

 does contain "fail-try "Driver" [main]" that looks like a starting 
 point but it is within the context. So in my mind that does not get 
 triggered.

With Red we can target the world, before that with REBOL we had to 
be more limited. And also, one targets domains that others haven't 
satisfactorily addressed yet. New land is easier to inhabit than 
occupied land

Got the OpenStreetMap GPS Map browser to work on the Raspberry

Good! :)

It's all very slow, though. I don't understand why everyone is so 
excited about the Raspberry if they're all running LInux

I've found a bug in Red on ARM: the polymorphic dispatching isn't 
working.

Don't think I've hit that yet

RPi slowness: I've noticed it too...Even overclocked, at 900MHz, 
the UI still feel sluggish...Amiga 500 was having a fast UI running 
at 7MHz, so no excuse for those bloated UI stacks...

Yes, it's really, really frustrating now that Syllable doesn't run 
on ARM

I really can't understand how the UI stacks nowadays can dare produce 
slow results, with CPU and GPU thousand times more performant than 
the poor A500.

That's exactly why :-)

There's something deeply wrong in the way most so-called "modern" 
OS/desktops are designed. My 133MHz Bebox with a poor PCI video card 
was able to provide a very responsive UI, even under heavy load.


The RPi feels like dying as soon as you launch the lightweight (no 
kidding!) web browser Midori...Of course, the browsing is very slow...I'm 
quite disappointed by that and it's not the hardware fault, the RPi 
is a great platform, but the software stack sucks a lot.