The initial iPod was released on October 23, 2001. I’m pleased to note that mine is still going strong 14 years later. It’s funny now to look back and remember that I was absolutely sure I’d never be able to fill up five gigs with just music, or as Apple put it “1000 songs in your pocket.”
I used my first iPod a lot for just listening to music, especially on the bus or working in the library, but I also used it for teaching. The fact that I could mount it as a drive via FireWire meant I could show students short film clips of plays or play audio files via the lecture hall’s sound system or workstation.
Now, I have music on my iPhone, but not so much as I used to; I’m streaming a lot more via local WiFi. Instead, that storage that might have been used for music is now being used for photos and ebooks.
I predicted that we’d be reading ebooks more; I missed entirely how much we’d be taking photos with our phone—though I used the cameras a lot on my iPhone 1 and 3, I mostly used them to take pictures of things I couldn’t see well, like street signs or small text on boxes. Now, I’m using the iPhone 5 camera more than my dedicated camera—and it’s changed the way I take pictures.
No, I’m not taking selfies, but I am taking a lot more spontaneous shotsbecause the iPhone is right there, and I’m still using the iPhone camera as a visual aid, even though new plastics have made distance and close reading glasses possible for me. But I’m sending friends and families more photos than I ever did before—and seeing more in response, too.
My co-writer Michael Cohen has an interesting piece over at TidBITS on the just published “Enhanced” edition of Rowling’s Harry Potter series. They were made with the current version of iBooks Author, and are therefor exclusively available at the iBooks store.
What’s interesting to me, especially, is that this version of iBooks Author looks like academics could use it to create basic annotated editions or course readers, ebooks with limited enhancements, that would be fairly simple to create and still look professional.
I have another article over at my publishers, Peachpit on the new iOS 8 keyboard features, including the ability to add third-party keyboards.
One of the innovative aspects of iOS in its initial release was the way the onscreen digital keyboard and multi-touch combined to make a large number of characters available within limited screen space. Since that first iOS release in June 2007, Apple has improved the onscreen keyboard enormously. In iOS 8, Apple also added a special keyboard for Emoji (smileys), a new typing feature called the QuickType bar (see Figure 1), and support for third-party onscreen keyboards from the App Store.
I first heard about Markdown back in 2004. I’d been blogging for a few years, and and hand-coding HTML. I came to HTML with surface familiarity with SGML in a library and deep familiarity with WordPerfect and WordStar. I’d been following Dean Allen’s development of Textile, and using Brad Choate’s MT-Textile plug-in for MovableType. John Gruber of Daring Fireball (one of the blogs that introduced me to blogging) created Markdown (with assistance from Aaron Swartz) as a way to format text for the Web without having to delve into HTML. In 2004 Gruber wrote about Markdown:
Markdown is a text-to-HTML conversion tool for web writers. Markdown allows you to write using an easy-to-read, easy-to-write plain text format, then convert it to structurally valid XHTML (or HTML).
One of the virtues of Markdown is that it is easy to use, and easy to remember. In Markdown, you use *for bold*, _ for italic_. Headings are marked by a leading *for the largest heading, **for the next size down, ***for the next level. The tags are easier to remember and shorter than those for HTML. They’re minimalist, and less likely to obscure text and slow down writing or editing.
When I discovered that Gruber’s Markdown Perl scripts worked with MovableType (this blog ran on MovableType then), I installed it and used it for a while. When I moved from MovableType, I stopped actively using Markdown, but I remained interested in both Markdown and Textile (and even used TextPattern Dean Allen’s CMS bases on Textile). But recently, I became much more actively interested in Markdown for a couple of reasons.
A Markdown file is liquid data; it’s going to be easy to convert in the future, just as it is easy now to covert Markdown formatted text files to HTML, RTF, .Doc, or .PDF.
Markdown means fewer keystrokes than HTML. That means less keyboarding and no reaching for a palette or button to click. The longest tag I know of is three characters in a row.
Markdown lets you use HTML as needed, without having to do anything exotic involving obscure technical feats or escape codes.
Markdown may be easier to implement than HTML when writing on an iPad. At least that’s my current theory.
Markdown allows you to concentrate on the text as content, rather than the text as document.
Last year I wrote a long essay (eventually published by Boing Boing) that I initially drafted in Markdown, then hand-converted to HTML. I know, now, that there were better ways to do that, but I used BBEdit for the Markdown version and for the conversion to HTML, so it was relatively trivial to do. BBEdit not only fully supports Markdown as a language, it was one of the first applications Gruber provided Markdown tools for. The current version of BBEdit (11.0.2) has built in support for Markdown (including the ability to Preview Markdown files in BBEdit and customizable syntax coloring). And using Markdown in documents destined for the Web doesn’t mean I can’t simply insert any HTML I need that isn’t covered by Markdown tags.
For any markup that is not covered by Markdown’s syntax, you simply use HTML itself. There’s no need to preface it or delimit it to indicate that you’re switching from Markdown to HTML; you just use the tags.— John Gruber
If you want more BBEdit Markdown support, Watts Martin has created a nifty BBEdit Markdown Extension Package that builds on the work of John Gruber and Aaron Swartz, and adds some additional commands, not the least of which are Transformation commands to convert Markdown to HTML, HTML to Markdown, and Markdown to BBCode. There’s a catch to using Markdown in BBEdit; you have to set Markdown as a Language in BBEdit’s Preferences, and you need to use “.md” and “.mdown” as file name suffixes/extensions.
I’m going to spend a few weeks or months deliberately using Markdown as much as possible. I’ve installed Watts Martins Markdown Extension Package in BBEdit. WordPress via a Jetpack plugin supports Markdown, and there are a number of dedicated Markdown editors for OS X (Markdown Pro from RADSense Software, Mou from 25.io, Typed from Realmac Software) and iOS (Editorial from OMZ Software, Byword from Metaclassy, and others).
Given the release of Yosemite for OS X and iOS 8, I’m taking the opportunity to re-examine and revise my writing workflow. I write a great deal, not only books and articles for publishers, but blog posts and email. I am an Admin for a number of large Websites. Two of the Websites include not only site Admin, but Managing Editor tasks, including answering questions from readers and general user support for contributors. Both of these involves email either to individuals or to one of several private email lists. One of the Websites, Absolute Write, requres a fair amount of user / member support, including writing (and answering) FAQs, emails, private email lists, local message systems, and the Absolute Write Website and blog.
And then there are the Websites I admin for various writers, and my own Websites.
It’s a lot of daily writing. And it’s fairly constant throughout the day (and night).
I have some workflow tools in place:
I use TextExpander on all my iOS and OS X devices, and it’s a huge labor and keystroke saver.
I use filters or “Rules” in Mail.app, but even so, I receive around 175 emails from individuals a day, and send about that many or more. ( I’m increasingly considering an alternative to mail.app, at least on iOS, just to reduce main-management frustrations.)
I use custom scripts and and droplets for many of my frequent tasks.
These are some of the changes I’m considering:
I generally draft my shorter articles and blog posts in BBEdit using HTML. I’m going to look more closely at using Markdown, especially because Markdown is thriving on iOS and BBEdit has built in support for Markdown.
I already use iOS a great deal for email triage (especially via my iPhone); I’d like to do more with email on iOS, especially responding to email on the iPad.
I’d like to try writing more of my shorter pieces on iOS. I can write longer pieces on the iPad more easily now with the Brydge + iPad keyboard.
I do a lot of writing in Google Docs/Google Drive, but for book-length pieces Google Docs is not optimal. I’d like to move to Apple’s Pages as my primary word processor, particularly given the newly released version of Pages with collaboration and sharing via the Web/iCloud and Pages for iOS, as well as on OS X.
I’m sure I’ll discover more ways to improve my workflow as I continue.