Page 4 of 4

Re: Plan for WinMerge 2.16

PostPosted: Sat Mar 09, 2013 3:04 pm
by christianlist
kimmov wrote:What I think we need to abandon the current thinking of doing such "fine" plugins. Nobody is implementing them even though the feature has been there for years.

We need just simple C-API with callbacks for the things the current plugins do. And rewrite some Visual Basic code to C++. Make plugins our internal tool without stable public API. Make them just code modules one can load dynamically via some GUI.


I agree with you. A little googling reveals very few plugins indeed.

Re: Plan for WinMerge 2.16

PostPosted: Sat Mar 09, 2013 3:08 pm
by christianlist
jtuc wrote:Command line tools like sort, tidy, MediaInfo, XDoc2Txt to name a few, read from a file and write to stdout. Like good old CGI in web servers. Easy to do with perl/php/python/whatever. WinMerge could technically support this model without messing with temporary files like existing unpackers do, and without requiring precompiled plugins in the form of DLLs, thereby taking away from most users the option to plug in their own code.


That's actually a good idea.
The xdocdiffplugin has long been one of the favorite plugins to use with WinMerge, and it is simply calling XDoc2Txt commandline to get the job done.