I just built TDF locally with Ant after "ant clean" and the first screens showed up for me on OSX.
-Alex On 6/20/19, 5:40 AM, "Yishay Weiss" <[email protected]> wrote: Right now, after building TDF I’m getting a runtime error.. TypeError: mx.core.EdgeMetrics is not a constructor Watch Call Stack mx.core.Container.get__viewMetricsAndPadding Container.js:532 mx.containers.beads.BoxLayout.updateDisplayList BoxLayout.js:138 mx.containers.beads.BoxLayout.layout BoxLayout.js:115 org.apache.royale.core.LayoutBase.performLayout LayoutBase.js:247 org.apache.royale.core.LayoutBase.handleInitComplete LayoutBase.js:169 goog.events.EventTarget.fireListeners eventtarget.js:284 goog.events.EventTarget.dispatchEventInternal_ eventtarget.js:381 goog.events.EventTarget.dispatchEvent eventtarget.js:196 org.apache.royale.events.EventDispatcher.dispatchEvent EventDispatcher.js:71 org.apache.royale.core.HTMLElementWrapper.dispatchEvent HTMLElementWrapper.js:245 mx.core.Container.addedToParent Container.js:128 mx.containers.Box.addedToParent Box.js:63 org.apache.royale.core.UIBase.addElement UIBase.js:414 mx.core.Container.addElement Container.js:272 org.apache.royale.utils.MXMLDataInterpreter.initializeStrandBasedObject MXMLDataInterpreter.js:236 org.apache.royale.utils.MXMLDataInterpreter.generateMXMLArray MXMLDataInterpreter.js:125 org.apache.royale.utils.MXMLDataInterpreter.generateMXMLInstances MXMLDataInterpreter.js:266 mx.core.Container.createChildren Container.js:139 mx.core.Application.createChildren Application.js:110 mx.core.UIComponent.initialize UIComponent.js:639 mx.core.UIComponent.addedToParent UIComponent.js:259 mx.core.Container.addedToParent Container.js:126 org.apache.royale.core.UIBase.addElement UIBase.js:414 mx.managers.SystemManager.addChild SystemManager.js:105 mx.managers.SystemManager.initializeTopLevelWindow SystemManager.js:235 mx.managers.SystemManager.start SystemManager.js:221 (anonymous) index.html:720 Scope ________________________________ From: Piotr Zarzycki <[email protected]> Sent: Thursday, June 20, 2019 2:38:36 PM To: [email protected] Subject: State of Emulation Components Hi Yishay, I think good idea what they can display and how you can find in Tour De Flex migration example. It's running as part of our Jenkins. [1] [1] https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fjob%2FTourDeFlexMigration%2FlastSuccessfulBuild%2Fartifact%2Fexamples%2Fmxroyale%2Ftourdeflexmodules%2Fbin%2F&data=02%7C01%7Caharui%40adobe.com%7C3e577d1bf77f4d89b2a408d6f57c748b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636966312222183716&sdata=lfjpM5scgHnCgDjJkRb%2BhY5rHWxWbDU3OgaAYJO%2Flvc%3D&reserved=0 Thanks, Piotr On Thu, Jun 20, 2019, 1:31 PM Yishay Weiss <[email protected]> wrote: > Hi, > > I had a look at the wiki [1], but it looks like the related issue [2] is > closed. Do we have some concrete goals we can set to get them in a release > state? I’d like to get involved. > > Yishay > > [1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2Femulation-components&data=02%7C01%7Caharui%40adobe.com%7C3e577d1bf77f4d89b2a408d6f57c748b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636966312222183716&sdata=hm3cqwGZlr0Io3wPyfCLjPDO8vvMP5xZVuZt09E%2FXw8%3D&reserved=0 > [2] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F136&data=02%7C01%7Caharui%40adobe.com%7C3e577d1bf77f4d89b2a408d6f57c748b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636966312222183716&sdata=baZMAR0X351z9ajSeZwT1KuVg1kWu2S1%2FJ%2BD1pHDClI%3D&reserved=0 > >
