Because SlickEdit also has Context Tagging, it has features like listing the symbols that changed between two versions and finding all the versions where a symbol changed that no other Version Control GUI can offer. Click here to try it free!
SlickEdit's GUI Update dialog will show you which of your local files are modified, and which ones need to be updated. You can commit changes from the update dialog, as well as update out-of-date files. You can also diff with the selected file with the server, launch the history dialog for the selected file, and merge files that are in conflict.
Use SlickEdit's Version Control History to view history for files in version control. General information about the file is displayed in the top left pane. A list of versions is displayed in the top right pane. At the bottom is information about the version currently selected in the version pane.
Also in the bottom pane, SlickEdit's History dialog lists symbols that changed between the selected version and its predecessor. Only SlickEdit can offer this level of functionality because it uses SlickEdit's Context Tagging.
DIFFzilla is at the backbone of SlickEdit's version control support. Use DIFFzilla to review your changes before committing them, view differences between two past versions, even compare where a symbol changed. Anywhere you need to compare two items, DIFFzilla is there, with all of SlickEdit's built in language support, including context tagging, color coding, and syntax expansion.
Use SlickEdit's Find Symbol changes feature to easily identify the places where a function changed, and view the changes to that funciton, or the entire file. You can also easily view the history for that verison.
Only SlickEdit can offer this level of functionality because it uses SlickEdit's Context Tagging.
SlickEdit's History Diff allows you to easily see the differences between two consecutive versions of a file. Pick any version and see the differences between it and its predecessor. The history information for the currently selected version is displayed at the top of the dialog.
This feature is great when you cannot remember exactly where a change was introduced, and the history information alone is not enough to go on.
Use SlickEdit's Repository Browser to get a comprehensive history of everything that has changed in your repository. Choose how far back to look, select individual revisions, and easily launch SlickEdit's History Dialog to find more information about changes on an individual file.
This feature is great for determining what files you and/or your team changed recently.
Git Repository Browser
SlickEdit's Git Repository Browser shows each commit in the Git repository, including showing branches. You can diff a file with its predecessor, launch the Git History Dialog, or History Diff.
SlickEdit's Shelving feature allows you to take changes that are not stored in version control, and easily put them aside for later, then revert the files.
This is great for when feature development is interrupted by a bug fix that has to be dealt with immediately.
"When did this function change?" It's not a question that you find yourself asking all the time. But when you do need to know, you really need to know.
SlickEdit now has a tool that will find those changes for you. It supports Git, Subversion, Perforce, Mercurial, and CVS.
Only SlickEdit can offer this feature because it uses SlickEdit's powerful Context Tagging engine.
Diff Current Symbol with Most Up-To-Date Version
The same way you can use SlickEdit to compare the current file to the most recent version in version control, you can do the same thing with the current function.
Only SlickEdit can offer this kind of feature because it uses SlickEdit's powerful Context Tagging engine.