The way I'm currently doing it is with two separate apps as well. I keep the Xcode GDB window open for building and debug output and I have MacVim open for editing the code. Of course, I have to open up the main project window if I want to add some files to the project, but I find that having Xcode open anyways is a good idea because I need to consult the documentation quite often (I'm new to Cocoa).
-- Michael Jackson http://mjijackson.com @mjijackson On Thu, Jun 17, 2010 at 11:52 AM, dan sinclair <d...@everburning.com> wrote: > I tried using TextMate with XCode for a while but I didn't like having to > switch back and forth between the two all the time. It felt clunky to develop > in TextMate and build and see the debug output in XCode. Having to run XCode > just to be able to build the application felt heavy. That was part of the > reason why I switched to a pure Rakefile method. > > dan > > > > On 2010-06-17, at 1:43 PM, Rich Morin wrote: > >> Xcode has some scripting capability. Might you be able to >> hack up some scripts to automate away some of the hassle? >> >> -r >> -- >> http://www.cfcl.com/rdm Rich Morin >> http://www.cfcl.com/rdm/resume r...@cfcl.com >> http://www.cfcl.com/rdm/weblog +1 650-873-7841 >> >> Technical editing and writing, programming, system design >> _______________________________________________ >> MacRuby-devel mailing list >> MacRuby-devel@lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > > _______________________________________________ > MacRuby-devel mailing list > MacRuby-devel@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
