Hans-Emil Skogh wrote:
>> I'd been thinking on this subject for the last few
>> days when I remembered something I'd seen in the
>> FreeImage documentation - FreeImage is itself based
>> on a plugin architecture. Why not just make use of that?
>
> I would like to go even further: Why don't we take the plunge and start
> distributing FreeImage with TortoiseSVN?
>
> I know that Stefan has indicated that he wants to keep TortoiseIDiff
> small and not dependent on external libraries, but FreeImage is not THAT
> big, and it has a lot of benefits:
> - Support for a lot of image types out of the box for all TSVN-users.
> - Ditching GDI+ in favour of FreeImage would lead to a single
> (efficient) API for accessing and manipulating images, using FIBITMAP
> internally. (Even for bit-wise operations.)
> - Support for multi-paged formats (GIF, Icons, TIFF) can be handled in a
> generic way, using FIMULTIBITMAP (where FIBITMAPs can be loaded from).
>
> As a bonus the whole question of extending TortoiseIDiff to support more
> image formats becomes the question of extending FreeImage to support
> more image formats. Everybody wins!
I like that idea. But we should keep using FreeImage optional. So I
suggest to keep the current CPicture class (the part that uses the
IPicture interface to show the most common image types) and use
FreeImage to show the rest.
Who's volunteering? :)
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Oct 3 21:50:06 2006