----- Carlos R. Mafra <[email protected]> a écrit : > On Fri, 30 May 2014 at 16:27:44 +0800, David Maciejak wrote: > > On Fri, May 30, 2014 at 6:29 AM, Carlos R. Mafra <[email protected]> wrote: > > > On Thu, 29 May 2014 at 20:45:42 +0800, David Maciejak wrote: > > >> [...] > > >> > > >> Now the question is: should it be used to load default bg image too ? > > > > > > I think it would be better to keep wrlib simple. Does wmaker really > > > need the EXIF orientation support in its wrlib? Why? > > > > > > This smells like 'creeping featurism' > > > (http://en.wikipedia.org/wiki/Feature_creep). > > > > > > > Completely agree, let's keep the graphic library simple and outdated. > > The question really is: why wmaker should _care_ about EXIF orientation? > Should it also care about GPS coordinates in the future?
Hello, If you'd allow me to jump into the troll too, I'd to add my personal point of view on the matter. WRaster is a *raster* library, that means providing helpful functions for images in memory (draw, rescale, rotate/flip, ...) and loading image is just a small service of the library. EXIF are metadata, thus not linked to raster operations, they are just additional information. The goal here is not to keep WRaster "outdated", it is to keep it reasonably maintainable. > This feature is not necessary. If someone wants to set a wallpaper > with an upside-down image, wmaker should not mess with this choice > and be "smart" in "fixing" the orientation automatically (as an > hypothetical use of this feature). Actually, that would also assume that EXIF info are right. Which may not be the case. They can be missing (in which case it's up to the user) but they can also be wrong (incorrect detection from camera's sensor, so... up to the user again). I believe it is the role of the *image viewer* to handle the rotation/flip/whatever because this has to interact with the user, something a library can't do. And on a long term notice (because I assume that wmiv is more than just a quick toy), integrating EXIF in wraster in not a good idea, because it is likely that someday you'll say yourself that it would be a neat feature to be able to display those EXIF info to the user, which will not be easy if those are loaded inside WRaster. And that's just an example. On a final note, did you consider libexif? It looks like to be widely available. -- To unsubscribe, send mail to [email protected].
