> --
> You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
> To post to this group, send email to rubyonra...@googlegroups.com.
> To unsubscribe from this group, send email to rubyonrails-ta...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
>
>
That's a pretty vague question. Please clarify.
Best,
--
Marnen Laibow-Koser
http://www.marnen.org
mar...@marnen.org
Sent from my iPhone
The Android SDK
http://developer.android.com/sdk/index.html
it's free
Craig
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Or you can use Rhodes/Rhomobile:
I saw their demo at RailsConf last month. It only does the most
simple form/list stuff, and what it draws is really very ugly. Yeah,
you can write your code once and then have it output both an iPhone
and an Android app, but no one is actually going to buy such simple
little apps. It has a long way to go before anyone will use it for
anything serious, and I doubt they will ever be able to keep up with
the speed at which Android evolves.
--
Greg Donald
destiney.com | gregdonald.com
rhomobile.
Best Regards,
Mohit.
8/7/2010 | 11:41 PM.
Kindof like the Rails scaffolding then...
I've used it to do a web-service front-end from Remedy; and seeing as
it's a web-page like any other Rails app, it looks as good as you can
style.
> you can write your code once and then have it output both an iPhone
> and an Android app, but no one is actually going to buy such simple
> little apps.
Really? I'm looking at my invoices and beg to disagree... but the OP
never said (much of anything to be fair) anything about what he wanted
it for, just "how to".
> It has a long way to go before anyone will use it for
> anything serious, and I doubt they will ever be able to keep up with
> the speed at which Android evolves.
Possibly... or alternatively it's being used seriously right now, but
it may left be left behind in the future.
Personally.... I hated using it - but I was limited to having to use
rhohub; it might be better using v2.x on your own hardware. But either
way, I'm just pointing out an option for the OP :-)
What's the market:// URL to your app(s)?
The work I did with Rhodes wasn't for a public app - it was a proof of
concept for a Remedy integrator to give them a mobile front-end to
their incident-reporting database.
Rhodes did the job well, but was a PITA to use. If the OP asks "how do
I develop for Android?" the answer is "Java!". If they ask "How do I
use Ruby/Rails to develop for Android?", one answer is Rhodes.
So you're saying that Rhodes was more of a pain than Java? (Quite a
tall order IMHO.) In what respect? I'm curious to know, because Rhodes
looks quite promising otherwise, both because it's Ruby and because it's
multi-OS.
I realize we've gone off topic for this list, so feel free to e-mail me
privately at mar...@marnen.org if you'd rather.