There are 2 approaches to using SVN inside GEDI. One approach is to launch the GUI interface that is part of SVN inside of GEDI when you right-click on some file like a script or panel. The other approach is like the old CVS, to run the SVN command line calls in the background and just update the status when done.
I have started to look at this solution as a hybrid of both the GUI and the background command line options. The user must be able to see the status of the file in the GEDI tree, but for things like committing a change to the repository, it seems useful to popup the GUI and let the user put in comments and use all of the features that SVN can do. For other things, like downloading the most up-to-date (update function) file from the repository to your project would be best to just click-and-go without the GUI to select?
I see 3 ways to present this hybrid concept. One is the provide the user with both options in the right-click menu (the menu already has 14 SVN items)? The other is to make an educated guess which the user wants by default? The third is to let the user set a keyword in the config file that switches the interface from all command line to all GUI?
I post this to the forum for discussion. I am interested in people who have used the CVS feature of WinCC OA and want to use SVN. I am also interested in hearing from people who use SVN because GEDI does not support it, and what parts you really use for WinCC OA?
Todd Malone
HMI CoC USA