I've heard a few horror stories about MOTODEV but I have not been experiencing them, it hasn't crashed once on me and the emulator is running fine (on a separate window). In other words, other than a crappy installation experience it's been a smooth experience.
Tuesday, February 16, 2010
Android Development
Installing MOTODEV was not the best of experiences. Upon installation I decided to download SDK 1.5, 1.6 and 2.0 since the phones in the lab were 1.5. It turns out that though after the lengthy installation process it was not able to find any other SDK than 1.5 installed, and trying to automatically install them through the IDE did not help since it would come back to me and say that I had all possible SDKs already downloaded. Fortunately I decided to download them manually and everything has been working out pretty well.
Wednesday, February 10, 2010
my second thoughts - android dev
everything went fine until section 2.4...running the emulator. i emailed the TA for help after reading a few websites with contradictory statements.
in win7, i followed the tutorial and i had to add the ANDROID_SDK_HOME to the environmental path and set it to the android sdk location (C:\Program Files (x86)\eclipse\android-sdk-windows). immediately after the change, the emulator runs much faster than the motodev version. also when closing the emulator, there aren't any error messages.
continuing the tutorial...section 3.6, when running the emulator for the first time AND with no AVDs present, the emulator crashed. this prompted me to created AVDs for 1.6 and 2.1 SDKs and then the emulator ran without issues.
in win7, i followed the tutorial and i had to add the ANDROID_SDK_HOME to the environmental path and set it to the android sdk location (C:\Program Files (x86)\eclipse\android-sdk-windows). immediately after the change, the emulator runs much faster than the motodev version. also when closing the emulator, there aren't any error messages.
continuing the tutorial...section 3.6, when running the emulator for the first time AND with no AVDs present, the emulator crashed. this prompted me to created AVDs for 1.6 and 2.1 SDKs and then the emulator ran without issues.
Monday, February 8, 2010
my first thoughts - android dev
i, by far, am not a great programmer. but in my experience, i know one thing! motodev sucks!!!
it's very buggy, does not properly install on win7. i've had better luck on xp and in fact, so far all my assignments have been done in xp. getting the emulator to properly load from within motodev is a hit or a miss. not to mention it's a rebranded version of eclipse with moto's integrated crap.
i still have to install eclipse with the android plug-in and google sdk...most likely my next post.
as for android itself...the GUI is created using xml files. it's certainly a lot easier than iphone programming because there's no need to learn objective-c and you don't have to put up with the cocoa bs. right now, i have 0 java experience but i feel like that's going to change real fast.
it's very buggy, does not properly install on win7. i've had better luck on xp and in fact, so far all my assignments have been done in xp. getting the emulator to properly load from within motodev is a hit or a miss. not to mention it's a rebranded version of eclipse with moto's integrated crap.
i still have to install eclipse with the android plug-in and google sdk...most likely my next post.
as for android itself...the GUI is created using xml files. it's certainly a lot easier than iphone programming because there's no need to learn objective-c and you don't have to put up with the cocoa bs. right now, i have 0 java experience but i feel like that's going to change real fast.
Subscribe to:
Posts (Atom)