It seems pretty impressive alright.
I would have liked to able to access the raw file paths, rather than
have the pix pass through this mediafire.com presentation gizmo. Some
people might worry that it's 'doing something' to taint the results of
your experiment.
If you don't have a public server, email the images to me off-list and
I'll be happy to host the (jpg, png, etc) examples for you.
It would be even better if we could host a running "example engine" for
people to try with their own images!
If adopted; I imagine this would be added as an additional
option/parameter to the current ImageResize() function, like
'isMultiPass'. A global code change would taunt the dependency gods, no?
Some people may rely on the classic behavior for quirks (those who want
processor speed and not quality, for example).
My .02 for the topic
Al
--
online documentation: http://openbd.org/manual/
google+ hints/tips: https://plus.google.com/115990347459711259462
http://groups.google.com/group/openbd?hl=en
