Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m using Eclipse to develop Android apps.
I’m using the latest SDK and Eclipse 3.6, my computer is macbook air with 4GB of ram.
Everytime I change a resource file ( an XML layout for example ), it takes eclipse between 1mn and 2mn to actually rebuild the binary and deploy it. My binary is about 10M ( it’s a game with lots of bitmaps ).
It’s very hard to program with such high response times, any way to make it shorter ?
If you have a lot of graphics you might want to read this android-dev post. aapt optimizes pngs during a build (perhaps unnecessarily so) but only if the extension is .png (case sensitive). Renaming them to .PNG skips the optimization step but the images are still useful when referenced.