b) Use SE Boolean values to enable "Intent MMAC" entries, thus
allowing for instance Camera access to only a certain set of apps
after it is allowed, "in principle";
Sorta sounds like the new AppOps service feature that was released with
4.3. Would that new functionality meet your design goals? We are
currently porting existing code and implementing new stuff on top of
that feature. We should have an initial release of that soon.
c) "Combine" the handling of the availability of a feature [e.g.
PackageManager.hasSystemFeature(PackageManager.FEATURE_CAMERA)] and a
"pre-defined", named SE Boolean, so that:
hasSytemFeature() returns "true", iff "device supports
camera" AND "SE Boolean allows its use";
Reflect this also in the method "getSystemAvailableFeatures()";
I certainly get that having a boolean to toggle the state of the camera
would be confusing if the device doesn't even have a camera. With your
proposed changes though, what if the camera use is toggled back on via
the boolean but the hasSytemFeature() has already executed and reported
back that no camera exists. Just a thought.
--
This message was distributed to subscribers of the seandroid-list mailing list.
If you no longer wish to subscribe, send mail to [email protected] with
the words "unsubscribe seandroid-list" without quotes as the message.
