On Wed, Apr 4, 2012 at 6:15 AM, Mark <[email protected]> wrote: > themes don't quite seem to handle what's needed. i have one > application or project that i want to deploy as 2 applications. build > as app a, then build as app b. i can easily copy in / out a different > resource folder, but that doesn't handle the application "package". >
Oh. I was confused with your talk of "branding". > each app in the "store" needs a different package. my app code uses > the namespace, org.bnb for the classes, but i want to deploy for > "Bob's Bed n Breakfast" and for "Sue's Bed and Breakfast", com.bbnb > and com.sbnb. Android seems to use the package name as the > application name (from the manifest). i've been able to override thus > far the package name that the R class uses, but when i try to run, the > other classes seem to want to come from the manifest package naming. > > argggg. > > any help on this is most appreciated. android could use an app name > and keep that separate from the code naming. > Create a base library project that has all the core code. Then derive a new app / project / "brand" that uses that library project with a new package name for each version you want. ------------------------------------------------------------------------------------------------- TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago transit tracking app for Android-powered devices -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
