From: Brian M. <ma...@ex...> - 2008-07-09 17:30:41
|
The Rucola approach doesn't quite work with Xcode, I think. Xcode has a bug where "Save changed files on build" doesn't consistently save changed files that live in folders (rather than Xcode groups). It's annoying when you make a change, have it not work, then discover it's because Xcode didn't save the changed file. I finally wrote an Applescript to really, really save before building. With that, I have a structure that works for both Xcode and your favorite editor, using Xcode's clever "don't use the Ruby files in the built directory when making a Debug build" trick. On Jul 3, 2008, at 12:38 PM, Tim Perrett wrote: > Have you tried Rucola? > > http://rucola.rubyforge.org/ > > On 3 Jul 2008, at 18:25, Brian Marick wrote: > >> Summary: Xcode seems to strongly prefer that all your Ruby files be >> at >> the top level of the resources directory. Can my preference for a >> source directory structure override its? > > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > Rubycocoa-talk mailing list > Rub...@li... > https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk ----- Brian Marick, independent consultant Mostly on agile methods with a testing slant www.exampler.com, www.exampler.com/blog, www.twitter.com/marick |