Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I would have found your article far more interesting if instead of ranting, you had undertaken an in-depth analysis of what your workflow actually is, why the current xcode doesn't meet your needs, an explanation of why your workflow can't change to fit in better with xcode, etc.

Even better would have been an article where, having analysed the problem, you have come up with a solution. For example, you seem to want a better mechanism for switching between source files in a project. How about a script for xcode that opens up a little search box where you can type in a file name from your current project - it auto-completes the name, and then opens the file? Way faster than clicking on a tab. It'd basically be a copy of the way Spotlight can be used to launch applications - Command-Space, type the first few letters of an app, and hit enter. Done in less time than it takes to reach for the mouse. As a bonus, it doesn't waste screen real-estate on tabs, and can be used to switch even to files that you haven't opened yet.

This is the point I was trying to get at in my first post. You're a programmer - this type of script is almost certainly well within your capacities. You could probably generate it in the time that it took to write your article.



demallien, I actually did offer a better solution: Xcode needs to implement tabs. As for your script idea, Xcode actually implements this via the "Open Quickly" command, but this doesn't solve any of the issues I outlined in my article.

There is a difference between open ecosystems that you can change at will (emacs, vim) and closed ecosystems that you can only change so far as the manufacturer lets you (Textmate, Xcode). To propose I "just write a script" is really to ignore my entire post and it's detailed explanation of why different window management systems work in different climates.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: