On 05/11/07 17:46:14, Enrico Tröger wrote:
On Mon, 05 Nov 2007 18:30:50 +0100, Tim Tassonis timtas@cubic.ch wrote:
It shouldn't matter wich technology is behind it all...
In future I think there should just be one plugin, say VCdiff for all common version control systems. The behaviour should be very similar, just with different command names, which could be stored in an array. Then the user just sets an option for the VC they
want
(or perhaps it could even be autodetected by looking for CVS/.svn/.hg/... subdirectories).
I'm not so sure this is a very good idea and worth the effort. Although a lot of VC's share some stuff, they do have their specialities, apart from a different command line syntax.
I don't know which way the coders of those plugins want to take,
but
if they want to add further VC operations support apart from diff (checkout,commit spring to my mind) I imagine that things would get more complicated by putting everything under one hood instead of having a separate plugin for each VC.
Yes, it would be fine to have one diff plugin for some VCs or one plugin with more actions than only diff specialised for one VC. Supporting many operations(commit, add, update, diff, revert, checkout, ...) for many VCs would probably cause more effort than necessary.
I thought that as Geany has diff filetype support a diff plugin makes sense with support for any VC system that has a simple 'vc diff path' style command.
As for the other actions, I'm not keen to see them really. But perhaps it could be done in a flexible way - just listing the commands and command names to run for each VC system: Add - $vcbin add $file Update - $vcbin up Revert - $vcbin revert $file
Commands more complex than this IMO might be best not supported - just use the CLI for commit, checkout.
That way there would be much less duplication of effort and feature requests for different VC support could be implemented much easier.
Regards, Nick