VCS Gui-Interface "Design"

[Andreas Pakulat]

Hi,

I'd like to discuss how the Vcs support should surface in the KDevelop
GUI. The main question here is: Do we want to "hide" the actual Vcs
System used for a file/folder from the user and provide something like a
"Version Control" entry in context menu and such?

That would mean we limit KDevelop to 1 Vcs System per project, which
isn't extremely unreasonable though there might be cases where people
have CVS and .svn in the same project (been there, done that). Of course
this would happen _only_ for the actions in IBasicVersionControl+ any
actions from the other vcs-ifaces that the plugin provides. A Vcs Plugin
may still provide an additional entry for any special actions it wants
to provide.

The main reason for this approach would be consistency, i.e. no matter
what Vcs you're using, you'd get the same GUI items. But it also would
mean we don't have to provide tons of API on the plugin class itself,
because this would simply use the IBasicVersionControl API that the
plugin has already - the svn plugin currently has I think 3 or 4 methods
for each action, 2 from the iface and 2 other which is a lot of
duplication.

Andreas

PS: Currently the two vcs plugins provide menu entries and some context
menu all of their own and I don't really like it :)

-- 
Write yourself a threatening letter and pen a defiant reply.