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.
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:
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.
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.
For better or worse, this is how I explain the product roadmap.
Sunday morning. Using my little microscope to get some details right.
Captured with Picflick
Touchcards and Cardboard can import Google Docs spreadsheets as flashcards. One benefit to using Google Docs is that you can keep your decks safe in the cloud. You can also share them with others and manage changes more easily.
To make sure your spreadsheets are imported properly, use the following formats. You can paste the URL to an image instead of text if you want to have the app import a photo.
The first row is a header row and isn't imported. The columns correspond to question and answer.
You can provide multi-line answers if you need to.
You can add worksheets to your spreadsheet document. Each worksheet is a set of flashcards.
Save time and organize your thoughts better with this simple tip.
I admit I didn't know you could do this for a long time. Some users have told me this makes writing in Chapters a dream. Hopefully this helps you too.
If you use Chapters for iPad at work for notes/meetings/CRM/projects I'd like to show you something I'm working on. You'll have access to an early version for beta testing and will get a promo code for a free copy when it's finished. Contact me and tell me a little bit about how you're currently using the app.
Thanks!
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.
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.
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.
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.
Michelle and I quit our jobs (for the second time) more than two years ago. We moved from Atlanta to a smaller town and she started medical school. She wanted me to do something different and not rush into a job search. I started working on things I found interesting and thought others might like. I had invested in a MacBook and an iPod touch six months prior and was enjoying learning the iPhone SDK. I even had a few customers on the then-new App Store. I didn't know if I could make it last but it felt right to do what I loved.
These years have been very enjoyable for me. I was surprised at just how sad I felt after reading the news.
The following is a nice tribute from the developers at Panic:
Screenshot from Panic.com
A Picflick for iPhone user just sent me a link to this Cinemagraph gallery, mostly pulled from cinemagraphs.com but with some interesting interview content.
It should come as no surprise that we live in a global economy, that
it just takes a second for someone on one side of the world to contact
someone on the other. I know this. And yet I find myself moved when
I receive a message from someone whose first language is obviously not
English saying they like using software I wrote.
A video I made (I was going to say threw together but that implies it took < 30 minutes) that shows Picflick and some .gifs I made with it.