🚀 go-pugleaf

I am working an old project going back long before MacOSX and I continue
to slowely bring it into the modern age. My current setup will
undoubtably seem rather odd, but factors beyond my control will keep me
here for awhile longer.

The project type is: Shared Library

I am using Nib Files and do have a .bundle folder associated with the
project to contain my nib files, Localizable.strings file, .icns files,
etc.

For one of my nib files (call it a.nib), I can 'Show Package Contents'
and it naturally contains 'classes.nib', 'info.nib' & 'objects.xib'.

By modifying the 'File Mappings' for my project, I can allow the adding
of my .bundle, .nib, etc..

However, when I place my .bundle (call it b.bundle) into the project
(Files Tab), I see the following in the project window:

  b.bundle
    Contents
      Resources
        English.lproj
          a.nib
  classes.nib
  info.nib
  objects.xib

Obviously, the 'classes.nib', etc. files did not need to be added into
the project. Is this a bug?

However, if I grab a.nib and drag only it into the project window (Files
Tab), only a.nib will appear and not the other three files (classes,
info, objects) inside the a.nib package.

Ok. So, I can get at least this far. Now, I would like to place a.nib
under version control.

At the moment, I am still using CWProjector (v3.4.1) (like I
said...living between two worlds). Now, when I select a.nib and do an
'ADD' from the version control menu, I get the following error:

  An error occured during the Projector command.
  ### CheckIn - Unable to get information on "a.nib".
  # OS error -43( Error message file not available

This is somewhat expected, but I was still hoping it would work.

But, since it doesn't...how can I place it under version control?

It is possible that I could switch to mwCVS...would this work any better
or at all?

When I build my project, is it possible for b.bundle to also get copied
to the build location? ... not a big deal...don't mind doing a manual
copy since it doesn't change that often.


Any suggestions on how to use CW 9 more efficiently in my situation?


I assume that if I could change my project type to:

  Shared Library Package

Things might work better...although, I did play with this and it was
unclear how to place a.nib under version control...although, I did not
try working with mwCVS.



  







--