🚀 go-pugleaf

David Phillip Oster <oster@ieee.org> wrote:

> In article <1gktii3.1l4hy2y145dccwN%egusenet@verizon.net>,
>  egusenet@verizon.net (Eric) wrote:
> 
> > I am curious what _good_ solutions (if any), within the CodeWarrior
> > environment, people have come up with that allow them to treat the .nib
> > folders as if they were files. 
> > 
> > If you have any suggestions, please let me know.
> 
> Initially, I put the .nib folder in the project, so I could double-click
> on it, but not under version control. Then, I manually used the 
> Contextual Menu Item in Finder: Create Archive, and put the resulting
> .zip file in the project, under version control. This requires that, as
> I change the .nib in Interface builder, I remember to check out the .zip
> file, delete it, then create a new .zip file.

This is essentially what was doing, except with the extra step of
needing to transfer the ckid from one .sit file to the new .sit file.

> I now believe that Miro is right: That I should individually check in
> the .xib and .nib contents files into version control (I can hide them
> in a group in the Codewarrior project file most of the time.)

This is the solution that I have switched to...transferring the ckids
was just to troublesome.

> Since .nib FILEs and .xib files are text files in Carbon, then I'll get
> the advantage of source code control diffing.

Good point.