Another solution would be to be able to associate a manifest with a
class in some manner and importing/using that class would aggregate
its manifest into your own. Potentially for only a subset of a
current manifest's features...
Hmmm... It just seems silly that if someone wants to use my Utility
class that includes SMS read/write capabilities, they have to add:
<uses-permission android:name="android.permission.RECEIVE_SMS" /> to
their project's manifest.
Heck, a new version of a class can therefore break currently compiling
code (although you can of course stipulate that the permissions
requirements have changed, but again, that puts the onus on the person
using your code when I'd rather do the work for them.)
Hans :)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
