> >>> Finally, we could use more image formats. We use
> >>> heavily TGA and DDS.
> > Another, less involving option would be to expose a
> > basic plugin API for TortoiseIDiff to expose. This
> > would allow for the support of all of the esoteric
> > formats out there without causing any additional
> > overhead (beyond implementing the plugin management)
> > to the rest of the TSVN project.
>
> I basically like that idea. But wouldn't it be a little steep for this
> little application to handle all those different file formats? An
> interface towards for example ImageMagick might be more appropriate..?
Including the whole of ImageMagick would make this little application
probably larger than the rest of TortoiseSVN combined.
A generic plugin interface introduces tons of complexity both for
developers and users. How are plugins installed into a system? How are
they distributed? How do plugins "claim" an image to be their own?
When a 3rd-party plugin crashes, will the user complain to the author,
or will he come to the TortoiseSVN mailing list? Will developers
bother to produce 64-bit DLLs for the plugins?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Sep 26 09:44:30 2006