I’m very pleased to announce the release of Capsule v1.1 (and Capsule Server v1.1). In this release we added some pretty handy features along with addressing the usual array of 1.0-related issues.
The download and an online demo are available on the Crowd Favorite website.
Some of the highlights in the new version include:
- A great icon, compliments of Matthew Spiel – awesome for use as a Fluid app icon
- Keyboard shortcuts to navigate home (shift-h), create a new post (shift-n), and set focus to the search field (shift-f)
- A background queue for sending posts to Capsule Server (saves are no longer held up by the remote request) – requires Capsule Server 1.1
- The ability to map multiple local projects to a single project on Capsule Server
- An indicator to show which Capsule Server(s) a post has been pushed to
We’ve also added some hooks and addressed a number of issues relating to syntax highlighting, additional default display styling and formatting, etc.
A big thank you to everyone who reported issues, suggested features and submitted patches. If you’re interested in contributing, please join us on GitHub.
Capsule is a developer’s code journal, implemented as a WordPress-based app. Think of it as a replacement for that text file you have open while you’re building things. Instead of throwing those artifacts away, easily tag and capture them for the future.
And only 30 minutes later, version 1.1.1 fixes the missing JS in the build file (optimized.js).
One of the interesting things about Devin’s list is how many are hosted services – outside of a user’s control. The Jekyll-style blog generators might end up being a threat on the other end where people want to control/customize/run their own platforms.
Our automation tools and WordPress hosting configurations are getting better and better; thanks in part to the generosity of so many in the community. I’m proud that Jon is taking the time to return the favor.
But with major user interface changes such as Aqua or iOS 7, Apple has another tendency: they overshoot the mark. Their incremental approach then becomes one where unnecessary items are removed (such as Aqua’s stripes) or improved (excessive shadows and transparency are toned down.)
It’s really hard to design any system with an unknown number of permutations and get it right the first time. Iteration is needed, as Craig outlines.
I haven’t yet installed iOS7 on a test device, so these are henceforth disclaimed as knee-jerk reactions based on hearsay and screenshots.
- 8 months is a short time and lots has been done, more than I thought was possible.
- It’s a little too candy colored and simplistic for my taste, especially the icons.
- I expect we’ll see some revisions before GM this fall.
- From what I hear from people who have already upgraded, the UX and interaction language is stellar – it feels good.
- It’s going to be jarring to move between the Apple apps that ship with iOS 7 and current 3rd party apps. The old ones will feel “broken” pretty fast.
- It seems like the handcuffs came off – so many obvious things have been added (quick access to settings, webOS style multi-tasking, ability to move NewsStand into a folder, auto-updating of apps and for the Mac the tabbed finder, better 2nd monitor support, etc.)
I think I’m going to like it. I definitely think it’s going to look more at home on the white iPhone than the black.
How to best provide support for the software you create is an interesting point of deliberation. I’ve gone through various stages and iterations, all different as circumstances have evolved, but all driven by the same question: How can I create the best experience for the user in a way that is sustainable? On a podcast…
Given a choice, in most situations I would opt for a blog over a traditional news section. That blog should be aimed at existing customers and have a focus on providing excellent customer support, while building a sense of customer loyalty.
This is what we’re doing in the next iteration of the Crowd Favorite website. I’ve resisted a company blog for about 10 years now, but the way we’re approaching it now makes sense to me.
Interesting… (thanks mrgan)
The Capistrano automation tools that we’ve created at Crowd Favorite have been a huge time saver. It’s on a list to package them along with “required set-up” docs so they can be useful to other shops as well.
I’ve released Twitter Tools version 3.0.4 which now uses the Twitter v1.1 API. Since Twitter has turned off the 1.0 API, this is pretty much a “must upgrade” situation. If Twitter Tools has been active for you over the last few days, you’ll need to do a little cleanup: enable the Tweet admin screens delete…
I took Caitlin to the Rockies game on Saturday along with another father/daughter duo. We all managed to stay through the 7th inning stretch, so I’m claiming success.