AltME groups: search

Well, Android x86 is basically Linux x86, so you should be able to 
already run Red/System binaries on it.

Integrating with the Android non-application model is the most interesting 
point of running Android on that machine. If I wanted to run Linux 
binaries on it, I could keep Ubuntu on it.

Having fully access to the whole Android framework from Red is the 
goal. Running Linux binaries is the just the first experimental step.

Android lets you bundle seperate binaries for ARM5 and ARM7 support 
in the same APK. Which binaries get loaded depends on which level 
the phone supports, though if there's no ARM7 binary the ARM7 phone 
can run an ARM5 binary. If you want to do the progressive use of 
ARM7 features if ARM7 is available, it's best to let the APK do it 
for you. I don't think that there are any ARM6 devices for Android, 
especially since the NDK doesn't support them, but if you want to 
add ARM6 support for other platforms then cool.

Well, I am not doing the ARM port only for Android, I target also 
iOS and some embedded boards (like e.g. the Raspberry Pi).

Anything else is big waste of time. Just recently, there are two 
top Android phones - Samsung Galaxy SII and HTC Sensation. Both 2.3.4. 
Those are going to be upgraded to ICS. Before you finish the job, 
pre 2.3 falls into absolute irrelevancy, no matter how many tens 
of millions devices out there you claim.

I think nothing bad of you :-) For me, it is easy - you can't compare 
PC world, which I would assign 3+ years of lifecycle easily, with 
mobile world. In mobile world, I would say it is 2- lifecycle, or 
even shorter. If each day 300K of Android phones is activated, then 
I would pretty much decide to start supporting the almost latest 
models, which is - 2.3. Even my girlfriend HTC Wildfire S, which 
was published on 15.2.2011, is 2.3 version. Before Doc finishes the 
product, it will be old, and unsupported phone by its vendor. Of 
course, it depends upon the featureset you are going to support - 
if supporting pre 2.3 is a no brainer, why not. But - if 2.3 contains 
some real anhancements you want to utilise,then based upon the above 
usagedata, forget at least pre 2.2 ...

Pekr, the top Android phones are the ones people already own, not 
the ones they haven't bought yet. And most of the ones they already 
own (in my country) are bought with 2-year contracts, not qualifying 
for a hardware upgrade until after that, and aren't able to be upgraded 
very much in software because that would compete with new phone purchases. 
It's good to see 2.2 adoption so high though. I am stuck on 2.2, 
btw.

In case you've missed it, you can already run this simple Red/System 
HelloWorld app on your Android phone: http://static.red-lang.org/android-hello.jpg

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

But it only runs in command-line mode for now, a Java bridge will 
be required to produce GUI apps on Android.

Perhaps, a line needs to be rephrased: "Such approach will allow 
us to build easily Android apps without having to write a single 
line of Java or Objective-C code" - AFAIK, Android apps are not written 
in Obj-C?

however, it is a bit difficult to use, and also - allowing non-market 
sources could be marked as dangerous. Will there be ability to produce 
native Android apps, which could be published via the market?

Produce native Android apps: certainly, but that requires the Java 
bridge. It should be possible to also use the NDK for accessing a 
subset of Android API, but I haven't investigated yet that option 
much, especially if it requires Dalvik code support or not.

Thanks Kaj, I hope to be able to demo some running Android app in 
Red/System (or Red) in march at the RedTopaz conf.

I've also compiled them for Android. I can't test them, but they 
do all compile

It's in the ANSI standard for the C library, but it may not be in 
the Bionic C library for Android

Red/Systerm ARM port on OSNews: http://www.osnews.com/story/25468/Red_System_Language_Gets_OS_X_ARM_Android_Backends

What I found for sure is that the Android Bionic C library has an 
atexit implementation

Finally I will be able to help a bit with a donation ... it's done! 
Will do better next time - New year was rough in terms of personal 
expenses - Keep up the good work everybody. For tring things a bit 
I recently ordered a Samsung Galaxy Tab 10.1 inches android tablet 
- I will receive it shortly and will try to test somewthing with 
it ... Don't know what for now but looking for something. For now 
I'm learning iOS programming in the mean time using Objective-C which 
I also have to learn ... A lot of new stuff going on.

I wonder what is written on the orange banner on top of the Android 
screenshot?

Evgeniy: you're sounding like you're volunteering for writing the 
X back-end, thanks, that would be nice! ;-))


The native GUI I have in mind for Red is a SWT-like one, but as light 
as possible (SWT has some really heavy widgets). So, yes back-ends 
for Win32, X, Cocoa and Android are planned. The Cocoa and Android 
back-ends would need obj-c and java bridges.