On Fri, June 8, 2007 8:59 am, Paul G. Allen wrote: > On Thu, 2007-06-07 at 19:30 -0700, Lan Barnes wrote: > >> >> I remember >> how one supposed professional (blessedly out of my life now) wasted 20 >> minutes in a tool-search meeting calculating how much "creative" time he >> would waste if it took him 2.5 seconds to toggle between his IDE and the >> Perforce GUI. I wanted to say "WHAT ABOUT MY DAMNED TIME IN THIS >> MEETING, >> BOZO?" but of course, I am far too professional for that. Yes. And >> mature. >> Far too mature. >> > > Yes, very mature. ;) > > That's funny in a sad sort of way. Considering Perforce is actually a > command line version control system, if the guy had an IDE that was > worth a crap, he could have extended the IDE to include the Perforce > commands he wanted to use. >
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. 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. Any SCM tool w/o a command level interface isn't worth serious consideration. > I can do this with any of the IDEs I use. The Sun IDE has a plug-in for > Perforce (which I use), Code Forge is extensible, Understand has both a > pair of APIs and the ability to add tool bar buttons for user commands, > and Eclipse is extensible. These are not all UNIX-only IDEs either. > > What I laugh at is those that insist on remaining "old school" because > they think it's better than using the IDE or GUI tool, when in actuality > they are slower at many tasks than they are when they use the IDE or GUI > tool. (Example: Typing in a complicated grep command instead of using > something like Understand where the answers can be found and browsed in > a matter of seconds.) I've found many of these types will talk about all > the negative things about a given GUI tool without ever even trying it > out. > > I've been known to use GUI and command line tools together, whichever > one will help me complete my task faster. I also like to try things > people recommend as time permits because I might find (as I have in the > past) that I actually like them better than whatever I've currently set > my mind on. > 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. -- Lan Barnes SCM Analyst Linux Guy Tcl/Tk Enthusiast Biodiesel Brewer -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
