On Fri, 2007-06-08 at 16:54 -0700, Lan Barnes wrote: > > Perforce has two (count them, 2) GUIs. p4win and p4v. Both have features > that give them local advantage over the command level in this or that.
I use p4v 99.9% of the time, and usually on Linux (on rare occasion I need to do something on Windoze). When I need to create a new depot (others will know this as a repository), I use p4 on the command line. > > Perforce is not a "command level" tool any more than Postgres is a command > level tool because it has psql. It's a server with several different > clients. > Let me re-phrase what I'd said before. The GUI clients use command line commands to carry out operations on the server. One can go straight to a shell (or Winsucks prompt) and perform the same operations. The GUI (as you state below) adds an easy to view picture of the data that is not so easy to see on the command line. > > The GUI tools for perforce are a perfect example of your screed. Whereas > one can get the history and relationships of branches from a command line > query in perforce, nothing beats the understanding that comes form having > the GUI generate a historical diagram. I couldn't imagine having to do everything on the command line with Perforce. That would just suck. /me wishing QUAKE would purchase Perforce so we could all use it, instead of just me. PGA -- Paul G. Allen BSIT/SE Owner/Sr. Engineer Random Logic Consulting www.randomlogic.com -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
