World: r3wp

Concretely: let's assume you have your internal sources in Subversion 
or Git.

Then the first step would be to create a post-commit hook (a script 
that runs on every commit), that exports your internal sources into 
the externally visible sources.

Those "externally visible sources" are what I consider to be the 
hostkit.

Andreas, we should probably switch to a different group to keep all 
this together... is there a group already on this?

Don't think so.

(And yes, we probably should.)

Ok, making it now.

hey there.. any Qs for me?

ssolie: ok, I'll make the changes over the weekend and let you know

Cyphre: thanks! I look forward to testing this out with freetype.

what would be the simplest code to open a window in r3?  the window 
doesn't have to have anything in it

From the REBOL side? view [] I guess

you might get a wee tiny window though

Doesn't have to have anything in it

I think Steven just wants to fire a window creation sequence in the 
host

I found some code to make the gob and then view it which is working 
fine for my testing now

win: make gob! [text: "Test Window" offset: 100x100 size: 300x200]

view/as-is win

Ah yes, you need it without using VID, of course

that was the tricky part for me

still getting used to rebol here.. :)

ssolie: the really 'bare-bone' sequence to show window is:


show append system/view/screen-gob make gob! [text: "Test Window" 
offset: 50x50 size: 200x200]
wait system/view/event-port

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

We have several users asking for Android

unless they've given up waiting

I have not given up waiting. Part of the reason I got an Android 
phone in the first place was to port R3 to it :)

They allow C libs now. So, if someone wants to make the host-kit 
work on Andoid, it might be a quick port.

First step would probably be a Linux ARM build. Which will be really 
rather quick.

ARM is good one too.

A console-mode core build could even be used on Android directly 
from the terminal.

Hmm, you push me to buy new Phone, right? :-) Win mobile 6.5 user 
here, hw keyboard powered device (HTC Touch Pro 2) .... but anything 
would be cool :-)

I thought Android API is in JAVA? How do you want to link/bind?

Enterprise users might need R3 on WinMobile 6.5.

btw - Carl - http://www.rebol.com/roadmap.html- is the Project pool 
the last few items before we claim the beta status?

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.