Personally, I’m a Subversion fan. I started off using CVS for version control many years ago, then moved to Subversion, and have since been perfectly happy. But the Apollo team (along with most other teams at Adobe) uses Perforce, so I’ve been having to adapt. I actually like Perforce in general, but there are two things that really bother me:
- I don’t like how you have to check files out (or add them to a changelist) before you can edit them. It’s really annoying to stop what you’re doing, switch to the P4Win client, and add a file to a changelist every time you want to edit it. It really interrupts my workflow.
- The P4Win client is kind of slow, and not the most intuitive and usable interface I’ve ever used. And that little jogging P4 icon was certainly an interesting choice.
Anyway, enough complaining. I decided I needed to make working with Perforce easier, so I tried installing the Perforce Eclipse plugin into Flex Builder 2, and was pleased to discover that not only does it work fine, but it really makes working with Perforce much easier and much more efficient. Now, when I want to edit a file, I can add it to a change list right form Flex Builder with a single click.
You can find out how to install the Perforce plugin here. To start using Perforce from Flex Builder, right click on a project, go to "Team", and select "Share project…". In the port field, enter the server and port in the format "server:port" and you’re all set.