[Development] Moving JP2 imageformat from qt-solutions to qtimageformats

[Konstantin Ritt]

Agreed with Jake. If ICNS files support doesn't require platform API calls,
let's simply add it and give the user an options.
That's quite the same as ICO files support: are they common/required on
Linux? - No. Are they supported? - Yes, optionally.

And since we're in Open Governance area, maybe KDE project could contribute
[some of] their image plugins to qtimageformats add-on, too.

Regards,
Konstantin


2013/11/5 Jake Petroules <jake.petroules at petroules.com>

> I do. Qt is by nature a cross platform framework, limiting support for
> ICNS files only to OS X doesn't really make sense.
>
> What if you want to create a cross platform icon editor or some other app
> that deals with image files? Or reuse your OS X icon(s) on Windows and
> other platforms, saving time and space not having to create multiple
> versions of everything? If you don't want to build the ICNS plugin, simply
> disable it when you configure qtimageformats. It's a common and well known
> format and it should be supported on all platforms Qt supports, just as ICO
> is supported on OS X, Linux and others.
>
> I could understand refusing to include it in QtCore, but we're talking
> about QtImageFormats here, the perfect place where something like this
> belongs.
>
>    --
> *Jake Petroules*
> Chief Technology Officer
> Petroules Corporation · www.petroules.com
> Email: jake.petroules at petroules.com
>
> On Nov 5, 2013, at 11:37 AM, Thiago Macieira <thiago.macieira at intel.com>
> wrote:
>
> On terça-feira, 5 de novembro de 2013 08:57:12, Saether Jan-Arve wrote:
>
> Is there any big benefits in having ICNS support on other platforms than
> OSX?
>
>
> I don't think anyone wants ICNS outside OS X. But JPEG2000 might be useful.
>
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>  Software Architect - Intel Open Source Technology Center
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
>
>
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20131105/e8136ded/attachment.html>