On Sat, 19 Jan 2008 06:40:27 GMT "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> babbled:
> > > > Man, we all say some silly things in time, but this has to be one > > > of the good ones from you. :) It's a 'load option' so it's fine > > > for this to be 'optionally' implemented in a loader? Wow! > > > > correct. load options include things like DPI settings. do you > > expect every loader to now scale images based on DPI - the loader > > doesnt even know what the DPI of most image formats is - will it > > "fake" one (eg 75dpi) just to make this "work" ? these options are > > Yes, because that's exactly what we did (for the one and only > loader that respects that, the svg one), except I believe it was 90 dpi > not 75 that we used. correct - though this was more a bi-product of svg being a vector, not pixel-based format. that's about the only reason dpi exists there in load options. > I can understand some 'option' so particular to a format that > it had absolutely no relevance to other formats.. eg. a format might > support various kinds of de-compressions, speed vs quality kinds of > things or whatnot.. but that's just not what's being adressed here. > We're talking about, essentially, about image sizes - likely the most > common attribute you can think of for "images". > > > there if the loader can do something easily/for "free" while loading. > > for some formats like SVG rendering at a DPI is part of loading - > > or at a size, so it comes for free. for jpeg scaling down by 2, 4 or > > 8 in each dimension is for "free". if every loader implements this > > i also need to add controls over the scalign quality (smooth or > > samples for example). > > None of this has any real bearing on the issue at hand - ie. > wether evas itself should do the re-sizing on load, or let everyone > who needs it have to copy&paste your e17 solution. But it's your call > so we'll leave at that. :) what you want is an: evas_object_image_rescale(Evas_Object *obj, int w, int h); which forcibly rescales ANY image to a particular size - be it loaded from a file or generated as ARGB data. this gives you the choice after load - if the load options didn't get you a size you are happy with "for free" to do extra work to fix it. with enignes like the opengl engine scaling is "free" so you might not want to pay the price of a software-scale on load when a "please pre-scale this to this size - if you can do it for no extra cost" is by far better - for jpeg in this case u can load a large jpeg image at a reduced size much faster and then scale with GL afterwards "for free". putting that into the load and load options takes that choice away. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
