Itunes共享机制实现
http://www.raywenderlich.com/1948/itunes-tutorial-for-ios-how-to-integrate-itunes-file-sharing-with-your-ios-app
The iPad and iOS 4 have a great new feature called File Sharing that provides a convenient way for users to transfer files between their computer and your app.
But figuring out exactly what you need to do to get this working in real-world scenarios can be tricky. So I thought it would be useful to write an iTunes tutorial that covers how to do that with a real app, step by step!
If you’ve been following the development of the “Scary Bugs” app in the simple app tutorial or NSCoding tutorial, it’s all been leading up to this!
In those tutorials, we’ve been creating an app that allows you to collect scary bugs and rate them. However, it would be even better if users could share bugs with their friends (or mortal enemies!)
So let’s do it! You’ll need a copy of the ScaryBugs project where we last left off – if you don’t have it already, you can grab a copy here.
File Sharing Overview
Let’s start with an overview with how File Sharing works.
To enable File Sharing in your app, you simply set the boolean flag “UIFileSharingEnabled” in your info.plist.
iTunes will then display anything you save to the Documents directory
in your app to the user, when they go to the “Apps” page in iTunes and
scroll to the bottom:
Of course, for this to be of any use, your app needs to have some smarts in it.
First, your app needs to be able to detect the files that the user puts into this directory.
Second, your app needs to be able to deal with the fact that the
contents of this folder can change at any time. The user can rename
files, delete files, or even put garbage in there if they want.
Third, your app needs to have a way to export your app’s document as a single file, even if it consists of multiple files.
“But wait!”, you may say. “What about packages, can’t I just set up
my app to use a Document Package and have my folder of files be treated
like a single file?”
Well, about that…
File Sharing and Document Packages
If you want to skip this section and move on, the TLDR summary is:
Document Packages don’t work the way you’d expect with iTunes currently,
so you need to use an alternative solution.
But if you’re curious about them and why they don’t work, here’s some more information.
For those of you who are unfamiliar, packages are a way that iOS and
MacOS can treat a directory of files as a single file. This is used for
.apps – these are actually directories of files, with a standard
structure (a “bundle”).
Many apps on the Mac use store their documents as packages – Document Packages
to be specific. Again, these are simply directories with whatever
makes up the app’s document contents inside, often with a particular
file extension.
You can register your app as the owner of files with a particular
extension in your info.plist, and mark the type as a package with the
LSTypeIsPackage key. If you do this on the Mac and install your app to
your Applications folder, the OS will detect it and start treating any
directory with your registered extension as a package.
You can register your iOS app as being the owner of a file
type/extension that is a package as well. If you save it to the
Documents directory, you might think that it will show up in File
Sharing as a single file rather than a directory.
Well it does – but it doesn’t work exactly the way you’d think. It will show up in iTunes as a single file just fine:
However, when you save the package to disk, it will be saved as a folder, not as a single file:
To make it worse, there’s no way for the user to import the folder
back into iTunes, and they can mess around with the contents of the
folder.
You could get the package to show up as a single file if you also had
a companion app installed on the Mac, but most of the time as app
developers we won’t be able to guarantee that the user has the companion
app installed as well. Plus, this wouldn’t work at all on a PC.
So as I said, document packages just aren’t the way to go with File
Sharing at this point. “But wait!”, you may say. “What about Pages and
other Apple iPad apps, don’t they use packages just fine?”
Well, about that…
File Sharing and Pages
If you’re curious how Apple handles things, if you don’t have Pages you might want to check out this great article with a summary of the File Sharing process with Pages.
But as a quick summary, here’s how I understand Pages to work:
- The Pages documents aren’t actually packages, they are zipped packages so they can be treated as a single file.
- Pages actually has two separate lists of documents:
- The list of documents that Pages uses, in a private directory not available to the user.
- The list of documents that is available for File sharing, in the Documents directory.
- The user has to actually take a step to import or export a document
to/from File Sharing (it doesn’t just automatically show up). I believe
this is because it would be a performance penalty to constantly create
zipped copies of documents mirroring the actual documents.
So, in our case with Scary Bugs, we are in a similar situation since
we have documents made up with several files. Therefore, we are going
to take Apple’s approach, and have manual steps to import/export files
to File Sharing, and export our documents as zipped directories.
Importing and Exporting Our Documents
Ok enough talk, time for action! First things first – we’re going to use some helper code from the users at CocoaDev.com for gzip/gunzip. So grab a copy, and drag the two files into the Helpers group of your project.
Also, while you’re at it, these files require zlib, so go to your project settings and add “-lz” to your “Other Linker Flags”.
Now onto the code! Let’s start by adding the code to our ScaryBugDoc
to support exporting and importing our documents as a zipped file that
we can share with File Sharing.
First make the following mods to ScaryBugDoc.h:
// After @interface |
Just declaring some methods we’re about to implement here. Switch over to ScaryBugDoc.m and let’s implement them one by one:
1) Implement getExportFileName
// Add to top of file |
This method will return the name that we’re going to export our bug as. We don’t want to export the bug with a simple numeric directory name like our documents are named internally, because then our user will have no good way of knowing what’s inside. So instead, we use the title of the bug to construct the filename.
Speaking of which, I’m not sure if there’s an easy way to massage the filename so it doesn’t contain any unsupported characters on both Mac and Windows, anybody know a solution to that?
The other thing to note is that we end the filename with an extension “.sbz” which we’ll register our app as being able to open later. When I was first playing around with this, I tried using a double extension such as “.scarybug.gz”, but when I was trying to open the attachment from Mail, it would never launch my app, and I suspect it didn’t like the double extension. So I recommend using just a single extension for now.
2) Implement exportToNSData
So now we need a method to take our directory and convert it into a single buffer of NSData so we can write it out to a single file.
There are different ways to do this – one popular way is to zip the directory up using the open source ZipArchive library. Another popular way is to use a combination of tar and gzip code. But I thought I’d show you another way: using NSFileWrapper to serialize the data, then gzipping that up.
- (NSData *)exportToNSData { |
NSFileWrapper is a new class available in iOS4+ that among other things provides an easy way to serialize entire directory contents. As you can see it’s pretty simple to use here: we just initialize it with a URL, then we can get an NSData representation of a directory by calling serializedRepresentation.
This isn’t compressed, so we use the gzipDeflate helper method from the NSData extensions we downloaded earlier to do that.
3) Implement exportToDiskWithForce
- (BOOL)exportToDiskWithForce:(BOOL)force { |
The first thing we do here is construct the full path to where we’re going to save our zipped document. Note this time we’re saving in the Documents directory (not Library\Private Data), because the Documents directory is what’s available for File Sharing.
Next we check to see if the file is already there. If it is, we’re going to want to present a warning to the user, so we return FALSE unless the user forces the save.
Finally, we just make a call to export it as NSData, and simply write it out to the disk.
4) Implement importFromPath
- (BOOL)importData:(NSData *)zippedData { |
We’re actually going to extract most of the work from importFromPath into a helper function called importData, because it will be useful later.
In importData, we just do the opposite of what we did in exportData – we inflate the zipped contents and use NSFileWrapper to expand it again with writeToURL:options:originalContentsURL:error.
As for the destination file name, we just create the next available file name. So we’re never overwriting an existing file when you import, we always create a new file. This is by design to avoid the user from accidentally overwriting their files. If they import the same file twice, they’ll have a duplicate, but they can easily delete files.
Ok – that’s it for the core code. There’s still a bit more to do to integrate into the rest of the app though – we have to make some mods to the ScaryBugDatabase and add some GUI elements to support this.
Integration into App
Just a few steps to integrate this into the rest of the app…
1) Add a helper function to ScaryBugDatabase
We’re going to need a method to return the list of documents that the user can choose to import, so add the following to ScaryBugDatabase.h:
+ (NSMutableArray *)importableScaryBugDocs; |
Then implement it in ScaryBugDatabase.m:
+ (NSMutableArray *)importableScaryBugDocs { |
This should be fairly straightforward stuff by now – we just enumerate all of the files in the Documents directory, looking for anything that ends with sbz, and add the full path of anything we find to a NSMutableArray.
2) Modify EditBugViewController to export documents
Make the following changes to EditBugViewController.h:
// Add the UIAlertViewDelegate protocol to the interface declaration |
Then make the following changes to EditBugViewController.m:
// Add inside viewDidLoad |
Here we just add a new navigation item to our bar with the title “Export”. When the user taps it, we’ll try exporting to disk – and if the file exists present them with a warning, and only overwrite it if they accept.
Note we’re using NSOperationQueues and an activity indicator to make for a nicer user experience for the user. If you’re unsure about how this works, check out the How To Create A Simple iPhone App Tutorial: Part 3/3 tutorial.
3) Create a new view controller to allow user to choose a document to import
We’re going to need a new view controller to list the importable documents so the user can choose one.
We’ll just do something quick and dirty for this. Right click on the View Controllers group, and click “Add\New File…”. Choose UIViewController subclass, and make sure “Targeted for iPad” and “With XIB for user interface” are unchecked, but “UITableViewController subclass” IS checked, and click Next. Name the file ImportBugViewController.m, and click Finish.
Then replace ImportBugViewController.h with the following:
#import <UIKit/UIKit.h> |
Note we’re setting up a delegate here so we can notify the root view controller when the user selects a bug to import.
Next make the following changes to ImportBugViewController.m:
// Under @implementation |
This should all be pretty standard table view setup to you by now, so no need to discuss this further.
One thing to note though: here we’re displaying just the filename of the object, because to get anything else we’d have to unzip the documents (an expensive operation). However Pages seems to have a thumbnail to go along with their documents. Anyone have any idea how they managed that?
4) Modify RootViewController to have an Import from File Sharing Option
Make the following mods to RootViewController.h:
// At top of file |
Next, make the following changes to RootViewController.m:
// Under @implementation |
So, what we did here was make it so when the user taps the “+” button, instead of just adding a row we ask the user if they want to add a row, or import an existing doc.
If they choose to import a doc, we create our import bug view controller, get the list of importable docs from the ScaryBugDatabase, and pass that onto the controller and dispaly it.
Finally when the user chooses a doc, we call the importFromPath method we wrote earlier, and add the document.
One last thing then we’re done!
5) Enable File Sharing in the Info.plist
Finally open up ScaryBugs-Info.plist and add a new boolean key called UIFileSharingEnabled and make sure it’s checked:
Phew! It was a long, crazy process but we’re finally done and get to enjoy the fruits of our labor!
Trying It Out
Build and run your project, and make sure you install it on your iPhone (i.e. not your Simulator), because File Sharing only works with iTunes on a physical device.
You can test that the OS detected your “UIFileSharingEnabled” flag by loading up iTunes, switching to the Apps Tab, and scrolling down: you should see your app there as long as your device is connected:
If it doesn’t show up, try deleting the app from your device and re-installing, and synching iTunes.
Next go ahead and create a new bug, and tap Export. You should immediately see a new entry in the Scary Bug Documents in iTunes File Sharing:
Now for some fun. Download a copy of a sample bug I made. Then in File Sharing in iTunes click “Add…” and browse to the file you downloaded.
Finally, go to the table view in Scary Bugs, tap the “+” button, and tap “Import Bug”. Choose the file you downloaded and you should see a new bug appear on your screen!
Where To Go From Here?
Attached is a sample project with the code we’ve developed in the above iTunes tutorial.
Theres still a little bit of life left in these bugs! Next up is a tutorial on how to import and export your bug documents via email – which will be a snap considering all of the groundwork we’ve laid so far!
Itunes共享机制实现的更多相关文章
- 使用WMI来控制Windows目录 和windows共享机制
1.使用WMI来控制Windows目录 本文主要介绍如何使用WMI来查询目录是否存在.文件是否存在.如何建立目录.删除目录,删除文件.如何利用命令行拷贝文件,如何利用WMI拷贝文件 using Sys ...
- ActiveMQ新的Master/Slave存储共享机制Replicated LevelDB Store
ActiveMQ新的Master/Slave存储共享机制Replicated LevelDB Store 使用ZooKeeper协调选择一个node作为master.被选择的master broker ...
- Android背后的设计思想——功能共享机制
Android的系统设计,与别的智能手机操作系统有很大区别,甚至在以往的任何操作系统里,很难找到像Android这样进行全面地系统级创新的操作系统.从创新层面上来说,Android编程上的思想和支持这 ...
- linux下的KSM内存共享机制分析
2017-04-26 KSM是内核中的一种内存共享机制,在2.6.36版本的内核中开始引入,简单来说就是其会 合并某些相同的页面以减少页面冗余.在内核中有一个KSM守护进程 ksmd,它定期扫描用户向 ...
- 分布式session共享机制分析
使用配置: 1.在pom文件中引入spring-session的jar包 <!--springsession--><dependency><groupId>org. ...
- unittest的前置后置,pytest的fixture和共享机制conftest.py
Unittest setUp/tearDown setUp当中得到的变量,用self.xxx = value传递给测试用例 setUpClass/tearDownClass setupClass当中得 ...
- 大叔也说Xamarin~Android篇~为HttpClient共享Session,android与api的session共享机制
回到目录 杂谈 在进行android进行开发时,我们的数据一般通过接口来获收,这里指的接口泛指web api,webservice,wcf,web应用程序等:它们做为服务端与数据库进行直接通讯,而AP ...
- Qt隐式共享机制
1.浅拷贝 浅拷贝-引用类型.浅拷贝是指源对象与拷贝对象共用一份实体,仅仅是引用的变量不同(名称不同),对其中任何一个对象的改动都会影响另外一个对象. 2.深拷贝 而深拷贝-值类型.深拷贝是指源对象与 ...
- JS的prototype的共享机制分析
function Super(){ } Super.prototype.aaa=[1,2,3]; Super.prototype.bbb=1; function Sub(){ Super.call(t ...
随机推荐
- 甩掉DataList,Repeater,列表数据显示得灵活--转
在WebForm 显示列表数据我们一般使用服务器控件Repeater.DataList或者GridView ,功强大能,使用简单.但同时也是有代价的, 一:不管你用哪个控件都需要牺牲一些额外的性能,因 ...
- HDU4248【DP】
题意: 有n种石头,每种石头有a[i]个,然后让你去组合,问有多少种组合: 思路: 这种题,排列组合知识一上,非常麻烦,已经搞了好几题,看似就是排列组合的姿势,然而最终都是一种递推,也就是DP,而且比 ...
- CentOS Linux 7 提示 lsof: 未找到命令
我们常使用 lsof -i:端口号 命令来查看某端口是否开放,如使用下面的命令,查看8080端口: lsof -i: 结果: 提示:lsof:未找到命令 解决办法 使用yum来安装lsof,命令如下: ...
- [Xcode 实际操作]七、文件与数据-(20)CoreML机器学习框架:检测和识别图片中的物体
目录:[Swift]Xcode实际操作 本文将演示机器学习框架的使用,实现对图片中物体的检测和识别. 首先访问苹果开发者网站关于机器学习的网址: https://developer.apple.com ...
- Spring Cloud:使用Ribbon实现负载均衡详解(下)
在上一篇文章(Spring Cloud:使用Ribbon实现负载均衡详解(上))中,我对 Ribbon 做了一个介绍,Ribbon 可以实现直接通过服务名称对服务进行访问.这一篇文章我详细分析一下如何 ...
- Aufree/trip-to-iOS
https://github.com/Aufree/trip-to-iOS?utm_source=next.36kr.com
- hyperledger fabric 1.0.5 分布式部署 (一)
环境是个人虚拟机ubuntu 16.04 64 位版本 前期用户需要先安装好:gcc.g++.git 软件 安装 golang 首先给环境安装一个 go 语言环境,版本最好在1.8 以上 golang ...
- Spring pom.xml配置
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/20 ...
- POJ3744(概率dp)
思路:一长段概率乘过去最后会趋于平稳,所以因为地雷只有10个,可以疯狂压缩其位置,这样就不需要矩阵乘优化了.另外初始化f[0] = 0, f[1] = 1,相当于从1开始走吧.双倍经验:洛谷1052. ...
- 关于JVM的一些东西
1.在JDK1.6(HotSpot虚拟机)及之前,运行时常量池(属于方法区的一部分)是永久代的,而在JDK1.7之后运行时常量池(里面用于存放编译期生成的各种字面量和符号引用,这部分内容将在类加载后进 ...