Hi
This is mainly a naming convention confusion for me but I also need to
understand the concept better.
Can someone clear up for me what really the scope of XFAs are ? (The
concept - not the code)
For example, in the script for fbx_switch and the subordinate qry_ and
act_ fuses, some values may be set which are read later by the dsp_
fuses of layout script.
In my last fusebox application, I tended to prefix these as $XFA_ ,
even if they weren't specifically the names of actions - I used $XFA_
for everything that was being set in the business logic layer which
was to be read by the displays and layouts.
I'm now thinking that XFA'a are a more specific concept - i.e. they
specifically refer to the names of fuseactions.
Is this correct ? If so could someone post an example of a typical use
of an exit fuseaction ? (If they can be bothered).
Here a schematic of the scenario I'm talking about:
[1] - Run fbx_switch,
call ---> qry_getActivities
call ---> act_doOrders
[2] - in act_doOrders, set some values (either in Active4D variables,
like $countActions, $Is_Valid, $helpMessage, or in a custom collection
etc)
call ---> dsp_doOrderList (In here, read the values that were
set in act_doOrders and act upon them)
My question is - are the values set in act_doOrders collectively known
as XFA's (i.e. I should prefix them XFA to indicate this) or are XFAs
a more specific thing - i.e. documented fuseactions only).
Many thanks for any assistance in setting me straight on this.
Regards
Peter
_______________________________________________
Active4D-dev mailing list
[email protected]
http://list.aparajitaworld.com/listinfo/active4d-dev
Archives: http://vasudev.aparajitaworld.com/archive/active4d-dev/
