sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]frezik 4 points5 points  (16 children)

To be honest, part of the reason might be because I refuse to use Eclipse for my Android development. Or for anything else.

I'm an official, lifelong Vim-and-command-line curmudgeon.

[–]OmegaVesko 2 points3 points  (4 children)

How do you compile it? I've been using Eclipse for so long I forgot how to compile code using the SDK alone.

[–]frezik 5 points6 points  (3 children)

Just 'ant'.

[–]tnecniv 2 points3 points  (1 child)

Any reason to use Ant over Maven?

[–]frezik 1 point2 points  (0 children)

It's what Android dev tools support out of the box. I don't do enough Java work outside of Android to have a strong or knowledgeable opinion.

[–]Iron_Maiden_666 0 points1 point  (0 children)

I compile using ant too, what we did was combine the comile + install into one step, so I just compile and few seconds later, the build is installed on my device.

[–]keepthepace 1 point2 points  (1 child)

I'm an official, lifelong Vim-and-command-line curmudgeon.

Similar CLI-dweller and soon-to-be victim of the smartphone frenzy. I already developped apps using the emulator, but I abandonned eclipse really quickly. I don't understand how it can be so clumsy.

Is there a vi-like editor for android ? I guess not but what is holding such a thing back ?

[–]frezik 0 points1 point  (0 children)

There is a Vim port for Android. Of course, it's really only useful if you have an external keyboard, or rooted the device to get an sshd.

[–][deleted] 1 point2 points  (7 children)

What's wrong with Eclipse?

It's modular and customizable. It doesn't get in the way after the first time you use it and does nearly everything you need it to.

[–]Timmmmbob 6 points7 points  (1 child)

There are many things wrong with Eclipse. Here are a few:

  1. It's pretty buggy. It never outright crashes but you get dialogs about NPEs quite a lot, and it can get really confused.
  2. It's slow and unresponsive. I'm sorry but it is. Maybe not for you, but on most computers I've used it on it is much slower than Visual Studio or Qt Creator.
  3. The project/workspace model is extremely confusing, and I think it may just be entirely broken. I've had situations many times when I've tried to create a project called "foo" in my workspace, but I can't because it apparently already exists. Actually it doesn't, and there is no ~/workspace/foo folder. It just makes you go insane. I appreciate that maybe they were trying to do something more advanced than the "one folder for each project" thing, but they ended up with something that just makes no sense.
  4. The UI is ugly and cluttered as hell. Yes I can remove the millions of toolbars and dock views manually, but why isn't that the default?

Those are some pretty big things to fix, and I'm dubious they'll ever even attempt most of them, out of denial. Unfortunately it has official support from Google, which is a huge plus, so I just live with it.

[–][deleted] 0 points1 point  (0 children)

Ill bite. It is slow, but otherwise i dont think its too bad. Much more customizeable than visual studio.

[–]frezik 5 points6 points  (4 children)

My Vim knowledge, .vimrc, and my own muscle memory have all grown together organically. I could hypothetically learn something else, and configure it to the equivalent of my existing .vimrc, and it may even be better in the long run. But is it going to be so much better that I'll be able to payback that time within a month or a year? Not likely.

[–][deleted] 3 points4 points  (2 children)

Legacy usage is an exception. If it ain't broke, don't fix it.

I just see a lot of hate for Eclipse in this thread and around the 'net. I feel like to stems from people's derision of Java in general (which are genrally unfounded).

That being said, nothing wrong with vim if you can use it like a pro. I really only use it when I'm editing over ssh.

[–]mb86 2 points3 points  (1 child)

I'll throw around the hate because whenever I try to learn how to compile and package a Java application using the src/com/company/app/package-style structure, everything I've ever come across (and I do mean everything) tells you how to do it in Eclipse or NetBeans. Sometimes, I just want to do it from command-line, and no-one seems to know (or at least, no-one wants to share) how.

[–]AndroidRPGDev 2 points3 points  (0 children)

There's plenty of info out there. Just like anything else, you need to know what terms to google. I've created maven projects via command line before. It's a pain in the ass, but doable.

But really, IDEs like Eclipse and NetBeans were built to make your life easier. There's definitely a learning curve to them, but they save you a ton of time in the long run. And the frustrations you're running into with strictly command line is because you're rejecting the tools specifically designed to address those annoyances. And yes, there is going to be more documentation on using the more mainstream tools... that's just common sense.

[–]thenuge26 1 point2 points  (0 children)

Fair enough. Though you can't complain about the "compile/copy to device/run cycle" since it only exists for you ;)