Sure. The majority of Mockingbird wasn't written using Atlas (we started on it a long time before Atlas existed), but we do use Atlas to make a lot of our panel

Sure. The majority of Mockingbird wasn't written using Atlas (we started on it a long time before Atlas existed), but we do use Atlas to make a lot of our panels (and if you use the --path flag with the flatten tool, you can load these panels up front to make the experience smoother). I've also heard good things about nib2cib in conjunction with interface builder if you're not liking Atlas. I work entirely in emacs and use OJTest to test my code as I write it. Sheena (my co-founder) uses TextMate though, and I think that might be a better environment for someone starting out. The best debugging trick I think I've learned is to use index-debug.html and enable objj_msgSend_decorate(objj_backtrace_decorator); (it's commented out by default). Other than that, I think I've learned to just try testing my code early and often with OJTest to catch things. I do want to try to build out better testing and debugging tools for Capp though. In general, just ask questions on the mailing list and don't be afraid of coming into IRC. The #cappuccino IRC channel is one of the most helpful ones I've been.