I've ended up with a 'build' project which is merely a set of symbolic links to 'real' projects. This approach works perfectly for me :)
On Dec 10, 9:30 pm, "Mark Murphy" <[email protected]> wrote: > > Well, in this case you have to go java way: > > getClassLoader().getResourceAsStream("name it what you like") > > will pick up whateher you like from jar files on classpath ( though > > not as > > convenient as android APIs ) > > Moreover, that'll just give you a stream. It won't work for anything that > needs a resource ID, won't support resource sets (e.g., i18n, landscape > vs. portrait), and so on. Unfortunately, Java's "resources" and Android's > "resources" share a name, a very high level concept, and nothing else. > > -- > Mark Murphy (a Commons Guy)http://commonsware.com > Android App Developer Books:http://commonsware.com/books.html -- 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
