rock and scroll

Thank you

Meetings for iPad climbed steadily after debuting earlier this week.  I'll have more to say about all this later but this is certainly one of many things I'm thankful for this year.

Moving entries from one device to another in Chronicle

It's possible to move entries written on one device in Chronicle to another device using the backup and import feature.  This lets you write things on your iPhone and later transfer them to your iPad, for example.

There are two ways to move the entries: one is by using iTunes File Sharing, and the other is by using Dropbox.

One way: Using iTunes File Sharing

When you connect your iPhone or iPad to your computer you can open the iTunes application on your computer and browse the contents of the Chronicle folder.  If you've created any .backup files, you can see them (and save them to your computer).

Here's how you would move some entries from your iPhone to your iPad using iTunes File Sharing:

• Create a .backup file on your iPhone by tapping the settings gear and tapping "Backup and Import"
• Connect your iPhone to your computer and open iTunes
• Browse Chronicle's folder on your iPhone using these steps (click to see steps)
• Save the .backup file to your PC or Mac
• Next, connect your iPad to your computer (you can disconnect your iPhone)
• Browse your iPad and view the Chronicle folder
• Drag-and-drop or add the .backup you saved in the step above to your iPad
• Next, open Chronicle on your iPad and tap the settings gear
• Tap "Backup and Import" and select the .backup you copied
• Tap the Import button

Put simply, you're copying the .backup file from your iPhone to your iPad and then importing it.

 

Another way: Using Dropbox

If you have Chronicle on your iPhone and iPad configured to use your Dropbox account you can easily move .backup files from one device to the other.  It's important to configure each app to use the same sub-folder of your Dropbox account (so both copies of the app "see" the same folder).  For example, you might have a Dropbox folder named 'chronicle' that both copies of the app are configured to use and store backups in.

• Create a .backup on your iPhone by tapping settings > "backup and import" > "backup"
• Grab your iPad and tap settings > "backup and import" > "import"
• The .backup file you created in the first step (from the iPhone) should appear in the listing on your iPad
• Tap to select the appropriate .backup file and then tap "Import"

 

This is much easier to do because the app can handle moving the .backup to and from each device via Dropbox.  When your copy of Chronicle is configured to use Dropbox, every .backup file you create is automatically uploaded to Dropbox.  Likewise, when you browse for .backup files to import on your device, you see ones that are present physically on your device as well as any that are in your Dropbox folder.  The app is able to download the files from Dropbox without you having to do anything.

Product roadmap - where is this going

For better or worse, this is how I explain the product roadmap.

Using a static library in Xcode 4

Today I'd like to share some information on a topic that is dear to me: building static libraries with your Xcode projects.

I launched into testing something today and ran into issues I hadn't encountered under Xcode 3.  In the course of searching for the one right way to add static libraries to my project I found many forum and blog posts, all a little different from one another (and most from earlier this year).

Here are the steps for setting up my test project.

Set up your Workspace

First I created a static library project using Xcode's static library template (File...New...New Project...)

Next I created a workspace using Xcode (File...New...New Workspace). This is the preferred way of grouping related projects, and in this case I want to group my static library project with the project that relies on it.

Note that existing projects can be converted into workspaces (File...Save As Workspace...).

I created a new project called SimpleSearchDemo within the workspace. I then control-clicked under that project in the navigator to add my existing SimpleSearch static library .xcodeproj file.

A note: I repeatedly tried adding my static library project to this workspace but it kept appearing without the disclosure arrow.  After an hour or two I had a headache and restarted Xcode and tried again. It worked as expected. I still think about those hours sometimes. Collateral damage.

Edit your static library build settings

Next I selected the static library project to edit its build settings. I set it up to skip install and made sure the Copy Headers build phase included the headers. In particular, I added the public-facing header to the Public section.

Configure the project that uses the library

Once the static library was set up, it was time to configure the client project.

Link the static library with the project target; it should appear under 'Workspace' libraries.

Adjust the build settings so that the User Header Search Paths include the directory where the static library's headers are copied. I used the BUILT_PRODUCTS_DIR after reading this post. Both projects belong to the same Workspace, and thus share a common build directory.  Enable recursive searching of the user header search paths, and enable Always Search User Paths.

Finally, ensure the static library is built for archiving.

One other thing. I had issues with code completion working. I dragged the "public" header from the static library into the client project, and unchecked the 'Add to targets' checkbox.  Autocompletion started working (the header is right there, after all), but this seems unnecessary - let me know how you got around it.  Any other improvements are welcome.