>> Which gets you little, since you cannot force the user to install A. > > But you can: > 1) Notify user the A is missing. And disable B completely or partially > (depending on effect of missing A).
Which will irritate your users. > 2) Ask user if she wants to install A. If she agrees, then: > > Intent intent = new Intent(Intent.ACTION_VIEW); > intent.setDataAndType(<package-uri>, "application/vnd.android.package- > archive"); > startActivity(intent); 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 -- 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
