Alan, Now I'm the one who is not really sure where to begin here. I was under the impression that this was a group discussion and not one in which responses were to be taken out of context and, moreover, personally. My suggestions to read about Java design patterns and OOP development in ColdFusion were not directed at any one particular individual, but the entire group of individuals who read this - many of whom simply read and learn from others in the group. It was in no way a condescending personal attack on your understanding of OOP, and I'm very sorry that I wobbled you on your horse and made you feel that way. Perhaps you should check your feelings at the door.
Having said that, I am not going to argue the point that ColdFusion is not a true OOP language, and I never claimed it was. I did, however, correctly state what ColdFusion returns. An image object. And I also correctly stated how it's implemented in ColdFusion. And since this is a discussion group about ColdFusion, I felt it was prudent to discuss. Again, I am very sorry if you felt it was a discussion on the internals of Java and how ImageNew() ought to function in a true OOP language. No worries. I will refrain from using this group to try and help BlueDragon users with furthering their understanding and familiarity of the language. I'll just stick with helping the folks of *that other commercially available* platform instead. I hate trolls. :( Sincerely, Denard Springle On Jan 26, 7:55 am, Alan Williamson <[email protected]> wrote: > 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 aImageNew() > 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
