Hi Alex,
Now I closed the HContainer tag; thanks for pointing it out.  But after making 
the corrections and rebuild, now the compiler got back to 
java.lang.NullPointerException again.
Also another error message: "internal error in outgoing dependency subsystem 
when generating code for c:\Projects\FBSearchBox\src\views\SearchBox.mxml ...."
Flash Builder finally got "unhandled event loop exception. GC overhead limit 
exceeded" error screen.

Regards,
Allen

-----Original Message-----
From: Alex Harui [mailto:aha...@adobe.com.INVALID]
Sent: Sunday, July 09, 2017 8:20 PM
To: dev@flex.apache.org
Subject: Re: [FlexJS] question about porting an Adobe Flex 3 project to HTML+JS

Did you close the Hcontainer tag?

On 7/9/17, 5:03 PM, "Allen YANG" <allen.y...@raritan.com> wrote:

>Hi Greg,
>Thanks for pointing out the xml errors.  I corrected them. The compiler
>doesn't hang any more.
>Now with "import com.iwobanas.core.ISearchable;" added within CDATA
>code block, I got a "definition com.iwobanas.core.ISearchable could not
>be found"
>Also, I got "js:Label is not allowed here" compilation error inside
><HContainer> Regards, Allen
>
>-----Original Message-----
>From: Greg Dove [mailto:greg.d...@gmail.com]
>Sent: Sunday, July 09, 2017 7:53 PM
>To: dev@flex.apache.org
>Subject: Re: [FlexJS] question about porting an Adobe Flex 3 project to
>HTML+JS
>
>I took a quick look at SearchBox.mxml
>
>there are at least some basic xml errors in it.
>
>xmlns:ns="library://ns.apache.org/flexjs/svg> <- missing quote
>
></js:View   <-incomplete end tag
>
>I think there is more, but I don't have time to check at the moment,
>sorry
>
>On Mon, Jul 10, 2017 at 11:05 AM, piotrz <piotrzarzyck...@gmail.com>
>wrote:
>
>> Allen,
>>
>> SearchBox.mxml - look good to me - of course if you have ISearchable
>> - but I don't see it. Apart of that you have in this project file
>> called "deallist.as" - which has a lot of old Flex classes - it's not
>> going to build. Not sure what you wanted to achieve ?
>>
>> Thanks,
>> Piotr
>>
>>
>>
>> -----
>> Apache Flex PMC
>> piotrzarzyck...@gmail.com
>> --
>> View this message in context: http://apache-flex-
>> development.2333347.n4.nabble.com/FlexJS-question-about-
>> porting-an-Adobe-Flex-3-project-to-HTML-JS-tp62698p62999.html
>> 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.

Reply via email to