I have spent some time trying to solve the same task in different ways and at the 1st end came to 2 mostly identical projects variant and at the 2nd end came to even more simple solution as suggested above - I have 1 project for both basic and pro versions, and basic version can become pro version at runtime depending on some constant in the code (in order to do this had to make difference with basic and pro versions minimal in order to avoid messing the code) because it was very hard to maintain 2 similar projects at the same time without using some kind of advanced tools like git or something like that.
You can have the shared code in the dependency project, but it can have only basic java code - no activities, shared resources and any other staff which should use generated R.java. You even will not be able to load layout.xml file by hands and set it as activity layout at runtime (if you would try to avoid using R.java with such hack) - there is API for that, but it thows runtime exception at some moment.
-- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
