Hi Greg, I moved the fx:Script tag outside of the HContainer tag; the compiler still took several minutes and hit the same problem. Regards, Allen
-----Original Message----- From: Greg Dove [mailto:greg.d...@gmail.com] Sent: Saturday, July 08, 2017 3:58 PM To: dev@flex.apache.org Subject: RE: [FlexJS] question about porting an Adobe Flex 3 project to HTML+JS I just glanced back at your mxml. Not sure if this will help... but you could try moving the fx:Script tag outside the HContainer tag so it is top level inside your mxml. This seems more conventional although I am not sure whether it is the cause of the compiler issues you are seeing or not. -Greg [sent from my phone] On 9/07/2017 6:32 AM, "Allen YANG" <allen.y...@raritan.com> wrote: Hi Alex, I am leaving SearchBox.mxml compiler issue aside for now since I have no idea how to solve it. Following the MyInitialView.mxml example, I was finally able to convert a Flex 3 MXML file called UpdateResources.mxml which starts with <mx:TitleWindow> and has a Canvas with HBox, VBox and Buttons inside. The result is a very slimmed down version of FlexJS implementation which starts with <js:View> and includes a <js:Group> with HContainer, VContainer, and TextButtons inside. I lost most of the formatting of the pages because many attributes are not there anymore. Could you comment whether that's about right, or I have completely got it wrong? (The complied result could run but certainly I lost most of the original UI's screen formatting due to many of the properties not being supported.) Thanks and Regards, Allen -----Original Message----- From: Alex Harui [mailto:aha...@adobe.com.INVALID] Sent: Saturday, July 08, 2017 10:42 AM To: dev@flex.apache.org Subject: Re: [FlexJS] question about porting an Adobe Flex 3 project to HTML+JS Hi Allen, These are great questions. Many examples have a MyInitialView.mxml file with js:View as the top tag. You might want to refer to those examples. The current Panel does have an optional close button so it can substitute as TitleWindow, but I am currently refactoring it for 0.9.0 to be more pay-as-you-go. Unless you need more than one floating window, you shouldn't need PopUpManager (which is why it doesn't exist in FlexJS yet). Instead use code like: var host:IPopUpHost; host = UIUtils.findPopUpHost(this); // this is the main view IPopUpHost(host).addElement(popUp as IChild); HGroup or HContainer can swap in for HBox. Use Group or Container instead of Canvas. Good luck, -Alex On 7/8/17, 6:00 AM, "Allen YANG" <allen.y...@raritan.com> wrote: >Hi Yishay, >You are right. I rechecked the demo.zip file and panelview.as is not >there. Maybe I was trying to learn about TitleWindow replacement and >break the code into a separate file, ended up leaving it there. >No luck yet in converting my MXML file for TitleWindow equivalent >because it also has PopUpManager and uses HBox and Canvas in the same >MXML file. >I cannot get a simple MXML file (less than 40 lines) to compile. > >I am confused why the same code compiles and works when it is part of >the MXML file inside of <Application> but when I tried to create a >separate MXML file for a panel inside of a View it doesn't compile. >In other words, <js:initialView><js:View></js:View></js:initialView> >will be fine inside <Application> but cannot be standalone. This must >be another newbie question. >Regards, >Allen > >-----Original Message----- >From: yishayw [mailto:yishayj...@hotmail.com] >Sent: Saturday, July 08, 2017 4:58 AM >To: dev@flex.apache.org >Subject: RE: [FlexJS] question about porting an Adobe Flex 3 project to >HTML+JS > >I don't see panelview.as in the sources. But anyway, I don't remember >it being part of the demo so you can ignore it for now. Any luck with >creating a TitleWindow equivalent? > > > >-- >View this message in context: >https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache- >fle >x-development.2333347.n4.nabble.com%2FFlexJS-question-about-porting-an- >Ado >be-Flex-3-project-to-HTML-JS-tp62698p62960.html&data=02%7C01%7C%7C547b2 >515 >c4244d1105d608d4c6014a6d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6 >363 >51156227326642&sdata=Vwy%2BU1qoAoMSD1R1jN3t%2BZLAjrCtOS1%2BMXjgdnWzUI8% >3D& >reserved=0 >Sent from the Apache Flex Development mailing list archive at Nabble.com. > >________________________________ > >Ce message, ainsi que tous les fichiers joints à ce message, peuvent >contenir des informations sensibles et/ ou confidentielles ne devant >pas être divulguées. Si vous n'êtes pas le destinataire de ce message >(ou que vous recevez ce message par erreur), nous vous remercions de le >notifier immédiatement à son expéditeur, et de détruire ce message. >Toute copie, divulgation, modification, utilisation ou diffusion, non >autorisée, directe ou indirecte, de tout ou partie de ce message, est >strictement interdite. > > >This e-mail, and any document attached hereby, may contain confidential >and/or privileged information. If you are not the intended recipient >(or have received this e-mail in error) please notify the sender >immediately and destroy this e-mail. Any unauthorized, direct or >indirect, copying, disclosure, distribution or other use of the >material or parts thereof is strictly forbidden. ________________________________ Ce message, ainsi que tous les fichiers joints à ce message, peuvent contenir des informations sensibles et/ ou confidentielles ne devant pas être divulguées. Si vous n'êtes pas le destinataire de ce message (ou que vous recevez ce message par erreur), nous vous remercions de le notifier immédiatement à son expéditeur, et de détruire ce message. Toute copie, divulgation, modification, utilisation ou diffusion, non autorisée, directe ou indirecte, de tout ou partie de ce message, est strictement interdite. This e-mail, and any document attached hereby, may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized, direct or indirect, copying, disclosure, distribution or other use of the material or parts thereof is strictly forbidden. ________________________________ Ce message, ainsi que tous les fichiers joints à ce message, peuvent contenir des informations sensibles et/ ou confidentielles ne devant pas être divulguées. Si vous n'êtes pas le destinataire de ce message (ou que vous recevez ce message par erreur), nous vous remercions de le notifier immédiatement à son expéditeur, et de détruire ce message. Toute copie, divulgation, modification, utilisation ou diffusion, non autorisée, directe ou indirecte, de tout ou partie de ce message, est strictement interdite. This e-mail, and any document attached hereby, may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized, direct or indirect, copying, disclosure, distribution or other use of the material or parts thereof is strictly forbidden.