From 11b075e218b9921a953eeebe73fcd1a8a81f764b Mon Sep 17 00:00:00 2001 From: Nick Pelly Date: Thu, 28 Oct 2010 13:39:37 -0700 Subject: Hide some NFC API's. We are leaving enough API so that you can see when any Tag is discovered, get its ID, and get its NDEF messages. But for advanced use - creating tag connections and writing messages - we have 2 problems. Firstly a lot of the code is untested (RawTagConnection.transceive()), or in some cases known not to work (NdefTagConnection.write()). Secondly, there is still debate about how to best expose information about Tags. The set of data/methods exposed for a Tag changes completely depending on the tag technology. There may be multiple sets of technology implemented in a single tag. Tag A may have technology X and Y, Tag B may have technology Y and Z. Furthermore, some NFC controllers will be not be able to use all technologies, and so Android Device 1 may see technology X and Y on Tag A but Android device 2 may only see technology X. So we have a pretty challenging set of constraints to work under, and we are not convinced the current Tag and NdefTag class is the best approach going forwards. The Tag application should be able to remain unbundled, since it just needs to get incoming NDEF Messages. Change-Id: Ic09f094f33794e10f8d730fffe011c9a5957e0ac Signed-off-by: Nick Pelly --- core/res/AndroidManifest.xml | 1 - 1 file changed, 1 deletion(-) (limited to 'core/res/AndroidManifest.xml') diff --git a/core/res/AndroidManifest.xml b/core/res/AndroidManifest.xml index a22c827..07a48e7 100644 --- a/core/res/AndroidManifest.xml +++ b/core/res/AndroidManifest.xml @@ -86,7 +86,6 @@ - -- cgit v1.1