I'm not sure what you mean by structures. You aren't using any in the
examples you gave.
When instantiating a content type or rule you should use
application.stCOAPI.xyz.packagepath. This will work for all rules and all
types.
Regarding formtools, you should never have to reference
farcry.core.packages.farcry.formtools. Everything you need is exposed via
ft:object. To see how core uses it for edit forms you can have a look in the
edit function on the types component.
Blair
On Mon, Nov 24, 2008 at 4:43 AM, Marco van den Oever <
[EMAIL PROTECTED]> wrote:
>
> In my attempt to use as much structures as possible i am rechecking
> code that is build with formtools, is it correct that using structures
> is faster?
>
> Trying now to use structures instead of query's with:
>
> <cfset oFormtoolUtil = createObject("component",
> "farcry.core.packages.farcry.formtools") />
>
> Is it correct that for rule table data you can't address without using
> oFormtoolUtil?
>
> You can't connect with:
>
> <cfset obj = createObject
> ('component',application.stcoapi.blablabla.typePath) />
>
> as it is not an type.
>
> You can't connect directly with:
>
> obj.getData(stobj.objectid) (or with additional properties)
>
> as the stobj.objectid refer to the rule table, so not directly to the
> data i need.
>
> Even when it works out eventually then you might end up with a couple
> of structures to do the same you can do with one oFormtoolUtil setup.
>
> What's your vision on this?
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"farcry-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/farcry-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
