>
> I am here by starting a wishlist for CFCs
>
Good stuff, lets see if we can get this sent on to MM once we've beaten
the subject to death ;)
> Here are my few items.
>
> 1- Ability to declaire multiple types in the "Type" attribute
> of the CFARGUMENT tag. Either by using multiple tags or
> using a list within the attribute.
>
I don't really see why this would provide a huge bonus unless you want
to be able to do method overloading. Even in that case you probably
should be using optional arguments with different names. One of the
fundamental reasons that cfargument needs the type attribute to work the
way it does is so that CFMX can create valid wsdl for a webservice. I
suppose you could have the first type in the type list as the one that
gets put into the wsdl, but that could just get horribly confusing for
people new to CFMX and webservices.
> 2- Ability to dynamicly populate the "ROLES" attribute of the
> CFFUNCTION tag.
>
Unless MM decide to change the basic mechanism that they use for
implementing roles, this one is dead in the water. When a class file is
generated from a .cfm, or a .cfc file, the roles are hard-coded into
that file. To do it in any other way would seriously impact on the
performance of CFMX because you would have to do a look-up for the
values of the variables assigned to the roles. In any case, it's not so
hard to create an abstraction layer for roles and implement dynamic
roles yourself.
> 3- Friendlier CFINVOKE syntax so you dont have to create the
> object ovewr and over for methods in the same CFC. eg.
>
> <cfinvoke component="componentsDemo.components.maths">
> <cfinvokemethod method="Average" returnVar="Bla">
> <cfinvokeargument name="Numbers" value="#Numbers#">
> </cfinvokemethod>
> <cfinvokemethod method="Sum" returnVar="Bla2">
> <cfinvokeargument name="Calculation"
> value="#Calculate#">
> </cfinvokemethod>
> </cfinvoke>
>
<cfscript>
objMath = createObject('component','componentsDemo.compoents.maths');
bla = objMath.Average(numbers);
bla2 = objMath.Sum(calculate);
</cfscript>
I'm not convinced that there's any real need for an improvement to
cfinvoke just so that there's a 3rd way to invoke methods on a
component.
Personally my biggest gripe about cfcs is the joke that is the
<cfproperty> tag. It does nothing useful apart from when you want to
generate the wsdl for a webservice. You can use getMetaData() to get the
attributes and values in the cfproperty tags in a cfc, but since that
function just reads the file and parses the cfproperty tags, it's just
as easy, and considerably more flexible to create your own mechanism
such as an external XML file, or a cfscript block at the top of the cfc
for defining object properties.
>
> I know you can do this by using the CreateObject and
> <CFOBJECT methods, but if they give us these tags to use,
> maybe they should be a little more flexible
>
> my 2 cents
>
> Steve Onnis
>
>
>
> ---
> You are currently subscribed to cfaussie as:
> [EMAIL PROTECTED] To unsubscribe send a blank email to
> [EMAIL PROTECTED]
>
> MX Downunder AsiaPac DevCon - http://mxdu.com/
>
---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
MX Downunder AsiaPac DevCon - http://mxdu.com/
