FlashForms are really Flex in disguise (with some big limitations). When I
was doing heavy flash forms work I would always have the flex documentation
open trying to figure out what the object actually were so I could use the
Flex methods. This is not always the safest/best way of doing things because
it's unsupported/documented but it does open a world of possibilities.
Anyway, here are a few things to wet your whistle:
1. After a flashform dump the form object to get the flex generated
code - note that this will dump a blob of code to the screen so use pre
tags. If you want to spend a second formatting save the output and replace
newline characters with break tags, this also allows you to add line number
which help when you get some weird error like 'error line 1292: .':
<cfform name="MyForm" format="flash">
<cfinput name="Name" type="text"/>
</cfform>
<pre>
<cfdump var="#MyForm#"/>
</pre>
2. You can write actionscript utilities in a separate file (say
util.as) and include it into your flashforms like:
<cfform name="MyForm" format="flash">
<cfformitem type="script">
#include "/path/to/file/util.as"
</cfformitem>
</cfform>
Just a side note that if you change code in an included file the page
including it looks like it didn't change to ColdFusion so you need to
refresh a bunch to make CF reparse the page.
3. If you need to need to see what is inside an object (say a cfinput
type=text) you can do:
<cfformitem type="script">
function dumpObject( object : Object ) : Void {
var objectKeyValues = "";
for(var i in object) {
}
}
</cfformitem>
_______________________________________________
Reply to DFWCFUG:
[email protected]
Subscribe/Unsubscribe:
http://lists1.safesecureweb.com/mailman/listinfo/list
List Archives:
http://www.mail-archive.com/list%40list.dfwcfug.org/
http://www.mail-archive.com/list%40dfwcfug.org/
DFWCFUG Sponsors:
www.HostMySite.com
www.teksystems.com/
