Programming posts

Welcome to Friday Favorites! Every Friday, one of us will get all sloppy over an app, web service, or Mac feature that makes us grin like an idiot every time we use it. This week, Brett tells us about his favorite new snippet manager.

If you write code, you probably reuse blocks of it. Whether you're working in HTML, CSS, AppleScript, Objective-C ... it's all code, and a really well-written chunk of it deserves to be used again. You can put a few of your most commonly used snippets into TextExpander, sure, but the biggest problem is finding that function you know you wrote last year but haven't used since. This common little conundrum has given rise to some very elegant applications that aim to solve this and other related problems.

There have been a few great options lately for snippet organization. CodeCollector Pro has been my long-running favorite, with Snippet a close second. I like Snippet's sexiness, but miss having a nice, big, multi-pane window to organize with. CodeCollector Pro is a solid workhorse, but actions such as adding new snippets are a little more cumbersome than I'd like. I often just clip things into Evernote when I'm in a hurry ...

Then, along came Snippets (note the 's' that differentiates it from Snippet) to steal my heart. It's got Code Collector's utility, Evernote's searchability, and it's got an extra dash of sexy, ala Snippet. It has the standard sytax-highlighted code viewer, and a sidebar with groups and folders. Snippets are classified by language, which can be set in a dropdown or by just dragging a snippet to a language folder. It functions on a hybrid folder/tag concept, which happens to be the way I do just about everything. Each snippet can have a description, as well as labels (tags) and all full-text indexed for searching. You've also got groups, which are like folders, but a snippet can belong to multiple groups. It has smart folders which, as you know, function like automatic groups with boolean criteria. On top of all that, folders, smart folders and groups can all be gathered hierarchically in nested folders, with parent folders showing all of the contents of their child folders. Whew!

Evernote, a versatile (and oft-mentioned) note-taking application for Mac and iPhone (as well as Windows and other mobile platforms), has recently opened up a Service API. This comes as an intriguing extension to the basic AppleScript support found in the 1.1.5 release, and opens up the possibility of creating homegrown interfaces ranging from simple calendar/todo managers to "thick" clients which can manipulate the entire collection of Evernote data.

The AppleScript library itself is quite useful, albeit slightly limiting. You can retrieve lists of notes based on searches, create new notebooks and notes from a variety of sources, and obtain properties for the various elements of Evernote. The most interesting feature of the AppleScript library is the import/export automation capability. You can export (in well-formed XML) entire notebooks, or notes from a list (such as one generated by a search). These can be transported automatically by whatever means work best for your purposes, and then imported on the other end. This, to me, is primarily interesting because it allows for "local" synchronization of large libraries without using up online quotas. It's also ideal for automatic backup of your notes, among other potential applications: a recent MacOSXHints tip shows a means of adding notes to Evernote via Quicksilver, complete with notebook, title and tagging syntax. Open the Evernote dictionary in Script Editor for the full set of definitions.

The AppleScript library lacks the ability to add tags to existing notes, move notes or delete notes and notebooks. These functions can, however, be found in the Service API. I'm waiting on an API key today, but I'm looking forward to exploring the possibilities for both desktop and web applications. Libraries for the API are available in Java, Perl, PHP, Python and Ruby -- along with sample code and documentation -- at the API overview page.

The last thing I'll mention is the query syntax, which can be of as much use in the Evernote search bar as it is in an AppleScript or API call. I hadn't fully realized the extent of the search grammar until I read the API documentation. For Evernote users who haven't explored this, it's a very effective way to build searches quickly without a lot of token-clicking. You can start with the basic tag syntax: tag:"tuaw", which will find every note tagged with "tuaw." Prefix it with a minus sign (-tag:"tuaw") to ignore any result with the "tuaw" tag. Combine multiple search parameters for boolean searches; the default search is "all", requiring the results to match every parameter in the string (AND), but you can prefix the query with any: to make it an OR search. Other possible parameters include created: and updated: (which respond to some natural language dates as well as a compact profile of ISO 8601), intitle: (search only in the titles of notes), as well as terms for narrowing to a specific notebook or querying just about any attribute of a note (latitude, longitude, altitude, author, source, etc.). See section C of the API docs for a full description of the search grammar.

It's great to see such a useful application continuing to expand itself and allow for third-party interaction. If you're interested in developing around Evernote, or just playing with the possibilities, stop by the developer page and take a look around.

Do you want to write Cocoa applications, but happen to be handier with Javascript than with Objective-C? JSCocoa to the rescue! Similar in concept to RubyCocoa, JSCocoa provides a bridge between Webkit's JavascriptCore and Cocoa, allowing you to call C and Objective-C code, as well as build Javascript classes which inherit from Objective-C classes.

Visit the Google Code page for a quickstart and some syntax explanations. JSCocoa is open source and available for subversion checkout or direct download.