8 ms·
I can't really argue with you because I'm only speaking from my own experience, but although with nbandroid I might wait 3 months for an update, with Eclipse I
by udp 16y ago
I can't really argue with you because I'm only speaking from my own experience, but although with nbandroid I might wait 3 months for an update, with Eclipse I would wait 3 months for the code completion popup.
:-)
- reginaldo 16y agoYou might want to edit your eclipse.ini and give it more memory[1] ... It worked like a charm for me on my Mac. The linux boxes I use don't have this problem. [1] The properties you want to change are: launcher.XXMaxPermSize, XX:MaxPermSize, Xms, and Xmx
- udp 16y agoNow that you mention it, it wasn't shy about how much memory it wanted to use either, but I'll give it a try next time I need to use Eclipse for something - thanks.
- loso 16y agoCode completion in Eclipse was a killer for me as well. I switched back to Netbeans for Android development (used it for php and python before) and was very happy. The only reason I switched to Eclipse in the first place was because all of the Android books and tutorials I found used it and it was easier to follow that way.
- gphil 16y agoHaven't used Eclipse for a while, but I'm pretty sure the amount of time you wait for the pop-up is a setting. Set it to zero and it's instantaneous on most modern hardware.
- udp 16y agoNo, this is a full "IDE locked up" kind of delay - and it's not just code completion, the whole thing feels sluggish compared to Netbeans. This is both on my Windows desktop and my MBP, so I guess the only thing left to blame is the size of the codebase I'm working with.