World: r3wp

Or BlackBerry (our company is unifying on BB in few weeks) ... but 
I don't know about BB OS much .... unless they make switch to QNX, 
it probably does not make sense, who knows ...

Android has a native library API model. We could make a host that 
acts like a native library for Java according to that API.

The old BB apps are written in Java. The new BB apps (only for the 
BlackPad so far) are written in AIR.

I assume that there is a native API for BB as well, but don't know 
anything about it.

cool then. It would be even nice to have View working, as we use 
SW rendering. I could write my mom special frontend with really BIG 
buttons, as she has her eyes strongly influenced by diabetes :-)

Couldn't the REBOL to Flash dialect be adapted to produce BB apps 
for the new models running AIR?

It could. The only problem is that AIR needs certification. I was 
not studying it deeply as I don't need it now and I have other priorities 
at this moment.

The BlackPad isn't even out yet, and people are only speculating 
that the new OS will be ported to the BB phones. I think you can 
afford to take your time :)

BlackPad? Do you mean PlayBook? It will surely use QNX ...

Oh right, they renamed it.

They only use the QNX kernel, not the full OS.

R3 is not an app, it is used to make apps. And if the apps on the 
system are written in AIR, then R3 would need to integrate with that. 
Or we can go Oldes' route.

I hope you know that RIM has bought QNX from Harman Kardon?

Yes, but not for the full OS. BB just needs the low-level stuff. 
They are providing their own user space.

I saw the demo of the PlayBook.

We can probably make an r3lib for QNX on that hardware and it will 
work on the PlayBook, but the host part of the code will likely need 
to be very different between the PlayBook and regular QNX.

Air probably is better (more polished) than their own gui architecture. 
 though they might have had really cool opportunities if they used 
elate instead.  things like flipping an application's gui from one 
tablet to another.

nothing prevents them from adding elate later.

And nothing prevents them from having the (much better) QNX programmers 
do the work :)

yep.

elate? From Tao? It does not exist anymore ...

ah.. yes... thats' true... I'm mixing the names... sorry... its photon.

Tao? they were going to be the kernel for the new AmigaAnywhere platform... 
good times :)

(yes, it went defunct a while back)

http://github.com/carls/R3A110-- a temp test area for Host-Kit A110

Only the linux libr3.so at this time. Will attempt to add the windows 
lib.

Windows lib added to repository

So the Amiga is first from non mainstream OSes. Which one do we choose 
next? Any mobile OS takers here? :-)

Petr, thanks for considering Syllable mainstream :-)

Kaj - I consider Syllable being covered, no? :-) I know there is 
not specific Syllable port, but it works somehow, no? :-)

Of course - from non-mainstream OSes, I would choose - QNX, Haiku, 
Aros, Syllable, MorphOS .....

Here is the problem with OS X host-kit release:
http://www.rebol.com/r3/docs/osx-linker-symbols.html

So, we can have Android instead?

or ARM?

Carl, what version of GCC are you using on OSX?
What happens if instead of
  

  gcc -dynamiclib -exported_symbols_list exported -o a.lib a.o b.o

you do

  gcc -dynamiclib -Wl,-x -o a.lib a.o b.o

Got an ARM?

and a LEG

Was waiting for that. ;)

checking...

I have this http://en.wikipedia.org/wiki/NSLU2

Intel XScale IXP420 CPU

Andreas: same result.

What version of GCC?

The Plug computers all use ARM too

(gcc -v)

gcc or -Wl,-v ?

gcc

gcc 4.0.1

ld -v?

cctools-590.23.2

ouch