XML2UI = XUL :-)
Since there’s no official docs on XML2UI from MM, I think everyone (or is that just me and Jesse – hehe) started to call it XUL as most of the info we gathered comes from xulplanet.com.
And XML2UI is a subset of (based on) XUL, right?

And writing XUL is much shorter than XML2UI or XML to UI ;-)

regards,
Muzak

(I read about “XML to UI” which seemed to imply Flex, then I read “XUL” which seemed to imply Mozilla creating a UI, then I read “JSAPI” which seemed to imply automating the Macromedia Flash MX authoring tool… I’m not getting a clear picture yet, couldn’t restate the desired question for confirmation yet.)

tx,
jd/mm

Thx for hosting the zip.
I’ve been struggling with the same problem. Communication between a XUL dialog and JSFL.
There seems to be a difference between calling a XUL file from a JSFL file and the other way around regarding getting/setting values in the XUL dialog.
When you open a XUL dialog using JSAPI, as in:
var xui = fl.getDocumentDOM().xmlPanel(fl.configURI + “Commands/xul-dialog.xml”);
That’s about all you can do (as far as I know). The rest has to be taken care of from inside the XUL dialog. Meaning, you then have to/can invoke functions inside a .jsfl file (and it doesn’t have to have the .jsfl extension by the way).
The JSFL file that launched the XUL dialog only reacts to the closing of the dialog and passes a ‘dismiss’ property with either an ‘accept’ or ‘cancel’ value.

if(xui.dismiss == “accept”){
fl.trace(“user clicked OK button”);
}
if(xui.dismiss == “cancel”){
fl.trace(“user clicked CANCEL button”);
}

And you can then retrieve property values from the XUL dialog using:
xui.propertyName

From within a XUL dialog you can invoke functions inside a JSFL file, which of course allows you to pass on arguments, using:

fl.runScript(filename, functionName, arg1, arg2);

Inside the function being invoked, you can then get/set property values from the XUL dialog using:

fl.xmlui.get(“propName”);
fl.xmlui.set(“propName”, “value”);

Hope this helps.

regards,
Muzak