punkassjim's dashboard

A comment on the idea "Coda Code Collapsing" in Panic Inc:

LOL at Moses in the dessert, with a cherry on top.

Also, LOL at "We are professionals and need to make decisions on how the products we invest in today, affect us months from now." You're absolutely right! I'm sure you learned a lesson from your impulse buy of Coda.

But, as professionals, it also behooves us to refrain from grilling the developers of Coda over hot coals without really thinking through what it is we know and don't know about the situation: of course, we've been given a metric boatload of updated features for our original entry price, and of COURSE the next major upgrade to Coda is going to include far more than just Code Folding. So, your ultimatum to walk away is really going to seem silly and not-well-thought-out. It's kinda like being that guy in traffic who speeds into the other lane, only to find out that he should have stayed in the lane he came from.

ALSO as professionals, we have to consider the "hidden costs" of re-tooling. No matter what software you would switch to, you would lose hours of valuable time simply in re-training your muscle memory for different keyboard commands, which would likely cost you more than the Coda upgrade fee. – punkassjim, on August 25, 2009 14:45

punkassjim reported a problem in Panic Inc on August 13, 2009 17:29:

"Go to Folder" has a buggy Go button

"Go to folder" has the following bug:

If you've already used the Go to Folder command, that path is saved for next time, in the drop-down menu. But, if you hit Opt-Cmd-G, then hit the down arrow twice (once to drop the menu, once to select the first entry), then hit return...you now have a path to go to, but the Go button is still disabled. Delete a character from the path and re-type it, and the Go button will be enabled.

A comment on the idea "Coda Code Collapsing" in Panic Inc:

Yeah, sorry Zack, but I'm not sure how you can feel "led on" when no one ever misled you. Not only that, but did you completely miss the widely-publicized Panic 50%-off sale a few months ago? The one where they said they were "clearing out inventory" (a funny turn of phrase) before new releases come along later this year? The one where they said that current owners would get discounts on the next release? Which kinda implies that it won't be free?

I mean, kudos for your keyword-rich username, you are truly an SEO mensch. But please try to keep the accusations holstered for when they're actually warranted. – punkassjim, on August 12, 2009 14:04

A comment on the idea "Coda Code Collapsing" in Panic Inc:

Have you forgotten the price of Panic software? I mean, even if the upgrade price is 100% of first-purchase, it kinda pays for itself within a week, if the new features add up to an hour or two of saved time here and there. And if it doesn't pay for itself in your situation, I'm pretty sure that means the upgrade wasn't needed. – punkassjim, on August 11, 2009 20:20

punkassjim marked one of Cabel Sasser's replies in Panic Inc as useful. Cabel Sasser replied to the idea "Coda Code Collapsing". punkassjim and 5 other people think it's one of the best replies.

punkassjim started following the idea "Coda Code Collapsing" in Panic Inc.

punkassjim replied on July 30, 2009 18:46 to the problem "Previously read tweets not dimmed after relaunching Tweetie" in atebits:

I'm not entirely sure I understand why a reasonably-limited number or tweet IDs (say, 300) couldn't be cached locally with a flag that denotes whether they've been read or not. Of course, you're the programmer and I'm not...I don't want to diminish your expertise. But the whole "mark all as read," as implemented in Tweetie, has extremely little value and comes off as "buggy" to non-developers.

For what it's worth, this is a much more interesting problem since the advent of Prowl. It seems like a bug when, every time I launch Tweetie, I get notified of 20 new Mentions and DMs. Keeping Tweetie running constantly, while no doubt "efficient," is also "sweeping the issue under the rug." I, for one, would like to minimize non-work distraction during my workday.

Hence, I'm posting to GS on 11:44am on a Thursday.

punkassjim started following the problem "Previously read tweets not dimmed after relaunching Tweetie" in atebits.

A comment on the problem "Tweetie mention notifications don't work with Prowl plugin for Growl" in atebits:

You can set each application as you see fit, and you can even get more granular than that: you can set each "action" from each application (like, @mentions, direct-messages, or timeline updates) to be whichever style you like. And, within the Prowl style prefpane, you can tell it to also display on the Mac as whatever style you want (say, Smoke) in addition to sending the message to Prowl. – punkassjim, on July 09, 2009 09:57

punkassjim marked one of Daryl Spitzer's replies in atebits as useful. Daryl Spitzer replied to the problem "Tweetie mention notifications don't work with Prowl plugin for Growl".

punkassjim replied on July 09, 2009 07:50 to the problem "Tweetie mention notifications don't work with Prowl plugin for Growl" in atebits:

Ah, sorry Daryl. I thought I had posted this the other day, but apparently not:
http://forums.macrumors.com/showthrea...

Googled it about 15 minutes after my last post.

punkassjim replied on July 08, 2009 01:20 to the problem "Tweetie mention notifications don't work with Prowl plugin for Growl" in atebits:

Sending a "preview" from the Growl prefpane ALWAYS works, though. Same with notifications from a Hahlo SSB from Fluid.app. So, I'm still thinking it's a Tweetie thing.

punkassjim replied on July 02, 2009 02:40 to the problem "Pricing policy" in Connected Flow:

Call me crazy, but:
a) I had no interest in FlickrExport.
b) Now I do.
c) I'd gladly pay for it.

One would think — what with social networking being "free" and all — that people, by and large, would be more willing to part with an extremely modest number of dollars in exchange for something that works well, makes their lives easier, and clearly had a lot of hard work put into it. Hopefully, one is wrong only occasionally. Give an inch, take a mile, and all that.

Funny, though: social networking is about as "free" as Gruber's content. Actually...far, far less so.

A comment on the problem "Twitter needs to support push notifications on the iPhone" in Twitter:

Thanks Craig, that puts it into perspective. As for the "look before you leap" advice, I definitely hear you. Truth be told, I'm not likely to buy anymore iPhone twitter clients. Between you, @atebits, @buzz and @camh, I'm pretty sure at least one of you will make the magic happen :-D – punkassjim, on June 30, 2009 15:53

punkassjim replied on June 30, 2009 14:36 to the problem "Twitter needs to support push notifications on the iPhone" in Twitter:

I'll go on record as saying I could care less if it's "push" in the traditional sense. Even if an app only polls the API four times a day, I'd be happy. Of course, that's just one man's opinion, and clearly I'm not some sort of "twitter thought leader."

Craig, are you saying that iPhone notifications simply can't be done with the tools at your disposal? Not even if they're on a timed interval?

And an observation: I know it's not the integrated solution that everyone's clamoring for, but what about RSS? If Twitter isn't jumping to accommodate on the push front, isn't it still true that you can subscribe to whatever Twitter information you want via RSS? Personally, I still haven't settled on a real "winner" RSS app, but I'd imagine the game is gonna get real interesting, real soon. First developer to put out an RSS app that supports iPhone notifications on a per-feed basis gets my money.

punkassjim started following the problem "Twitter needs to support push notifications on the iPhone" in Twitter.

punkassjim replied on April 29, 2009 04:25 to the idea "Please expand capabilities of tweetie url scheme" in atebits:

I'll hop onto this suggestion, and put a less corporate spin on it...

In terms of sheer intra-platform integration, Tweetie takes the cake. The simple act of sending a link from Tweetie to Instapaper brings me joy every time I use it, and I find myself cursing every 3rd-party app that doesn't employ this feature.

However, I (unfortunately) often find myself stumbling upon a tweet URL in MobileSafari. And every time, I wish I had a 2nd Tweetie bookmarklet: the first is just to shorten/post the current URL in Tweetie, and the second would be to parse the current twitter.com URL into a format that would bring you to the same place in the Tweetie app. Hell, it could even be the same bookmarklet, if it were written smartly.

I imagine Tweetie kinda already does something like this within the app itself...after all, when you click a posted URL that points to a tweet or a user from within Tweetie (shortened or not), the app will take you to the right place, without bouncing you out to MobileSafari. It's one of the app's best features. So, what's the likelihood of expanding the tweetie: url scheme to be a little more useful like that?

punkassjim started following the idea "Supporting remote/local iTunes libraries." in boxee.

punkassjim replied on March 20, 2009 18:41 to the praise "Coda's keyboard shortcuts ROCK" in Panic Inc:

"...from the Help menu..."

Type in "keyboard."

punkassjim shared an idea in Panic Inc on February 25, 2009 17:35:

Source Control should have its own "mode."

Source Control should have its own "mode." One-window web development is getting stretched by the SCM Status Window. I wouldn't mind hitting CMD-7. Besides, CTRL-CMD-V conflicts with CopyPaste clip revolver (not that Panic should care, but still)