I’ve had a couple of interesting days, stretching some mental muscles:
- Finally digging into creating some Alfred workflows to streamline common stuff I do on my Macs. I’m just scratching the surface of what workflows are capable of, and just getting started.
- Spending some time digging into using SQL Server’s XML handling capabilities to shred highly-structured XML into relational data. Kind of mind-warping, but an interesting challenge. Definitely learning, and fairly impressed with the speed.
Gone for most of last week on work-related travel to DC, and just now catching up:
- My travel mojo is alive and well: I made it home without any interruptions or delays for a change, but awoke on the date of my scheduled departure to find a text message from Delta indicating my first leg had been canceled and that I had been rebooked on a different set of flights arriving (thankfully) very late the same day.
- A new CFML server showed up last week: Lucee, a fork from Railo and which likely spells the end of Railo as a thing. I’ve deployed it via Tomcat on two of the systems where I do development so that I can play with it a bit.
- 4,700 spam comments on various entries in my blog. Ugh.
- TUAW is being shut down. Ugh. That’s a loss, as TUAW has been one of my go-to sites for keeping tab on all things Apple, Mac OS X, and iOS.
Version 0.2.4 of my language extension supporting CFML for ActiveState’s Komodo IDE/Edit is now available. This update represents a minor bump in the version number but also represents more work behind the scenes than any update in recent memory, as all of the plumbing in the extension has been replaced so that it will work with the forthcoming Komodo v9 releases while still working with Komodo v8.x in addition to the changes below.
A Quick Summary of Changes
In addition to the rework noted above to support Komodo v9, this update provides the following changes:
- Tag and attribute support for Adobe ColdFusion v11
- Numerous updates and fixes to the tag and attribute support for Adobe ColdFusion v10
- Switched to cfdocs.org for CFML-specific language help
- Includes a small set of CFML-specific macros (look for “CFML Tools” in Komodo’s Toolbox panel) and puts the scaffolding in place for language-specific macros, snippets, abbreviations, etc.
- A minor change to the syntax highlighting applied to CFML comments occurring within function calls (very edge-case-ish)
A Note About Installation/Upgrading
With this update, you will notice that the structure of the name of the editor extension file itself has changed. Where in the past, the editor extension file was named cfml-0.2.3-ko.xpi, this version is named komodo-cfml-0.2.4a0-ko.xpi. There are two changes there to note:
- The base part of the file name has changed, primarily as part of the reworking of the basic structure of the editor extension for compatibility with Komodo v9; and
- I have changed the embedded versioning information for the extension so I have a bit more flexibility in how I keep track of updates and additions to the extension.
With these changes to the name of the editor extension file, you will want to explicitly uninstall whatever version of Komodo-CFML you may currently be using and then install this new version to avoid any sort of potential confusion within Komodo about how CFML files are to be handled.
The updated version of the extension is available for download:
As always, comments and follow-up are welcome here or on the Komodo-CFML page.
I’ve been using Google’s Inbox for the past couple months — almost exclusively, in fact — since getting my invitation, and my initial impression is that at this point it is pretty good for reading email but it currently has holes.
The most significant deficiency for me seems like a huge hole for anyone who does anything other than read and delete email: no access to contacts. None. No way to look for contacts or their information. No way to add addresses and information from email to contacts. No way to create contacts. (I have not tried using it with address lists.) It does use contacts to help address emails but as best I can tell, that’s the extent of its use of contacts. This, so far, is the one thing that has forced me several times to go back to Gmail when I needed to either look up something about a contact or create a new contact.
I like the ability to snooze emails (but I think Dropbox’s Mailbox does it better), and I like the ability to pin emails with “remember to…” annotations. Most of the normal Gmail keyboard interactions — aside from labeling, more on this below — for archiving, deleting, marking as spam, etc., work. I like that Inbox works well on my Android phone and tablet (both running different versions on Android, neither of which is Lollipop — something I can’t do with Mailbox).
The other significant hole is that Gmail’s keyboard interface for labeling emails (yes, I’m a labeler) is not supported. This would be a more significant gap for me at work, where I often apply multiple labels to an individual email and where I am almost exclusively on a computer (as opposed to phone or tablet), but even in my personal email I miss the easy/quick keyboard-driven way of tagging messages. Inbox’s current UI makes it difficult (maybe impossible) to apply multiple labels to a message, and is more based on the “messages in folders” metaphor.
I’m still hoping Inbox sees some significant evolution in the near future. Without that evolution, I’m likely to abandon it and go back to Gmail. I would be giving up the annotated pinning and message snoozing, but would still have better-than-just-decent interfaces on phone and tablet, integration with contacts, and full keyboard interaction support when at a computer.
I spent a bit of time today playing with Atom, and it does not suck. I have to admit I went into it with low expectations.
Things I like (in no particular order):
- a UI that obviously is designed to support largely keyboard-driven interaction (e.g., it is very straightforward to turn on/off soft-wrapping of text, something that I need for whatever I use for my Q&D text editing, as soft-wrap for drafting text = necessary while soft-wrap for any sort of code = worse than bad),
- a language mode for CFML (thank you, Adam Tuttle) already available,
- availability of Emmet as a package,
- a reasonably-polished preferences UI that makes it simple to configure.
Perfect? Not by a long shot. But good enough to convince me that I need to poke a little further before I write it off.