Titanium Community Questions & Answer Archive

We felt that 6+ years of knowledge should not die so this is the Titanium Community Questions & Answer Archive

Android module development best practices

I'm trying to add some Android specific modules to extend Titanium Mobile. My question is what best practices you suggest? For the moment, what I have to do is:

  • Add custom module
  • Rebuild (ant)
  • Copy distributed packages to Titanium Installation folder
  • Rebuild the testing app (js, etc…) to see if it works.

The cycle takes pretty much time, that's why I wonder if you guys at Appcelerator have some suggestions. Is there anyway to set breakpoints for debugging?

The second question is what your testing framework for Java? JUnit I suppose !? I don't find the test cases in the titanium_mobile source code.

Thank you!!!

— asked March 31st 2010 by Anh Tuan Kieu
  • android
  • modules
  • practices
  • test

1 Answer

  • Accepted Answer

    We haven't optimized the process and are still going to be making additions to the module structure to account for Android issues like Activities, Permissions, intra-module dependencies etc.

    We develop in Eclipse. The titanium_mobile/android and each of the modules in titanium_mobile/android/modules have Eclipse projects, they can easily be imported into Eclipse. You must have the latest SDKTools v5 and android plugin for Eclipse.

    The other thing we do is create an Android project that does not use the jars, but rather uses the Eclipse project dependencies and that becomes the target app. Here is the github project I use for KitchenSink http://github.com/donthorp/ks4

    As far as testing, KitchenSink is currently our test framework. Since so much of Titanium is devoted to UI we use it as the reference.

    — answered March 31st 2010 by Don Thorp
The ownership of individual contributions to this community generated content is retained by the authors of their contributions.
All trademarks remain the property of the respective owner.