3 ms·

They should first build an IDE for Android rather than keep piggybacking forever on Eclipse which is not very lightweight or suitable for a specific purpose, le

by fakeer 14y ago

They should first build an IDE for Android rather than keep piggybacking forever on Eclipse which is not very lightweight or suitable for a specific purpose, let's say.

jrockway 14y ago
Why? Eclipse is just reusable UI widgets and a Java editor. That's basically what you want for writing an "Android IDE", whatever that might be. (I personally just use Emacs.)
- fakeer 14y ago
  It never works seamlessly. I would love to do away with all the clinks and cracks which becomes an integral part of it. Becomes more painful when you have to deal with the "whole code" (say guys at those OEMs and those indie ROMs).
  - jrockway 14y ago
    I fail to see how throwing away Eclipse would solve this problem. What you probably want is more engineer time thrown at Android tools, which is something I can certainly agree with.
gizmo686 14y ago
Eclipse is a popular Java IDE (with plugins for other languages). Android programs are java with an XML file describing the UI. No need to re-invent the wheel here. If you have another IDE you want to use, see if there is an android plugin for it, or right the XML files yourself and use any java IDE, or use a plaintext editor and curse Google for making Android run Java.
- fakeer 14y ago
  Do you know why all the other text editors were built even after the first one was already in use? Try finding answer to it and I am sure you'll find the answer to what is reinventing the wheel and why is it very different from having an IDE that specifically caters to the need of Android development, with total focus and integration, and is supported/promoted/maintained by Google - somewhat the way Xcode is done or hopefully even better.
  - gizmo686 14y ago
    They already built a new user space for Android. Sometimes wheels need re-inventing, but that does not mean you should abandon all established ecosystems for the sake of inventing the wheel yourself.

by fakeer 14y ago

They should first build an IDE for Android rather than keep piggybacking forever on Eclipse which is not very lightweight or suitable for a specific purpose, let's say.

jrockway 14y ago

Why? Eclipse is just reusable UI widgets and a Java editor. That's basically what you want for writing an "Android IDE", whatever that might be. (I personally just use Emacs.)

fakeer 14y ago
It never works seamlessly. I would love to do away with all the clinks and cracks which becomes an integral part of it. Becomes more painful when you have to deal with the "whole code" (say guys at those OEMs and those indie ROMs).
- jrockway 14y ago
  I fail to see how throwing away Eclipse would solve this problem. What you probably want is more engineer time thrown at Android tools, which is something I can certainly agree with.

gizmo686 14y ago

Eclipse is a popular Java IDE (with plugins for other languages). Android programs are java with an XML file describing the UI. No need to re-invent the wheel here. If you have another IDE you want to use, see if there is an android plugin for it, or right the XML files yourself and use any java IDE, or use a plaintext editor and curse Google for making Android run Java.

fakeer 14y ago
Do you know why all the other text editors were built even after the first one was already in use? Try finding answer to it and I am sure you'll find the answer to what is reinventing the wheel and why is it very different from having an IDE that specifically caters to the need of Android development, with total focus and integration, and is supported/promoted/maintained by Google - somewhat the way Xcode is done or hopefully even better.
- gizmo686 14y ago
  They already built a new user space for Android. Sometimes wheels need re-inventing, but that does not mean you should abandon all established ecosystems for the sake of inventing the wheel yourself.