green leaves

Has anyone been playing with Panic’s Coda yet? I just downloaded it yesterday, and I like it, so far, though I’m still feeling my way around. The CSS editor, in particular, makes sense to me. The tag autocompletion has been driving me a bit crazy, but not so crazy that I’ve turned it all the way off yet.


Photo: green leaves by Friedemann Wulff-Woesten; some rights reserved.

4 thoughts on “Coda

  1. I’ve been playing with it since release and for the most part, I’m in love.

    It changes my workflow.

    I fiddle with small bits on the server and then I wonder, how can I get this BACK locally.

    The text editor is fine for my needs. I’ve yet to fiddle with the intriguing grep find and replace.

    The CSS editor, while welcome, isn’t CSSEdit which I still prefer for one main reason: it gives an indication as to which groups of styles have been altered, making it easier to see what’s happening.

    I love the UI of Coda. I love how it is bringing disparate applications together, that don’t need to be separate.

    For a 1.0 release, I am smitten – using it for small things, unsure how to bring it into my workflow, and looking forward to small changes (and understanding) to make it bow-down awesome.

  2. I still don’t have FTP access to our server, for reasons I can only speculate snarkily about, so I don’t get to play with the yummy Transmit integration or the “Sites” thingy. Oh, to have a website I could actually edit. So for me, it’s just a text editor right now. But a nice one.

    Some of the split-window behavior is a little confusing—but, hey! there’s split-window behavior! I’d like to be able to save workspace layouts—like, always display files with windows split vertically into source code, preview, and CSS. I thought I might be able to do this by cloning a tab, but it doesn’t copy splits. A minor wish.

    Clearly, I must RTFM, and I’ve also been meaning to look through Steven F.’s tips posts on his blog.

  3. This makes me want to cry.

    Right now I have to deal with a three-zillion-field, user-hostile CMS that we currently use — for which workflow is so broken that we’re currently managing copy flow in a separate wiki — and for which the publishing system is so wonky that it requires the copydesk 3 hours to assemble the homepage and then some technical folks on the opposite coast another few hours to actually make it go live — and which breaks, regularly, leaving broken links and oddly mis-sized images here and there. Oh, and there’s also a separate blogging system, TypePad, which is just like Movable Type only you have less control and it’s even slower, and by the way it wouldn’t let us publish for several hours today, while news was breaking. FTP access to the server? In my dreams, baby, in my dreams.

    So looking at Coda, I feel a bit like someone standing in the middle of a half-built house, surrounded by the rubble and debris of construction, with rain falling on my head, holding a broken hammer and a dull saw, while I look through the window at the neighbors eating sushi in a warm, fire-lit dining room with zenlike decor, books on the walls, and a full complement of power tools and household appliances.

  4. Huh. Maybe your Typepad was down yesterday at the same time that our entire site was down—ten minutes after we posted the first part of the day’s feature. Something about an MSN spambot? I didn’t bother inquiring further; there’s never any point. We didn’t get the second half of the piece linked up until nearly 7pm. Fortunately, the world does not clamor so fiercely for our news as it does for yours.

    (And I hope you don’t have any personal experience of standing in the middle of a half-built house, surrounded by the rubble and debris of construction, with rain falling on your head, holding a broken hammer and a dull saw. Not the broken hammer and dull saw part, at least.)

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.