1. What limitations are there in the RCS/Dolphin integration?

      The biggest limitations is that code is stored into RCS but is never loaded from RCS. When you check something out from RCS the disk file is checked out, but the code in that file is not re-loaded into your image. Thus, if the code has been changed by someone/something else you won't see those changes.

    2. I work alone. Is RcsSourceManager suitable for me?

      Yes, assuming that you work the same way I do. If you keep one big "Swiss Army Knife" image with absolutely everything loaded, and do all your work in that one image, RcsSourceManager will work well for you. Since you're the only developer and your image is always current with what's in RCS you'll be fine.

    3. I keep a bunch of separate images around, one for each of my projects. Will RcsSourceManager work for me?

      Maybe. If the packages in your images don't overlap (i.e. image A loads packages Aleph, Bet, and Gimel, image B loads packages Alpha, Beta and Gamma, and image C loads packages Zort, Nobble, and Foobar) you should be fine. If, on the other hand, you use the same package in multiple images you'll have to coordinate the updating and use of these shared packages.

    4. I need to coordinate work between multiple developers. Can I use RcsSourceManager?