So just a status update on this I've got this partially working now, so that my addon resources also are added as part of the platform default resources but still kept completely separate from the framework resources. I'm now able to create custom views inside an app library project that uses various custom resources but instead of building the library into the app itself it is loaded as a system library.
No everything works yet though. Will keep you posted on my progress Br Thorbjørn On Monday, January 28, 2013 2:17:23 PM UTC+1, Thorbjørn Vynne wrote: > > Hi > > I know this has been asked a few times, but has anyone had any success in > creating a platform addon with custom resources lying outside of the > framework resources > > It would make a lot of sense to be able to create an addon at platform > level which is fully self contained with java classes and resources etc > just like an app level library project. Since the app library project will > always be copied into all applications that makes use of it this is not > exactly an efficient usage of resources. > > I've been playing around with a custom addon project with resources in a > seperate project and namespace but it seems that changes might be needed in > aapt to make this happen. > > So I've basically created a addon.jar and a addon-res.apk just as it's > done in the frameworks/base project which works out fine, but when I try to > include it in my apps by added an base include to aapt I seem to run into > namespace issues.. > > Anybody got any experience with this? Or should I revert to using overlays > in the device project? > > /Thorbjørn > > > -- -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting --- You received this message because you are subscribed to the Google Groups "android-porting" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
