[ http://issues.apache.org/jira/browse/XAP-9?page=comments#action_12430571 ] Turyn, Michael commented on XAP-9: ----------------------------------
That's "mco's", not "mxo's". If someone can edit the title, I'd appreciate it. > Should be able to specify source for mxo's used in XAL files. > ------------------------------------------------------------- > > Key: XAP-9 > URL: http://issues.apache.org/jira/browse/XAP-9 > Project: XAP > Issue Type: Improvement > Environment: HTML > Reporter: Turyn, Michael > > Currently, to use an MCO declared in a XAL file, one must include the source > for it in the HTML defining the page, e.g. for > .xal file > ====== > <mco:mco > xmlns:mco="http://www.openxal.org/mco"; > id="handler" > src="aHandlerObject" > /> > we need to have > .html file > ======= > <script language="JavaScript" > src="uriToSomeFileWhere_aHandlerObject_isDefined.js"> </script> > ---the "src" would more accurately be a "bean" or "object" attribute, since > it doesn't refer to a source file, but to a constructor defined ...somewhere. > Typically, this is in a <script/> tag in the html for the page, tying the > page to a particular XAL and vice versa. > Just as bridge classes should load their peer classes, relieving the page > designer of knowing about the widgets, mco's under JS should be able to have > a URI which can be used to load the object needed. > (Perhaps we should keep the freedom for people who really want to to load > from the page---that allows locally-defined versions of handlers....) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
