Denny, i am not really sure where to begin here, with that rather
patronizing and condescending reply. I am somewhat tickled to think
that you believe I don't know about OOP!
Fascinating to read your preaching on OOP techniques.
Which is kinda of ironic, when you consider that the ImageXX() breaks
all the rules of OOP with its implementation. Now if this was a proper
OOP, then it would have been an image object with methods you act on it.
Maybe you need to read some of the books to understand the difference.
It should have been:
im = new Image();
im.resize();
etc
Now if it has evolved from a CFC implementation, then that means the
designers of this suite, took a beautiful OOP model, unwrapped it and
made it back into a linear suite of functions. Thus breaking all the
work and goodness and encapsulation that comes with a proper object model.
So yes, a very poorly designed suite of functions
Now let us think about the original problem here. Which is that a
ImageNew() makes no sense as it stands. Now you think it does that is
fine. But you are missing the point.
If the default behavior is to create an arbitrary size of image
underneath then great. But you can't have an image of no size yet!
Java does not permit it.
So, the question was, what default size of image should we create?
--
Open BlueDragon Public Mailing List
http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon
official manual: http://www.openbluedragon.org/manual/
Ready2Run CFML http://www.openbluedragon.org/openbdjam/
mailing list - http://groups.google.com/group/openbd?hl=en
