Here is how I have solved this riddle; it is a compromise. It seems pretty much impossible to implement any sort of class/ inheritance structure around the way resources are implemented for the Android resources via Eclipse. They are tied too tightly with R. and the special apk builder.
So I've spilt on the boundary between what classes access resources and what classes do not (the UI classes tend to be the resource users). Some classes that were light users of resources can be restructured a bit to have resource info parameterized to them thereby gaining them a home in reusable .jars. The stuff that does not use resources can be organized into other Eclipse Java projects with JRE System library and android.jar on the Libraries build path. The classes that implement the UI for a specific app are housed in a regular Eclipse Android project with a Manifest and menus and such…. It has the Projects and Libraries of the reusable classes on its build paths. I had really wanted to push reuse further into the UI but it is a diminishing returns thing where copy+paste looks more attractive. Maybe someday Google will share with us an improved way to package Android resources within jar files. On Nov 11, 7:29 am, WoodManEXP <[email protected]> wrote: > Does anyone know of suggestions/recommendations on how to structure > Eclipse projects in order to build an apk from multiple projects? I > would like to share classes & resources (strings, layouts, etc…) > across multiple apps. > > Any pointers on how to structure Eclipse projects to do such a thing > is appreciated! -- 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
