[cfobjects-developers] Super Object vs. instance properties

[Steven B. <or...@ms...>]

Ben:

Why would you want to have all keys inherited by all objects?  Let me know 
if I'm reading that wrong.  You state "You can add new keys to the object 
class that you want all objects to inherit, instead of having to add them to 
the cfoCreateObject tag."  These are properties of the object, not keys of 
the class, so I'm confused about what you actually mean.  If you take all 
object-scope properties and assign them to the object class instead, then 
you remove the distinctiveness of all objects.  Again, let me know if I'm 
off base here on what you're saying.

Also, the reason that I made the changes in 3.x was so that the class' 
namespace would dictate what its parent was - unless overriden. This makes 
the framework much more OO compliant IMO.  It already makes object the 
oldest grandparent of every class, so I'm not sure what benefit your change 
provides by forcing object to be the parent of every class.

I think I'm confused about what you've done.  Could you provide some code 
examples and the benefits?

Lastly, the <cfsetting> tag doesn't really remove a whole lot of white 
space.  <cfsilent> seemed to do a much better job.  At least with the tests 
I did.

Thanks in advance.

- Steve

-----Original Message-----
From: Ben Bloodworth [mailto:be...@el...]
Sent: Friday, March 01, 2002 8:09 AM
To: web...@or...
Subject: RE: The cfobjects website is down


Steven,
I didn't know there was such a thing, so please subscribe me.

I have some updates to the 3.0.6 release if you like me to send them to you. 
  I'll highlight the changes I made below.

Most of the keys that were assigned to a class during the register class 
call have been moved to the class definition for the object class.

When cfoRegisterClass is called, it first checks to see if the object class 
has already been registered. If it has been registered it creates a copy of 
it and then keys from the class that is to be registered are copied into it. 
  If object isn't registered, it registers it first and then continues 
registering the class it was on.

The combination of these two changes does a couple of things.  You can add 
new keys to the object class that you want all objects to inherit, instead 
of having to add them to the cfoCreateObject tag.  It also removed the need 
to specify stClassDef = StructNew() in all class.cfm files.  In fact, unless 
that line is removed, it won't work.

I made object's superclass object and put in a check when registering 
classes to stop registering a class if the superclass is the same as the 
class.  When combined with the change above, all classes will have object as 
their superclass unless superclass is overridden in the class.cfm file.

I removed cfoutput call from the method include lines in cfoInvokeMethod.  
That should help speed things up.  I removed all references to cfsilent and 
instead wrapped the cfoTags in cfsetting enablecfoutputonly=yes, which cuts 
way back on whitespace.
-----Original Message-----
From: Steven Brownlee [mailto:web...@or...]
Sent: Thursday, February 28, 2002 5:02 PM
To: Ben Bloodworth
Subject: RE: The cfobjects website is down


Ben I passed this message along.  Also, would like to be subscribed to the 
cfobjects-developers mailing list?
-----Original Message-----
From: Ben Bloodworth [mailto:be...@el...]
Sent: Thursday, February 28, 2002 3:57 PM
To: web...@or...
Subject: The cfobjects website is down


To whom it concerns,

I have been unable to reach the cfobjects website all week.  If you have any 
control over the cfobjects website, please check into why it is not 
responding.


Benjamin Bloodworth
Advanced Certified ColdFusion 5.0 Developer
ElectroNet - 850.222.0229


_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com