Project dependency: reusing code and resources from another Android project

by Mark Murphy » Thu, 10 Dec 2009 22:29:37 GMT


Sponsored Links
 > According to

Which gets you little, since you cannot force the user to install A.

-- 
Mark Murphy (a Commons Guy)
 http://commonsware.com 
Android App Developer Books:  http://commonsware.com/books.html 


--



Project dependency: reusing code and resources from another Android project

by Mark Murphy » Thu, 10 Dec 2009 22:49:37 GMT


 >> Which gets you little, since you cannot force the user to install A.

Which will irritate your users.


Which will irritate your users.

Hence, I stand by my assessment that, while there are ways for B to access
A's resources at runtime, in general, that's not a viable reuse model. You
are trading a trivial development-time inconvenience for a crappy user
experience, which won't be a good trade in most cases.

Your development-time symlink approach is about as good as it gets today,
at least for solo developers.

-- 
Mark Murphy (a Commons Guy)
 http://commonsware.com 
Android App Developer Books:  http://commonsware.com/books.html 


--


Sponsored Links


Project dependency: reusing code and resources from another Android project

by Mark Murphy » Fri, 11 Dec 2009 03:31:14 GMT


 > Well, in this case you have to go java way:

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 


--