Re: [Development] Moving JP2 imageformat from qt-solutions to qtimageformats
On Nov 8, 2013, at 9:53 AM, Knoll Lars wrote: > +1 to moving the plugins to qtimageformats. That¹s what we have the module > for. > > And I don¹t think moving ICNS is an issue neither, as long as we have a > configure test in qtimageformats to detect whether we can compile the > plugin. > > Cheers, > Lars I've begun the process of moving the JPEG 2000 handler to QtImageFormats. https://codereview.qt-project.org/#change,71245 https://codereview.qt-project.org/#change,71246 I did the minimum necessary to get the JP2 plugin fitting with the layout of the existing repository - filenames, class names, fixed code style (indentation, d-pointer) and spelling errors in comments enough to quiet sanity bot, but other than that no significant changes were made. Amazingly, the ancient JasPer still builds on modern OS X 10.9. I used version 1.701.0 in my testing as a comment in the Qt Solutions documentation indicated that the latest 1.900.1 does not work. Build and install JasPer (default install prefix is /usr/local): ./configure --enable-shared make sudo make install Build and test QtImageFormats: qmake -r make cd tests/ make check The JP2 plugin should be built and should work; I turned the example from the Qt Solutions versions into an autotest. The plugin code looks very messy and the testing is obviously minimal, but any cleanup and possible replacement of JasPer with OpenJPEG as previously discussed, can be done in a followup commit if someone's up to the task. -- Jake Petroules Chief Technology Officer Petroules Corporation · www.petroules.com Email: jake.petrou...@petroules.com___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Moving JP2 imageformat from qt-solutions to qtimageformats
On Friday 08 November 2013 14:18:24 Rutledge Shawn wrote: > On 8 Nov 2013, at 9:59 AM, Mikkel Krautz wrote: > > That's how I'm imagining it working as well. No 3rdparty source tree > > needs to be bundled (it isn't bundled in qt-solutions either, at the > > moment) - but link against the JasPer lib if it's present on the > > system, or JASPER_CFLAGS and JASPER_LIBS are specified to configure > > (or however we want it to function). > > Why should it use jasper instead of OpenJPEG? I'm not familiar with either > one but wikipedia seems to say OpenJPEG implements more of the spec. And it's actually has an active upstream, while Jasper doesn't seem to be maintained at all. Cheers, Albert > > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Moving JP2 imageformat from qt-solutions to qtimageformats
On Fri, Nov 8, 2013 at 3:21 PM, Albert Astals Cid wrote: > On Friday 08 November 2013 14:18:24 Rutledge Shawn wrote: >> >> Why should it use jasper instead of OpenJPEG? I'm not familiar with either >> one but wikipedia seems to say OpenJPEG implements more of the spec. > > And it's actually has an active upstream, while Jasper doesn't seem to be > maintained at all. > I wasn't really picking sides. :-) It's just my understanding that the jp2k image format currently in qt-solutions currently only builds against JasPer. OpenJPEG seems preferable if it has more features and is actively maintained. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Moving JP2 imageformat from qt-solutions to qtimageformats
+1 to moving the plugins to qtimageformats. That¹s what we have the module for. And I don¹t think moving ICNS is an issue neither, as long as we have a configure test in qtimageformats to detect whether we can compile the plugin. Cheers, Lars On 06/11/13 11:27, "Saether Jan-Arve" wrote: >Actually I support moving qtjp2k to qtimageformats. > >However, I'm still not convinced if there is a need for ICNS plugin >outside OSX (It's not common on Windows, I have no idea about Linux). >As for your cross platform icon editor, why can't it use ICO files? >Although the ICO file format itself is somewhat weird, ICO files are much >more > likely to be supported on all platforms, since it won't rely on any >3rdparty library. It can also store PNG files, which Qt already have >built-in support for. > > >Jan Arve > > >From: development-bounces+jan-arve.saether=digia@qt-project.org > [mailto:development-bounces+jan-arve.saether=digia@qt-project.org] >On Behalf Of >Jake Petroules >Sent: 5. november 2013 17:48 >To: Thiago Macieira >Cc: development@qt-project.org >Subject: Re: [Development] Moving JP2 imageformat from qt-solutions to >qtimageformats > > > >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 <http://www.petroules.com> > >Email: jake.petrou...@petroules.com > > > > > > > > >On Nov 5, 2013, at 11:37 AM, Thiago Macieira >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 <http://intel.com> > Software Architect - Intel Open Source Technology Center >___ >Development mailing list >Development@qt-project.org >http://lists.qt-project.org/mailman/listinfo/development > > > > > > > >___ >Development mailing list >Development@qt-project.org >http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Moving JP2 imageformat from qt-solutions to qtimageformats
On 8 Nov 2013, at 9:59 AM, Mikkel Krautz wrote: > That's how I'm imagining it working as well. No 3rdparty source tree > needs to be bundled (it isn't bundled in qt-solutions either, at the > moment) - but link against the JasPer lib if it's present on the > system, or JASPER_CFLAGS and JASPER_LIBS are specified to configure > (or however we want it to function). Why should it use jasper instead of OpenJPEG? I'm not familiar with either one but wikipedia seems to say OpenJPEG implements more of the spec. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Moving JP2 imageformat from qt-solutions to qtimageformats
> From what I can see, though, the real blocker here is the JasPer dep. > I wholeheartedly agree that including JasPer as a dependency just for > an icon engine seems like a rather insane requirement. But if there Yes, and that's why I asked if it was relevant for OSX only, since then I believe the dependency to JasPer wouldn't be necessary then. But regardless of that, I realize that it is better to just depend on the jp2k image plugin. That plugin might depend on JasPer or not (on Mac it can probably be done differently if people feel there is a good reason for it). > (Also, it's worth noting that the JP2K image format is not a hard > dependency. For many use cases, including mine, displaying a small > icon in a dropdown or list view might be sufficient - and the JP2K > image format might not be needed at all. In fact, I'm not even > building the JP2K image format myself at present - I only display the > small variants of the .icns.) > True, I didn't think about that. Jan Arve Sæther ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Moving JP2 imageformat from qt-solutions to qtimageformats
On Fri, Nov 8, 2013 at 8:45 AM, Rutledge Shawn wrote: > > Still, I don't see a good reason to try to avoid making it available on the > other platforms. I agree. > As long as we ensure that when the library is missing, the ability to decode > the larger versions of the icons is missing (or the ability to decode the > icons at all is missing), and that doesn't cause any other problems at > runtime, is there any other reason not to have it available? Agreed, again. The code already handles this case. It checks for the presence of the jp2k Qt image format plugin, and only then will it attempt to decode the larger sized representations of the icon. > It's not like we'd have to include the JPEG2000 decoder source with Qt, just > have the ability to detect the library and compile the plugin only if it's > there, right? That's how I'm imagining it working as well. No 3rdparty source tree needs to be bundled (it isn't bundled in qt-solutions either, at the moment) - but link against the JasPer lib if it's present on the system, or JASPER_CFLAGS and JASPER_LIBS are specified to configure (or however we want it to function). Mikkel ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Moving JP2 imageformat from qt-solutions to qtimageformats
On 7 Nov 2013, at 11:11 PM, Mikkel Krautz wrote: > On Tue, Nov 5, 2013 at 9:57 AM, Saether Jan-Arve > wrote: >> >> Is there any big benefits in having ICNS support on other platforms than OSX? … > So my own use of the icon engine is restricted to OS X. As such, my > own use of the engine could just as well be satisfied by having an > ICNS icon engine in QtMacExtras (or wherever) that wraps NSImage - or > some native code in Mumble to load the icons via native APIs. Still, I don't see a good reason to try to avoid making it available on the other platforms. As I wrote elsewhere in the thread, maybe .icns can even turn out to be a good cross-platform icon solution. And JPEG2000 might be useful in other contexts, too; however that comes at the cost of linking with yet another library. As long as we ensure that when the library is missing, the ability to decode the larger versions of the icons is missing (or the ability to decode the icons at all is missing), and that doesn't cause any other problems at runtime, is there any other reason not to have it available? It's not like we'd have to include the JPEG2000 decoder source with Qt, just have the ability to detect the library and compile the plugin only if it's there, right? ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Moving JP2 imageformat from qt-solutions to qtimageformats
On Tue, Nov 5, 2013 at 9:57 AM, Saether Jan-Arve wrote: > > Is there any big benefits in having ICNS support on other platforms than OSX? > I can comment a bit about my own use of the plugin. The ICNS icon engine from the code review in my initial mail is used in Mumble (http://mumble.info/) on OS X (and only OS X) to display icons from appliactions on the system (you can add applications to a black/white list for Mumble's overlay feature). That's the extent of its use in Mumble. So my own use of the icon engine is restricted to OS X. As such, my own use of the engine could just as well be satisfied by having an ICNS icon engine in QtMacExtras (or wherever) that wraps NSImage - or some native code in Mumble to load the icons via native APIs. Let's take a step back... Having access to ICNS via QIcon on OS X would be very convenient for Qt applications that need to integrate with native apps somehow. (For example, a Web IDE providing a drop-down of available browsers on the system, or obviously the Mumble use-case mentioned earlier). So the question is, how do we implement such a thing? My proposed implementation is an icon engine that only depends on Qt functionality, and as such can work on any platform that Qt supports. The unfortunate thing about it is that access to icons in the ICNS container that have sizes greater than 128x128, we need a JP2K decoder. (This check happens at runtime. If no jp2k decoder is present, a QIcon with only the smaller sizes available is returned to the caller.) When I wrote the engine a couple of years ago, that seemed to be the best approach, and the "Qt way", if you will. All the pieces were available in Qt (JP2K was available as separate component, but still available). Another implementation strategy could be, as I mentioned previously, a wrapper around the native frameworks. It would only run on OS X, but it would not need the JasPer dependency to access the full range of icons. Back when I did my implementation, there was no QtMacExtras (Qt 4!), so perhaps that's why it didn't seem very Qt-like to wrap the native frameworks for an icon engine. I don't know what the general feeling on that subject is now. It might be the sensible thing to do. >From what I can see, though, the real blocker here is the JasPer dep. I wholeheartedly agree that including JasPer as a dependency just for an icon engine seems like a rather insane requirement. But if there are other users of the JP2K image format, then I don't see why a native wrapper would be preferred for an icon engine over a Qt-native solution that's able to run and be tested across all platforms. (Also, it's worth noting that the JP2K image format is not a hard dependency. For many use cases, including mine, displaying a small icon in a dropdown or list view might be sufficient - and the JP2K image format might not be needed at all. In fact, I'm not even building the JP2K image format myself at present - I only display the small variants of the .icns.) I am obviously also not opposed to just keeping it out of the Qt tree like I've been doing previously. It just seemed like something that would be useful for others to have . :-) (And other seem to agree. The reason I'm upstreaming the code is because Jake Petroules had wanted ICNS support In Qt, and was considering writing an icon engine for it himself. Instead, he found mine and asked me whether I was interested in submitting it upstream...) Mikkel ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Moving JP2 imageformat from qt-solutions to qtimageformats
Yes, it is. 2013/11/7 Rutledge Shawn > > On 6 Nov 2013, at 6:56 PM, Иван Комиссаров wrote: > > > Sorry for an offtop:) > > I have a DDS image format plugin, does someone interested?:) > https://gitorious.org/andromeda/imageformats/source/c637e7d8c3719e0a5cf27a32f8ea425adc09f40c:src/plugins/imageformats/dds > > DirectDraw Surface? http://en.wikipedia.org/wiki/DirectDraw_Surface ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Moving JP2 imageformat from qt-solutions to qtimageformats
On 6 Nov 2013, at 6:56 PM, Иван Комиссаров wrote: > Sorry for an offtop:) > I have a DDS image format plugin, does someone interested?:) > https://gitorious.org/andromeda/imageformats/source/c637e7d8c3719e0a5cf27a32f8ea425adc09f40c:src/plugins/imageformats/dds DirectDraw Surface? http://en.wikipedia.org/wiki/DirectDraw_Surface ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Moving JP2 imageformat from qt-solutions to qtimageformats
On Nov 6, 2013, at 5:27 AM, Saether Jan-Arve wrote: > Actually I support moving qtjp2k to qtimageformats. > > However, I'm still not convinced if there is a need for ICNS plugin outside > OSX (It's not common on Windows, I have no idea about Linux). > As for your cross platform icon editor, why can't it use ICO files? Although > the ICO file format itself is somewhat weird, ICO files are much more likely > to be supported on all platforms, since it won't rely on any 3rdparty > library. It can also store PNG files, which Qt already have built-in support > for. > > Jan Arve The cross platform icon editor could use both ICO and ICNS files. My example was talking about the end _user_ perspective. If they want to create ICNS files, the fact that your editor decided to "use ICO instead" doesn't help them. I also don't see how "outside of OS X" is even a concern when the code's already written and tested and doesn't depend on anything except the jp2 plugin (and certainly not any native APIs). Specifically making it not work outside of OS X would require more time and effort for seemingly no reason. The plugin is barely 400 lines of code, you wouldn't be saving much by switching to native APIs. You'd either offset it with overhead from Objective-C APIs, or end up simply having the same amount of code from the verbosity of the C APIs. Furthermore, a comment in Mikkel's source appears to indicate that GDK-pixbuf supports ICNS, and if GNOME (which doesn't have very good OS X support and integration, especially compared to Qt) supports it, I don't see why we shouldn't. Besides, this is targeted for an optional, non-essential module. If you don't want the very minimal overhead of the ICNS plugin, just don't build it, and/or don't deploy it with your app. It is my understanding that is the whole point of the QtImageFormats module in the first place: to support optional, lesser used formats. http://qt-project.org/doc/qt-5.1/qtimageformats/qtimageformats-index.html We have TGA or WBMP support - does anyone *really* use those? At least we can say with a straight face and reasonable conviction that ICNS support would be useful. -- Jake Petroules Chief Technology Officer Petroules Corporation · www.petroules.com Email: jake.petrou...@petroules.com___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Moving JP2 imageformat from qt-solutions to qtimageformats
Sorry for an offtop:) I have a DDS image format plugin, does someone interested?:) https://gitorious.org/andromeda/imageformats/source/c637e7d8c3719e0a5cf27a32f8ea425adc09f40c:src/plugins/imageformats/dds Иван Комиссаров ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Moving JP2 imageformat from qt-solutions to qtimageformats
Actually I support moving qtjp2k to qtimageformats. However, I'm still not convinced if there is a need for ICNS plugin outside OSX (It's not common on Windows, I have no idea about Linux). As for your cross platform icon editor, why can't it use ICO files? Although the ICO file format itself is somewhat weird, ICO files are much more likely to be supported on all platforms, since it won't rely on any 3rdparty library. It can also store PNG files, which Qt already have built-in support for. Jan Arve From: development-bounces+jan-arve.saether=digia@qt-project.org [mailto:development-bounces+jan-arve.saether=digia@qt-project.org] On Behalf Of Jake Petroules Sent: 5. november 2013 17:48 To: Thiago Macieira Cc: development@qt-project.org Subject: Re: [Development] Moving JP2 imageformat from qt-solutions to qtimageformats 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<http://www.petroules.com> Email: jake.petrou...@petroules.com<mailto:jake.petrou...@petroules.com> On Nov 5, 2013, at 11:37 AM, Thiago Macieira mailto:thiago.macie...@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<http://intel.com> Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.org<mailto:Development@qt-project.org> http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Moving JP2 imageformat from qt-solutions to qtimageformats
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 > 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.petrou...@petroules.com > > On Nov 5, 2013, at 11:37 AM, Thiago Macieira > 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@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development > > > > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development > > ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Moving JP2 imageformat from qt-solutions to qtimageformats
05.11.2013, 21:19, "Konstantin Ritt" : > That's quite the same as ICO files support: are they common/required on > Linux? - No. Are they supported? - Yes, optionally. favicon.ico -- Regards, Konstantin ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Moving JP2 imageformat from qt-solutions to qtimageformats
On 5 Nov 2013, at 5:47 PM, Jake Petroules wrote: > 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.petrou...@petroules.com > > On Nov 5, 2013, at 11:37 AM, Thiago Macieira > 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. ICNS could maybe be a useful cross-platform icon format as long as it doesn't have encumbrances. I assume not, since http://icns.sourceforge.net/ is LGPL. (Wikipedia says there are some JPEG2000 patents, but the committee has set up agreements so that it can be royalty-free in practice). It would be a neater alternative to the current naming convention on Linux (find /usr/share/icons -type d, each theme has a subdirectory and each resolution has a directory under that). Of course ubiquity would depend on at least one of the major desktops to adopt the practice; but even if not, it would still be nice to have one icon file per app as the icon's "source" and generate the others. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Moving JP2 imageformat from qt-solutions to qtimageformats
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.petrou...@petroules.com On Nov 5, 2013, at 11:37 AM, Thiago Macieira 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@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Moving JP2 imageformat from qt-solutions to qtimageformats
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 signature.asc Description: This is a digitally signed message part. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Moving JP2 imageformat from qt-solutions to qtimageformats
On 4 Nov 2013, at 10:51 PM, Mikkel Krautz wrote: > Hello, > > I'm process of attempting to integrate support for the ICNS (OS X icon > files) format into Qt as an icon engine. > (https://codereview.qt-project.org/#change,60290) > > An optional, but desirable part of the ICNS format is support for > JP2/JPEG2000 images. It's desirable because all variants of the icon > greater than 128x128 are stored as JPEG2000 - so without JPEG2000 > support, the icon engine will only be able to render images at 128x128 > and below. > > It was pointed out during the review that a jp2 image format is > available in the qt-solutions repository: > > https://github.com/qtproject/qt-solutions/tree/master/qtjp2imageformat > > and that it might make sense to move it into qtimageformats along with > the icns icon engine itself. > > Does anyone see and/or have any problems with moving qtjp2imageformat > to qtimageformats? JPEG2000 apparently has some advantages, such as having multiple resolutions in one file and otherwise scaling better, as well as having a lossless compression option. So it seems like a good format to use for icons. I keep hoping that some day we will have the toolset to generate application icons from a single master file: .ico, .icns, various sizes for various Linux desktops, etc. It should be enough to specify something like ICON = myapp.jp2 (or svg) in your .pro file and we should take care of the rest, consistently on all platforms. (https://bugreports.qt-project.org/browse/QBS-73) (Of course those who want to have separate icons for separate platforms would still be able to.) I had thought SVG would be the best, but JPEG2000 would be a nice alternative for those who prefer a high-res raster representation. Then maybe we should write a cross-platform icon editor which allows managing the various resolutions, if possible, or do the lower resolutions have to be generated from the high-res original? If that were possible then maybe Apple would not have needed multiple sizes inside the .icns file at all. BTW (unrelated) a fractal compresson format would be nice to have too; the patents from 1987 have expired now. http://en.wikipedia.org/wiki/Fractal_compression ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Moving JP2 imageformat from qt-solutions to qtimageformats
Hi I'm just wondering if we need yet another library (Jasper), therefore my question: Is there any big benefits in having ICNS support on other platforms than OSX? Jan Arve > -Original Message- > From: development-bounces+jan-arve.saether=digia@qt-project.org > [mailto:development-bounces+jan-arve.saether=digia@qt-project.org] > On Behalf Of Mikkel Krautz > Sent: 4. november 2013 22:52 > To: development@qt-project.org > Subject: [Development] Moving JP2 imageformat from qt-solutions to > qtimageformats > Hello, > > I'm process of attempting to integrate support for the ICNS (OS X icon > files) format into Qt as an icon engine. > (https://codereview.qt-project.org/#change,60290) > > An optional, but desirable part of the ICNS format is support for > JP2/JPEG2000 images. It's desirable because all variants of the icon > greater than 128x128 are stored as JPEG2000 - so without JPEG2000 > support, the icon engine will only be able to render images at 128x128 > and below. > > It was pointed out during the review that a jp2 image format is > available in the qt-solutions repository: > > https://github.com/qtproject/qt-solutions/tree/master/qtjp2imageformat > > and that it might make sense to move it into qtimageformats along with > the icns icon engine itself. > > Does anyone see and/or have any problems with moving qtjp2imageformat > to qtimageformats? > > Thanks, > Mikkel > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Moving JP2 imageformat from qt-solutions to qtimageformats
Hi Mikkel, it would be great to have native support for JP2K. Kurt > On 04 Nov 2013, at 22:51, Mikkel Krautz wrote: > > Hello, > > I'm process of attempting to integrate support for the ICNS (OS X icon > files) format into Qt as an icon engine. > (https://codereview.qt-project.org/#change,60290) > > An optional, but desirable part of the ICNS format is support for > JP2/JPEG2000 images. It's desirable because all variants of the icon > greater than 128x128 are stored as JPEG2000 - so without JPEG2000 > support, the icon engine will only be able to render images at 128x128 > and below. > > It was pointed out during the review that a jp2 image format is > available in the qt-solutions repository: > > https://github.com/qtproject/qt-solutions/tree/master/qtjp2imageformat > > and that it might make sense to move it into qtimageformats along with > the icns icon engine itself. > > Does anyone see and/or have any problems with moving qtjp2imageformat > to qtimageformats? > > Thanks, > Mikkel > ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Moving JP2 imageformat from qt-solutions to qtimageformats
+1 from me! Qt 5's modularization should be put to good use. -- Jake Petroules Chief Technology Officer Petroules Corporation · www.petroules.com Email: jake.petrou...@petroules.com On Nov 4, 2013, at 4:51 PM, Mikkel Krautz wrote: > Hello, > > I'm process of attempting to integrate support for the ICNS (OS X icon > files) format into Qt as an icon engine. > (https://codereview.qt-project.org/#change,60290) > > An optional, but desirable part of the ICNS format is support for > JP2/JPEG2000 images. It's desirable because all variants of the icon > greater than 128x128 are stored as JPEG2000 - so without JPEG2000 > support, the icon engine will only be able to render images at 128x128 > and below. > > It was pointed out during the review that a jp2 image format is > available in the qt-solutions repository: > > https://github.com/qtproject/qt-solutions/tree/master/qtjp2imageformat > > and that it might make sense to move it into qtimageformats along with > the icns icon engine itself. > > Does anyone see and/or have any problems with moving qtjp2imageformat > to qtimageformats? > > Thanks, > Mikkel > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
