project

I would like my activity to use some features of 2.01, but i need it to be able to run on 1.5 devices. I understand that the 1.5 devices will not be able to run the 2.01 features and thats fine. But i still want them to be able to use the rest of the activity. I am using Eclipse as my IDE, how do i setup my project correctly? what am i going to have to watch out for? and what the heck does verifyerror mean? See http://developer.android.com/resources/articles/backward-compatibility.html VonC For the VerifyError part, the question Android java.lang.VerifyError? mentions the necessity to run any

After some naming confusing my team decided to rename some projects and the namespaces for all the existing code files in the project. (In Visual Studio 2012) We've changed: the Project Names the Assembly Name, Default namespace, Title and Product entries in the Project Properties the namespaces for each code file in each project that was renamed all the using statements for the revised namespaces cleared out the old .dll files in the /bin directory (for the routing engine to not find multiple controllers) the actual folders themselves, requiring removing and re-adding the projects to the

I am wondering, how to create flexible package structure for an Android application, such that it'll be easy to extend and manage. My first idea is to put each application component in separate package, such as: spk.myapp.main.(all classes used in Main activity) spk.myapp.processor.(all classes used by Processor provider) ...and so on. However, the aspect I don't like is, that the class and package naming convention may quickly became inconsistent with other fully qualified names, such as provider authorities (in this case I would rather name these spk.myapp.processor than spk.myapp.processor

I'm moving from Eclipse to android studio and this is my set up in eclipse: I have several Android app projects, depending on several library projects (some shared) all within one workspace. In Android studio I first started creating a project per app, but quickly realized that I would have to have the library projects as modules within each project that uses them. This would mean duplicating the library projects and including them in each app, which is highly redundant and would require maintaining multiple copies of the libraries. So I switched to having all my apps and libraries as modules