I think a library project will do what you want, and be pretty easy to manage to. You'd create your basic app as a library, then create a new app for each customer, and include that shared library. Any customer specific changes, including drawables, just get placed in a non- library project. The library drawables would be replaced with the customer specific ones and you could even do code changes there too.
More on library projects: http://developer.android.com/guide/developing/projects/projects-eclipse.html -Kevin On Aug 1, 7:21 am, Kostya Vasilyev <kmans...@gmail.com> wrote: > You can reference resources via a theme, with "?attr/blahblah" syntax. > It certainly works for drawables, and should be easy to test if it works > for layouts as well. > > 01.08.2011 16:18, Christine пишет: > > > I have tried whitelabeling an app, so I can use the same codebase for > > a number of customers. What's different in the apps is the graphics, > > styles and layouts, not the code. The best way I could think of is > > have an ant script that copies the res folder and the manifest file > > into a separate project, and copy it back to the main project. By > > running this ant script I switch between skins. But there must be a > > more elegant way of having skins for an app. Styles won't do it, > > because that's too limited, you can only change android: attributes, > > not layouts and drawables. > > Wouldn't it be nice if a Theme didn't just have it's own styles, but > > also its own res folder? > > -- > Kostya Vasilyev -- 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
