World: r4wp

Well, it's not a phone :)

Daughter has a HP touchpad running Android.  Should work?

I imagine anything running Android should work.  I don't know if 
the architecture of the processor matters, but I think it must not 
because I don't see different compilations of Angry Birds for different 
Android processor architectures.

Only if it's compiled for the lowest end processor

Robert and Cyphre : As already stated under the Android group I have 
succeessfully tested the new console based R3 for Android under my 
Samsung Galaxy Tab 10.1 tablet - running Android 3.2. works well 
- thanks again a lot for this achievement - I wil shortly follow 
with some donation - simply waiting for my next salary deposit ...

Thx.

Thanks Gerard, glad it works for you!

Graham, it should work on anything that has at least Android 2.2 
and an arm cpu. Moreover the APK contains additional build  of the 
R3 interpreter for arm cpus that have hardware floating point operations. 
I haven't made any benchamrks so I don't know if this is really performance 
advantage (in case of Rebol code) for Devices with such better and 
newer hardware.

I'm proud to say I have the second fastest Android phone tested so 
far. ;-)  I am SO excited for the future, especially for the Android 
network and file access and the graphics port.  Cyphre, how do we 
make donations again?

Bo, I upped my matching donation and additional $500 today.  Cyphre's 
doing fantastic work on Android.  Please help them stay funded, and 
I'll match donations.

and additional -> an additional

Bo, you can make a donation to us via http://development.saphirion.com

I really apreciate all your support.

I just donated $100 now.

Endo, thanks a lot for this! :-)

So we currently have another 20 days we can spend on the Android 
port.

Great!

Nice work Kaj. I'm working on Unicode support for the tokenizer, 
so the console should get at least Unicode support for the DevCon. 
I plan to write a real cross-platform console engine as nobody has 
stepped out to build one so far, I guess it should be ready for the 
DevCon.

Great

Robert, when you say that I can make a donation to Saphirion, does 
that help Cyphre with his Android port?  Or is that a different fund? 
 It sounds like it is the same fund because Endo's $100 donation 
added some days to the Android port, but I just wanted to be clear.

There is a different fund for Red as well, correct?

Red is a different fund, it goes to Dockimbel ....

Where is the Red fund link located?  I created a new checklist called 
"Donation Links" so we can direct people there when they want to 
know where to donate.

http://www.red-lang.org/p/donations.html

http://www.red-lang.org/p/donations.html

ah :-)

Thanks for adding those links to the checklist.  Now to dig out my 
checkbook... ;-)

It's been a difficult year financially, but I wanted to donate something, 
so just donated $20 to Saphirion for the Android port.

Hopefully more to come as business improves...

I want to also donate some to Red.  Soon...

Thanks a lot Bo! To make things easier, all donations for the R3/Droid 
port I'm wokring on are going thru Saphirion's webpage.

Bo, thanks a lot! That's really great.

Good job with the prebuild site

Thanks!

A very kind gift to the REBOL community.

Nice work Andreas!

Andreas: you should let Carl know by mentioning it on the GitHub, 
I think

I wrote Carl a mail to tell him about it.

Yes, Andreas, very nice looking site. And thanks too to Saphirion 
for the build farm.

Build farm is 2/3 mine, 1/3 Saphirion :)

Saphirion contributes the OSX machine, for which I'm very grateful.

Very nice work Andreas!

Andreas, good idea.


I'd only add that you should append the rebol version to the executables/archives 
(if ever), so that when we download them, they don't overwrite each 
other.  adding the version will also classify each version based 
on its platform.

Maxim, thanks.

The version is already appended to the executable names, that's the 
-g.... suffix. For these automated builds, the Rebol version is currently 
rather meaningless, it will always be 2.101.0.


I'll think about appending a platform key to the binary names themselves.

thanks for considering it.    :-)

at some point, the version will be incremented no?

Are you going to keep older versions?

when some dramatic changes will occur, it might be necessary... for 
example, some tools might require older binaries until they are updated.

it would be good for doing triage on bugs

maybe, simply adding a folder with the date of any automated builds. 
 this way we can easily backtrack any issues in time.