I was being a bit sarcastic, yeah there’s no Swing/AWT but it seems there are no JavaSE or JavaME libraries present. It seems you’re supposed to use only the Android classes. I imagine this still has java.lang, but is that it?
We are all very proud of what you are working on. It seems like a very nice blend of Java SE + some cool UI packages optimized for the mobile platform. The UI in the demos looks pretty sexy, thanks to you probably :-)
hi romain,
congrats on android initiative. one thing i would like to know is like which all mobile hadsets does it support. i mean what are the target handsets.
I’m pretty excited about the platform. Had a quick look yesterday evening and noticed some of your pictures Romain. (the one with the telescope) Did you do part of the interface. It looks very good imo.
Now that you can talk about the project (right?). Are the UI components native peers and if so, what library are they using, or are they rendered at the Java level?
How do you feel about not using Swing, is this good, or was it absolutely necessary (issues with size of toolkit)?
The emulator is an SWT app, yet it’s not easy to see why this was needed.
I wonder – is the Android UI toolkit powerful enough to write “filthy rich” style clients? Obviously, it’s not Swing… and it’s still new to everyone. Some perspective from you on the platform capability would be really valuable.
Thanks for this Romain. Just had a quick glance through the docs… looks like nice support for gradients, alpha transparency, transforms etc etc. Good news!
Congrats on Android! Looking over the SDK, I’m salivating at the thought of having such low level access to a mobile phone, and all in Java =)
Aha! I see your photos in the gallery demo! Very nice. Android is looking great; I just wish there were some devices available.
Where’s my Graphics2D class???
[...] to Bob, Cedric, Romain, and the many many engineers that worked on [...]
This is a very exciting moment and a milestone in the history of mobile devices. Congratulations to all Android developers.
@Augusto:
It seems there is no Graphics2D class in the Android API. I think you are supposed to use the Canvas class instead.
I was being a bit sarcastic, yeah there’s no Swing/AWT but it seems there are no JavaSE or JavaME libraries present. It seems you’re supposed to use only the Android classes. I imagine this still has java.lang, but is that it?
Never mind, seems like a good chunk of the JavaSE classes are there;
http://code.google.com/android/reference/packages.html
Of course no Swing/AWT at all.
We are all very proud of what you are working on. It seems like a very nice blend of Java SE + some cool UI packages optimized for the mobile platform. The UI in the demos looks pretty sexy, thanks to you probably :-)
hi romain,
congrats on android initiative. one thing i would like to know is like which all mobile hadsets does it support. i mean what are the target handsets.
All the information regarding Android are available on openhandsetalliance.com and code.google.com/android.
Hello Romain,
Does you not planned yet to write plugin for IntelliJ IDEA? Cos, if not, i would like to take a try to write this one.
Thanks!
I’m pretty excited about the platform. Had a quick look yesterday evening and noticed some of your pictures Romain. (the one with the telescope) Did you do part of the interface. It looks very good imo.
I did not work on the UI design. I work on the UI toolkit though.
Alexey: I don’t think anyone is working on an IntelliJ plugin.
Romain;
Now that you can talk about the project (right?). Are the UI components native peers and if so, what library are they using, or are they rendered at the Java level?
How do you feel about not using Swing, is this good, or was it absolutely necessary (issues with size of toolkit)?
The emulator is an SWT app, yet it’s not easy to see why this was needed.
Romain,
I wonder – is the Android UI toolkit powerful enough to write “filthy rich” style clients? Obviously, it’s not Swing… and it’s still new to everyone. Some perspective from you on the platform capability would be really valuable.
Simon, you should take a look at the SDK. But definitely yes.
Thanks for this Romain. Just had a quick glance through the docs… looks like nice support for gradients, alpha transparency, transforms etc etc. Good news!
Hi Romain,
We already started: http://code.google.com/p/idea-android/
It still in development stage (if you know what devkit is), but i guess it can be enduser downloadable soon :)
Any idea of where is the bug traker for Android ?
Refactoring a package in Eclipse is not working correctly: it does not refactor the package in androidmanifest.xml.
Is there any public bug tracker?
Romain;
I haven’t found any info on this, but the components, are they peer based ala AWT or all rendered in the Java layer (or a mix)?
Augusto, I cannot answer this question. Please ask it on code.google.com/android.
Hi,
As you maybe already know. We just released beta version of plugin. Here is getting started tutorial:
http://code.google.com/p/idea-android/wiki/GettingStarted
Here is plugin:
http://plugins.intellij.net/plugin/?id=1792
Thanks!
Really good and really interesting post. I expect (and other readers maybe :)) new useful posts from you!
Good luck and successes in blogging!