RE: [FlexJS] question about porting an Adobe Flex 3 project to HTML+JS

[Allen YANG]

Hi Alex,
After I following the 4 steps, then cleaned and rebuilt the project in Flash 
Builder, running demo_for_presentation still got the same errors.
Error 1079: "Native methods are not allowed in loaded code", and Error 1065: 
"variable demo_for_presentation is not defined".
I will move on from this for now.
Thanks and Regards,
Allen

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

Hi Allen, Yishay,

Looks like the Flash Builder project was set up for Yishay's development 
environment and won't translate well to others.  As a workaround, try this:

1) In Project -> Properties -> Flex Build Path, remove airglobal

2) Shut down Flash Builder

3) Open the .actionScriptProperties file in a text editor and remove these two 
lines from excludedEntries:

  

4) Use the file system to remove bin folder from the project folder.


5) Restart Flash Builder, clean and rebuild the project.

HTH, it worked for me.

-Alex

On 6/30/17, 11:48 PM, "Alex Harui"  wrote:

>Hi Allen,
>
>Hmm. I'm having the same problem.  Not sure why yet.  I'm looking into
>it, but I won't much time this weekend.
>
>-Alex
>
>On 6/30/17, 3:25 PM, "Allen YANG"  wrote:
>
>>Hi Alex,
>>After I was able to build the project without error; I checked running
>>demo_for_presentation from Flash Builder.   My default browser is Google
>>Chrome, I know that wouldn't work; so I downloaded the debug version
>>of Flash Player for Firefox and set the default browser to be Firefox
>>on Flash Builder.  Then I ran demo_for_presentation.  Firefox came up,
>>then I got "Error 1079: are not allowed in loaded code", and Error 1065:
>>variable demo_for_presentation is not defined".
>>Do you know of a way I can run this without Flash Player?
>>Best Regards,
>>Allen
>>
>>-Original Message-
>>From: Allen YANG [mailto:allen.y...@raritan.com]
>>Sent: Friday, June 30, 2017 5:22 PM
>>To: dev@flex.apache.org
>>Subject: RE: [FlexJS] question about porting an Adobe Flex 3 project
>>to
>>HTML+JS
>>
>>Hi Alex,
>>You are correct.  After deleting al the errors out of the error log
>>and cleaned and built and project, the error went away.
>>Thank you so much!
>>Best Regards,
>>Allen
>>
>>-Original Message-
>>From: Alex Harui [mailto:aha...@adobe.com.INVALID]
>>Sent: Friday, June 30, 2017 5:08 PM
>>To: dev@flex.apache.org
>>Subject: Re: [FlexJS] question about porting an Adobe Flex 3 project
>>to
>>HTML+JS
>>
>>Hi Allen,
>>
>>Delete all of the errors out of the error log so we know you are still
>>getting new ones.
>>
>>Go back to project properties to make sure Core and Basic were removed.
>>Maybe grab a screenshot of the dialog box and post a link to it.
>>
>>Then clean and build the project and in the Project Explorer, see if
>>the demo has a red X on it.  If it still does, reatart Flash Builder,
>>then repeat the above steps.  The errors went away for me.
>>
>>HTH,
>>-Alex
>>
>>
>>On 6/30/17, 2:03 PM, "Allen YANG"  wrote:
>>
>>>Hi Alex,
>>>Thanks for looking into this.  I removed  Core.swc and Basic.swc from
>>>Flex Build Path and cleaned the project and rebuilt.  The result is
>>>still the same.
>>>Best Regards,
>>>Allen
>>>
>>>-Original Message-
>>>From: Alex Harui [mailto:aha...@adobe.com.INVALID]
>>>Sent: Friday, June 30, 2017 4:48 PM
>>>To: dev@flex.apache.org
>>>Subject: Re: [FlexJS] question about porting an Adobe Flex 3 project
>>>to
>>>HTML+JS
>>>
>>>Hi Allen,
>>>
>>>Looks like you ran into a bug.  I will look into a fix for it.  As a
>>>workaround, go to the Project menu, choose Properties, then Flex
>>>Build Path.  Remove the Core.swc and Basic.swc.  Yishay probably had
>>>his own development versions of them but you can use the ones in the FlexJS 
>>>SDK.
>>>
>>>That should clear up the error.
>>>
>>>HTH,
>>>-Alex
>>>
>>>On 6/30/17, 11:50 AM, "Allen YANG"  wrote:
>>>
Hi Yishay,
Thank you for uploading the presentation demo to OneDrive.  After
downloading the demo for presentation demo.zip file and importing
that to my Flash Builder 4.7, I made sure the SDK is set to FlexJS,
then I did a build and got an error: "An internal error has
occurred, see error log for more information" in plug-in
"com.adobe.flexbuilder.project"
Could you help to shed some light?
Thanks,
Allen

The stack trace is as follows:

--
-
---
--
java.lang.NullPointerException
at
flex2.tools.oem.Application.processMXMLCReport(Application.java:681)
at flex2.tools.oem.Application.compile(Application.java:644)
at
flex2.tools.flexbuilder.BuilderApplication.compile(BuilderApplication.
j
ava
:366)
at

RE: [FlexJS] question about porting an Adobe Flex 3 project to HTML+JS

[Allen YANG]

Hi Piotr,
I followed your instructions and it worked.
Thank you very much!
Best,
Allen

-Original Message-
From: piotrz [mailto:piotrzarzyck...@gmail.com]
Sent: Sunday, July 02, 2017 5:46 PM
To: dev@flex.apache.org
Subject: RE: [FlexJS] question about porting an Adobe Flex 3 project to HTML+JS

Hi Allen,

I've prepared HelloWorld [1] app for you which is building by Maven. You need 
to make following things before you build it (Windows user):

1) Install Maven [2]
2) In my example you have file "settings.xml" - This file is simply telling 
where maven should look for artifacts (swc) in order to build your project.
- Copy this file to: "c:\Users\{your user}\.m2\"
3) Open folder with project in VSCode and hit Ctrl + Shift + B or Go to folder 
where pom.xml file is and type in console "mvn clean install" - Thanks to 
VSCode you can debug your app (Try to hit F5 - Maven build app and launch it in 
debugger mode)

That's all and you have totally IDE agnostic build. Take a look into the 
pom.xml - As you can see I did comment Express and MaterialDesignLite - If you 
use some of the components from those modules you have to un-comment it.
This build produce only JS version of application - Line:

JSFlex

It would be good idea also change org.apache to maybe some 
related to you company for example.

[1] https://1drv.ms/u/s!ApVpLyjpHDC20GzswOaytmRVWHMo
[2] https://maven.apache.org/install.html#

Good Luck with farther FlexJS exploring :)

Piotr




-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-question-about-porting-an-Adobe-Flex-3-project-to-HTML-JS-tp62698p62762.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.

RE: [FlexJS] question about porting an Adobe Flex 3 project to HTML+JS

[piotrz]

Hi Allen,

I've prepared HelloWorld [1] app for you which is building by Maven. You
need to make following things before you build it (Windows user):

1) Install Maven [2] 
2) In my example you have file "settings.xml" - This file is simply telling
where maven should look for artifacts (swc) in order to build your project.
- Copy this file to: "c:\Users\{your user}\.m2\"
3) Open folder with project in VSCode and hit Ctrl + Shift + B or Go to
folder where pom.xml file is and type in console "mvn clean install" -
Thanks to VSCode you can debug your app (Try to hit F5 - Maven build app and
launch it in debugger mode)

That's all and you have totally IDE agnostic build. Take a look into the
pom.xml - As you can see I did comment Express and MaterialDesignLite - If
you use some of the components from those modules you have to un-comment it.
This build produce only JS version of application - Line:

JSFlex

It would be good idea also change org.apache to maybe
some related to you company for example.

[1] https://1drv.ms/u/s!ApVpLyjpHDC20GzswOaytmRVWHMo
[2] https://maven.apache.org/install.html#

Good Luck with farther FlexJS exploring :)

Piotr




-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-question-about-porting-an-Adobe-Flex-3-project-to-HTML-JS-tp62698p62762.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] PAYG definitions and guidance, Please participate

[yishayw]

To me it's a bit difficult to digest in its current format. I would prefer to
see a list of design patterns with descriptions of concrete problems and
proposed solutions. This doc could be PAYG in itself. You come across a
problem, solve it with PAYG, add an item in the doc, if the idea isn't
already there. 




--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-PAYG-definitions-and-guidance-Please-participate-tp62738p62760.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [ANNOUNCE] Apache FlexJS 0.8.0 and Apache Flex FalconJX 0.8.0 Released

[Nemi]

Can't install it using Installer, it looks download flexjs link is wrong,
log:

Installer version 3.2.0 (windows)
Using Locale: hr_HR
Fetched the SDK download mirror URL from the CGI.
SDK version Apache FlexJS 0.8.0
AIR version 25.0
Flash Player version 25.0
Creating Apache FlexJS home
Creating temporary directory
Downloading Apache FlexJS from:OCTYPE html>


  
  
  
  
  https://www.apache.org/dyn/closer.cgi; />
  

[...CROPPED HTML...]




http://apache-flex-development.247.n4.nabble.com/ANNOUNCE-Apache-FlexJS-0-8-0-and-Apache-Flex-FalconJX-0-8-0-Released-tp62718p62758.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Failed to download nightly build FlexJS 0.9.0

[PKumar]

I am trying to download FlexJS0.8.0 via installer but getting error. please
check the following error log.

[image: Inline image 1]

On Thu, Jun 29, 2017 at 1:27 PM, piotrz [via Apache Flex Development] <
ml+s247n62679...@n4.nabble.com> wrote:

> Alex,
>
> Now it's working!
>
> Thanks,
> Piotr
> Apache Flex PMC
> piotrzarzyck...@gmail.com
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-flex-development.247.n4.nabble.
> com/FlexJS-Failed-to-download-nightly-build-FlexJS-0-9-0-
> tp62664p62679.html
> To start a new topic under Apache Flex Development, email
> ml+s247n1...@n4.nabble.com
> To unsubscribe from Apache Flex Development, click here
> 
> .
> NAML
> 
>



-- 
*Regards,*
Prashant Kumar* | *Mob.: +91 8408811225


image.png (258K) 





--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-Failed-to-download-nightly-build-FlexJS-0-9-0-tp62664p62757.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] PAYG definitions and guidance, Please participate

[Harbs]

Great start.

I just made some additions and changes. Hopefully I helped make it clearer and 
not the other way around… ;-)

I just want to say, that while PAYG is hard both from a framework development 
perspective and from an application development perspective, I firmly believe 
that strict adherence to the concepts are worthwhile. I say this after using 
FlexJS full time on both sides of the equation for more than a year.

We DEFINITELY want to make it easier for application developers to get started, 
and hopefully the Express set is a step in the right direction. We also 
DESPERATELY need better documentation and guides. Unfortunately most of us are 
not great writers. :-(

Harbs

> On Jul 2, 2017, at 1:40 AM, Greg Dove  wrote:
> 
> Thanks Alex,
> 
> I look forward to your feedback. It would be great to see  (from you or
> anyone else) -  within this thread - suggested improvements/corrections or
> other topics that should be added, or questions that should be addressed.
> 
> I know there are areas that need improvement in a number of areas of the
> document, but I'm hoping that this will be 'fixed' by making it a shared
> goal and getting input from others, not by me kludging away in the
> background. I wanted to get something up that is a starting point only.
> 
> I do understand the avoidance of the 'swiss army knife' approach to base
> classes in Flex 4, but had wondered about whether we were focusing on the
> 19% of functionality that might be useful for 5% of developers (Basic) vs.
> the 20% of that will suit 80% of developers (e.g. express) -I'm not saying
> that the pareto relationships there are correct, just using it for
> 'relative' comparison. But I think it is just a case of getting used to a
> new way to thinking, which is different to Flex4 (and Flex3). It would be
> really great if you can lead a thread specifically about this.
> 
> I also suspect there will be no 'one true way' to make incremental
> functionality beads either. But documenting the pros and cons of each
> approach (which we already started in one of the other threads) might
> provide useful guidance about when to choose which approach (inheritance
> and/or utility functions etc). I'm looking forward to that discussion
> because I think I was getting a lot out of the earlier discussion on that
> already.
> 
> In the end writing these things in a document is not something I call fun.
> "I'd much rather be coding". But I do believe that having 'team-sourced'
> content, as an output of focused list discussions, could make the
> generation of the document content a much easier process, and that the
> process itself could help  improve decision quality, build consensus, and
> provide resources that will be useful for team alignment and future
> reference info for others. I think any one of those reasons is enough for
> me to stop trying to create more of the content myself!
> 
> 
> 
> On Sun, Jul 2, 2017 at 3:57 AM, Alex Harui  wrote:
> 
>> Hi Greg,
>> 
>> Thanks for writing this up.  I took a quick read.  I'll do a more careful
>> read next week and have more detailed comments.  One thing I wanted put up
>> for discussion now is the notion of "defaults".  Really, I'm trying to get
>> away from the notion that there is one default we have to decide on.  IMO,
>> that's another old way of thinking from Flex.  FlexJS is designed to
>> support multiple component sets.  Express will have different defaults.
>> MDL has different defaults.  The Basic set has a particular design goal
>> (feature parity with SWF) and thus will have different defaults.  There is
>> often no one right answer, so we build different component sets and folks
>> will try them and decide for themselves.
>> 
>> Thoughts?
>> -Alex
>> 
>> On 6/30/17, 3:29 PM, "Greg Dove"  wrote:
>> 
>>> Following on from other discussions, I have made a start on something here
>>> https://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Fcwiki.apa
>>> che.org%2Fconfluence%2Fpages%2Fviewpage.action%3FpageId%
>> 3D71013028=02
>>> %7C01%7C%7C35f519d4ea87431fd80808d4c0078bc3%
>> 7Cfa7b1b5a7b34438794aed2c178de
>>> cee1%7C0%7C0%7C636344586020292933=aj4YiAsUQDGoW5Bf%
>> 2BQ2wyJxgqmguZ18T
>>> Zng2jGcWIkY%3D=0
>>> 
>>> In the end this will only work if people want to do it. But I do believe
>>> that one way of getting everyone on the same page here (and we do have
>>> clear signs that not everyone is), is to, quite literally, get everyone on
>>> the same page :).
>>> 
>>> It is currently half content, half notes. There is more to harvest from
>>> list discussions I think, some topics have progressed further than when I
>>> started trying to capture ideas, so please correct any mistakes in the
>>> definitions or add topics and questions that need 'resolution'/guidance.
>>> 
>>> I personally would like to see some concrete guidance in the 'How does
>>> PAYG
>>> get implemented' section. There were definitely