Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
MIME-Version: 1.0
In-Reply-To: <CANDXkxAEZD0_1tqnyGuVK8ddmpDPjhkpx6Z0Q6F=Puyp6gFX8A@mail.gmail.com>
References: <DB6PR0602MB28702A98F075CE71764C3F3993D50@DB6PR0602MB2870.eurprd06.prod.outlook.com>
 <CA+vpnOhs3wKTNwnZGSpVwuPWWX70EBgJ+jFeibHNnNfdktOt4A@mail.gmail.com>
 <DB6PR0602MB2870D25C8E2F91BB78D5A0FF93D50@DB6PR0602MB2870.eurprd06.prod.outlook.com>
 <1499365916687-62886.post@n4.nabble.com> <DB6PR0602MB287077E5AC181D516E82A48F93D50@DB6PR0602MB2870.eurprd06.prod.outlook.com>
 <D5840A61.97B74%aharui@adobe.com> <DB6PR0602MB2870B37F0114A60789287EF093AA0@DB6PR0602MB2870.eurprd06.prod.outlook.com>
 <D5847F2A.97BE3%aharui@adobe.com> <DB6PR0602MB2870F01BFD49F41814B5969C93AA0@DB6PR0602MB2870.eurprd06.prod.outlook.com>
 <DB6PR0602MB2870835B5BADA9910D0CDF8A93AA0@DB6PR0602MB2870.eurprd06.prod.outlook.com>
 <1499504266765-62960.post@n4.nabble.com> <HE1PR0602MB2874D3BE4CAE37F04C95867E93AB0@HE1PR0602MB2874.eurprd06.prod.outlook.com>
 <D5863ACA.97D3B%aharui@adobe.com> <DB6PR0602MB28705F2B70C8B263FF14510993AB0@DB6PR0602MB2870.eurprd06.prod.outlook.com>
 <CANDXkxAEZD0_1tqnyGuVK8ddmpDPjhkpx6Z0Q6F=Puyp6gFX8A@mail.gmail.com>
From: Greg Dove <greg.dove@gmail.com>
Date: Sun, 9 Jul 2017 07:57:32 +1200
Message-ID: <CANDXkxC3zk47FS8Y67_-VryiML75iVO1MDdtBLQ62-_9jSR9Hg@mail.gmail.com>
Subject: RE: [FlexJS] question about porting an Adobe Flex 3 project to HTML+JS
To: dev@flex.apache.org
Content-Type: multipart/alternative; boundary="94eb2c1a0a62ba7d5e0553d3c254"
archived-at: Sat, 08 Jul 2017 19:57:41 -0000

--94eb2c1a0a62ba7d5e0553d3c254
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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.yang@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:aharui@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 =3D 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.yang@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:yishayjobs@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=3Dhttp%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=3D02%7C01%7C%7C547b2
>515
>c4244d1105d608d4c6014a6d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6
>363
>51156227326642&sdata=3DVwy%2BU1qoAoMSD1R1jN3t%2BZLAjrCtOS1%2BMXjgdnWzUI8%
>3D&
>reserved=3D0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.
>
>________________________________
>
>Ce message, ainsi que tous les fichiers joints =C3=A0 ce message, peuvent
>contenir des informations sensibles et/ ou confidentielles ne devant
>pas =C3=AAtre divulgu=C3=A9es. Si vous n'=C3=AAtes pas le destinataire de =
ce message
>(ou que vous recevez ce message par erreur), nous vous remercions de le
>notifier imm=C3=A9diatement =C3=A0 son exp=C3=A9diteur, et de d=C3=A9truir=
e ce message.
>Toute copie, divulgation, modification, utilisation ou diffusion, non
>autoris=C3=A9e, 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 =C3=A0 ce message, peuvent
contenir des informations sensibles et/ ou confidentielles ne devant pas
=C3=AAtre divulgu=C3=A9es. Si vous n'=C3=AAtes pas le destinataire de ce me=
ssage (ou que
vous recevez ce message par erreur), nous vous remercions de le notifier
imm=C3=A9diatement =C3=A0 son exp=C3=A9diteur, et de d=C3=A9truire ce messa=
ge. Toute copie,
divulgation, modification, utilisation ou diffusion, non autoris=C3=A9e, di=
recte
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.

--94eb2c1a0a62ba7d5e0553d3c254--