Anyway, the bounty is to make a CVS plugin so we can update from and commit to a CVS repository using code::blocks.
(I grabbed the idea from dev-cpp, which already has a CVS menu. The plugin DOESN'T need to be exactly the same as dev's, altho it would be preferred for compatibility reasons).
I'd really appreciate if the plugin used the TortoiseCVS modules, in case they were installed on the user's machine (applies to windows only).
To use Tortoise it's not C::B to modify but wxWidgets. The issue here is that you need access to "hidden" windows shell functions like ILFree(), ILCombine(), SHChangeNotifyRegister(), SHGetFileInfo(), etc. to use PIDLs (LPCITEMIDLIST) and actualy "hook" the windows directory tree inside a widget and react on the right-click just like explorer does.
This all sucks and you just should write a simple plugin that allows to set the cmd path and a SSH protocol.
set CVS_RSH=c:\Progra~1\TortoiseCVS\tortoiseplink.exe
path=C:\Progra~1\TortoiseCVS
cvs -d:pserver:anonymous@codeblocks.org:/cvs -q checkout -P html
or
cvs -d:ext:rickg22@codeblocks.org:/cvs -q checkout -P html
cvs.exe commit -r 9.0
Then the plugin has a popup menu that reacts on a filelist/directorytree
update() { shellexec("cvs -q update -dP"); }
updatelocal() { shellexec("cvs -q update -dPl"); } // non-recursive
updatereset() { shellexec("cvs -q upd -dPA"); } // Reset any sticky tags/date/kopts.
Or based on the action (add, update, commit, remove, (r)tag, (un)edit, diff, etc.) show the available options and allow the C::B user to configure "default" menu options himself to easy up his common used actions.