hced's dashboard

Searching for the SlideShare iPhone app I had anticipated already existed I landed here...

A SlideShare app would be one of the greatest apps for my iPhone! Please, please try to make this happen.

I don't think code collapsing is __the__ utmost important feature to wish for, just one of the nice things to have. As said, the code navigator will do fine in the meantime.

I think the CSS department is much more important, and I'm still wishing for Coda to catch up with the snappiness that (still) makes CSS Edit theTM css editor that nobody except yesteryear programming mummies could suffice without.

Am I missing something in saying, there's already the Server: field and Remote Path: field that you need to fill in when creating a new connection — wouldn't that be enough (presumably just the address provided in the Server: field) for a proper web URL reference to be generated? I'm super tired after a week's duty at my son's kinderkarten, so I may very well be missing something crucial here. :)

This type of inspection would be a great improvement, but I would like more to have something like CSSEdit. I remember watching a presentation on Cabel Sasser's blog about how Panic tried to work out an agreement with MacRabbit on CSSEdit but it eventually fell through. Perhaps this is the reason that the DOM inspector in Coda is (relatively) featureless?

Sometimes it's convenient to simply explore the hierarchy of the DOM tree, which Coda's DOM inspector does well, but it doesn't have all the features I would like. The two features I would like to see the most are exemplified in Firebug and CSSEdit 2.6.

In Firebug, the DOM inspector takes you to the code for that element in the HTML code. Also, like the Safari DOM inspector, it shows you which CSS rules are applied to the element. Again, Safari has this, but I like Firebug's better because it doesn't require right-clicking elements to view their location in the DOM tree. You click on an element, and you can quickly see its location in the DOM hierarchy, or the HTML code from which it was generated.

CSSEdit has more what I'm looking for in an integrated environment like Coda. The entire core feature of CSSEdit is to rapidly style web pages without having to refresh the preview. The crux of this is some new features added in CSSEdit 2.5, which allows you to use the X-ray tool (just an inspector) to click on an element, and see which style rules in the actual CSS document are applied to it. Imagine this: two panes in Coda, one of the page preview, and one of the CSS file. You can click on elements with the inspector, and see a panel (Function viewer, maybe?) with a list of the CSS rules from the CSS document that are applied to the element. Clicking on one of those symbols takes you to the CSS rule in the CSS document itself, rather than requiring you to hunt your way through the CSS file.

This would enhance the amount of integration between each of Coda's panes. Coda is phenomenal in for its integration of its constituent apps into one window, but there's very little in the way of integration between those "apps". I think there is a lot of room to streamline CSS development in Coda. Currently, CSSEdit is the only web development app that I use aside from Coda. This type of integration could be expanded by allowing the user to pick a preview page for JavaScript or CSS (read: drag and drop, I'm aware I can type in a URL). If I drag and drop an HTML file from the file browser onto the preview pane, I would like for it to open that page as preview, not open the file in a new tab. It seems silly to have the preview pane by default just spilling the contents of the JavaScript or CSS file into the preview!

Thanks for the great software, and I'm excited for Coda's future!

Utter fantastic, Markus!

The new cross connection feature looks great, as well as the fullscreen and context menu. You're doing a great job with this application and thanks for your interest in your users' feedback.

I think that looks brilliant, Markus! And Shift-dragging sounds like a good deal as well.

Your term, Cross Connection also sounds better than mine. ;)

Curious, would it be possible to Shift-drag from the "We have to wait for..."-node, back to the "Task2"-node again, to create a bi-directional cross connection? Maybe "Task2" could use the same line, but receive an arrow pointing back to itself. (I.e. one arrow in either end of the same cross connection line.)

I guess it's a huge undertaking, though. General stability has probably been of highest priority so far, but IF there were to be S3 support, I'd be completely sold. (My S3 account is still being idle since there's no tool for it that I like.)

S3 coupled with the possibility to right-click and copy public URL address of files, would be the killing blow.

re: Nick

The application icon is located at: /Applications/ExpanDrive.app/Contents/Resources/ExpanDrive.icns

Just replace that one with anything you like. Maybe the old icon could be retrievable from the nice developers? I have deleted my older ExpanDrive .dmg's, so I don't have it.

On another note: one rarely get to see ExpanDrive's application icon, as it's usually just a menu bar citizen, and the menu bar mini-icon isn't much of a big deal. But I'm still inclined to agree in the lines of what you (Nick) said. The app icon needs attendance. The idea is great (!). A tickler file with a hard drive case; why not. That part definitely works _as an idea_. But the image is too generic and anonymous, and I don't think it will sell the product more than the old icon did. Ideas and visual end results are an odd couple who doesn't always mix that well.

This criticism is of course a little unwarranted, since the application is really neato. But the moral of the story is that buyer attraction is not just a matter of gaining more custmers, but also something for the current users to be concerned about, knowing whether or not their app will see a profitable future, meaning further maintenance and more improvements.

Now, hit me with a baseball bat, please.