What makes P4Win better than P4V? – P4V deficiencies

p4v-deficiencies-compared-to-p4win

P4V deficiencies compared to P4Win

Here’s list of P4V deficiencies & features missing as compared to P4Win…  

1). In P4V you can’t paste paths onto the tree view as way to quickly navigate to items. The nearest equivalent is to paste in to the address bar but that has the annoying side effect of switching between workspace/depot view depending on the format of the address. 

2). P4V has an inferior (broken) ability to copy paths from depot treeview using Crtl+C. P4V copies the string in a totally un-usable format, P4Win copies it ready for use in command line P4 operations etc. 

3). P4V has inferior drag/drop of filenames from treeview. P4Win allows you to drag/drop filenames in local workspace syntax. P4V on the other hand drags/drops in depot syntax – there does not seem to be any way to quickly get filenames in workspace syntax. 

4). P4V can’t integrate a selection of files, it can only integrate single files or entire folders. 

5). P4V doesn’t provide the ability to sort pending changelist by criteria. 

6). P4V doesn’t offer safe automatic merge when integrating a single file. 

7). P4V doesn’t have a default resolve type. 

8). P4V doesn’t allow use of Enter/Ctrl+Enter to select the default action in dialogs (instead you have to use a mouse or press TAB several times). 

9). Many dialogs lack a Cancel button but escape key, in many cases, does the same thing. 

10). P4V suffers from a general lack of keyboard shortcuts (like Ctrl+Shift+M for resolve). 

11). P4V provides no way to “p4 set” defaults and hence interoperates badly with command prompts and scripts. 

13). P4V has lacks command line features of P4Win. 

14). And finally, IMO, P4V is just a more cluttered interface, you spend forever having to resize, switch views and generally fiddle with things. P4Win was fine!But 2008.2 beta release notes that several more dialogs and column-width settings are remembered now 

15). P4V bookmarks no longer cross depots and don’t have keyboard shortcuts. Under P4Win, I constantly switch my current window between depots and file areas using keyboard shortcuts. I have no idea why P4V separates favorites from bookmarks with neither doing the whole job.Favorites is also intent on opening a new app each time rather than just switching which just clutters my desktop. P4V needs the more powerful bookmark function from P4Win. 

16). There is no P4V “resync to same changelist” menu item. I use this frequently when I am testing something and want to wipe out the source and generated binaries and do a quick re-sync. 

17). There is no P4V menu item to update an existing client’s view from another client. We use this all the time with P4Win to update client views from template clients. 

18). P4V does not show the “Explore” and “Command Prompt here” context menus for folders—just for files. I often use this to open a window for the current folder to do something. 

19). Popping up an editor for a file that is not open for edit no longer says read-only with the revision number in the caption bar in P4V. AuthorRobert Pitt & Barry Wilks

Tagged : / / / / / / / / / / / / / / /

Benefits of CVSNT, What are the advantages of CVSNT over CVS ?

advantages-of-cvsnt-over-cvs

Advantages of CVSNT over CVS

Feature CVSNT CVS
Server
Supports authentication via Microsoft Active Directory or SSH (windows only) YES NO
Set enforced protocols allow server to lock out clients connecting over insecure protocols or using insecure/inefficient options. YES NO
Easily remove protocols (without recompile) YES NO
Branch ACLs can be used to restrict access YES NO
LockServer provides file level locking YES NO
More sophisticated / extra triggers available e.g. postcommit. Triggers also available via COM/DLL/.so interfaces YES NO
Supports Unicode files with additional keyword expansion switches YES NO
Efficient storage of binary files using binary deltas YES NO
Extended modules functionality using the modules2 file YES NO
Advanced Reserved Edits and checked commits (supercedes exclusive locking concept) YES NO
Server-side default options (cvsrc) YES NO
CVSROOT/config scripts etc. YES YES
Repository browsing via cvs ls command YES YES
Pluggable server-side diff programs YES NO
Supports Unicode files with additional keyword expansion switches YES NO
Server-side default options (cvsrc) YES NO
UTF-8 (Unicode) Server. YES NO
Multi Lingual filenames suport. YES NO
Rendevous Support YES NO
Binary availability for Windows, Mac OS X, Linux, Solaris, HPUX YES YES
Client support for IBM iSeries (AS/400) OS/400 YES NO
Windows Server
Supports encrypted authentication via SSL (all platforms) YES NO
Configurable with Windows Control Panel YES NO
Compatible with NTFS ACL’s for using permissions based on Windows username or group. YES NO
Triggers also available via COM and DLL interfaces YES NO
Cshdump handler YES NO
Native file access YES NO
Native MSI Installer YES NO
Client
Smart Merge using MergePoint YES NO
Supports Unicode files with additional keyword expansion switches YES NO
“Import-and-go” by optionally turning freshly imported trees into a new sandbox automatically. No more need to purge and do a fresh checkout first YES NO
Version OSX resource fork extensions keyword expansion switches YES NO

Source: Related Website & http://www.cvsnt.org

Tagged : / / / / / / / / / / / / / /

Major differences between CVS and CVSNT | CVS Vs CVSNT

cvs-vs-cvsnt

Major differences between CVS and CVSNT | CVS Vs CVSNT

CVSNT was started as a variation (or branch) of CVS in 1999 because patches contributed to CVS were not considered to be suitable for that project by those responsible for making such decisions at that time.
CVSNT has continued to add features to the original CVS that support modern version control and configuration management best practice as well as maintain feature parity with CVS.
Today CVSNT is the most widely deployed version of CVS and is distributed with TortoiseCVS and WinCVS.

Similarities between CVS and CVSNT

  • From a SCM perpective, they share similarity in purpose, Commands including syntax and functionality
  • Both are freeware
  • Both can be accessed through clients.
  • Both are supported with Unix-like, Windows, Mac OS X

Difference between CVS and CVSNT

  • An alternative to CVS with advance features and support
  • CVS is being maintained but new features are not being added henceforth CVSNT is being maintained and new features are under development.
  • CVS is having only merge function instead of CVSNT is having merge and locking system as well.
  • CVS is having limited features than CVSNT
Tagged : / / / / / / / / / / / / / /