Re: [RESULT] [VOTE] Release Apache Flex BlazeDS 4.8.0 RC1

[Yishay Weiss]

Thanks!

Get Outlook for Android

From: Josh Tynjala 
Sent: Monday, April 17, 2023 6:39:29 PM
To: Apache Flex Development 
Subject: [RESULT] [VOTE] Release Apache Flex BlazeDS 4.8.0 RC1

Vote passes with 3 binding +1 votes.

Thank you,

Josh


On Wed, Mar 8, 2023 at 3:05 PM Josh Tynjala 
wrote:

> Hi,
>
> This is the vote for the 4.8.0 release of Apache Flex BlazeDS.
>
> This release disables or removes certain modules that required third-party
> dependencies that are no longer maintained, and it updates a number of
> other dependencies.
>
> The release candidate can be found here:
> https://dist.apache.org/repos/dist/dev/flex/BlazeDS/4.8.0/rc1/
>
> Before voting please review the section, "What are the ASF requirements on
> approving a release?", at:
> https://www.apache.org/dev/release.html#approving-a-release
>
> At a minimum you would be expected to check that:
> - SHA and signed packages are correct
> - README, RELEASE_NOTES, NOTICE and LICENSE files are all fine
> - That you can compile from source package using `mvn clean install`
>
> The KEYS file is at https://dist.apache.org/repos/dist/release/flex/KEYS
>
> Please vote to approve this release:
> +1 Approve the release
> -1 Don’t approve the release (please provide specific comments to why)
>
> This vote will be open for 72 hours or until a result can be called.
>
> The vote passes if there is:
> - At least 3 +1 votes from the PMC
> - More positive votes than negative votes
>
> If you find an issue with the release that's a "show stopper" please don't
> hold off voting -1. If someone votes -1, please continue testing. We want
> to try and catch as many issues as we can and cut down on the number of
> release candidates. Remember existing voters can change their vote during
> the voting process.
>
> People who are not in the PMC are also encouraged to test out the release
> and vote, although their votes will not be binding, they can influence how
> the PMC votes.
>
> Please put all discussion about this release in the DISCUSS thread – not
> in this VOTE thread.
>
> Thanks,
> Josh
>

Re: [VOTE] Release Apache Flex BlazeDS 4.8.0 RC1

[Yishay Weiss]

+1

Windows 11
JDK 17.0.5
Apache Maven 3.8.1

Signatures match and key verified against 
https://dist.apache.org/repos/dist/release/flex/KEYS

Source builds



From: Josh Tynjala 
Sent: Monday, March 20, 2023 7:07 PM
To: Apache Flex Development 
Subject: Re: [VOTE] Release Apache Flex BlazeDS 4.8.0 RC1

+1

macOS Ventura 13.2.1
Temurin JDK 11.0.17
Apache Maven 3.8.6

Source package builds, SHA512 and GPG signature match.

I tested runtime behavior using a modified version of Adobe's BlazeDS
turnkey distribution v4.0.0.14931 (which I archived on my personal Github,
to make it easier to find).

https://github.com/joshtynjala/blazeds-turnkey-archive

I upgraded the distribution to Tomcat 9, and I replaced the original Adobe
BlazeDS jar files with the Apache BlazeDS jar files.

For the client side, I replaced the SWF browser samples with functionally
equivalent AIR apps (built with Feathers UI and Haxe, but they still
use AIR's native AMF implementation, so they're testing what needs to be
tested). For completeness, I also ensured that they work when built for JS
and served from Tomcat.

https://github.com/feathersui/feathersui-blazeds-turnkey-samples

--
Josh Tynjala
Bowler Hat LLC 


On Wed, Mar 8, 2023 at 3:05 PM Josh Tynjala 
wrote:

> Hi,
>
> This is the vote for the 4.8.0 release of Apache Flex BlazeDS.
>
> This release disables or removes certain modules that required third-party
> dependencies that are no longer maintained, and it updates a number of
> other dependencies.
>
> The release candidate can be found here:
> https://dist.apache.org/repos/dist/dev/flex/BlazeDS/4.8.0/rc1/
>
> Before voting please review the section, "What are the ASF requirements on
> approving a release?", at:
> https://www.apache.org/dev/release.html#approving-a-release
>
> At a minimum you would be expected to check that:
> - SHA and signed packages are correct
> - README, RELEASE_NOTES, NOTICE and LICENSE files are all fine
> - That you can compile from source package using `mvn clean install`
>
> The KEYS file is at https://dist.apache.org/repos/dist/release/flex/KEYS
>
> Please vote to approve this release:
> +1 Approve the release
> -1 Don’t approve the release (please provide specific comments to why)
>
> This vote will be open for 72 hours or until a result can be called.
>
> The vote passes if there is:
> - At least 3 +1 votes from the PMC
> - More positive votes than negative votes
>
> If you find an issue with the release that's a "show stopper" please don't
> hold off voting -1. If someone votes -1, please continue testing. We want
> to try and catch as many issues as we can and cut down on the number of
> release candidates. Remember existing voters can change their vote during
> the voting process.
>
> People who are not in the PMC are also encouraged to test out the release
> and vote, although their votes will not be binding, they can influence how
> the PMC votes.
>
> Please put all discussion about this release in the DISCUSS thread – not
> in this VOTE thread.
>
> Thanks,
> Josh
>

RE: [DISCUSS] Release Apache flex-sdk-converter-maven-extension 1.1.0 RC1

[Yishay Weiss]

This is actually stated in the README, sorry for missing that. If you do decide 
to fix this issue you should probably modify the Install Prerequisites section 
in README as well.

Thanks for doing this

From: Josh Tynjala<mailto:joshtynj...@bowlerhat.dev>
Sent: Thursday, February 9, 2023 6:24 PM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>
Subject: Re: [DISCUSS] Release Apache flex-sdk-converter-maven-extension 1.1.0 
RC1

I confirm that PlatformTypeTest fails with JDK 17, but works in JDK 8 and
11. The test seems to be using reflection to change a private property in
the JDK to non-final so that it can pretend to be running on a different
platform temporarily. Some quick research turned up that the JDK authors
made things stricter in JDK 12 because doing something like this should not
be encouraged.

This test is broken, but the behavior of flex-sdk-converter-maven-extension
is still correct. I will definitely fix the test for future releases.

Yishay, would you be willing to test `mvn clean install` with JDK 11 so
that we don't need to do a new RC? If you're going to try it with
royale-compiler, you can switch back to JDK 17 for that.

--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Wed, Feb 8, 2023 at 11:10 PM Yishay Weiss  wrote:

> I’m getting this:
>
> C:\dev\apache-flex-sdk-converter-1.1.0>mvn clean install
> Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
> [INFO] Scanning for projects...
> [INFO]
> 
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Apache Flex - SDK-Converter
> [pom]
> [
> (…)
>
> [INFO]  T E S T S
> [INFO] ---
> [INFO] Running
> org.apache.flex.utilities.converter.retrievers.types.PlatformTypeTest
> [ERROR] Tests run: 5, Failures: 0, Errors: 5, Skipped: 0, Time elapsed:
> 0.082 s <<< FAILURE! - in
> org.apache.flex.utilities.converter.retrievers.types.PlatformTypeTest
> [ERROR] [0] IS_OS_WINDOWS, WINDOWS
> (it_detects_the_current_platform_type)(org.apache.flex.utilities.converter.retrievers.types.PlatformTypeTest)
> Time elapsed: 0.009 s  <<< ERROR!
> java.lang.NoSuchFieldException: modifiers
> at
> org.apache.flex.utilities.converter.retrievers.types.PlatformTypeTest.setFinalStatic(PlatformTypeTest.java:74)
> at
> org.apache.flex.utilities.converter.retrievers.types.PlatformTypeTest.setUp(PlatformTypeTest.java:51)
>
> From: Josh Tynjala<mailto:joshtynj...@bowlerhat.dev>
> Sent: Friday, February 3, 2023 6:23 PM
> To: dev@flex.apache.org<mailto:dev@flex.apache.org>
> Subject: Re: [DISCUSS] Release Apache flex-sdk-converter-maven-extension
> 1.1.0 RC1
>
> At minimum, extract the source-release .zip file and run `mvn clean
> install` in the root directory that contains pom.xml.
>
> OPTIONAL: After `mvn clean isntall`, you can also test that it works with
> the royale-compiler repo (be sure to pull the latest commits). Here's what
> you need to do:
>
> (Prerequisite: Make sure that you have the FLASHPLAYER_DEBUGGER env var
> pointing to a Flash Player projector executable. If you don't have this
> executable already, the royale-compiler README explains how you can still
> download it from Adobe.)
>
> 1. In royale-compiler, go into .mvn/extensions.xml and set the version to
> 1.1.0: 1.1.0
> 2. Go into ~/.m2/repository/com/adobe/flash/ and move the "framework"
> directory somewhere else temporarily. This lets you put it back later, if
> something goes wrong.
> 3. In royale-compiler, run `mvn clean install -P option-with-swf`.
>
> If the royale-compiler option-with-swf build passes, then the extension
> successfully installed playerglobal 32.0.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Thu, Feb 2, 2023 at 11:28 PM Harbs  wrote:
>
> > What do I need to do to test this?
> >
> > > On Feb 3, 2023, at 1:15 AM, Josh Tynjala 
> > wrote:
> > >
> > > Hi,
> > >
> > > Please discuss the flex-sdk-converter-maven-extension 1.1.0 release
> > > candidate here and not in the vote thread.
> > >
> > > Thanks,
> > > Josh
> >
> >
>
>

RE: [VOTE] Release Apache flex-sdk-converter-maven-extension 1.1.0 RC1

[Yishay Weiss]

+1


  *   Source code compiles (JDK 8)
  *   Sha512 matches
  *   README repo link and java versions correct



From: Harbs
Sent: Sunday, February 12, 2023 2:45 PM
To: dev@flex.apache.org
Subject: Re: [VOTE] Release Apache flex-sdk-converter-maven-extension 1.1.0 RC1

+1

It built correctly on my machine.

I gave it a general look-over and it looks fine to me.

I didn’t check that it downloaded playerglobal because I don’t have a valid 
maven build on my machine (I needed to upgrade maven just to test this).

Harbs

> On Feb 3, 2023, at 1:15 AM, Josh Tynjala  wrote:
>
> Hi,
>
> This is the vote for the 1.1.0 release of Apache
> flex-sdk-converter-maven-extension.
>
> This release fixes an HTTP to HTTPS redirect issue that causes Mavenized
> downloads to fail.
>
> The release candidate can be found here:
> https://dist.apache.org/repos/dist/dev/flex/flex-maven-tools/flex-sdk-converter/1.1.0/rc1/
>
> Before voting please review the section, "What are the ASF requirements on
> approving a release?", at:
> https://www.apache.org/dev/release.html#approving-a-release
>
> At a minimum you would be expected to check that:
> - SHA and signed packages are correct
> - README, RELEASE_NOTES, NOTICE and LICENSE files are all fine
> - That you can compile from source package
>
> The KEYS file is at https://dist.apache.org/repos/dist/release/flex/KEYS
>
> Please vote to approve this release:
> +1 Approve the release
> -1 Don’t approve the release (please provide specific comments to why)
>
> This vote will be open for 72 hours or until a result can be called.
>
> The vote passes if there is:
> - At least 3 +1 votes from the PMC
> - More positive votes than negative votes
>
> If you find an issue with the release that's a "show stopper" please don't
> hold off voting -1. If someone votes -1, please continue testing. We want
> to try and catch as many issues as we can and cut down on the number of
> release candidates. Remember existing voters can change their vote during
> the voting process.
>
> People who are not in the PMC are also encouraged to test out the release
> and vote, although their votes will not be binding, they can influence how
> the PMC votes.
>
> Please put all discussion about this release in the DISCUSSION thread not
> this VOTE thread.
>
> Thanks,
> Josh

RE: [DISCUSS] Release Apache flex-sdk-converter-maven-extension 1.1.0 RC1

[Yishay Weiss]

I can confirm that it compiles on windows for java 8. I’ll try to do some more 
checks later and vote. Thanks.

From: Josh Tynjala<mailto:joshtynj...@bowlerhat.dev>
Sent: Thursday, February 9, 2023 6:24 PM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>
Subject: Re: [DISCUSS] Release Apache flex-sdk-converter-maven-extension 1.1.0 
RC1

I confirm that PlatformTypeTest fails with JDK 17, but works in JDK 8 and
11. The test seems to be using reflection to change a private property in
the JDK to non-final so that it can pretend to be running on a different
platform temporarily. Some quick research turned up that the JDK authors
made things stricter in JDK 12 because doing something like this should not
be encouraged.

This test is broken, but the behavior of flex-sdk-converter-maven-extension
is still correct. I will definitely fix the test for future releases.

Yishay, would you be willing to test `mvn clean install` with JDK 11 so
that we don't need to do a new RC? If you're going to try it with
royale-compiler, you can switch back to JDK 17 for that.

--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Wed, Feb 8, 2023 at 11:10 PM Yishay Weiss  wrote:

> I’m getting this:
>
> C:\dev\apache-flex-sdk-converter-1.1.0>mvn clean install
> Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
> [INFO] Scanning for projects...
> [INFO]
> 
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Apache Flex - SDK-Converter
> [pom]
> [
> (…)
>
> [INFO]  T E S T S
> [INFO] ---
> [INFO] Running
> org.apache.flex.utilities.converter.retrievers.types.PlatformTypeTest
> [ERROR] Tests run: 5, Failures: 0, Errors: 5, Skipped: 0, Time elapsed:
> 0.082 s <<< FAILURE! - in
> org.apache.flex.utilities.converter.retrievers.types.PlatformTypeTest
> [ERROR] [0] IS_OS_WINDOWS, WINDOWS
> (it_detects_the_current_platform_type)(org.apache.flex.utilities.converter.retrievers.types.PlatformTypeTest)
> Time elapsed: 0.009 s  <<< ERROR!
> java.lang.NoSuchFieldException: modifiers
> at
> org.apache.flex.utilities.converter.retrievers.types.PlatformTypeTest.setFinalStatic(PlatformTypeTest.java:74)
> at
> org.apache.flex.utilities.converter.retrievers.types.PlatformTypeTest.setUp(PlatformTypeTest.java:51)
>
> From: Josh Tynjala<mailto:joshtynj...@bowlerhat.dev>
> Sent: Friday, February 3, 2023 6:23 PM
> To: dev@flex.apache.org<mailto:dev@flex.apache.org>
> Subject: Re: [DISCUSS] Release Apache flex-sdk-converter-maven-extension
> 1.1.0 RC1
>
> At minimum, extract the source-release .zip file and run `mvn clean
> install` in the root directory that contains pom.xml.
>
> OPTIONAL: After `mvn clean isntall`, you can also test that it works with
> the royale-compiler repo (be sure to pull the latest commits). Here's what
> you need to do:
>
> (Prerequisite: Make sure that you have the FLASHPLAYER_DEBUGGER env var
> pointing to a Flash Player projector executable. If you don't have this
> executable already, the royale-compiler README explains how you can still
> download it from Adobe.)
>
> 1. In royale-compiler, go into .mvn/extensions.xml and set the version to
> 1.1.0: 1.1.0
> 2. Go into ~/.m2/repository/com/adobe/flash/ and move the "framework"
> directory somewhere else temporarily. This lets you put it back later, if
> something goes wrong.
> 3. In royale-compiler, run `mvn clean install -P option-with-swf`.
>
> If the royale-compiler option-with-swf build passes, then the extension
> successfully installed playerglobal 32.0.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Thu, Feb 2, 2023 at 11:28 PM Harbs  wrote:
>
> > What do I need to do to test this?
> >
> > > On Feb 3, 2023, at 1:15 AM, Josh Tynjala 
> > wrote:
> > >
> > > Hi,
> > >
> > > Please discuss the flex-sdk-converter-maven-extension 1.1.0 release
> > > candidate here and not in the vote thread.
> > >
> > > Thanks,
> > > Josh
> >
> >
>
>

RE: [DISCUSS] Release Apache flex-sdk-converter-maven-extension 1.1.0 RC1

[Yishay Weiss]

I’m getting this:

C:\dev\apache-flex-sdk-converter-1.1.0>mvn clean install
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
[INFO] Scanning for projects...
[INFO] 
[INFO] Reactor Build Order:
[INFO]
[INFO] Apache Flex - SDK-Converter[pom]
[
(…)

[INFO]  T E S T S
[INFO] ---
[INFO] Running 
org.apache.flex.utilities.converter.retrievers.types.PlatformTypeTest
[ERROR] Tests run: 5, Failures: 0, Errors: 5, Skipped: 0, Time elapsed: 0.082 s 
<<< FAILURE! - in 
org.apache.flex.utilities.converter.retrievers.types.PlatformTypeTest
[ERROR] [0] IS_OS_WINDOWS, WINDOWS 
(it_detects_the_current_platform_type)(org.apache.flex.utilities.converter.retrievers.types.PlatformTypeTest)
  Time elapsed: 0.009 s  <<< ERROR!
java.lang.NoSuchFieldException: modifiers
at 
org.apache.flex.utilities.converter.retrievers.types.PlatformTypeTest.setFinalStatic(PlatformTypeTest.java:74)
at 
org.apache.flex.utilities.converter.retrievers.types.PlatformTypeTest.setUp(PlatformTypeTest.java:51)

From: Josh Tynjala
Sent: Friday, February 3, 2023 6:23 PM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] Release Apache flex-sdk-converter-maven-extension 1.1.0 
RC1

At minimum, extract the source-release .zip file and run `mvn clean
install` in the root directory that contains pom.xml.

OPTIONAL: After `mvn clean isntall`, you can also test that it works with
the royale-compiler repo (be sure to pull the latest commits). Here's what
you need to do:

(Prerequisite: Make sure that you have the FLASHPLAYER_DEBUGGER env var
pointing to a Flash Player projector executable. If you don't have this
executable already, the royale-compiler README explains how you can still
download it from Adobe.)

1. In royale-compiler, go into .mvn/extensions.xml and set the version to
1.1.0: 1.1.0
2. Go into ~/.m2/repository/com/adobe/flash/ and move the "framework"
directory somewhere else temporarily. This lets you put it back later, if
something goes wrong.
3. In royale-compiler, run `mvn clean install -P option-with-swf`.

If the royale-compiler option-with-swf build passes, then the extension
successfully installed playerglobal 32.0.

--
Josh Tynjala
Bowler Hat LLC 


On Thu, Feb 2, 2023 at 11:28 PM Harbs  wrote:

> What do I need to do to test this?
>
> > On Feb 3, 2023, at 1:15 AM, Josh Tynjala 
> wrote:
> >
> > Hi,
> >
> > Please discuss the flex-sdk-converter-maven-extension 1.1.0 release
> > candidate here and not in the vote thread.
> >
> > Thanks,
> > Josh
>
>

RE: BlazeDS release

[Yishay Weiss]

Thanks for working on this.

Chris gave some guidelines [2] for the release process.

Maybe the plc4x check-list [1] is helpful?

[1] https://plc4x.apache.org/developers/release/release.html

[2]
The release itself should be the normal Maven release process … you can see in 
the plc4x release documentation on how you need to configure your system:
https://plc4x.apache.org/developers/release/release.html


The short version of a release should be:



mvn release:prepare



mvn elease:perform

And the plc4x documentation describes what has to be done in the nexus repo for 
staging and releasing the maven artifacts.

From: Josh Tynjala
Sent: Tuesday, January 10, 2023 2:03 AM
To: dev@flex.apache.org
Subject: Re: BlazeDS release

Okay, some updates on my progress with BlazeDS.

- I made the necessary changes to remove the vulnerable xalan dependency.
- I looked at the proxy module issue, where we need to replace the obsolete 
commons-httpclient 3.x with its successor, httpcomponents-httpclient 4.x. It 
seems to be non-trivial to upgrade. I'm not sure that we have much test 
coverage either, so there would be a certain amount of risk. I can see why 
Piotr said that we should exclude the proxy module from the release instead. I 
want to do a little bit of testing/investigation to see how much impact 
removing the proxy module might have.
- I moved the OWASP dependency checker into a 'with-owasp' profile. We don't 
want that being a default part of the build because a failing build will be 
confusing for users that want to build from source, if any new CVEs are issued 
in the future. It should be mainly for our CI and release managers instead. It 
can be enabled by adding `-P with-owasp` to the `mvn install` command.
- I replaced the 'flex-ci-build' profile with a new 'with-distribution' 
profile. It builds not only the source distribution, but also a **new** binary 
distribution, which we didn't have before. The binary distribution is identical 
to the source distribution, except that it also has a 'lib' directory that 
contains all of the built .jar files and their required dependencies.
- I merged everything from security-updates into develop. I'll continue any 
further work on develop.

Folks, I need help with one thing: Do we have release manager 
instructions/checklist for BlazeDS? Thanks!

- Josh

On 2023/01/04 20:59:29 Josh Tynjala wrote:
> I'd like to spend some time this month finishing up the recent BlazeDS
> stuff so that we can get it released.
>
> Can someone confirm that the changes listed here are still what should be
> done? It looks straightforward enough.
>
> https://lists.apache.org/thread/9h7th05wc57399jp7l7mj11c45nq8jbn
>
> And which branch should I commit to? security-updates? develop? master?
> Something else?
>
> Thanks,
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>

RE: Retiring the project

[Yishay Weiss]

For what it’s worth, I am aware of several Flex projects that are still in 
production. They are all considering transitioning, but have not yet made the 
decision, or have not finished the transition. I am not aware of new Flex 
projects being created.

From: Csomák Gábor
Sent: Wednesday, June 8, 2022 1:44 PM
To: dev@flex.apache.org
Subject: Re: Retiring the project

Do we have any statistics we can use for data on guiding this discussion?
like download stats, etc?

On Wed, Jun 8, 2022 at 8:35 AM Harbs  wrote:

> That document is for podlings — not for TLPs.
>
> There’s nothing wrong with a project being in maintenance mode as long as
> there’s enough of a PMC active.
>
> I think we still have enough of a PMC to maintain the project and I think
> people are still using Flex.
>
> Harbs
>
> > On Jun 8, 2022, at 8:26 AM, Olaf Krüger  wrote:
> >
> > Hi guys,
> >
> > we should thinking about retiring the project.
> > This seems to be the guideline to retire a project at Apache [1]
> >
> > It looks like we need a community vote and some volunteers who helps
> with the process of retiring a project.
> >
> > What do you think?
> >
> > Thanks,
> > Olaf
> >
> > [1] https://incubator.apache.org/guides/retirement.html
> >
>
>

RE: Board report for June 2022 has been submitted

[Yishay Weiss]

>
## Community Health:
During the last quarter, there was no mailing list activity at dev and nearly
no activity at users.

I would add that questions about Flex have been posted to Royale mailing lists.

From: Olaf Krüger
Sent: Wednesday, June 8, 2022 8:16 AM
To: dev@flex.apache.org
Subject: Board report for June 2022 has been submitted

## Description:
The mission of the Apache Flex project is to create and maintain software
related to the development of expressive web applications that deploy to all
major browsers, desktops and devices (including smartphones, tablets and tv)

## Issues:
There are no issues requiring board attention.

## Membership Data:
Apache Flex was founded 2012-12-19 (9 years ago)
There are currently 68 committers and 45 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.

Community changes, past quarter:
- No new PMC members. Last addition was Olaf Krüger on 2017-08-28.
- No new committers. Last addition was Greg Dove on 2016-09-07.

## Project Activity:
No changes have been made to the Flex framework for a long
time and it is unlikely that another release will appear.
We should think about retiring the project.

## Releases:
- Apache Flex SDK 4.16.1 on 2017-11-25
- Apache Flex Installer 3.3.2 on 2018-07-14.

## Community Health:
During the last quarter, there was no mailing list activity at dev and nearly
no activity at users.

RE: [GitHub] [flex-flexunit] piotrzarzycki21 merged pull request #5: Update README

[Yishay Weiss]

If it’s just to fix a README then I don’t think it needs to go to dev.

From: Piotr Zarzycki
Sent: Monday, April 18, 2022 4:32 PM
To: dev@flex.apache.org
Subject: Re: [GitHub] [flex-flexunit] piotrzarzycki21 merged pull request #5: 
Update README

Maybe I shouldn't approve this for master, but rather to develop ?

pon., 18 kwi 2022 o 15:31 GitBox  napisał(a):

>
> piotrzarzycki21 merged PR #5:
> URL: https://github.com/apache/flex-flexunit/pull/5
>
>
> --
> This is an automated message from the Apache Git Service.
> To respond to the message, please log on to GitHub and use the
> URL above to go to the specific comment.
>
> To unsubscribe, e-mail: dev-unsubscr...@flex.apache.org
>
> For queries about this service, please contact Infrastructure at:
> us...@infra.apache.org
>
>

--

Piotr Zarzycki

RE: How To Debug Flash Apps on Packaged Browser

[Yishay Weiss]

> IIRC, the SWF needs to have been built for debugging.

Forgot about that. I’ll check if it was built that way.

Harman support should be able to provide a debug player for their packaged 
browser, I’ll make sure that’s working as well.

Good to know there are ways around not having a debugger player. This specific 
app does use ExternalInterface though.

Thanks!


From: Alex Harui<mailto:aha...@adobe.com.INVALID>
Sent: Sunday, December 26, 2021 7:17 PM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>
Subject: Re: How To Debug Flash Apps on Packaged Browser

IIRC, the SWF needs to have been built for debugging.  The browser may also 
need to have a debugger version of FlashPlayer installed.

If the SWF does not use ExternalInterface, you can sometimes connect FDB 
without a debugger player by having FDB launch the SWF w/o its HTML wrapper.  
That changes the security model though, so doesn't always work.

On 12/26/21, 3:46 AM, "Yishay Weiss"  wrote:

Hi,

I am trying to connect fdb to a client's packaged browser. I tried simply 
calling run and launching the browser but no success. Any ideas?

Thanks
Yishay

How To Debug Flash Apps on Packaged Browser

[Yishay Weiss]

Hi,

I am trying to connect fdb to a client's packaged browser. I tried simply 
calling run and launching the browser but no success. Any ideas?

Thanks
Yishay

RE: Nabble doesn't work http://apache-flex-users.2333346.n4.nabble.com/

[Yishay Weiss]

I think Alex tried getting Apache to fix it to no avail. Maybe we should remove 
Nabble from our website and retain only ponymail links.

From: Piotr Zarzycki
Sent: Monday, August 2, 2021 11:06 AM
To: dev@flex.apache.org
Subject: Nabble doesn't work http://apache-flex-users.246.n4.nabble.com/

Hi Guys,

One of the user reported me that nabble doesn't work - Do we have any power
over this ?

Thanks,
--

Piotr Zarzycki

RE: Dot Net (C#) Flex Runtime

[Yishay Weiss]

Hi Jason,

Royale was designed to target more than one platform. It currently supports js 
and swf. Have you considered adding .NET as a 3rd target platform?

Thanks,
Yishay

From: Andrew Wetmore
Sent: Thursday, July 15, 2021 3:19 PM
To: dev@flex.apache.org
Subject: Re: Dot Net (C#) Flex Runtime

Hi, Jason:

While the Royale project is fairly active, the Flex project has not been
moving forward of late. Incorporating this interesting initiative into
Apache Flex would give you a structure in which to develop and to which to
attract contributors, and would give the Flex project new life.

I am a doc guy rather than a hard-core developer, but I would be happy to
help document the Dot Net solution.

Andrew


Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Wed, Jul 14, 2021 at 8:03 PM Jason Taylor  wrote:

> Hi Guys, I've struggled with this idea for a long time and finally started
> action on this project.  I experimenting with building a Dot Net version of
> Flex which includes rudimentary flash as well.  Currently I have a bare
> bones working prototype using SKIA as the front end demonstrating the
> concept is doable, but obviously will take a ton of work.I am not
> implementing everything 100% as I'm making some choices on which flash
> features are implemented as well as leveraging some of C# language and
> runtime features, but the idea is most MXML would be able to run with minor
> modification.  I also have an AS3 to C# converter which should assist since
> the C# syntax is very similar to AS3 but far more powerful.
>
> My main motivation for this project is the direction of the current UI
> frameworks that support dot not including WinUI, UNO, Avalonia.   All of
> them don't meet my needs in one way or another including full cross
> platform compatibility, pixel perfect control, and an XML like dialect that
> is clean, simple, and powerful.   If you've ever worked on XAML after
> working on MXML it's crazy how much more complicated simple things are in
> XAML and you still don't get full control of what is rendered.
>
> I have been coding in flash since Flash 6, Flex since it's inception, and
> C# since it's launch and I have developed and maintain what is possibly the
> most complex application ever made in Flex (Dedoose).  The only reason I
> was able to do this is how Flex makes it fast and easy to rapidly develop,
> iterate, expand, and maintain.I have other avenues going at Dedoose to
> make a compatible version of Dedoose in one of those newer frameworks but
> the amount of technical debt we will take on in doing so is something I'm
> not terribly excited about.
>
> While I respect the groups decision with Royale, I believe a Dot Net
> solution could be far more powerful, far easier to develop & maintain.
>
> If anyone is interested in assisting me in this project I will be looking
> for collaborators with experience in flash, flex, and C#, and potentially
> be offering pay for this work.   Please email me directly if interested,
> and if I see interest I'll setup a Discord and we can talk and figure out
> the details.
>
> ~ JT
>


--
Andrew Wetmore

http://cottage14.blogspot.com/

RE: Is Any Browser At All Supporting Flash as of today?

[Yishay Weiss]

This is a better source for wildcard syntax. It turns out that

http://* is not allowed. But

http://*.example.com/ is allowed. A wildcard symbol needs at least 2 specific 
labels following, otherwise it’s considered too permissive.

[1]https://www.adobe.com/content/dam/acom/en/devnet/flashplayer/articles/flash_player_admin_guide/pdf/latest/flash_player_32_0_admin_guide.pdf



From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Tuesday, January 12, 2021 1:09 PM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>
Subject: RE: Is Any Browser At All Supporting Flash as of today?

> The wildcard syntax is explained

Actually the wildcards are not working for me.



From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Tuesday, January 12, 2021 12:13 PM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>
Subject: RE: Is Any Browser At All Supporting Flash as of today?

Thanks.

Following this guide [1] which was in one of Harbs’ links we were able to get 
it working forf FF and Windows

By editing mms.cfg under C:\Windows\SysWOW64\Macromed\Flash and adding the 
following content

EOLUninstallDisable=1
SilentAutoUpdateEnable=0
EnableAllowList=1
AutoUpdateDisable=1
ErrorReportingEnable=1
AllowListUrlPattern=http:*

The wildcard syntax is explained here [2]. Apparently the ports cannot be 
specified in a wildcard.


[1] 
https://blogs.sap.com/2020/12/10/how-to-keep-enterprise-flash-applications-accessible-in-2021/
[2] 
https://avid.secure.force.com/pkb/servlet/fileField?retURL=%2Fpkb%2Farticles%2Fen_US%2FFAQ%2FAvid-video-products-and-FLASH-replacement-for-2020=ka05A01DcvEQAS=Attachment_3__Body__s

From: after24<mailto:vinc...@after24.net>
Sent: Tuesday, January 12, 2021 11:51 AM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>
Subject: RE: Is Any Browser At All Supporting Flash as of today?

Hi yishayw,

Don't sure if it will last but at the moment Firefox *ESR* 52.3.0 still
works for us (flash player 26.0.0.131)

If you want to make a try, you can download specific version of Firefox here
:  https://ftp.mozilla.org/pub/firefox/releases/
<https://ftp.mozilla.org/pub/firefox/releases/>

Vincent.




--
Sent from: http://apache-flex-development.247.n4.nabble.com/

RE: Is Any Browser At All Supporting Flash as of today?

[Yishay Weiss]

> The wildcard syntax is explained

Actually the wildcards are not working for me.



From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Tuesday, January 12, 2021 12:13 PM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>
Subject: RE: Is Any Browser At All Supporting Flash as of today?

Thanks.

Following this guide [1] which was in one of Harbs’ links we were able to get 
it working forf FF and Windows

By editing mms.cfg under C:\Windows\SysWOW64\Macromed\Flash and adding the 
following content

EOLUninstallDisable=1
SilentAutoUpdateEnable=0
EnableAllowList=1
AutoUpdateDisable=1
ErrorReportingEnable=1
AllowListUrlPattern=http:*

The wildcard syntax is explained here [2]. Apparently the ports cannot be 
specified in a wildcard.


[1] 
https://blogs.sap.com/2020/12/10/how-to-keep-enterprise-flash-applications-accessible-in-2021/
[2] 
https://avid.secure.force.com/pkb/servlet/fileField?retURL=%2Fpkb%2Farticles%2Fen_US%2FFAQ%2FAvid-video-products-and-FLASH-replacement-for-2020=ka05A01DcvEQAS=Attachment_3__Body__s

From: after24<mailto:vinc...@after24.net>
Sent: Tuesday, January 12, 2021 11:51 AM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>
Subject: RE: Is Any Browser At All Supporting Flash as of today?

Hi yishayw,

Don't sure if it will last but at the moment Firefox *ESR* 52.3.0 still
works for us (flash player 26.0.0.131)

If you want to make a try, you can download specific version of Firefox here
:  https://ftp.mozilla.org/pub/firefox/releases/
<https://ftp.mozilla.org/pub/firefox/releases/>

Vincent.




--
Sent from: http://apache-flex-development.247.n4.nabble.com/

RE: Is Any Browser At All Supporting Flash as of today?

[Yishay Weiss]

Thanks.

Following this guide [1] which was in one of Harbs’ links we were able to get 
it working forf FF and Windows

By editing mms.cfg under C:\Windows\SysWOW64\Macromed\Flash and adding the 
following content

EOLUninstallDisable=1
SilentAutoUpdateEnable=0
EnableAllowList=1
AutoUpdateDisable=1
ErrorReportingEnable=1
AllowListUrlPattern=http:*

The wildcard syntax is explained here [2]. Apparently the ports cannot be 
specified in a wildcard.


[1] 
https://blogs.sap.com/2020/12/10/how-to-keep-enterprise-flash-applications-accessible-in-2021/
[2] 
https://avid.secure.force.com/pkb/servlet/fileField?retURL=%2Fpkb%2Farticles%2Fen_US%2FFAQ%2FAvid-video-products-and-FLASH-replacement-for-2020=ka05A01DcvEQAS=Attachment_3__Body__s

From: after24
Sent: Tuesday, January 12, 2021 11:51 AM
To: dev@flex.apache.org
Subject: RE: Is Any Browser At All Supporting Flash as of today?

Hi yishayw,

Don't sure if it will last but at the moment Firefox *ESR* 52.3.0 still
works for us (flash player 26.0.0.131)

If you want to make a try, you can download specific version of Firefox here
:  https://ftp.mozilla.org/pub/firefox/releases/


Vincent.




--
Sent from: http://apache-flex-development.247.n4.nabble.com/

RE: Is Any Browser At All Supporting Flash as of today?

[Yishay Weiss]

Thanks, Harbs. I’ll see if there’s some magic there.



From: Harbs<mailto:harbs.li...@gmail.com>
Sent: Tuesday, January 12, 2021 10:27 AM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>
Subject: Re: Is Any Browser At All Supporting Flash as of today?

Some ideas to look into. No idea how well any will work.

- https://ruffle.rs/ <https://ruffle.rs/>
- Use the Flash Player Debugger
- Make a thin AIR wrapper to load the swf.

Here’s a useful-looking article with some more possible suggestions:

https://blogs.sap.com/2020/12/10/how-to-keep-enterprise-flash-applications-accessible-in-2021/
 
<https://blogs.sap.com/2020/12/10/how-to-keep-enterprise-flash-applications-accessible-in-2021/>

> On Jan 12, 2021, at 9:03 AM, Yishay Weiss  wrote:
>
> Hi,
>
> We are in the process of converting a Flex app to Royale. The customer was 
> under the impression that they could afford to give us another few weeks by 
> telling the customers to use an old version of FF, but now they’ve learned 
> that plan is not working.
>
> Any ideas for an emergency workaround?
>
> Thanks.
>
>
>

Is Any Browser At All Supporting Flash as of today?

[Yishay Weiss]

Hi,

We are in the process of converting a Flex app to Royale. The customer was 
under the impression that they could afford to give us another few weeks by 
telling the customers to use an old version of FF, but now they’ve learned that 
plan is not working.

Any ideas for an emergency workaround?

Thanks.

Using Fdb

[Yishay Weiss]

When I try running fdb I get the following message:

C:\Program Files\Adobe\Adobe Flash Builder 4.7 (64 Bit)\sdks\4.6.0\bin>fdb.exe
Error loading: C:\Program Files\Java\jdk1.8.0_261\jre\bin\server\jvm.dll

Does it only run with java 7?

Any help appreciated.

Yishay

RE: Flash builder 4.7

[Yishay Weiss]

Have you seen this link [1]?

[1] 
https://www.adobe.com/products/flash-builder-standard/faq.html#gettingstarted

From: inkong
Sent: Wednesday, August 5, 2020 11:00 AM
To: dev@flex.apache.org
Subject: Flash builder 4.7

Hi, I'm currently maintaining an application built in flex. Currently I'm
using Flah builder 4.6. At some point I need to build a 64 bit for .dmg
package for it to work in the latest OS in mac or also soon in windows. I
tried searching for the Flash builder 4.7 installer but I can no longer find
it. DO you guys have any idea where I can buy or download it? Or possibly
another way on how to build the app in 64 bit? Help is really much
appreciated. Thank you.



--
Sent from: http://apache-flex-development.247.n4.nabble.com/

RE: Royale File Upload

[Yishay Weiss]

Does the emulation example [1] work for you?

[1] 
https://github.com/apache/royale-asjs/blob/develop/examples/mxroyale/FileReference/src/main/royale/FileReference.mxml

From: MikeH
Sent: Friday, May 29, 2020 10:05 PM
To: dev@flex.apache.org
Subject: Royale File Upload

Hi, im trying to convert a Flash Builder(Flex) project into an Apache Royale
project for the web. and im getting stuck over file uploads. I have looked
at the samples using the FileProxy method but keep getting errors. I am
using the new 0.9.7 sdk. My code is below. Any thoughts would be great.

My mxml declaration for FileProxy














My Actionscript: Taken from the sample file:


//called on button click
protected function
select_file_clickHandler(event:org.apache.royale.events.MouseEvent):void{
myBrowser.browse();

}


protected function
FP_ModelChangedHandler(event:org.apache.royale.events.Event):void{
myFileProxy.model.addEventListener("blobChanged", blobChangedHandler);

trace('loading: ' +  myFileProxy.name);
myLoader.load();

}

private function blobChangedHandler(e:org.apache.royale.events.Event):void{
var fileModel:FileModelWithParams = myFileProxy.model as
FileModelWithParams;
fileModel.addEventListener(Event.COMPLETE,onUploadComplete);

fileModelWithParams.setParam("username",my_user_name,fileModel.name);
fileModelWithParams.setParam("visibility_rights",0,fileModel.name);
fileModelWithParams.setParam("userid",67,fileModel.name);


fileUploaderWithResponseData.upload("https://localhost/royale/uploadfile.php;);
}

// Called on upload complete
private function onUploadComplete(event:Event):void {
trace("onUploadComplete: " + event)
}


//Error message in vscode:

TypeError: Failed to execute 'set' on 'FormData': parameter 2 is not of type
'Blob'.
at org.apache.royale.file.beads.FileModelWithParams.setParam (c:\xampp
1.8.1\htdocs\AthenaEportfolioJSVS\bin\js-debug\org\apache\royale\file\beads\FileModelWithParams.js:57:72)
at
components.EportfolioEvidenceTypeSelector.components_EportfolioEvidenceTypeSelector_blobChangedHandler
(c:\xampp
1.8.1\htdocs\AthenaEportfolioJSVS\src\components\EportfolioEvidenceTypeSelector.mxml:247:37)
at
org.apache.royale.file.beads.FileModelWithParams.org.apache.royale.events.EventDispatcher.fireListeners
(c:\xampp
1.8.1\htdocs\AthenaEportfolioJSVS\bin\js-debug\org\apache\royale\events\EventDispatcher.js:117:24)
at Function.goog.events.EventTarget.dispatchEventInternal_ (c:\xampp
1.8.1\htdocs\AthenaEportfolioJSVS\bin\js-debug\library\closure\goog\events\eventtarget.js:382:27)
at
org.apache.royale.file.beads.FileModelWithParams.org.apache.royale.events.EventDispatcher.dispatchEvent
(c:\xampp
1.8.1\htdocs\AthenaEportfolioJSVS\bin\js-debug\org\apache\royale\events\EventDispatcher.js:80:38)
at org.apache.royale.file.beads.FileModelWithParams.set__fileContent
(c:\xampp
1.8.1\htdocs\AthenaEportfolioJSVS\bin\js-debug\org\apache\royale\file\beads\FileModelWithParams.js:67:9)
at org.apache.royale.file.beads.FileLoader.fileLoadHandler (c:\xampp
1.8.1\htdocs\AthenaEportfolioJSVS\bin\js-debug\org\apache\royale\file\beads\FileLoader.js:60:71)
at Function.goog.events.fireListener [as googFireListener] (c:\xampp
1.8.1\htdocs\AthenaEportfolioJSVS\bin\js-debug\library\closure\goog\events\events.js:753:22)
at Object.org.apache.royale.core.ElementWrapper.fireListenerOverride [as
fireListener] (c:\xampp
1.8.1\htdocs\AthenaEportfolioJSVS\bin\js-debug\org\apache\royale\core\ElementWrapper.js:62:52)
at FileReader.goog.events.handleBrowserEvent_ (c:\xampp
1.8.1\htdocs\AthenaEportfolioJSVS\bin\js-debug\library\closure\goog\events\events.js:879:23)



--
Sent from: http://apache-flex-development.247.n4.nabble.com/

RE: Variable Reference

[Yishay Weiss]

I had a look and FlexGlobals.topLevelApplication is an Object in Royale, so 
you’re not obliged to cast it.

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Sunday, May 24, 2020 12:02 PM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>
Subject: RE: Variable Reference

Hi Mike,

That should work. I don’t remember if Flex required you to cast 
FlexGlobals.topLevelApplication to your specific app class, but I think you 
would need to do that in Royale.

Yishay


From: MikeH 
Sent: Friday, May 22, 2020 6:27:23 PM
To: dev@flex.apache.org 
Subject: Variable Reference

Hi I am looking at converting a Flex application over to Royale. In Flex I
can use FlexGlobals.topLevelApplication.myVar to reference data set in the
main application. Does Royale have an equivalent th this?

Thanks
MikeH



--
Sent from: http://apache-flex-development.247.n4.nabble.com/
From: MikeH<mailto:mikehort...@googlemail.com.INVALID>
Sent: Sunday, May 24, 2020 10:01 AM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>
Subject: Variable Reference

Hi I am looking at converting a Flex application over to Royale. In Flex I
can use FlexGlobals.topLevelApplication.myVar to reference data set in the
main application. Does Royale have an equivalent th this?

Thanks
MikeH



--
Sent from: http://apache-flex-development.247.n4.nabble.com/

RE: Variable Reference

[Yishay Weiss]

Hi Mike,

That should work. I don’t remember if Flex required you to cast 
FlexGlobals.topLevelApplication to your specific app class, but I think you 
would need to do that in Royale.

Yishay


From: MikeH 
Sent: Friday, May 22, 2020 6:27:23 PM
To: dev@flex.apache.org 
Subject: Variable Reference

Hi I am looking at converting a Flex application over to Royale. In Flex I
can use FlexGlobals.topLevelApplication.myVar to reference data set in the
main application. Does Royale have an equivalent th this?

Thanks
MikeH



--
Sent from: http://apache-flex-development.247.n4.nabble.com/
From: MikeH
Sent: Sunday, May 24, 2020 10:01 AM
To: dev@flex.apache.org
Subject: Variable Reference

Hi I am looking at converting a Flex application over to Royale. In Flex I
can use FlexGlobals.topLevelApplication.myVar to reference data set in the
main application. Does Royale have an equivalent th this?

Thanks
MikeH



--
Sent from: http://apache-flex-development.247.n4.nabble.com/

RE: MXRoyale question - styleName

[Yishay Weiss]

Yes, I was meaning to respond to that. Our client opened up our POC on his 
default browser, which is IE11, and saw nothing working. It’s still out there.

>It's interesting that in the same month as someone wants modules to work in 
>IE11 we also want to get rid of IE11 support.

On 5/7/20, 2:09 AM, "Greg Dove"  wrote:

Assuming you meant add/remove from classList as you proposed in the first
post, then I think the answer is yes.

yes, that's what I really meant. Ok, I will add that to MXRoyale probably
tomorrow.

Other:
I do expect to be contributing more to MXRoyale over coming weeks/months -
such as mxDataGrid which still needs more work over time.
I also saw different behavior with GridItems inside GridRow recently when
there was no height set for example, it was not being set to full height by
default, so I will look into that at some point (I am often using
workarounds for issues, but noting them as needs attention in Royale - I
don't have time for logging issues for everything with repro at this point).
For styles, yeah I think I saw alternatingColors for datagrid in MXRoyale
is not correctly processed (I think it goes the browser which does not
understand it - and so ignores it).
I am working on a client project with similar justifications for choosing
emulation I know others are looking at emulation as well for the same
reasons.

For people who don't care about IE11, (and I actually had someone from my
client ask me 'why do we care about that?' recently with genuine surprise)
then es6 Proxy would support a lot of 'runtime' emulations I think, which I
mentioned to you previously, so I know you are aware of it. I know at least
for certain browsers that es6 Proxy is very performant in spite of it being
a 'Proxy' approach. I am not thinking about this for now, but really I
think IE11 is the only thing holding us back there. I personally would like
to see us let go of IE11 asap after 1.0 - the more it continues to be
supported, the more it lingers and I do think we should look forward more
rather than back. I think if people want to keep using old IE browsers
internally with its risks etc, then they could probably keep using IE10
just for swf apps (iirc IE10 probably won't, but IE11 will get the
maintenance update that removes flash player at the end of the year if
IE11 did not, then I can't understand why we would continue to support it
for Royale, IMO, it is just holding us back).

anyway... that's off topic. For another time



On Thu, May 7, 2020 at 6:37 PM Alex Harui  wrote:

> Assuming you meant add/remove from classList as you proposed in the first
> post, then I think the answer is yes.  I think that's simple enough to
> emulate and will work most of the time.  I think you have to use classList
> instead of className because there will be other things in the classList.
>
> For MXRoyale/SparkRoyale we are trying to have people change their code as
> little as possible.  We are not trying to set them up for the future.  
IMO,
> if the migrator is willing to change a lot of code then Jewel or Basic
> should be considered.
>
> CSS is already funky in MXRoyale/SparkRoyale.  Flex supported style
> properties that don't exist in the browser (like gap and horizontalCenter,
> IIRC) and width=100% has a completely different meaning.  The emulation
> will eventually watch for certain styles and decide whether to emulate it
> in browser CSS or never set it in the browser and store the values
> elsewhere for use by getStyle calls from other code.  The layouts do the
> latter in most cases.  PercentWidth is never set on the HTMLElement.  The
> old Flex layout code runs and interprets it.
>
> In the end, it should be a collaborative effort for the migrating team and
> the framework team.  Time is running out on 2020 so the main question is
> what will get someone migrated faster?  Emulation is usually faster and
> safer than changing code paths in many places in the application and helps
> others trying to use the emulations.  But some emulations (runtime 
property
> access) are too hard or slow so the application does need to be changed.
>
> HTH,
> -Alex
>
> On 5/6/20, 11:08 PM, "Greg Dove"  wrote:
>
> Thanks Alex, but - as a follow-on, do you think the styleName setter
> should
> set the className if it has a string value assignment? Or should we be
> telling people to manually edit the code/mxml and swap styleName 
string
> value assignments to 'className' value assignments? I think for the
> majority of cases (which I think will be string values), it might be
> good
> to have it 'work by default' and we can add the warnings for
> non-strings,
> like you suggest, 

RE: [Vote] Moving JIRA issues and Confluence Wiki to GitHub

[Yishay Weiss]

+0.



As others, I don’t see a clear benefit. Both tracking systems are solid.



On the other hand, if a member of the community is keen to do something and 
sees some benefit in it I think we shouldn’t stand in his/her way.




From: Olaf Krueger 
Sent: Saturday, January 19, 2019 8:42:42 PM
To: dev@flex.apache.org
Subject: Re: [Vote] Moving JIRA issues and Confluence Wiki to GitHub

+1

In 2018, 15 issues were created by using JIRA.
So I don't expect too many duplicates for the future.
If it is possible, we would set JIRA and the Conflucence Wiki read-only.



--
Sent from: http://apache-flex-development.247.n4.nabble.com/

RE: Flex Old Support

[Yishay Weiss]

Adobe hasn’t dropped AIR but there has been debate [1] over its level of 
commitment to the platform. Anyway, Apache Flex cannot speak for Adobe. I think 
you should inquire in Adobe forums about the roadmap post 2020.



[1] https://forums.adobe.com/thread/2362234?start=240=0




From: Joel Tan 
Sent: Tuesday, December 5, 2017 11:21:59 AM
To: dev@flex.apache.org
Subject: Re: Flex Old Support

Hi Chris,

>> However Adobe have anounced to stop *Flash and Air around 2020*. So for
long term Support, you should think about other alternatives.

You were mentioning about Adobe will stop Flash and AIR around 2020, wasn't
it just Flash player on the browser? AIR will continue to work right?
Because we are planning to move our Flex web app to AIR desktop app, just
want to double confirm is AIR will continue to work after 2020.

Thanks!

Joel



On Tue, Dec 5, 2017 at 2:55 PM, Christofer Dutz 
wrote:

> Hi Manisch,
>
> Even If you should probably direct this question at the Apache flex
> mailinglist. There should be No reason for it to stop working. However
> Adobe have anounced to stop Flash and Air around 2020. So for long term
> Support, you should think about other alternatives.
>
> Chris
>
> Outlook for Android herunterladen
>
>
>
> Von: manish sharma
> Gesendet: Dienstag, 5. Dezember, 07:05
> Betreff: Flex Old Support
> An: flex-...@incubator.apache.org
>
>
> Hi Team, I Have a old project created on Flex SDK 3.5. Do I need to
> upgrade it on Apache Flex or It will be continuing working in future on
> that same SDK? Regards, Manish
>
>

RE: [VOTE] Release Apache Flex SDK Installer 3.3 - RC3

[Yishay Weiss]

 [echo]
 [echo] +1
 [echo] Package 
https://dist.apache.org/repos/dist/dev/flex/installer/3.3/rc3/apache-flex-sdk-installer-3.3.0-src.zip
 [echo] Java 1.8
 [echo] OS: Windows 10 amd64 10.0
 [echo] Source kit signatures match: y
 [echo] Source kit builds: y
 [echo] README is ok: y
 [echo] RELEASE_NOTES is ok: y
 [echo] NOTICE is ok: y
 [echo] LICENSE is ok: y
 [echo] No unapproved licenses or archives: y
 [echo] No unapproved binaries: y

From: Piotr Zarzycki
Sent: Sunday, November 12, 2017 10:50 PM
To: dev@flex.apache.org
Subject: [VOTE] Release Apache Flex SDK Installer 3.3 - RC3

Hi Folks,

This is official thread for Vote to approve Apache Flex SDK Installer
version 3.3 to be released.

It's RC3. Changes:
- Download in Get of Ant on Air library has been switched to use Powershell
on Windows. There is no changes in case of Mac.

This version address fix for one major issue:
- Unable to download Apache Flex SDK with Air greater than 23 - Windows [1]

In order to test issue [1] you have to use Nightly Build of SDK, cause
during work on fix I have discovered that script in SDK which installer is
using was broken [2]. Release process for SDK has been started.

[1] https://issues.apache.org/jira/browse/FLEX-35295
[2] https://issues.apache.org/jira/browse/FLEX-35364

Sources can be found:
*https://dist.apache.org/repos/dist/dev/flex/installer/3.3/rc3/
*

Binary distributions for Windows and Mac:
*https://dist.apache.org/repos/dist/dev/flex/installer/3.3/rc3/binaries/
*

Before voting review ASF requirements:
http://www.apache.org/dev/
http://www.apache.org/legal/release-policy.html#approving-a-release

To use ApproveInstaller.xml script (assuming you have Ant installed) you
have to:
- Create an empty folder
- Download ApproveInstaller.xml into that folder from:
   
*https://dist.apache.org/repos/dist/dev/flex/installer/3.3/rc3/ApproveInstaller.xml
*

- Run: ant -f ApproveInstaller.xml -Drelease.version=3.3 -Drc=3

Vote
[ ] +1 Approve the release
[ ] -1 Veto the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks for your patience and voting so far!,
--

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

RE: [Discuss] Release Apache Flex SDK Installer 3.3 - RC3*

[Yishay Weiss]

When running the ant approve script I get this:

gpg: Can't check signature: No public key

Where can I get the public key?





From: Piotr Zarzycki 
Sent: Sunday, November 12, 2017 10:51:23 PM
To: dev@flex.apache.org
Subject: [Discuss] Release Apache Flex SDK Installer 3.3 - RC3*

Hi,

This is official discuss thread! I need folks who try installer especially
on Windows with Nightly/RC1 Flex SDK.

Thanks,
--

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

RE: [VOTE] Release Apache Flex SDK Installer 3.3 - RC3

[Yishay Weiss]

I’m getting this:



gpg: Can't check signature: No public key



Where can I get the public key?




From: Piotr Zarzycki 
Sent: Sunday, November 12, 2017 10:49:54 PM
To: dev@flex.apache.org
Subject: [VOTE] Release Apache Flex SDK Installer 3.3 - RC3

Hi Folks,

This is official thread for Vote to approve Apache Flex SDK Installer
version 3.3 to be released.

It's RC3. Changes:
- Download in Get of Ant on Air library has been switched to use Powershell
on Windows. There is no changes in case of Mac.

This version address fix for one major issue:
- Unable to download Apache Flex SDK with Air greater than 23 - Windows [1]

In order to test issue [1] you have to use Nightly Build of SDK, cause
during work on fix I have discovered that script in SDK which installer is
using was broken [2]. Release process for SDK has been started.

[1] https://issues.apache.org/jira/browse/FLEX-35295
[2] https://issues.apache.org/jira/browse/FLEX-35364

Sources can be found:
*https://dist.apache.org/repos/dist/dev/flex/installer/3.3/rc3/
*

Binary distributions for Windows and Mac:
*https://dist.apache.org/repos/dist/dev/flex/installer/3.3/rc3/binaries/
*

Before voting review ASF requirements:
http://www.apache.org/dev/
http://www.apache.org/legal/release-policy.html#approving-a-release

To use ApproveInstaller.xml script (assuming you have Ant installed) you
have to:
- Create an empty folder
- Download ApproveInstaller.xml into that folder from:
   
*https://dist.apache.org/repos/dist/dev/flex/installer/3.3/rc3/ApproveInstaller.xml
*

- Run: ant -f ApproveInstaller.xml -Drelease.version=3.3 -Drc=3

Vote
[ ] +1 Approve the release
[ ] -1 Veto the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks for your patience and voting so far!,
--

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

RE: [3/4] git commit: [flex-asjs] [refs/heads/develop] - Allow drag and drop item renderers to be more that simpkle labels.

[Yishay Weiss]

There’s no change in PAYG rules. My guideline was to not add anything 
significant to runtime cost or download size by enhancing the bead. I may have 
missed something, so if there’s a specific line number that you see which is 
adding to either of those please let me know.

We did have a concern regarding elements being swapped In runtime, but that is 
fixed in 95922ad776e39208e3d515bd7a484219779271d1.

Thanks.


From: Justin Mclean
Sent: Friday, September 29, 2017 4:22 AM
To: dev@flex.apache.org
Subject: Re: [3/4] git commit: [flex-asjs] [refs/heads/develop] - Allow drag 
and drop item renderers to be more that simpkle labels.

Hi,

> Possibly. Which part adds overhead in your opinion?

In that it a feature that not all users may use that's being implemented by 
conditional logic so it adds to both run time and possibly size cost. While 
that cost would be small in the past on the Flex list code similar to this has 
been called out as not PAYG and it’s been suggested to move it to a new class. 
It may however be that PAYG is now less strict and that adding new features in 
this way is now acceptable?

Thanks,
Justin

RE: [3/4] git commit: [flex-asjs] [refs/heads/develop] - Allow drag and drop item renderers to be more that simpkle labels.

[Yishay Weiss]

Possibly. Which part adds overhead in your opinion?

From: Justin Mclean
Sent: Wednesday, September 27, 2017 11:59 AM
To: dev@flex.apache.org
Subject: Re: [3/4] git commit: [flex-asjs] [refs/heads/develop] - Allow drag 
and drop item renderers to be more that simpkle labels.

Hi,

This doesn’t look very PAYG to me. Wouldn’t the code be better off in another 
class?

Thanks,
Justin

RE: Royale website and domain registration

[Yishay Weiss]

Personally I think it should be a FlexJS App/Site. It would take longer to have 
something running but if the framework isn’t ready for this kind of thing then 
it’s probably a good idea to delay publishing the site until it is ready.

Frankly, I don’t think we’re in a Royale state right now. There are too many 
bugs. When we have a nice app/site with good layout and some cool functionality 
I’ll feel better about us creating a buzz.


From: Harbs
Sent: Sunday, September 24, 2017 10:37 AM
To: dev@flex.apache.org
Subject: Re: Royale website and domain registration

I’m late to this party, but what’s the advantage of using WordPress for the 
site? Wouldn’t Github Pages be more appropriate? That would allow pull requests 
for folks to improve the site.

Thanks,
Harbs

> On Sep 23, 2017, at 10:27 AM, Carlos Rovira  
> wrote:
>
> Hi Alex, an apache VM with WP will be optimal for sure.
> Better wait as you said, in the meanwhile I'll be working
> in some website design that could serve us whatever we end doing.
>
> 2017-09-23 9:05 GMT+02:00 Alex Harui :
>
>> Yes, their concern is legitimate.
>>
>> Let's be patient and see if there is a practical way to host WP on an
>> Apache server.  Maybe we can get our own VM and put WP on it.  Or maybe
>> we'll have to try that plugin you found.
>>
>> Later,
>> -Alex
>>
>> On 9/22/17, 11:58 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
>> 
>> wrote:
>>
>>> Thanks Erik, for registering the domain.
>>>
>>> I just read the trademarks thread and must say that I understand
>>> completely
>>> about what they are concerned to.
>>> So I was searching for a solution. It seems there's a WP plugin that
>>> allows
>>> to create a static site from a WP site
>>> and as well a WP to Jekyll exporter (thinking in github pages that seems
>>> to
>>> use Jekyll). I never use that and don't know about the workflow once
>>> you'll
>>> go maintenance mode. But I could look at it and see if how it behaves. In
>>> that way I could host my WP
>>> installation where we do work and then export to the real site hosted on
>>> GitHub or in whatever host that would conform
>>> with apache policies. It will complicate things but could be the best
>>> option for us.
>>>
>>>
>>>
>>>
>>>
>>> 2017-09-23 8:13 GMT+02:00 Erik de Bruin :
>>>
 Hi,

 I have just registered the 'royalesdk.org' domain. It will live (for
 now?)
 on my AWS' Route 53 account. Just for now, I've given it a cname record
 to
 point it to:

 royale.codeoscopic.com

 As soon as the contents there move to their final place behind '
 royale.apache.org', I'll change the DNS record accordingly.

 The domain has been payed for for one year, with automatic renewal. I'll
 donate these costs.

 If the domain needs to move to somewhere else, I'll remove the locks and
 provide the code, or take care of the move myself.

 If needed, I can give other folks karma to manage the domain, but that
 would have to be on a person to person basis, as it lives on a
 commercial
 AWS account that I can't give everyone access to.

 Thanks,

 EdB



 On Sat, Sep 23, 2017 at 2:35 AM, OmPrakash Muppirala
 
 wrote:

> On Fri, Sep 22, 2017 at 4:51 PM, Alex Harui >>
> wrote:
>
>> Initial response from trademarks was not encouraging.  Is it
 possible
 for
>> Erik to "own" the domain and redirect it to Carlos's server?  That
 might
>> satisfy Trademarks that we could rescind Carlos's use of that
 domain if
>> Carlos stopped conforming to trademark policy.  Apparently there
 have
> been
>> problems like that for other projects.
>>
>
> That is the best way.  We buy the cool sounding domains and simply
 redirect
> them to royale.apache.org.  There are hosting providers who charge $0
 for
> just hosting.  We will just need to pay for the domain re-registration
> every year.
>
> Thanks,
> Om
>
>
>>
>> Thoughts?
>> -Alex
>>
>> On 9/22/17, 3:04 PM, "Alex Harui"  wrote:
>>
>>> I will verify with Trademarks@.  At the worst it will have to
 redirect
> to
>>> royale.apache.org, so I don't think you have to wait.  It would be
 nice
>> to
>>> have that domain no matter what.
>>>
>>> -Alex
>>>
>>> On 9/22/17, 2:57 PM, "omup...@gmail.com on behalf of OmPrakash
> Muppirala"
>>>  wrote:
>>>
 On Sep 22, 2017 2:22 PM, "Erik de Bruin" 
 wrote:

 How about I grab 'royalesdk.org' and we take 

RE: [VOTE] What should be the new Project Name for Proposed fork of FlexJS?

[Yishay Weiss]

  1.  Bend
  2.  Roayle
  3.  Action

From: Harbs
Sent: Monday, September 18, 2017 10:21 AM
To: dev@flex.apache.org
Subject: Re: [VOTE] What should be the new Project Name for Proposed fork of 
FlexJS?

1. Limber
2. Arise
3. Boja

Harbs

> On Sep 17, 2017, at 10:19 PM, Piotr Zarzycki  
> wrote:
>
> Hi,
>
> In this thread I've gathered list of names proposition for fork of FlexJS
> project.
>
> LIST:
>
> Royale
> Boja
> Strand
> Bead
> Limber
> Boinga
> Braid
> Arise
>
> HOW DO WE VOTE:
> 1) Pick up 3 names from the list and order them from the most favorite
> 2) We will give points for each items in the list which you have choose
> 3) In your list you can propose your own name - others can follow it in
> their lists
>
> EXAMPLE:
> 1) Name1 - 3 points
> 2) Name2 - 2 points
> 3) Name3 - 1 point
>
> WINNER:
> We will pickup winner based on gathered points by one of the name.
>
> The vote will be open until Tuesday September 19, 23:00 UTC
>
> Thanks,
>
> Piotr

RE: Build failed in Jenkins: flex-asjs #2567

[Yishay Weiss]

It fails on  , basically it looks like it’s 
running an example like this [1] and verifying that the label value is correct. 
When running [1] manually it seems to work so to me it looks like the test is 
bad.

[1] https://paste.apache.org/vnDx

From: Harbs
Sent: Monday, September 18, 2017 10:34 AM
To: dev@flex.apache.org
Subject: Re: Build failed in Jenkins: flex-asjs #2567

Alex,

The mustella tests have been failing, and I’m not sure why.

Could you take a look?

Thanks,
Harbs

> On Sep 18, 2017, at 9:27 AM, flex.ci.bui...@gmail.com wrote:
>
> See 
>
> --
> [...truncated 9395 lines...]
>[mxmlc] sorted filename: string/string.js
>[mxmlc] sorted filename: dom/nodetype.js
>[mxmlc] sorted filename: debug/error.js
>[mxmlc] sorted filename: asserts/asserts.js
>[mxmlc] sorted filename: array/array.js
>[mxmlc] sorted filename: labs/useragent/browser.js
>[mxmlc] sorted filename: useragent/useragent.js
>[mxmlc] sorted filename: debug/errorcontext.js
>[mxmlc] sorted filename: string/string.js
>[mxmlc] sorted filename: dom/nodetype.js
>[mxmlc] sorted filename: debug/error.js
>[mxmlc] sorted filename: asserts/asserts.js
>[mxmlc] sorted filename: array/array.js
>[mxmlc] sorted filename: debug/debug.js
>[mxmlc] sorted filename: events/browserevent.js
>[mxmlc] sorted filename: string/string.js
>[mxmlc] sorted filename: dom/nodetype.js
>[mxmlc] sorted filename: debug/error.js
>[mxmlc] sorted filename: asserts/asserts.js
>[mxmlc] sorted filename: debug/entrypointregistry.js
>[mxmlc] sorted filename: string/string.js
>[mxmlc] sorted filename: dom/nodetype.js
>[mxmlc] sorted filename: debug/error.js
>[mxmlc] sorted filename: asserts/asserts.js
>[mxmlc] sorted filename: events/events.js
>[mxmlc] sorted filename: string/string.js
>[mxmlc] sorted filename: dom/nodetype.js
>[mxmlc] sorted filename: debug/error.js
>[mxmlc] sorted filename: asserts/asserts.js
>[mxmlc] sorted filename: disposable/idisposable.js
>[mxmlc] sorted filename: disposable/disposable.js
>[mxmlc] sorted filename: events/eventtarget.js
>[mxmlc] using extern: externs/svg.js
>[mxmlc] using SWC: 
> 
>[mxmlc] using SWC: 
> 
>[mxmlc] using SWC: 
> 
>[mxmlc] using SWC: 
> 
>[mxmlc] using SWC: 
> 
>[mxmlc] using SWC: 
> 
>[mxmlc] using SWC: 
> 
>[mxmlc] using SWC: 
> 
>[mxmlc] using SWC: 
> 
>[mxmlc] using SWC: 
> 
>[mxmlc] using SWC: 
> 
>[mxmlc] using SWC: 
> 
>[mxmlc] using SWC: 
> 
>[mxmlc] using SWC: 
> 
>[mxmlc] using SWC: 
> 
>[mxmlc] using SWC: 
> 
>[mxmlc] using SWC: 
> 
>[mxmlc] using SWC: 
> 
>[mxmlc] using SWC: 
> 
>[mxmlc] using SWC: 
> 
>[mxmlc] using SWC: 
> 

RE: Re: [DISCUSS] Name of the FlexJS Fork

[Yishay Weiss]

> For migration : As a customer, I don't think migration is a real option.

I can’t say I agree with that. The business logic is almost seamlessly ported. 
The UI is more involved but still pretty similar.

Also, most examples one sees these days are using the Basic component set. I 
can envision a component set that will be targeted at migration that will make 
it pretty easy to do, and certainly easier than rewriting in JS/HTML.

I have to say that I don’t see Flex as a liability, but rather Flash. When you 
see these guys acting awkward when you mention Flex it’s probably because 
they’re thinking of Flash. But I haven’t done any market research so it’s 
basically speculation.

RE: [DISCUSS] Name of the FlexJS Fork

[Yishay Weiss]

How is Royale pronounced? Can Americans pronounce it and stay alive? I would go 
with a max 2 syllable word. If it’s Roh-yah-lay, then sorry Carlos, I’d send 
you back to the drawing board.

From: Harbs
Sent: Thursday, September 14, 2017 12:55 PM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] Name of the FlexJS Fork

I agree that for a new name it should just be something unique with a good 
“ring” to it.

Harbs

> On Sep 14, 2017, at 12:49 PM, Olaf Krueger  wrote:
>
> Hi,
> I just would like to mention that it seems to me that there's an inner urge
> inside most of us to leave the beaten paths and to build a new identity for
> FlexJS which is more appropriate to this awesome technology in any respects.
>
> Moreover, it seems to me more and more that such a new shiny identity
> provides a fair chance to get more people involved.
>
> I just fear the effort.
> So thank you, Carlos, for your offer to help out with this!!!
>
> I like "bøje" which is the Danish translation for "bend"
> (I think this was already suggested by Harbs anywhere).
>
> I also like anagrams and words as names that don't exist yet, e.g.:
> Flex -> elfX
>
> However and whatever name, you got me!
>
> Olaf
>
>
>
> --
> Sent from: http://apache-flex-development.247.n4.nabble.com/

RE: [DISCUSS] Name of the FlexJS Fork

[Yishay Weiss]

My main concern was with the JS suffix. If we can create new products without 
the JS suffix that’s fine with me.

On the other hand, if Carlos or someone else feels passionate about a name 
change and volunteers to deal with the overhead I wouldn’t go against it.

From: Alex Harui
Sent: Wednesday, September 13, 2017 6:33 PM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] Name of the FlexJS Fork

Actually, my question was whether the PROJECT name is more or less
important than the PRODUCT name.  Mostly, the board/infra doesn't want us
to change the PROJECT name.  Infra replied that we can create PRODUCTs
with names that do not match the PROJECT name.

So, could we live with the PROJECT being called FlexJS forever?  If we
think we can target a different group of customers with a different
PRODUCT name we can discuss what that name is later.  Now AIUI, if we do
stick with FlexJS as the PROJECT, and later decide to create a PRODUCT
called Foo, I think somewhere on web pages for Foo it will link back
eventually to our source repositories and other pages that have the
PROJECT name "FlexJS" on it and people might go "Huh, I didn't know that
Foo was based on FlexJS".  But will they run away?

I buy lots of foods with brand names that I have no idea who the actual
manufacturer is.  In the US, a fancy brand of cookies (Pepperidge Farm) is
manufactured by the same company that makes cheap condensed soup
(Campbells).  A popular salad dressing is made by a well-known bleach
company (Clorox).  So, I agree with Carlos that it might be worth building
a whole new brand without the word Flex in it, but I think the only
question we need to answer right now is whether the PROJECT name "FlexJS"
will be a hindrance to building that brand.

Thoughts?
-Alex

On 9/13/17, 4:07 AM, "Harbs"  wrote:

>Yes. If we might change the name after forming the new PMC, it’s a
>concern. Alex’s question is more about the framework developing into
>something else in the future. That’s something I don’t think we need to
>be concerned about right now.
>
>I’d rather capitalize on the FlexJS name.
>
>Harbs
>
>> On Sep 13, 2017, at 1:41 PM, Piotr Zarzycki 
>>wrote:
>>
>> I thought that name things was one of the concerns in the thread from
>> board.
>

RE: [VOTE] Fork FlexJS from Apache Flex

[Yishay Weiss]

t and Apache Maven for building the various
release artifacts.

Cryptography

Apache FlexJS does not currently does not distribute cryptography code
other than an MD5 hash algorithm.

Required Resources

Mailing Lists

-private@
-dev@
-commits@
-users@
-issues@

Version Control

We would like to use GitBox if it is practical to convert the current git
repos listed above.  We want to explore using GitHub's wiki and
documentation tools.

Issue Tracking

If GitBox allows us to use GitHub issues, we will use that, otherwise, we
will request a new JIRA project from Infra.

Other Resources

We would like to try using Git for our website version control and
whatever the publishing process is.  We will probably continue to run jobs
on builds.a.o.

Initial PMC

Harbs
Yishay Weiss
Alex Harui
Peter Ent
Josh Tynjala
Piotr Zarzycki
Carlos Rovira
Erik De Bruin
Omprakash Muppirala
Frédéric Thomas
Olaf Krueger
Michael Schmalle
Dave Fisher


Initial Committers

Christofer Dutz
Greg Dove
Andy Dufilie
Darrell Loverin



We propose Harbs as initial PMC Chair and VP Apache FlexJS.

Affiliations

Alex Harui and Peter Ent are currently employees of Adobe Systems Inc.
Nobody else works for a large corporation.

--- End Proposal ---

RE: [FlexJS] Finding (x,y) position

[Yishay Weiss]

This [1] discussion touches on it.

A PAYG approach might be to add PointUtils.getPositionInParent(uibase:UIBase) 
which would do the same thing PointUtils.localToGlobal() for element and parent 
and output the difference.

[1] 
http://apache-flex-development.247.n4.nabble.com/FlexJS-Layouts-td61120.html#a61330

From: Alex Harui<mailto:aha...@adobe.com.INVALID>
Sent: Wednesday, August 30, 2017 7:02 PM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>
Subject: Re: [FlexJS] Finding (x,y) position

Hopefully Peter will find a solution based on your input.  But I think a
problem still exists.

The basic problem is how to find the x,y position of a child within its
parent.  I believe Peter is saying that the x and y getters in UIBase are
not reporting correct values in many cases in the browser.  Apparently,
you can ask for the child.x and child.y of a child that is visibly not at
0,0 in its parent and you will get 0.  I think we haven't noticed that
because nobody currently cares, but it kinds of bugs me that something
that "basic" doesn't do the right thing all of the time.

Thoughts?
-Alex


On 8/30/17, 7:53 AM, "Peter Ent" <p...@adobe.com.INVALID> wrote:

>I'm trying to draw a drop indicator above the row in the DataGrid where
>new data would be inserted if the user releases the mouse button at that
>point.
>
>The drop indicator is being drawn in a layer (added by a new bead) that is
>floating above the  containing the DataGrid's column lists.
>
>As the mouse is detected over an itemRenderer, I need to know the
>itemRenderer's position within its list so I can translate that into
>global space and then into the space of the layer.
>
>However, what you just wrote gave me another idea that might just work.
>
>Thanks!
>—peter
>
>On 8/30/17, 10:30 AM, "Yishay Weiss" <yishayj...@hotmail.com> wrote:
>
>>Strike that. I don’t see what you’re saying. Why not just use 0,0? Why do
>>you need x,y? Or you could add w/2, h/2 if you want to center the drop
>>target.
>>
>>Looking at PointUtils.localToGlobal() it just calls
>>element.getBoundingClientRect() (as you suggested) and adds the given x,y
>>to the result.
>>
>>From: Yishay Weiss<mailto:yishayj...@hotmail.com>
>>Sent: Wednesday, August 30, 2017 5:11 PM
>>To: dev@flex.apache.org<mailto:dev@flex.apache.org>
>>Subject: RE: [FlexJS] Finding (x,y) position
>>
>>I see what you’re saying. I think we worked around that issue in our app
>>by relying on MouseEvent.clientX, MouseEvent.clientY. But let’s hear
>>other ideas for a more complete solution.
>>
>>From: Peter Ent<mailto:p...@adobe.com.INVALID>
>>Sent: Wednesday, August 30, 2017 4:48 PM
>>To: dev@flex.apache.org<mailto:dev@flex.apache.org>
>>Subject: Re: [FlexJS] Finding (x,y) position
>>
>>PointUtils works when it has the correct data. For example, if you are
>>over an itemRenderer, say the first one, and want to get its global
>>location, you might do:
>>
>>var pt0:Point = new Point(itemRenderer.x, itemRenderer.y)
>>
>>and use pt0 in PointUtils.localToGlobal function. The problem is,
>>itemRenderer.x/y are not correct at all times. Because this itemRenderer
>>is the first itemRenderer and in the upper-left corner of its List, you
>>would expect it to be (0,0) but instead it is (0,30) for example where 30
>>is the height of the ButtonBar used for the header.
>>
>>Further, the itemRenderer's parent, a , also has location (0,30) and
>>its parent, again a  is (0,30).
>>
>>This happens because the layout used to place everything is just relying
>>on display:block and none of the s have position set to anything;
>>the
>>only  with position is the one representing the DataGrid itself.
>>
>>The .x and .y functions look at the "left" and "top" styles first.
>>Finding
>>these are not set, the functions then return offsetLeft and offsetTop,
>>which are the offsets from the ancestor with position set. That's the
>> for the DataGrid. Hence they are at (0,30).
>>
>>I see two choices: use getClientBoundingRect or change the layouts to set
>>position:relative on their contentView but this might break something
>>else
>>at some point.
>>
>>I was wondering if anyone had experience trying to figure out screen
>>positions when using the offset properties.
>>
>>
>>‹peter
>>
>>On 8/30/17, 3:02 AM, "Yishay Weiss" <yishayj...@hotmail.com> wrote:
>>
>>>Peter,
>>>
>>>Is PointUtils.localToGlobal() not working for you? From what I
>>>understand
>>>it takes appro

RE: [FlexJS] Finding (x,y) position

[Yishay Weiss]

Strike that. I don’t see what you’re saying. Why not just use 0,0? Why do you 
need x,y? Or you could add w/2, h/2 if you want to center the drop target.

Looking at PointUtils.localToGlobal() it just calls 
element.getBoundingClientRect() (as you suggested) and adds the given x,y to 
the result.

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Wednesday, August 30, 2017 5:11 PM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>
Subject: RE: [FlexJS] Finding (x,y) position

I see what you’re saying. I think we worked around that issue in our app by 
relying on MouseEvent.clientX, MouseEvent.clientY. But let’s hear other ideas 
for a more complete solution.

From: Peter Ent<mailto:p...@adobe.com.INVALID>
Sent: Wednesday, August 30, 2017 4:48 PM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>
Subject: Re: [FlexJS] Finding (x,y) position

PointUtils works when it has the correct data. For example, if you are
over an itemRenderer, say the first one, and want to get its global
location, you might do:

var pt0:Point = new Point(itemRenderer.x, itemRenderer.y)

and use pt0 in PointUtils.localToGlobal function. The problem is,
itemRenderer.x/y are not correct at all times. Because this itemRenderer
is the first itemRenderer and in the upper-left corner of its List, you
would expect it to be (0,0) but instead it is (0,30) for example where 30
is the height of the ButtonBar used for the header.

Further, the itemRenderer's parent, a , also has location (0,30) and
its parent, again a  is (0,30).

This happens because the layout used to place everything is just relying
on display:block and none of the s have position set to anything; the
only  with position is the one representing the DataGrid itself.

The .x and .y functions look at the "left" and "top" styles first. Finding
these are not set, the functions then return offsetLeft and offsetTop,
which are the offsets from the ancestor with position set. That's the
 for the DataGrid. Hence they are at (0,30).

I see two choices: use getClientBoundingRect or change the layouts to set
position:relative on their contentView but this might break something else
at some point.

I was wondering if anyone had experience trying to figure out screen
positions when using the offset properties.


‹peter

On 8/30/17, 3:02 AM, "Yishay Weiss" <yishayj...@hotmail.com> wrote:

>Peter,
>
>Is PointUtils.localToGlobal() not working for you? From what I understand
>it takes approach (1).
>
>From: Peter Ent<mailto:p...@adobe.com.INVALID>
>Sent: Tuesday, August 29, 2017 11:29 PM
>To: dev@flex.apache.org<mailto:dev@flex.apache.org>
>Subject: [FlexJS] Finding (x,y) position
>
>Hi,
>
>While working on drag-and-drop, I've made an "interesting" discovery
>having to do with the HTML-side's x and y getter functions.
>
>Let's say you have a nesting of s:
>
>
>   Š
>
>
> Š
>
>
>
>
>(this structure is similar to what is generated for DataGrid).
>
>If you attempt to get the y location of "first" itemRenderer, you will
>get 30 back as the answer. That happens because the y getter first looks
>to see if the object has a "top" style value and, finding none, returns
>its offsetTop. In this case, offsetTop is 30 and offsetParent is "outer".
>If you get the y value of "inner" you will also get 30 as the answer for
>the same reason.
>
>If each of the s had position:relative (or absolute), then offsetTop
>would be as you would expect with each offsetParent being the  above
>it.
>
>Our layout functions (and x and y setters) do not normally set the
>position style on element. I removed this a good while ago. Now I am
>trying to place a drop target indicator and to do that I need accurate
>(x,y) locations.
>
>I have a couple of solutions:
>
>
>  1.  For any element, look at its getBoundingClientRect and compare with
>its elementParent.getBoundingClientRect. The difference between then
>gives the child's position relative to the parent. This seems reliable.
>  2.  Attempt to divine a child's position using the offset information.
>I can't make this work.
>  3.  Modify the layouts to check the contentView's value of position and
>if not set already, set it to "relative". This makes the x and y getters
>return the right thing but may have unintended consequences.
>
>Any advice from seasoned JavaScript developers is greatly appreciated!
>
>Thanks,
>Peter
>

RE: [FlexJS] Finding (x,y) position

[Yishay Weiss]

I see what you’re saying. I think we worked around that issue in our app by 
relying on MouseEvent.clientX, MouseEvent.clientY. But let’s hear other ideas 
for a more complete solution.

From: Peter Ent<mailto:p...@adobe.com.INVALID>
Sent: Wednesday, August 30, 2017 4:48 PM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>
Subject: Re: [FlexJS] Finding (x,y) position

PointUtils works when it has the correct data. For example, if you are
over an itemRenderer, say the first one, and want to get its global
location, you might do:

var pt0:Point = new Point(itemRenderer.x, itemRenderer.y)

and use pt0 in PointUtils.localToGlobal function. The problem is,
itemRenderer.x/y are not correct at all times. Because this itemRenderer
is the first itemRenderer and in the upper-left corner of its List, you
would expect it to be (0,0) but instead it is (0,30) for example where 30
is the height of the ButtonBar used for the header.

Further, the itemRenderer's parent, a , also has location (0,30) and
its parent, again a  is (0,30).

This happens because the layout used to place everything is just relying
on display:block and none of the s have position set to anything; the
only  with position is the one representing the DataGrid itself.

The .x and .y functions look at the "left" and "top" styles first. Finding
these are not set, the functions then return offsetLeft and offsetTop,
which are the offsets from the ancestor with position set. That's the
 for the DataGrid. Hence they are at (0,30).

I see two choices: use getClientBoundingRect or change the layouts to set
position:relative on their contentView but this might break something else
at some point.

I was wondering if anyone had experience trying to figure out screen
positions when using the offset properties.


‹peter

On 8/30/17, 3:02 AM, "Yishay Weiss" <yishayj...@hotmail.com> wrote:

>Peter,
>
>Is PointUtils.localToGlobal() not working for you? From what I understand
>it takes approach (1).
>
>From: Peter Ent<mailto:p...@adobe.com.INVALID>
>Sent: Tuesday, August 29, 2017 11:29 PM
>To: dev@flex.apache.org<mailto:dev@flex.apache.org>
>Subject: [FlexJS] Finding (x,y) position
>
>Hi,
>
>While working on drag-and-drop, I've made an "interesting" discovery
>having to do with the HTML-side's x and y getter functions.
>
>Let's say you have a nesting of s:
>
>
>   Š
>
>
> Š
>
>
>
>
>(this structure is similar to what is generated for DataGrid).
>
>If you attempt to get the y location of "first" itemRenderer, you will
>get 30 back as the answer. That happens because the y getter first looks
>to see if the object has a "top" style value and, finding none, returns
>its offsetTop. In this case, offsetTop is 30 and offsetParent is "outer".
>If you get the y value of "inner" you will also get 30 as the answer for
>the same reason.
>
>If each of the s had position:relative (or absolute), then offsetTop
>would be as you would expect with each offsetParent being the  above
>it.
>
>Our layout functions (and x and y setters) do not normally set the
>position style on element. I removed this a good while ago. Now I am
>trying to place a drop target indicator and to do that I need accurate
>(x,y) locations.
>
>I have a couple of solutions:
>
>
>  1.  For any element, look at its getBoundingClientRect and compare with
>its elementParent.getBoundingClientRect. The difference between then
>gives the child's position relative to the parent. This seems reliable.
>  2.  Attempt to divine a child's position using the offset information.
>I can't make this work.
>  3.  Modify the layouts to check the contentView's value of position and
>if not set already, set it to "relative". This makes the x and y getters
>return the right thing but may have unintended consequences.
>
>Any advice from seasoned JavaScript developers is greatly appreciated!
>
>Thanks,
>Peter
>

RE: [FlexJS] Finding (x,y) position

[Yishay Weiss]

Peter,

Is PointUtils.localToGlobal() not working for you? From what I understand it 
takes approach (1).

From: Peter Ent
Sent: Tuesday, August 29, 2017 11:29 PM
To: dev@flex.apache.org
Subject: [FlexJS] Finding (x,y) position

Hi,

While working on drag-and-drop, I've made an "interesting" discovery having to 
do with the HTML-side's x and y getter functions.

Let's say you have a nesting of s:


   …


 …




(this structure is similar to what is generated for DataGrid).

If you attempt to get the y location of "first" itemRenderer, you will get 30 
back as the answer. That happens because the y getter first looks to see if the 
object has a "top" style value and, finding none, returns its offsetTop. In 
this case, offsetTop is 30 and offsetParent is "outer". If you get the y value 
of "inner" you will also get 30 as the answer for the same reason.

If each of the s had position:relative (or absolute), then offsetTop would 
be as you would expect with each offsetParent being the  above it.

Our layout functions (and x and y setters) do not normally set the position 
style on element. I removed this a good while ago. Now I am trying to place a 
drop target indicator and to do that I need accurate (x,y) locations.

I have a couple of solutions:


  1.  For any element, look at its getBoundingClientRect and compare with its 
elementParent.getBoundingClientRect. The difference between then gives the 
child's position relative to the parent. This seems reliable.
  2.  Attempt to divine a child's position using the offset information. I 
can't make this work.
  3.  Modify the layouts to check the contentView's value of position and if 
not set already, set it to "relative". This makes the x and y getters return 
the right thing but may have unintended consequences.

Any advice from seasoned JavaScript developers is greatly appreciated!

Thanks,
Peter

RE: FlexJS Bead dilemma

[Yishay Weiss]

But you would need to override all these calls (or remove the layout bead from 
CSS)

addBead(new (ValuesManager.valuesImpl.getValue(this, 
"iBeadLayout")) as IBead);

You wouldn’t need to if the wrapper was in itself an IBeadLayout, but then it 
would have to remove itself before adding its wrapped bead.

To me it seems the main mode of communication between beads should be 
notifications. Another thing that might work here is to create a 
CheckForVisibleBeforeLayoutBead which would be added before the layout bead. It 
would listen on ‘layoutNeeded’  and stopImmediatePropagation() unless the host 
is visible.

From: Alex Harui<mailto:aha...@adobe.com.INVALID>
Sent: Tuesday, August 8, 2017 8:55 AM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>
Subject: Re: FlexJS Bead dilemma

I was thinking the wrapper would just wait for the show event then set the
strand on the actual layout bead.  I'm not sure how much actually would
need to be proxied or forwarded in that case.  Or maybe the wrapper could
just put the actual layout bead on the strand.

Just tossing ideas around...
-Alex

On 8/7/17, 10:47 PM, "Yishay Weiss" <yishayj...@hotmail.com> wrote:

>That would make it a pretty thick wrapper. It would have to dispatch all
>the events that layout beads expect ,and implement ILayoutChild and
>ILayoutParent. Have a look at LayoutBase to see the dependencies on the
>strand  assumed by most layouts (and there are probably more in the
>concrete classes).
>
>
>Adding a meager LayoutOnShow bead seems cleaner to me.
>
>
>From: Alex Harui <aha...@adobe.com.INVALID>
>Sent: Monday, August 7, 2017 6:58:29 PM
>To: dev@flex.apache.org
>Subject: Re: FlexJS Bead dilemma
>
>
>  
>
>   
>
>  
>
>A bead could have a property which is another bead.
>
>Of course, I could be wrong...
>-Alex
>
>On 8/7/17, 11:13 AM, "yishayw" <yishayj...@hotmail.com> wrote:
>
>>Alex Harui-2 wrote
>>> A fancier alternative would be a bead that wraps a layout bead and adds
>>> the visible check.  That might be the best way to apply PAYG.
>>
>>Can you explain what you mean? How would you wrap a bead?
>>
>>
>>
>>
>>--
>>View this message in context:
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fl
>>e
>>x-development.247.n4.nabble.com%2FFlexJS-Bead-dilemma-tp63681p63726.h
>>t
>>ml=02%7C01%7C%7C4491569503864889292108d4ddc03a7b%7Cfa7b1b5a7b3443879
>>4
>>aed2c178decee1%7C0%7C0%7C636377265065337580=XfcOsF4uBbpuF9DW2Mt%2Fu
>>5
>>zxSJYQth3mYyAwjLWJ88s%3D=0
>>Sent from the Apache Flex Development mailing list archive at Nabble.com.
>

Re: FlexJS Bead dilemma

[Yishay Weiss]

That would make it a pretty thick wrapper. It would have to dispatch all the 
events that layout beads expect ,and implement ILayoutChild and ILayoutParent. 
Have a look at LayoutBase to see the dependencies on the strand  assumed by 
most layouts (and there are probably more in the concrete classes).


Adding a meager LayoutOnShow bead seems cleaner to me.


From: Alex Harui 
Sent: Monday, August 7, 2017 6:58:29 PM
To: dev@flex.apache.org
Subject: Re: FlexJS Bead dilemma


  

   

  

A bead could have a property which is another bead.

Of course, I could be wrong...
-Alex

On 8/7/17, 11:13 AM, "yishayw"  wrote:

>Alex Harui-2 wrote
>> A fancier alternative would be a bead that wraps a layout bead and adds
>> the visible check.  That might be the best way to apply PAYG.
>
>Can you explain what you mean? How would you wrap a bead?
>
>
>
>
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-Bead-dilemma-tp63681p63726.ht
>ml=02%7C01%7C%7C4491569503864889292108d4ddc03a7b%7Cfa7b1b5a7b34438794
>aed2c178decee1%7C0%7C0%7C636377265065337580=XfcOsF4uBbpuF9DW2Mt%2Fu5
>zxSJYQth3mYyAwjLWJ88s%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: FlexJS Bead dilemma

[Yishay Weiss]

>The bead is probably more PAYG, but it’s also more “pay” when you do go. 
>Changing bead >notifications would probably make it cheaper though.

That’s a major point in my opinion. If we knew the cost of dispatching a 
notification was next to nothing we would be able to provide lots of hooks, and 
PAYG would become much simpler. A  heavy notification sort of beats the purpose 
because of the performance overhead.

>unnecessary layouts), but not do #2. The question I have is whether to add the 
>LayoutOnShow >bead to the defaults for Basic, or should that only go into 
>Express?

I would add it to express. There might be basic apps without any invisible 
components.



>Harbs

> On Aug 3, 2017, at 11:57 PM, Harbs  wrote:
>
> My ideas on bead lifecycles might help for this. Not sure.
>
> I’m not sure there’s a perfect solution to this problem.
>
> If I have to weigh a single check for visible vs an entire layout, I’d go for 
> the former.
>
> I seem to recall that we did something to prevent non-visible components for 
> going throw layout, but I don’t remember any details. Maybe Yishay knows what 
> I’m talking about.
>
>> On Aug 3, 2017, at 7:18 PM, Alex Harui  wrote:
>>
>> Yeah, but I also remembered on other thing.  The vast majority of
>> components are never made invisible, so adding a check in each layout bead
>> just-in-case they are made invisible isn't very PAYG.
>>
>> So maybe there is some other way that setting visible=false can inject
>> code that handles sharing the CSS display property with the layouts.  Or
>> maybe it isn't worth worrying about right now.
>>
>> My 2 cents,
>> -Alex
>>
>> On 8/3/17, 8:50 AM, "Harbs"  wrote:
>>
>>> But it it doesn’t set display, we’re going to have to run layout every
>>> time the visibility changes.
>>>
>>> I’ve already made my changes. I’ll commit soon.
>>>
>>> Ah. I see what you mean. By doing it your way, there’s no reason to
>>> actually run layout until (or if) the visibility is set to true.
>>>
>>> That probably *is* better. I’ll commit what I did for now, because it at
>>> least fixes the bug, and when I have time, I’ll look into improving the
>>> layouts.
>>>
>>> Another thought:
>>>
>>> If visibility is turned on and off multiple times, this might be less
>>> efficient, but the layout might be able to store a flag to avoid running
>>> the layout if not needed…
>>>
>>> Harbs
>>>
 On Aug 3, 2017, at 6:24 PM, Alex Harui  wrote:

 Right, so layout code would have to check for display=="none" and not
 set
 display and listen for the show event.

 Maybe as you clean up the setting of display multiple times it will be
 come clear as to whether listening for "show" is cheaper/cleaner than
 displayStyleForLayout.

 -Alex

 On 8/3/17, 8:18 AM, "Harbs"  wrote:

> The problem is that visible is set before the bead exists.
>
> BTW, Some of the layout seem to be reading and setting display multiple
> times. That can cause layout thrashing. That should probably be
> resolved.
>
>> On Aug 3, 2017, at 6:05 PM, Alex Harui 
>> wrote:
>>
>> FWIW, I'm not sure this is the best pattern.  It was what we did to
>> get
>> the examples to run.
>>
>> Another option is that layout beads listen for changes to visible and
>> reset the CSS display style when visible changes.
>>
>> Food for thought,
>> -Alex
>>
>> On 8/3/17, 8:00 AM, "Harbs"  wrote:
>>
>>> I’m using a VerticalFlexLayout in a component. Under certain
>>> circumstances, I need to set the visibility of the component to
>>> false.
>>>
>>> These two settings are contradictory in JS.
>>>
>>> visible=false sets display to none
>>> VerticalFlexLayout sets the display to flex
>>>
>>> When setting visible to false, it uses a property
>>> “displayStyleForLayout”
>>> to store the value set by the layout. The problem is that the layout
>>> might be applied AFTER visible is already set to false (which is the
>>> case
>>> in my situation).
>>>
>>> I’m thinking of solving this by exposing displayStyleForLayout so it
>>> can
>>> be set by beads if necessary.
>>>
>>> Scratch that. I see that already exists. Problem solved… I’ll fix the
>>> layouts.
>>>
>>> Harbs
>>
>

>>>
>>
>

RE: [FlexJS, MDL] Menu with dataProvider and itemRenderer API

[Yishay Weiss]

I don’t think those lines would be enough for all MDL controls. We’re only 
using a subset.

From: piotrz
Sent: Wednesday, August 2, 2017 2:02 PM
To: dev@flex.apache.org
Subject: RE: [FlexJS, MDL] Menu with dataProvider and itemRenderer API

Yishay,

I think I will create jira and add those css to MDL in order to get rid off
that ugly line with exclusion.

Anyone seeing some danger doing that ?

Thanks,
Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Menu-with-dataProvider-and-itemRenderer-API-tp57637p63659.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: [FlexJS, MDL] Menu with dataProvider and itemRenderer API

[Yishay Weiss]

Good catch. You’re correct that we’re not using 
-compiler.exclude-defaults-css-files anywhere.

We have some CSS overrides that take care of the controls we’re using. 
Generally, we just inspect the DOM and figure out which styles need to be fixed 
and add those to our CSS. Hopefully, this won’t be necessary when the good 
looking basic look is ready.

.mdl-checkbox__label
{
font-size: 12px;
}

.mdl-slider
{
margin: 0px;
}

.mdl-textfield{
padding: 0px;
}

.mdl-button:hover{
padding: 0 16px;
border: none;
background-color: rgba(158,158,158,.2);
}

.mdl-slider__background-flex
{
margin: 0px;

/*width: calc(100% - 12px);*/
}

From: piotrz
Sent: Wednesday, August 2, 2017 1:11 AM
To: dev@flex.apache.org
Subject: RE: [FlexJS, MDL] Menu with dataProvider and itemRenderer API

Hi Yishay,

I've analyzed your stacktrace and I think I understand why it is working in
your app and it is not in MDLExample.

As I remember from Harbs presentation from ApacheCON that your app is using
MDL library along with Basic module.

In general when someone would like to build your application using MDL
module you have to exclude default.css from Basic, cause UI is breaking up
if we will not do this.

-compiler.exclude-defaults-css-files=Basic-0.9.0-SNAPSHOT-js.swc:defaults.css

Since you probably do not have above line anywhere in your application your
list has following bead:

IBeadController:
ClassReference("org.apache.flex.html.beads.controllers.ListSingleSelectionMouseController");

Above bead emits "change" event, cause it listens to emitted by each item
click provided by bead

IBeadController:
ClassReference("org.apache.flex.html.beads.controllers.ItemRendererMouseController");

I just pushed fix for this issue, but it would be great if you could
describe in separate thread how did you combined MDL library with Basic in
your app without excluding defaults.css.

Thanks,
Piotr





-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Menu-with-dataProvider-and-itemRenderer-API-tp57637p63639.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: MDL and Material Components Web (was Re: Help with 0.8)

[Yishay Weiss]

Maybe slightly off topic but I would love for an ambitious soul to skin a nice 
default FlexJS look and feel. I would be glad to help with that, but we need 
someone (else) to come up with a good graphic design.

From: piotrz
Sent: Thursday, July 27, 2017 9:12 AM
To: dev@flex.apache.org
Subject: Re: MDL and Material Components Web (was Re: Help with 0.8)

Hah Harbs! That ambitious soul thinking about it every day :)
Wish someone could give me time for this one <3 :)

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/Help-with-0-8-tp63568p63583.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: [FlexJS, MDL] Menu with dataProvider and itemRenderer API

[Yishay Weiss]

Is the example I posted on JIRA working for you?

From: piotrz
Sent: Thursday, July 27, 2017 9:00 AM
To: dev@flex.apache.org
Subject: RE: [FlexJS, MDL] Menu with dataProvider and itemRenderer API

I'm thinking about it more and despite that is working for you I think
something is evidently  wrong.

Maybe I have to produce in the MenuView change event. Currently after attach
your ItemRendererMouseController we have click on each renderer.

On the other hand this "change" for some reason do not suit for me to that
control...

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Menu-with-dataProvider-and-itemRenderer-API-tp57637p63581.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: [FlexJS, MDL] Menu with dataProvider and itemRenderer API

[Yishay Weiss]

Piotr, sorry for the confusion, I’m not reverting my change. After it, I am 
getting the ‘change’ event, no need for an ‘itemClicked’ event which, is Alex 
had proposed, would be confusing for other input methods. I fixed the visual 
confusion.

I assigned you a JIRA [1] regarding the example, thanks.

[1] https://issues.apache.org/jira/browse/FLEX-35344

From: piotrz
Sent: Wednesday, July 26, 2017 11:48 AM
To: dev@flex.apache.org
Subject: RE: [FlexJS, MDL] Menu with dataProvider and itemRenderer API

Ahh...I didn't understand you then. I thought it is all about click - I
thought that you do not getting "change" event which is suppose to be
reaction on click on item. If I think about it more it could confuse user:
"change" -> "click", but we are using such model in more places, that change
is a representation of more general approach.

Sometimes is "click" in the other places is selectedItem (MDL DropDownList)
etc. Do you see some component in Basic where we are using "itemClick" event
and expose it to the user ?

Thanks,
Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Menu-with-dataProvider-and-itemRenderer-API-tp57637p63555.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: [FlexJS, MDL] Menu with dataProvider and itemRenderer API

[Yishay Weiss]

Piotr, after thinking about it, I’m reverting the change. I don’t think it’s 
right for a menu to have a selected item, and it causes visual confusion the 
next time it appears. It’s probably best to just propagate the ‘itemClicked’ 
event with some info on the item renderer data.

From: piotrz
Sent: Wednesday, July 26, 2017 10:30 AM
To: dev@flex.apache.org
Subject: Re: [FlexJS, MDL] Menu with dataProvider and itemRenderer API

Yishay,

I did quick look into this problem and not sure what is happening yet.
Please raise jira for me where you describe that your code in the example is
working, but this one in MDLExample not.

I will look into that soon.

Thanks,
Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Menu-with-dataProvider-and-itemRenderer-API-tp57637p63553.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: [FlexJS] String.match()

[Yishay Weiss]

Good catch. I was misled by the docs [1].

[1] 
http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/String.html#match()

From: Harbs
Sent: Thursday, July 20, 2017 9:40 AM
To: dev@flex.apache.org
Subject: Re: [FlexJS] String.match()

Both Flash and JS engines automatically convert to RegExp. I had not realized 
that at first.

It seems that the only difference between the Flash engine and JS engines is 
what happens when constructing a RegExp object from invalid input. Flash 
matches nothing, while JS throws an error.

By just wrapping the call in a try/catch, that seems to resolve the issue.

I added the trace because I think it’s bad practice to use strings instead of 
RegExp because it can lead to unexpected results and a new RegExp instance 
needs to be constructed every time.

> On Jul 20, 2017, at 3:32 AM, Alex Harui  wrote:
>
> It looks like they just trace a warning instead of trying to convert to a
> RegExp.  Is that what we want to do?  Or should we add code that converts
> a string to regex?
>
> Thoughts?
> -Alex
>
> On 7/19/17, 4:32 AM, "Harbs"  wrote:
>
>> I added the utility functions. I think they can be very simple.
>>
>>> On Jul 19, 2017, at 9:30 AM, Alex Harui 
>>> wrote:
>>>
>>> Unless we are absolutely sure that everybody will need the code
>>> generated
>>> by the compiler, having the compiler call a framework function makes it
>>> easier for an app developer to make any adjustments to that code.  It is
>>> easier to monkey-patch a utility function than find-and-replace some
>>> sequence of code the compiler has sprinkled throughout the output.
>>>
>>> My 2 cents,
>>> -Alex
>>>
>>> On 7/18/17, 11:36 AM, "yishayw"  wrote:
>>>
 Alex Harui-2 wrote
> By
> calling new utility functions, the developer has control over the
> conversion.

 I don't understand that point. Do you mean an app developer?




 --
 View this message in context:

 https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-f
 le

 x-development.247.n4.nabble.com%2FFlexJS-String-match-tp63392p63405.
 ht

 ml=02%7C01%7C%7C9ff1088402ef439ca27908d4ce0e97eb%7Cfa7b1b5a7b344387
 94

 aed2c178decee1%7C0%7C0%7C636360009448210304=nprl9yHUtlsTHbIZxeFq2h
 %2
 FQNWmtimM%2BxAt0kJA8EcA%3D=0
 Sent from the Apache Flex Development mailing list archive at
 Nabble.com.
>>>
>>
>

RE: [FlexJS] findPopupHost issue

[Yishay Weiss]

Even if the Application instance isn’t an IPopUpHost the method will just 
return null, so the effect is the same as just doing (appInstance as 
IPopUpHost). I suspect the method is being misused rather than there being a 
problem with the method.

From: Alex Harui
Sent: Tuesday, July 18, 2017 8:33 AM
To: dev@flex.apache.org
Subject: Re: [FlexJS] findPopupHost issue

FWIW, it may not be safe to assume that Application will always be an
IPopUpHost, hence the utility function.

Thanks,
-Alex

On 7/17/17, 9:59 PM, "piotrz"  wrote:

>Hi Yishay,
>
>That's a good point - Application is itself an IPopupHost. I've asked him
>what is the use case for his host popup search.
>
>Thanks,
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-findPopupHost-issue-tp63362p6
>3366.html=02%7C01%7C%7Cbfd19d2deba646c64df208d4cd9c9798%7Cfa7b1b5a7b3
>4438794aed2c178decee1%7C0%7C0%7C636359519816386890=CyeQuoJ0gVVl2UHUB
>W%2B6hbyDNw%2FOSFuswfzeLTqUf3c%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: [FlexJS] findPopupHost issue

[Yishay Weiss]

I think there’s confusion over what a popup host is. A popup host is where you 
would add an IPopUp. UIUtils.findPopUpHost(myComp as IUIBase) finds the closest 
ancestor for myComp to which a popup can be added. These lines from 
ComboBoxView demonstrate the usage:

   var popupHost:IPopUpHost = 
UIUtils.findPopUpHost(_strand as IUIBase);
   popupHost.addElement(list);

Regarding Prashant’s issue, an application is usually in itself an IPopUpHost 
so there’s no need to use that function on an app.

From: piotrz
Sent: Tuesday, July 18, 2017 7:31 AM
To: dev@flex.apache.org
Subject: [FlexJS] findPopupHost issue

Hi Team,

Prashant on users list raised an issue with UIUtils.findPopUpHost(this as
IUIBase) [1]. I did quick look into that and I think we should have in
findPopUpHost(start:IPopupHost) instead findPopUpHost(start:IUIBase) or Am I
miss something ?

[1]
http://apache-flex-users.246.n4.nabble.com/FlexJS-findPopUpHost-Issue-td15474.html

Thanks,
Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-findPopupHost-issue-tp63362.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: [Falcon] operand stack underflow?

[Yishay Weiss]

This [1] is what I get when building DataBindingExample. Says build is 
successful but the following message suggests it is not:

[mxmlc] Exception in thread "main" java.lang.AssertionError: Unsupported 
property value: 1px solid #808080scanning for overrides: IUIBase

[1] https://paste.apache.org/STWV

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Monday, July 17, 2017 4:24 PM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>
Subject: RE: [Falcon] operand stack underflow?

I’m actually able to build after running the following batch file:

cd \dev\flexjs\flex-falcon
git pull
call ant wipe-all
cd \dev\flexjs\flex-typedefs
call ant wipe
git pull
cd \dev\flexjs\flex-asjs
call ant super-clean
git pull
ant clean all


I am however getting a runtime error because of the following line in 
PortedPrintUI.js:

function() {this["border"] = ;

Which probably comes from basic -> defaults.css:

Button
{
   background-color: #f8f8f8;
   border: 1px solid #808080;
   border-radius: 2px;
   padding: 4px;
   margin: 0px;
}

I’ll try to create a simple test case.

From: Harbs<mailto:harbs.li...@gmail.com>
Sent: Monday, July 17, 2017 3:09 PM
To: dev<mailto:dev@flex.apache.org>
Subject: [Falcon] operand stack underflow?

I just updated flex-falcon and flex-asjs. After rebuilding everything, I’m 
getting the following error when compiling my app:

https://paste.apache.org/3wBr <https://paste.apache.org/3wBr>

This is a new one for me…

Suggestions?

Harbs

RE: [Falcon] operand stack underflow?

[Yishay Weiss]

I’m actually able to build after running the following batch file:

cd \dev\flexjs\flex-falcon
git pull
call ant wipe-all
cd \dev\flexjs\flex-typedefs
call ant wipe
git pull
cd \dev\flexjs\flex-asjs
call ant super-clean
git pull
ant clean all


I am however getting a runtime error because of the following line in 
PortedPrintUI.js:

function() {this["border"] = ;

Which probably comes from basic -> defaults.css:

Button
{
   background-color: #f8f8f8;
   border: 1px solid #808080;
   border-radius: 2px;
   padding: 4px;
   margin: 0px;
}

I’ll try to create a simple test case.

From: Harbs
Sent: Monday, July 17, 2017 3:09 PM
To: dev
Subject: [Falcon] operand stack underflow?

I just updated flex-falcon and flex-asjs. After rebuilding everything, I’m 
getting the following error when compiling my app:

https://paste.apache.org/3wBr 

This is a new one for me…

Suggestions?

Harbs

RE: FYI: React appears to be a no-no

[Yishay Weiss]

Does that rule out a reactjs component set (ala createjs)?

From: Harbs
Sent: Monday, July 17, 2017 12:47 PM
To: dev@flex.apache.org
Subject: Re: FYI: React appears to be a no-no

No.

I just thought this was newsworthy.

> On Jul 17, 2017, at 10:27 AM, Alex Harui  wrote:
>
> I"m not following.  Do we currently have a required dependency on React?
>
> -Alex
>
> On 7/16/17, 6:19 AM, "Harbs"  wrote:
>
>> The incompatibility of React’s license is potentially significant for
>> FlexJS.[1]
>>
>> [1]https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues
>> .apache.org%2Fjira%2Fbrowse%2FLEGAL-319=02%7C01%7C%7C4c6a9d8c95534e63
>> 772208d4cc4d45db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636358079641
>> 383681=Ag6aXVH9z9XDazv6hpTakzzcNA%2BdIUBrCS1sYTLGTho%3D=0
>> > pache.org%2Fjira%2Fbrowse%2FLEGAL-319=02%7C01%7C%7C4c6a9d8c95534e6377
>> 2208d4cc4d45db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63635807964139
>> 3686=KeNChB38k71gekwa0h%2Fq6P8P3VN%2FbB2TYzICzB%2BosTo%3D=0
>>>
>>
>>
>

RE: [FlexJS] Falcon AsJS Mismatch?

[Yishay Weiss]

Yea, flex-falcon is up2date. My ‘fix’ was to change TabStopsProperty.as:191 to

  private static const _escapeBackslashRegex:RegExp = new 
RegExp("\\" + "\\", "g");

I’m not pushing this yet so Alex or others can debug the RTE.

From: Harbs
Sent: Sunday, July 16, 2017 3:17 PM
To: dev@flex.apache.org
Subject: Re: [FlexJS] Falcon AsJS Mismatch?

Is this with Alex’s latest changes?

These backslash escapes seem really difficult to get right… :-(

> On Jul 16, 2017, at 2:41 PM, yishayw  wrote:
>
> Looks like falcon is incompatible with TabStopsPropety.as in TLF. When
> initializing that file I'm getting the following RTE:
>
> Uncaught syntax error: Invalid regular expression: missing /
>
> which originates in TabStopsProperty.as:191
>
>private static const _escapeBackslashRegex:RegExp = //g;
>
>
> which transpiles to TabStopsProperty.js:143
>
>
> org.apache.flex.textLayout.property.TabStopsProperty._escapeBackslashRegex =
> /\/g;
>
>
>
>
>
> --
> View this message in context: 
> http://apache-flex-development.247.n4.nabble.com/FlexJS-Falcon-AsJS-Mismatch-tp63296.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: Moonshine 1.5.0 Release

[Yishay Weiss]

It does, thanks.

From: piotrz
Sent: Sunday, July 16, 2017 10:28 AM
To: dev@flex.apache.org
Subject: Re: Moonshine 1.5.0 Release

Hi Yishay,

Does this link working for you [1]

[1] http://moonshine-ide.com/downloads/releases/windows/Moonshine-1.5.0.exe

Thanks,
Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/Moonshine-1-5-0-Release-tp63237p63285.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: git commit: [flex-asjs] [refs/heads/develop] - Add FileUploaderWithResponseData

[Yishay Weiss]

Generally speaking it feels like sometimes I need to insure the order of 
invocation. Since beads communicate with one another through events it’s 
difficult to achieve. Regarding the upload response data I understand your 
suggestion as follows (edges contain event names):

--uploadRequested-complete--modelChanged--

And for the case where the user isn’t interested in the response, just in the 
status:

---uploadRequested-complete-modelChanged--

Is that right?


From: Alex Harui
Sent: Wednesday, July 12, 2017 9:58 AM
To: dev@flex.apache.org
Subject: Re: git commit: [flex-asjs] [refs/heads/develop] - Add 
FileUploaderWithResponseData

I think I still don't understand.

It is ok for beads to require other beads.  If a ResponseData bead
requires a model with a slot for responseData and a controller that knows
to record that data, that's how you are supposed to "re-compose"
components.  There doesn't have to be one model or controller per
component.  The strand is a gathering place for small pieces to work
together.

I'm not sure what work CheckPermissions needs to do, but is totally fine
to split its work amongst a set of beads.

HTH,
-Alex

On 7/11/17, 11:21 PM, "yishayw"  wrote:

>Ideally we wouldn't have to record data that's never read. This may be an
>extreme case, but some users will want to know the response on an upload,
>while some will just want to make sure the status is ok. I'd rather not
>anticipate too many use cases when writing the strand and the model
>because
>I might end up with code that's never used. If the bead was responsible
>for
>both recording the response and exposing it to the user, we wouldn't have
>to
>do that.
>
>Perhaps a better example is permissions. I already have an Upload bead.
>Now
>I want an alert to pop up if the user is not permitted to upload. I'd like
>to be able to add a 'CheckPemissionsOnUpload' bead. Right now I don't see
>how to do that, instead I would probably have to replace 'UploadBead' with
>'UploadButCheckPermissionsBead'. This takes us away from composition and
>forces inheritance.
>
>Maybe we don't need to modify class definitions. I think it's enough to
>modify the bead instance. In JS we could simply replace the function, and
>in
>flash we could maybe replace the whole original bead with a
>flash.utils.Proxy. But this will make things a bit complicated to read and
>maintain.
>
>
>
>
>
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FRe-git-commit-flex-asjs-refs-heads-d
>evelop-Add-FileUploaderWithResponseData-tp63051p63139.html=02%7C01%7C
>%7Cbd5414b3ced9495c188908d4c8f0f59b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0
>%7C0%7C636354384624691027=BGn1g0wbTZr7ikn3uuhcIGDGPEmSVWTwIF%2BlaF6d
>v8w%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: git commit: [flex-asjs] [refs/heads/develop] - Uploads are assumed to be POST

[Yishay Weiss]

Normally I would agree, but I was trying to be strict about PAYG in these 
commits. Let’s see what the others say.

From: piotrz
Sent: Tuesday, July 11, 2017 12:05 PM
To: dev@flex.apache.org
Subject: RE: git commit: [flex-asjs] [refs/heads/develop] - Uploads are assumed 
to be POST

I just think that we should use const whenever we can, but won't fight for
that if no one think similar. :) If I found such code around my interest my
natural move would be change it :)

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/Re-git-commit-flex-asjs-refs-heads-develop-Uploads-are-assumed-to-be-POST-tp63070p63078.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: git commit: [flex-asjs] [refs/heads/develop] - Uploads are assumed to be POST

[Yishay Weiss]

I was trying to save an extra import. Will wait for more thoughts on this.

From: Piotr Zarzycki
Sent: Tuesday, July 11, 2017 11:15 AM
To: dev@flex.apache.org
Subject: Re: git commit: [flex-asjs] [refs/heads/develop] - Uploads are assumed 
to be POST

Hi Yishay,

I think you could use constant here -> HTTPConstants.POST

Thanks, Piotr

2017-07-11 10:09 GMT+02:00 :

> Repository: flex-asjs
> Updated Branches:
>   refs/heads/develop cc098932c -> 3b5053f91
>
>
> Uploads are assumed to be POST
>
>
> Project: http://git-wip-us.apache.org/repos/asf/flex-asjs/repo
> Commit: http://git-wip-us.apache.org/repos/asf/flex-asjs/commit/3b5053f9
> Tree: http://git-wip-us.apache.org/repos/asf/flex-asjs/tree/3b5053f9
> Diff: http://git-wip-us.apache.org/repos/asf/flex-asjs/diff/3b5053f9
>
> Branch: refs/heads/develop
> Commit: 3b5053f91f869a7fd4cd1eccf80e696e5171b532
> Parents: cc09893
> Author: DESKTOP-RH4S838\Yishay 
> Authored: Tue Jul 11 11:08:32 2017 +0300
> Committer: DESKTOP-RH4S838\Yishay 
> Committed: Tue Jul 11 11:08:32 2017 +0300
>
> --
>  .../src/main/flex/org/apache/flex/file/beads/FileUploader.as| 1 +
>  1 file changed, 1 insertion(+)
> --
>
>
> http://git-wip-us.apache.org/repos/asf/flex-asjs/blob/
> 3b5053f9/frameworks/projects/Network/src/main/flex/org/
> apache/flex/file/beads/FileUploader.as
> --
> diff --git 
> a/frameworks/projects/Network/src/main/flex/org/apache/flex/file/beads/FileUploader.as
> b/frameworks/projects/Network/src/main/flex/org/apache/flex/
> file/beads/FileUploader.as
> index e9aad3c..194a1d6 100644
> --- a/frameworks/projects/Network/src/main/flex/org/apache/flex/
> file/beads/FileUploader.as
> +++ b/frameworks/projects/Network/src/main/flex/org/apache/flex/
> file/beads/FileUploader.as
> @@ -80,6 +80,7 @@ package org.apache.flex.file.beads
>  // }
> var binaryUploader:URLBinaryLoader = new
> URLBinaryLoader();
> var req:URLRequest = new URLRequest();
> +   req.method = "POST";
> req.data = (host.model as FileModel).blob;
> req.url = url;
> binaryUploader.addEventListener(Event.COMPLETE,
> completeHandler);
>
>

RE: git commit: [flex-asjs] [refs/heads/develop] - Add FileUploaderWithResponseData

[Yishay Weiss]

I was thinking the same thing but it’s complicated to make it into a bead. It 
would have to catch the ‘complete’ event and record the response data before 
anyone else does. Since we don’t have event listener priorities I don’t know 
how to do that. I hope to update the wiki Greg wrote when I’m done with this. 
Maybe I can pass on some of my experiences.

From: Piotr Zarzycki
Sent: Monday, July 10, 2017 8:40 PM
To: dev@flex.apache.org
Subject: Re: git commit: [flex-asjs] [refs/heads/develop] - Add 
FileUploaderWithResponseData

Hi Yishay,

I'm wondering whether it is possible to have it bead instead class ? What
do you think ?

Thanks, Piotr

2017-07-10 18:30 GMT+02:00 :

> Repository: flex-asjs
> Updated Branches:
>   refs/heads/develop c6a24011b -> 54d00a044
>
>
> Add FileUploaderWithResponseData
>
>
> Project: http://git-wip-us.apache.org/repos/asf/flex-asjs/repo
> Commit: http://git-wip-us.apache.org/repos/asf/flex-asjs/commit/54d00a04
> Tree: http://git-wip-us.apache.org/repos/asf/flex-asjs/tree/54d00a04
> Diff: http://git-wip-us.apache.org/repos/asf/flex-asjs/diff/54d00a04
>
> Branch: refs/heads/develop
> Commit: 54d00a044196ec62e81840b3134f9f17f26f4cb1
> Parents: c6a2401
> Author: DESKTOP-RH4S838\Yishay 
> Authored: Mon Jul 10 19:30:12 2017 +0300
> Committer: DESKTOP-RH4S838\Yishay 
> Committed: Mon Jul 10 19:30:12 2017 +0300
>
> --
>  .../main/flex/org/apache/flex/file/FileProxy.as |  9 
>  .../flex/file/beads/FileLoaderAndUploader.as|  2 +-
>  .../org/apache/flex/file/beads/FileUploader.as  | 18 
>  .../file/beads/FileUploaderWithResponseData.as  | 43 
>  .../src/main/resources/basic-manifest.xml   |  1 +
>  5 files changed, 72 insertions(+), 1 deletion(-)
> --
>
>
> http://git-wip-us.apache.org/repos/asf/flex-asjs/blob/
> 54d00a04/frameworks/projects/Network/src/main/flex/org/
> apache/flex/file/FileProxy.as
> --
> diff --git 
> a/frameworks/projects/Network/src/main/flex/org/apache/flex/file/FileProxy.as
> b/frameworks/projects/Network/src/main/flex/org/apache/flex/
> file/FileProxy.as
> index 738cf55..38c2fe8 100644
> --- a/frameworks/projects/Network/src/main/flex/org/apache/flex/
> file/FileProxy.as
> +++ b/frameworks/projects/Network/src/main/flex/org/apache/flex/
> file/FileProxy.as
> @@ -23,6 +23,15 @@ package org.apache.flex.file
> import org.apache.flex.file.beads.FileModel;
>
> /**
> +*  Indicates that the model has changed
> +*
> +*  @langversion 3.0
> +*  @playerversion Flash 10.2
> +*  @playerversion AIR 2.6
> +*  @productversion FlexJS 0.9
> +*/
> +   [Event(name="modelChanged", type="org.apache.flex.events.Event")]
> +   /**
>  *  The FileProxy class is where beads regarding file operations
> are added.
>  *  Information about operations can be queried in the file model,
> or by
>  *  listenening to events dispatched by beads.
>
> http://git-wip-us.apache.org/repos/asf/flex-asjs/blob/
> 54d00a04/frameworks/projects/Network/src/main/flex/org/
> apache/flex/file/beads/FileLoaderAndUploader.as
> --
> diff --git a/frameworks/projects/Network/src/main/flex/org/apache/flex/
> file/beads/FileLoaderAndUploader.as b/frameworks/projects/Network/
> src/main/flex/org/apache/flex/file/beads/FileLoaderAndUploader.as
> index 77ba96c..2b66552 100644
> --- a/frameworks/projects/Network/src/main/flex/org/apache/flex/
> file/beads/FileLoaderAndUploader.as
> +++ b/frameworks/projects/Network/src/main/flex/org/apache/flex/
> file/beads/FileLoaderAndUploader.as
> @@ -21,7 +21,7 @@ package org.apache.flex.file.beads
> import org.apache.flex.events.Event;
>
> /**
> -*  The FileLoaderUploader is a compound bead that allows you
> +*  The FileLoaderAndUploader is a compound bead that allows you
>  *  to load a file and upload it in one operation.
>  *
>  *
>
> http://git-wip-us.apache.org/repos/asf/flex-asjs/blob/
> 54d00a04/frameworks/projects/Network/src/main/flex/org/
> apache/flex/file/beads/FileUploader.as
> --
> diff --git 
> a/frameworks/projects/Network/src/main/flex/org/apache/flex/file/beads/FileUploader.as
> b/frameworks/projects/Network/src/main/flex/org/apache/flex/
> file/beads/FileUploader.as
> index 0cf4d5f..470eb28 100644
> --- a/frameworks/projects/Network/src/main/flex/org/apache/flex/
> file/beads/FileUploader.as
> +++ b/frameworks/projects/Network/src/main/flex/org/apache/flex/
> file/beads/FileUploader.as
> @@ -19,6 +19,8 @@ 

RE: [1/2] git commit: [flex-asjs] [refs/heads/develop] - Camera API requires flash verion 11.4

[Yishay Weiss]

I’m not sure. See here [1]

[1] 
http://apache-flex-development.247.n4.nabble.com/FlexJS-Mobile-Depends-on-Flash-11-4-td62811.html

From: Piotr Zarzycki
Sent: Wednesday, July 5, 2017 11:56 AM
To: dev@flex.apache.org
Subject: Re: [1/2] git commit: [flex-asjs] [refs/heads/develop] - Camera API 
requires flash verion 11.4

Hi Yishay,

Does Maven build require this changes also ? I will look into that later
today, but maybe you can beat me :)

Thanks,
Piotr

2017-07-05 9:20 GMT+02:00 :

> Repository: flex-asjs
> Updated Branches:
>   refs/heads/develop 722e9eed7 -> 73c18eccf
>
>
> Camera API requires flash verion 11.4
>
>
> Project: http://git-wip-us.apache.org/repos/asf/flex-asjs/repo
> Commit: http://git-wip-us.apache.org/repos/asf/flex-asjs/commit/a4e43605
> Tree: http://git-wip-us.apache.org/repos/asf/flex-asjs/tree/a4e43605
> Diff: http://git-wip-us.apache.org/repos/asf/flex-asjs/diff/a4e43605
>
> Branch: refs/heads/develop
> Commit: a4e43605769cb812ef772f9ed224fbc141959fbd
> Parents: 722e9ee
> Author: DESKTOP-RH4S838\Yishay 
> Authored: Wed Jul 5 10:11:35 2017 +0300
> Committer: DESKTOP-RH4S838\Yishay 
> Committed: Wed Jul 5 10:11:35 2017 +0300
>
> --
>  frameworks/projects/Mobile/build.xml | 6 --
>  1 file changed, 4 insertions(+), 2 deletions(-)
> --
>
>
> http://git-wip-us.apache.org/repos/asf/flex-asjs/blob/
> a4e43605/frameworks/projects/Mobile/build.xml
> --
> diff --git a/frameworks/projects/Mobile/build.xml
> b/frameworks/projects/Mobile/build.xml
> index 53302cc..d2aef52 100644
> --- a/frameworks/projects/Mobile/build.xml
> +++ b/frameworks/projects/Mobile/build.xml
> @@ -21,10 +21,12 @@
>
>  
>  
> -
> +
>  
>  
> -
> +   
> +
> +   
>  
>
>  
>
>

RE: git commit: [flex-asjs] [refs/heads/develop] - Added FileIUploader, fixed BinaryUploader

[Yishay Weiss]

I removed it, thanks.

From: Piotr Zarzycki
Sent: Tuesday, July 4, 2017 2:30 PM
To: dev@flex.apache.org
Subject: Re: git commit: [flex-asjs] [refs/heads/develop] - Added 
FileIUploader, fixed BinaryUploader

Hi Yishay,

Do we need this trace in BinaryUploader ? :)

Thanks,
Piotr

2017-07-04 13:16 GMT+02:00 :

> Repository: flex-asjs
> Updated Branches:
>   refs/heads/develop f1108167c -> e083f6ab1
>
>
> Added FileIUploader, fixed BinaryUploader
>
>
> Project: http://git-wip-us.apache.org/repos/asf/flex-asjs/repo
> Commit: http://git-wip-us.apache.org/repos/asf/flex-asjs/commit/e083f6ab
> Tree: http://git-wip-us.apache.org/repos/asf/flex-asjs/tree/e083f6ab
> Diff: http://git-wip-us.apache.org/repos/asf/flex-asjs/diff/e083f6ab
>
> Branch: refs/heads/develop
> Commit: e083f6ab14acafd07fad8fa2b1827a931cefb4fd
> Parents: f110816
> Author: DESKTOP-RH4S838\Yishay 
> Authored: Tue Jul 4 14:14:33 2017 +0300
> Committer: DESKTOP-RH4S838\Yishay 
> Committed: Tue Jul 4 14:14:33 2017 +0300
>
> --
>  .../org/apache/flex/file/beads/FileBrowser.as   |  1 -
>  .../org/apache/flex/file/beads/FileLoader.as|  4 +-
>  .../org/apache/flex/file/beads/FileModel.as | 32 +++
>  .../org/apache/flex/file/beads/FileUploader.as  | 98 
>  .../flex/org/apache/flex/net/BinaryUploader.as  | 13 ++-
>  .../src/main/resources/basic-manifest.xml   |  2 +
>  6 files changed, 144 insertions(+), 6 deletions(-)
> --
>
>
> http://git-wip-us.apache.org/repos/asf/flex-asjs/blob/
> e083f6ab/frameworks/projects/Network/src/main/flex/org/
> apache/flex/file/beads/FileBrowser.as
> --
> diff --git 
> a/frameworks/projects/Network/src/main/flex/org/apache/flex/file/beads/FileBrowser.as
> b/frameworks/projects/Network/src/main/flex/org/apache/flex/
> file/beads/FileBrowser.as
> index 029cf97..5d48c00 100644
> --- a/frameworks/projects/Network/src/main/flex/org/apache/flex/
> file/beads/FileBrowser.as
> +++ b/frameworks/projects/Network/src/main/flex/org/apache/flex/
> file/beads/FileBrowser.as
> @@ -32,7 +32,6 @@ package org.apache.flex.file.beads
> import org.apache.flex.events.Event;
> import org.apache.flex.core.WrappedHTMLElement;
> import goog.events;
> -
> }
>
> /**
>
> http://git-wip-us.apache.org/repos/asf/flex-asjs/blob/
> e083f6ab/frameworks/projects/Network/src/main/flex/org/
> apache/flex/file/beads/FileLoader.as
> --
> diff --git 
> a/frameworks/projects/Network/src/main/flex/org/apache/flex/file/beads/FileLoader.as
> b/frameworks/projects/Network/src/main/flex/org/apache/flex/
> file/beads/FileLoader.as
> index f49fb87..0110719 100644
> --- a/frameworks/projects/Network/src/main/flex/org/apache/flex/
> file/beads/FileLoader.as
> +++ b/frameworks/projects/Network/src/main/flex/org/apache/flex/
> file/beads/FileLoader.as
> @@ -17,14 +17,12 @@
>  
> 
>  package org.apache.flex.file.beads
>  {
> -   import flash.events.Event;
> -
> import org.apache.flex.core.IBead;
> import org.apache.flex.core.IStrand;
> import org.apache.flex.file.FileProxy;
> import org.apache.flex.utils.BinaryData;
>
> -   COMPILE::JS
> +   COMPILE::SWF
> {
> import flash.events.Event;
> }
>
> http://git-wip-us.apache.org/repos/asf/flex-asjs/blob/
> e083f6ab/frameworks/projects/Network/src/main/flex/org/
> apache/flex/file/beads/FileModel.as
> --
> diff --git 
> a/frameworks/projects/Network/src/main/flex/org/apache/flex/file/beads/FileModel.as
> b/frameworks/projects/Network/src/main/flex/org/apache/flex/
> file/beads/FileModel.as
> index bddbb09..fa5b314 100644
> --- a/frameworks/projects/Network/src/main/flex/org/apache/flex/
> file/beads/FileModel.as
> +++ b/frameworks/projects/Network/src/main/flex/org/apache/flex/
> file/beads/FileModel.as
> @@ -19,7 +19,9 @@ package org.apache.flex.file.beads
>  {
> import org.apache.flex.core.IBeadModel;
> import org.apache.flex.core.IStrand;
> +   import org.apache.flex.events.Event;
> import org.apache.flex.events.EventDispatcher;
> +   import org.apache.flex.utils.BinaryData;
>
> COMPILE::SWF
> {
> @@ -40,6 +42,7 @@ package org.apache.flex.file.beads
> public class FileModel extends EventDispatcher implements
> IBeadModel
> {
> private var _strand:IStrand;
> +   private var _blob:BinaryData;
> COMPILE::SWF
>  

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

[Yishay Weiss]

Thanks Alex. These lines were necessary for the last part of the presentation 
where I show how to change stuff in the framework. I commented them out in the 
uploaded zip.

From: Alex Harui-2 [via Apache Flex 
Development]
Sent: Saturday, July 1, 2017 6:36 PM
To: yishayw
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" <[hidden 
email]> 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" <[hidden 
>email]> 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:[hidden 
>>email]]
>>Sent: Friday, June 30, 2017 5:22 PM
>>To: [hidden email]
>>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:[hidden 
>>email]]
>>Sent: Friday, June 30, 2017 5:08 PM
>>To: [hidden email]
>>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" <[hidden 
>>email]> 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:[hidden 
>>>email]]
>>>Sent: Friday, June 30, 2017 4:48 PM
>>>To: [hidden email]
>>>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" <[hidden 
>>>email]> 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
com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder$
M
yBu
ilder.mybuild(ASApplicationBuilder.java:309)
at

RE: [FlexJS] TileLayout

[Yishay Weiss]

It’s a bit different because horizontal/vertical layouts don’t size the 
children. Tile does according to the set number of rows and columns.

Peter, FlexBox works fine, the question is how to calculate the childrens’ 
size. It looks to me like another PAYG question. Is the basic tile 
functionality without gaps good enough?

From: piotrz
Sent: Thursday, June 22, 2017 6:13 PM
To: dev@flex.apache.org
Subject: Re: [FlexJS] TileLayout

Hi Yishay,

I think Josh wrote some bead - not sure whether it is related to your
problem [1][2]

[1]
https://github.com/apache/flex-asjs/blob/release0.8.0/frameworks/projects/Basic/src/main/flex/org/apache/flex/html/beads/layouts/HorizontalLayoutWithPaddingAndGap.as
[2]
https://github.com/apache/flex-asjs/blob/release0.8.0/frameworks/projects/Basic/src/main/flex/org/apache/flex/html/beads/layouts/VerticalLayoutWithPaddingAndGap.as

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-TileLayout-tp62568p62574.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: [FlexJS] How Binding works?

[Yishay Weiss]

I agree it’s wasteful, but there’s a lot of old code that we’re porting that 
uses this as a shortcut.  I’ve changed all interface get definitions to be 
prefixed with [Bindable("__NoChangeEvent__")] and the compiler now seems happy. 
It should probably be enough to add it the interface declaration instead.

If I were to rewrite the code what syntax would you suggest instead of mailto:aha...@adobe.com.INVALID>
Sent: Tuesday, June 20, 2017 9:57 AM
To: dev@flex.apache.org
Subject: Re: [FlexJS] How Binding works?

I believe the warning was that the value of PURCHASED could change.  The
Bindable subsystem does not know that the getter will always return the
same string literal.  If other stuff could change, but didn't specify a
change event, I would hope the compiler would warn about that part of the
bindable expression.

IMO, one should never use plain [Bindable] with getters and setters.  That
just wraps the getter/setter in another getter/setter with change event
detection.  That adds up eventually both in code size and runtime.
Suddenly you are making two function calls instead of one to access the
underlying value.

You could use [Bindable("__NoChangeEvent__")] if you know a value doesn't
change but isn't a const.  You probably don't want to add listeners for
when PURCHASED changes, just when the current location manager changes.

Of course, I could be wrong.

-Alex



On 6/19/17, 11:28 PM, "yishayw"  wrote:

>It looks like changing the definitions of the interface and the class to
>
>   [Bindable]function get PURCHASED():String;
>and
>[Bindable]public function get PURCHASED():String { return
>"PURCHASED"; }
>
>worked.
>
>So is it a bug that declaring the class and the interface as bindable was
>not enough?
>
>
>
>
>
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-How-Binding-works-tp57096p624
>85.html=02%7C01%7C%7Cdeee45fa75c74c1828da08d4b7a7f7f2%7Cfa7b1b5a7b344
>38794aed2c178decee1%7C0%7C0%7C636335379433525746=uK6hxHRAC%2BkVi8%2B
>igjlqgOKAypeFlS1EwLbZ6qNniDk%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: [FlexJS] How Binding works?

[Yishay Weiss]

It’s more to let the compiler know the implementations are bindable. I don’t 
expect them to automatically become bindable.

From: piotrz
Sent: Tuesday, June 20, 2017 9:52 AM
To: dev@flex.apache.org
Subject: RE: [FlexJS] How Binding works?

Hi Yishay,

Actaully what is the purpose to have Bindable in the interface ? I have
never seen such things in old Flex.

You are expecting that once you implement such interface you will have
[Bindable] inherited ?

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-How-Binding-works-tp57096p62486.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: [FlexJS] How Binding works?

[Yishay Weiss]

public function get PURCHASED():String { return 
"PURCHASED"; }

But the class has

[Bindable]public class DefaultStrings implements IUIStrings

From: Alex Harui
Sent: Tuesday, June 20, 2017 9:33 AM
To: dev@flex.apache.org
Subject: Re: [FlexJS] How Binding works?

How is PURCHASED defined?

On 6/19/17, 11:10 PM, "yishayw"  wrote:

>We have an mxml component where
>
>   [Bindable]public var locStrings:IUIStrings =
>LocaleManager.localeStrings;
>...
>
>   
>   
>...
>
>
>LocaleManager is declared thus:
>
>   [Bindable]
>   public class LocaleManager
>
>and it has:
>public static function get
>localeStrings():IUIStrings
>
>where IUIString is declared thus:
>
>   [Bindable]public interface IUIStrings
>
>and its implementation is declares like this:
>
>   [Bindable]public class DefaultStrings implements
>IUIStrings
>
>Can anyone explain why I'm seeing this?
>
>   Data binding will not be able to detect assignments
>to 'PURCHASED'.
>
>
>
>
>
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-How-Binding-works-tp57096p624
>81.html=02%7C01%7C%7Cb672a18d7b984dac8a1008d4b7a56890%7Cfa7b1b5a7b344
>38794aed2c178decee1%7C0%7C0%7C636335368449199077=B9M048Wm1IsFYGOD%2F
>WAwrNhEmrJvAVEWXyPfP4MFuIQ%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: [FlexJS] DataBinding Problem

[Yishay Weiss]

It looks like Alex is modifying Panel to fix the problem in Accordion. I’m good 
with that.

From: piotrz
Sent: Tuesday, June 6, 2017 10:10 AM
To: dev@flex.apache.org
Subject: Re: [FlexJS] DataBinding Problem

I think we can make it as feature request and Yishay probably need to handle
"modelChanged" event on your own to have such code working on the fly.

What do you think Yishay ?

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-DataBinding-Problem-tp62073p62141.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: [FlexJS] setDocument()

[Yishay Weiss]

flexibleChild is a string, which is the id of the flexible child, so using it 
to reference the object won’t work. Document (which is a model of the MXML 
document) should be loaded at some point if it’s being used in mxml. I would 
put a condition to see whether it has been loaded already, and return if it 
hasn’t. The layout method should be called at least once after the document is 
loaded, so the logic would apply then.

If the document is never loaded then we have a bigger problem.

From: Harbs
Sent: Tuesday, May 23, 2017 10:21 PM
To: dev
Subject: [FlexJS] setDocument()

I have an app which uses OneFlexibleChildVerticalLayout. I have not built the 
app recently, and I noticed that it’s currently failing.

It seems like the error is in layout() from the following code:

actualChild = document[flexibleChild];

document is never being set, and I’m not sue what the purpose of “document” is 
at all. Why not just use flexibleChild?

Harbs

RE: [LAST CALL] Release FlexJS/FalconJX 0.8.0

[Yishay Weiss]

I had to change \frameworks\flex-config.xml and remove sfw- from 
 and . Otherwise there’s no code 
hinting in new FB project. Shouldn’t that be the default configuration?

From: Alex Harui
Sent: Saturday, May 20, 2017 4:51 PM
To: dev@flex.apache.org
Subject: Re: [LAST CALL] Release FlexJS/FalconJX 0.8.0

"Pulled changes" as in syncing up the repo or grabbing the release CI
build?

Looks like the CI build was stuck, maybe for 3 days!  I've just unstuck
it.  It should take a couple of hours to finish building the latest from
the release branches.

If you are working from the repos, make sure you compiler jars are up to
date in the FlexJS SDK that FB is using.

-Alex

On 5/20/17, 7:01 AM, "yishayw"  wrote:

>I just pulled the changes and tried to build using FB. I'm getting this
>
>1319: unknown configuration variable 'compiler.targets'.
>C:\dev\flexjs\flex-asjs\frameworks\projects\Core\src\main\config\compile-s
>wf-config.xml
>(line: 25)
>
>So Core doesn't build.
>
>
>
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FLAST-CALL-Release-FlexJS-FalconJX-0-
>8-0-tp61275p61704.html=02%7C01%7C%7C82d9b3c3bd5a43be7d9b08d49f8a9d10%
>7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636308865070833457=Cthw
>oTulwCSM4Y8cjtNNiZosHUyCNd24BhNDjCm9vNg%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: [LAST CALL] Release FlexJS/FalconJX 0.8.0

[Yishay Weiss]

Also, I don’t see changes in Framework reflected in test project.

From: Alex Harui
Sent: Saturday, May 20, 2017 4:51 PM
To: dev@flex.apache.org
Subject: Re: [LAST CALL] Release FlexJS/FalconJX 0.8.0

"Pulled changes" as in syncing up the repo or grabbing the release CI
build?

Looks like the CI build was stuck, maybe for 3 days!  I've just unstuck
it.  It should take a couple of hours to finish building the latest from
the release branches.

If you are working from the repos, make sure you compiler jars are up to
date in the FlexJS SDK that FB is using.

-Alex

On 5/20/17, 7:01 AM, "yishayw"  wrote:

>I just pulled the changes and tried to build using FB. I'm getting this
>
>1319: unknown configuration variable 'compiler.targets'.
>C:\dev\flexjs\flex-asjs\frameworks\projects\Core\src\main\config\compile-s
>wf-config.xml
>(line: 25)
>
>So Core doesn't build.
>
>
>
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FLAST-CALL-Release-FlexJS-FalconJX-0-
>8-0-tp61275p61704.html=02%7C01%7C%7C82d9b3c3bd5a43be7d9b08d49f8a9d10%
>7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636308865070833457=Cthw
>oTulwCSM4Y8cjtNNiZosHUyCNd24BhNDjCm9vNg%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: [FlexJS] MDL Text Buttons Not Looking Good

[Yishay Weiss]

The link you sent looks fine to me too, so it’s not some Chrome weirdness. Your 
guess that it’s the wrong excluded lib sounds reasonable so I’ll report when 
I’ve change the Ant script. Thanks.

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Thursday, May 11, 2017 12:21 PM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>
Subject: RE: [FlexJS] MDL Text Buttons Not Looking Good

I’m looking here [1] on Chrome. Does it look ok to you?

[1]
http://apacheflexbuild.cloudapp.net:8080/job/MDLExample/lastSuccessfulBuild/artifact/examples/flexjs/MDLExample/bin/js-debug/index.html

From: piotrz<mailto:piotrzarzyck...@gmail.com>
Sent: Wednesday, May 10, 2017 6:14 PM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>
Subject: Re: [FlexJS] MDL Text Buttons Not Looking Good

Hi Yishay,

I don't see jumps in Maven build [1].

Maybe there is problem with build parameter. Before we moved not related
HTML component to Basic, we were excluded HTML.swc css during build of
MDLExample, now need to be exluded Basic.swc. - That's my shot. In case of
Maven I did such changes - maybe there should be also changed for ant build.

[1]
https://builds.apache.org/job/FlexJS%20Framework%20(maven)/916/artifact/examples/flexjs/MDLExample/target/javascript/bin/js-debug/index.html

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Text-Buttons-Not-Looking-Good-tp61532p61533.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: [FlexJS] MDL Text Buttons Not Looking Good

[Yishay Weiss]

I’m looking here [1] on Chrome. Does it look ok to you?

[1]
http://apacheflexbuild.cloudapp.net:8080/job/MDLExample/lastSuccessfulBuild/artifact/examples/flexjs/MDLExample/bin/js-debug/index.html

From: piotrz
Sent: Wednesday, May 10, 2017 6:14 PM
To: dev@flex.apache.org
Subject: Re: [FlexJS] MDL Text Buttons Not Looking Good

Hi Yishay,

I don't see jumps in Maven build [1].

Maybe there is problem with build parameter. Before we moved not related
HTML component to Basic, we were excluded HTML.swc css during build of
MDLExample, now need to be exluded Basic.swc. - That's my shot. In case of
Maven I did such changes - maybe there should be also changed for ant build.

[1]
https://builds.apache.org/job/FlexJS%20Framework%20(maven)/916/artifact/examples/flexjs/MDLExample/target/javascript/bin/js-debug/index.html

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Text-Buttons-Not-Looking-Good-tp61532p61533.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: [ApacheCon/FlexJSSummit] Just registered...

[Yishay Weiss]

I’ll be there on the 13th as well. Cyall.

From: piotrz
Sent: Monday, May 8, 2017 6:16 PM
To: dev@flex.apache.org
Subject: Re: [ApacheCon/FlexJSSummit] Just registered...

OMG!! :) I meant 13 May!! 9:30 PM!! :)



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/ApacheCon-FlexJSSummit-Just-registered-tp61516p61522.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: [FlexJS] flex-asjs build failing

[Yishay Weiss]

I did.

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Wednesday, April 5, 2017 1:37 PM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>
Subject: RE: [FlexJS] flex-asjs build failing

Hi Chris,

You’re right. That’s why I said to ignore that mail. I was mixing Ant and 
Maven. The font download problem is on a Maven only env.

Yishay

From: Christofer Dutz<mailto:christofer.d...@c-ware.de>
Sent: Wednesday, April 5, 2017 1:35 PM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>
Subject: Re: [FlexJS] flex-asjs build failing

Hi Yishay,

I guess that problem is related to running the build in Ant and Maven. I think 
the Ant build used to download stuff into the “source” directories so you had 
checked in stuff and not checked in stuff. I would assume the complaints are 
related to that. Another reason could be that you have built with Maven and are 
re-building with less projects enabled. In that case RAT thinks the files of 
the project belong to the parent project and need a License.

I’d just do a search for the swfobject.js

Chris

Am 05.04.17, 09:47 schrieb "yishayw" <yishayj...@hotmail.com>:

I think I got passed the fontkit problem by copying the contents of

%JAVA_HOME%/../jre/lib/security
to
%JAVA_HOME%/lib/security

(Copying it to %JAVA_HOME%/jre/lib/security didn't make a different to me.)
Apparently there's a bunch of files other than local_policy.jar and
US_export_policy.jar that need to be there.

Now rat.txt is telling me that templates/swfobject/swfobject.js has an
unapproved license. This is strange because I don't even see it in the file
system, so I'm not sure how to fix that.



--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-flex-asjs-build-failing-tp60461p61006.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: [FlexJS] flex-asjs build failing

[Yishay Weiss]

Hi Chris,

You’re right. That’s why I said to ignore that mail. I was mixing Ant and 
Maven. The font download problem is on a Maven only env.

Yishay

From: Christofer Dutz
Sent: Wednesday, April 5, 2017 1:35 PM
To: dev@flex.apache.org
Subject: Re: [FlexJS] flex-asjs build failing

Hi Yishay,

I guess that problem is related to running the build in Ant and Maven. I think 
the Ant build used to download stuff into the “source” directories so you had 
checked in stuff and not checked in stuff. I would assume the complaints are 
related to that. Another reason could be that you have built with Maven and are 
re-building with less projects enabled. In that case RAT thinks the files of 
the project belong to the parent project and need a License.

I’d just do a search for the swfobject.js

Chris

Am 05.04.17, 09:47 schrieb "yishayw" :

I think I got passed the fontkit problem by copying the contents of

%JAVA_HOME%/../jre/lib/security
to
%JAVA_HOME%/lib/security

(Copying it to %JAVA_HOME%/jre/lib/security didn't make a different to me.)
Apparently there's a bunch of files other than local_policy.jar and
US_export_policy.jar that need to be there.

Now rat.txt is telling me that templates/swfobject/swfobject.js has an
unapproved license. This is strange because I don't even see it in the file
system, so I'm not sure how to fix that.



--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-flex-asjs-build-failing-tp60461p61006.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: [FlexJS] OneFlexibleChildVerticalLayout

[Yishay Weiss]

Hi Peter,

Yes, we noticed the problem where 100% is needed but takes up all the space. 
I’m glad you’re working on it. In the meantime we were able to hack something 
to get around this problem but I’m looking forward to implementing a cleaner 
solution so do let us know when that’s fixed. Would have been nice if we had a 
proper unit test for layouts…

Thanks,
Yishay

From: Peter Ent
Sent: Monday, April 3, 2017 4:46 PM
To: dev@flex.apache.org
Subject: Re: [FlexJS] OneFlexibleChildVerticalLayout

Hi,

I believe I have fixed part of the problem. Please refresh your copy of
feature/chart-work. There was a problem with the
OneFlexibleChildVerticalLayout.

However, there is also another problem, but that might take longer to
resolve. In the meantime, leave your example exactly as you have it.

Ideally, the flexible child should not have a height specified since that
is the child whose height you want to be determined by the layout; you
don't know how high to make it. But for some reason (yet to be
determined), removing the height attribute causes it to have a height of
zero.

When I now run your sample using the correction I just pushed, I see a
green bar all the way across the top of the browser and blue fills the
rest of the browser space.

Regards,
Peter

On 4/3/17, 8:50 AM, "Peter Ent"  wrote:

>Something is not right with the layouts. I'm looking into it today.
>‹peter
>
>On 4/3/17, 2:43 AM, "yishayw"  wrote:
>
>>I just tested the test case upthread on feature/chart-work and I'm
>>getting
>>the same problem. 'cont2' does not get sized and is not shown.
>>
>>
>>
>>--
>>View this message in context:
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fl
>>e
>>x-development.247.n4.nabble.com%2FFlexJS-OneFlexibleChildVerticalLayo
>>u
>>t-tp60953p60975.html=02%7C01%7C%7C96b52cdb2e66494ea8c308d47a5deed0%7
>>C
>>fa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636267991233417705=6Ug8j
>>d
>>VRghPx47WMNiewf7e1qfhIIf1wjwqJmmP2eAg%3D=0
>>Sent from the Apache Flex Development mailing list archive at Nabble.com.
>

RE: [FlexJS] Simple App Not Running

[Yishay Weiss]

I’m using ant:

Build.xml [1], build_example.xml [2]

The console output is (see upthread):

Uncaught TypeError: Cannot read property 'prototype' of undefined
at Object.goog.inherits (base.js:2408)
at a_project.js:106

[1] https://paste.apache.org/Utyt
[2] https://paste.apache.org/Wq3U


From: Alex Harui
Sent: Wednesday, March 29, 2017 6:32 PM
To: dev@flex.apache.org
Subject: Re: [FlexJS] Simple App Not Running

Are you using Ant or Maven?

What build steps are you using, and what is the console output?

Thanks,
-Alex

On 3/29/17, 8:22 AM, "yishayw"  wrote:

>I just tried it with the latest falcon from repo and am getting the same
>results.
>
>
>
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-Simple-App-Not-Running-tp6082
>5p60901.html=02%7C01%7C%7C4a01f5e84a2e4b6b7a4808d476b890e0%7Cfa7b1b5a
>7b34438794aed2c178decee1%7C0%7C0%7C636263982453087548=%2BwPWydqvIs9c
>CetBbyKXCCZOMekF0rcdMOU%2Fojuf7Qs%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: [FlexJS, Maven] Local build failing occasionally

[Yishay Weiss]

I’ll keep that in mind (and so will Piotr)…

From: Christofer Dutz
Sent: Wednesday, March 29, 2017 2:11 PM
To: dev@flex.apache.org
Subject: Re: [FlexJS, Maven] Local build failing occasionally

Hi Yishay,

I would be careful with parallel compilation as the compiler internally has a 
lot of static stuff that multiple parallel executions will mess up randomly (
Hopefully we will have the time to clean this up some time … parallel 
compilation would be a cool feature to use.

Chris



Am 29.03.17, 10:26 schrieb "piotrz" :

Once I off parallel compilation everything went smoothly.

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-Maven-Local-build-failing-occasionally-tp60859p60892.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: [FlexJS, Maven] Local build failing occasionally

[Yishay Weiss]

I believe the reason Graphics needs ByteArray is so it can read the pixel 
bender object files.

From: piotrz
Sent: Tuesday, March 28, 2017 11:24 PM
To: dev@flex.apache.org
Subject: Re: [FlexJS, Maven] Local build failing occasionally

I was going farther by that, but I don't really understand why errors in this
logs, are around XML module not in Graphics.

Graphics need ByteArray. Maybe Harbs or Yishay shed some light on this one.

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-Maven-Local-build-failing-occasionally-tp60859p60868.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

[FlexJS] flex-asjs build failing

[Yishay Weiss]

I’m getting the below error when building from scratch using maven. Any ideas?

For what it’s worth I couldn’t find
com.adobe:fontkit:jar:1.0
in
https://repository.apache.org/content/repositories/releases
Either.

[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.5.0:java 
(compile-font) on project Fonts: Execution compile-font of goal 
org.codehaus.mojo:exec-maven-plugin:1.5.0:java failed: Plugin 
org.codehaus.mojo:exec-maven-plugin:1.5.0 or one of its dependencies could not 
be resolved: Failure to find com.adobe:fontkit:jar:1.0 in 
https://repository.apache.org/content/repositories/releases was cached in the 
local repository, resolution will not be reattempted until the update interval 
of apache-plugins-release has elapsed or updates are forced -> [Help 1]

Nabble

[Yishay Weiss]

Everytime I start a session Nabble tells me my password is incorrect and I have 
to change it. Anyone else having that problem?

RE: [FlexJS] Embed Workaround

[Yishay Weiss]

I’m getting

command line Error: unknown configuration variable 
'compiler.byte-array-embed-class'.

After downloading the nightly.

From: Alex Harui
Sent: Monday, March 6, 2017 9:35 PM
To: dev@flex.apache.org
Subject: Re: [FlexJS] Embed Workaround

I just pushed an untested attempt to allow using a different class for
embeds.  It is in the develop branch.

Normally, the compiler expects to find a flex SDK swc with
mx.core.ByteArrayAsset in it.  You should be able to create an
org.apache.flex.core.ByteArrayAsset class that extends
flash.utils.ByteArray and add the compiler option
-compiler.byte-array-embed-class=org.apache.flex.core.ByteArrayAsset.  I
don't think the IFlexAsset interface is required.

HTH,
-Alex

On 3/6/17, 9:32 AM, "Harbs"  wrote:

>I’m sorry but you totally lost me there… ;-)
>
>What name, used where?
>
>I don’t understand how the [Embed] tag works and where the ByteArrayAsset
>comes from.
>
>> On Mar 6, 2017, at 7:27 PM, Alex Harui  wrote:
>>
>>
>>
>> On 3/6/17, 9:05 AM, "Harbs"  wrote:
>>
>>> How to add full support for [Embed] is a complicated question.
>>>
>>> I think it would be great to support it, but the details get sticky. I
>>> think we need a list of use cases for [Embed] to figure out the right
>>> behavior for each and a way to differentiate the use cases. On the
>>> simplest level, it could simply copy files and set src to the copied
>>> path. Maybe get fancy with BinaryData? What to do with BitmapData? What
>>> about Class assignment? I’m not sure what the right answer is to these
>>> questions.
>>>
>>> For the BlendBead, all we really need though, is SWF support. The JS
>>>side
>>> does not rely on the PixelBender files.
>>
>> Well, in keeping with other compiler changes, the answer would be to
>>make
>> the name of the ByteArrayAsset class configurable like we did for the
>> PropertyChangeEvent.  If you want a quick fix for now, just change the
>> name used in DataTranscoder.java.
>>
>> Thanks,
>> -Alex
>>
>

RE: git commit: [flex-asjs] [refs/heads/develop] - Add JS support for non pixel numeric properties ie fontWeight

[Yishay Weiss]

Sorry, I missed the fontWeight entry in SimpleCSSStyles. You have a point then.

From: Justin Mclean
Sent: Sunday, March 5, 2017 1:45 PM
To: dev@flex.apache.org
Subject: Re: git commit: [flex-asjs] [refs/heads/develop] - Add JS support for 
non pixel numeric properties ie fontWeight

Hi,

> SimpleCSSStyles contains all the style names that SimpleCSSStylesImpl is 
> guaranteed to support.

Of which font weight is an existing one. I’m not added support for something it 
didn’t support just fixing a bug for something it supported.

> So I wouldn’t say fontWeight not being supported by SimpleCSSStylesImpl was a 
> bug, unless it were added to SimpleCSSStyles.

As I said it already supports it. If you look at the class you’ll see this 
property:

native public var fontWeight:*;

> I think if you want to be safe in MXML, it’s best to avoid using string 
> values for style and to use objects such as SimpleCSSStyles insead.

Which is what I did. My fix allows this:


   
   
   
   
   


Without that change the above code has no effect and the font weight is not set.

Thanks,
Justin

RE: git commit: [flex-asjs] [refs/heads/develop] - Add JS support for non pixel numeric properties ie fontWeight

[Yishay Weiss]

SimpleCSSStyles contains all the style names that SimpleCSSStylesImpl is 
guaranteed to support.  So I wouldn’t say fontWeight not being supported by 
SimpleCSSStylesImpl was a bug, unless it were added to SimpleCSSStyles.

I think if you want to be safe in MXML, it’s best to avoid using string values 
for style and to use objects such as SimpleCSSStyles insead.

From: Justin Mclean
Sent: Sunday, March 5, 2017 12:33 PM
To: dev@flex.apache.org
Subject: Re: git commit: [flex-asjs] [refs/heads/develop] - Add JS support for 
non pixel numeric properties ie fontWeight

Hi,

> Again, with PAYG, we want SimpleCSSStylesImpl to be simple and we want the
> SWF side to remain at parity.

IMO this is not a PAYG issue it is a bug. FontWeight does accept px values see 
[1]

Without this change any font weight values are ignored in JS and no warnings 
given.

Thanks,
Justin

1.https://www.w3.org/wiki/CSS/Properties/font-weight 

RE: [FlexJS]Layout redux

[Yishay Weiss]

One more thing to consider is how effects will fit in here. I can imagine 
scenarios where items inside of a container need to have an effect applied to 
them. Currently, the move effect relies on changing x, y values, which implies 
absolute positioning. If they’re all part of a flexbox I’m not sure how effects 
would apply.



I ran into these issues when implementing LayoutTweener and EasyCollapseBead 
for the Accordion component.



If we’re serious about having swf feature parity, I think we’ll end up doing 
everything with absolute positioning on the swf side anyway, so we might as 
well implement it the same way on the JS side. The only downside to this that I 
see is possible performance issues.



What are your thoughts on this?



From: Peter Ent
Sent: Friday, February 24, 2017 9:42 PM
To: dev@flex.apache.org
Subject: Re: [FlexJS]Layout redux



Hi,

I've pushed an update to the HorizontalFlexLayout and VerticalFlexLayout
that adds code for the SWF side. In general, the SWF and JS sides look the
same. There are some differences which I'm working on, but these should be
usable.

In doing this I've uncovered some incomplete work and/or exposed some
issues. These are, in no particular order:

UIBase vs. IUIBase. Since some of our components do not inherit from
UIBase, you cannot cast everything to this class. Now as we should really
use interfaces and not classes, casting to IUIBase generally works.
However, IUIBase is missing a lot of useful function prototypes which is
why there is a lot of casting to UIBase. I'd like to see IUIBase become
more complete. The layout code does a lot of extra, unnecessary casts on
the SWF side.

JS vs SWF layouts. When you think about it, once you've set up your 
to have the property display style, adding/removing/changing elements gets
taken care by the browser. If I set up my  with display:flex and then
put in a number of elements and start changing them via JavaScript, they
just change. Of course that doesn't work on the SWF side because there
isn't anything to size and position elements except the layout algorithms.
But the events that trigger those algorithms to execute are in the
Container class which causes the layout - SWF or JS - to execute.
Basically, it seems unnecessary to re-execute JS layouts every time since
the browser does the work. I think this should be revisited.

Padding. This still isn't working right for the Container with layout.
Part of the problem is that padding on the SWF side isn't really padding.
What it does it offset the inner contentArea. This was done so that when
you have a Container with padding=10 and you place a child into it, the
child's (x,y) reads as (0,0) and not (10,10). When I did a test with a
 that had padding:10px, the first item in it reported left:10,
top:10. So I wonder if we shouldn't treat padding the same way?

Basically, I'm wondering if we should revisit the concept of container
components again and nail it down. The SWF and JS platforms are very, very
different here and I think we need to put more thought into it. For
example, maybe layouts should be SWF only and then only to mimic what you
can do with CSS. That might be too complex though.

What I still need to do for the Flex layouts is handle visibility. Or more
specifically, state changes. The DataBindingExample doesn't work right
when the state changes.

The next thing is to add just a couple of Flexbox features. Specially, I
think justify-content, align-items, and align-content. Easy enough to add
for JS of course.

—peter

On 2/23/17, 8:25 AM, "Peter Ent"  wrote:

>
>
>On 2/23/17, 1:54 AM, "Alex Harui"  wrote:
>
>>A few comments/questions:
>>
>>What does flex-box do when it runs out of room?  Doesn't it wrap to a new
>>row/column?  Or can that be controlled?  I think most folks expect
>>VerticalLayout to not create a new column but to keep going vertically
>>and
>>be clipped or scrolled.
>
>Flexbox has a number of options. Wrapping is one of them but is not the
>default. It set these layouts to not wrap so you get a single column or
>row. I did not set overflow, but it probably should be set to hidden or
>auto; trying to match up what we want the SWF side - which takes much more
>effort/code to mimic - requires us to make a choice for default behavior.
>
>I think that using the Flexbox layout will give good results on the JS
>side. I deliberately didn't add more features just to see what people
>think of using it. It has some cool layout features and seems to solve a
>lot of layout problems people have had using CSS. It might not be right
>for all situations of course.
>
>>
>>On the SWF side, I am hopefully going to get buy-in to unwrap the Sprites
>>again.  That's what the dual branch is all about.
>>
>>+1 for lighterweight (one div) Container.  I thought we'd already done
>>something like that in one of the Item Renderers.  But Panel and other
>>ChromContainers 

RE: [FlexJS] Horizontal list missing scrollbar

[Yishay Weiss]

DAYG is excellent. I also advocate R(eport)AYG. Justin’s inputs have escalated 
issues we’ve been dealing with, but haven’t necessarily found time or 
motivation to report. So If someone wants to DWYHT (Do When You Have Time), the 
Jira list is there.

From: Alex Harui
Sent: Thursday, February 23, 2017 9:09 AM
To: dev@flex.apache.org
Subject: Re: [FlexJS] Horizontal list missing scrollbar




On 2/22/17, 2:44 PM, "Justin Mclean"  wrote:

>Hi,
>
>Anyone have any ideas here?

Expect lots of bugs and missing features.  If some example hasn't needed
it, it could be that nobody has written the code for it.  Here's a new
acronym: DAYG (Do as you go).  We are writing code as we need it.

Do not expect FlexJS to be Flex 4.  It just isn't possible for the two
full-timers and some other volunteers to replicate what a much large team
did over 8 years and make it work on two platforms.  That's why I've been
asking folks to pitch in for years now.  It is great to see that finally
starting to happen.

-Alex

FW: [FlexJS] resize event not working?

[Yishay Weiss]

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Wednesday, February 22, 2017 8:07 AM
To: Justin Mclean<mailto:jus...@classsoftware.com>
Subject: RE: [FlexJS] resize event not working?


Looks like you’re using a flash event instead of the flexjs one.



From: Justin Mclean<mailto:jus...@classsoftware.com>
Sent: Wednesday, February 22, 2017 6:12 AM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>
Subject: [FlexJS] resize event not working?



Hi,

This code doesn’t seem to work - anyone have any ideas why?

I tried with and with out the bead and also tried “this.” instead of “view.”


http://ns.adobe.com/mxml/2009;
xmlns:js="library://ns.apache.org/flexjs/basic" 
initialize="init()">



















BTW this:

public function init():void {
this.addEventListener(flash.events.Event.RESIZE, resized);
}

Also gives this warning when compiling:

WARNING - variable flash is undeclared
  this.addEventListener(flash.events.Event.RESIZE, 
org.apache.flex.utils.Language.closure(this.resized, this, 'resized'));

Thanks,
Justin

RE: [FlexJS] COMPILE::SWF and COMPILE::JS

[Yishay Weiss]

We haven’t needed conditional compilation in our ported app so far. What cases 
have you run into?



From: Justin Mclean
Sent: Wednesday, February 15, 2017 2:42 AM
To: dev@flex.apache.org
Subject: Re: [FlexJS] COMPILE::SWF and COMPILE::JS



Hi,

> I'm not sure Maven is set up to handle these flags properly for applications.

Chris what's needed to support this? Is it possible?

>  In theory, we want app developers to not need to use these flags.

Currently AFAIKS an application developer needs these as there several AS only 
components and/or code ended in JS that doesn't compile on AS. Writing very 
simple example apps I run into cases when its required.

Thanks,
Justin

RE: [FlexJS] Spacers and positioning

[Yishay Weiss]

CenterElement (name can change) takes the RightAlignBead approach. It deals 
with conflicts by listening to the layoutComplete event and making the changes 
then. Maybe a bit expensive but it works.



From: Alex Harui
Sent: Sunday, February 12, 2017 8:56 AM
To: dev@flex.apache.org
Subject: Re: [FlexJS] Spacers and positioning



In the current layouts, %width works the way it does in the browser and
not the way it did in Flex.  Where should we document that so folks find
it easily?

If someone wants to port the Flex layouts that's fine with me.  They will
be at least twice as slow, if not more, but that's PAYG for you.

I think you might be able to use Spacer as the FlexibleChild in
OneFlexibleChildHorizontalLayout

And we want the recommended JS patterns to work.  Nice to know that you
got position:absolute;right:0px; to work.  Supposedly "float: right" will
work as well, but I don’t think the SWF side supports that.

We are in the business of finding common patterns and encapsulating them.
So, it is totally within the FlexJS philosophy to have a bead called a
RightAlignBead that injects position:absolute;right:0px; into the styles
block.  There is probably some trickiness to dealing with conflicts if the
styles are also being set in some other way, but then you could do:



  

  


I'm not sure I understand the last code snippet, but there is no reason
not to create a 4ColumnLayout.  We have a VerticalColumnLayout already.
Find the pattern and encapsulate it so others can use it.  Try to keep it
small and loosely coupled.

My 2 cents,
-Alex

On 2/11/17, 10:07 PM, "Harbs"  wrote:

>Currently, the best you can do to spread elements in FlexJS is by using
>OneFlexibleChildVerticalLayout and OneFlexibleChildHorizontalLayout.
>
>The more we use FlexJS, the more we’re coming to the conclusion that we
>really need a ConstrainedLayout which has the features of the classic
>Flex layout…
>
>Harbs
>
>> On Feb 12, 2017, at 4:46 AM, Justin Mclean 
>>wrote:
>>
>> Hi,
>>
>> An old trick to get things to be pined to the RHS was to use a 100%
>>spacer in MXML.
>>
>> However code like this doesn’t work in FlexJS:
>>
>> 
>>
>>
>>
>> 
>>
>> But in FlexJS the spacer is 100% of the containers width and the button
>>wraps onto the next line.
>>
>> You can do this but is seems bit cumbersome:
>>
>> 
>>
>>
>> 
>>
>> And a little more cumbersome once you have several items you want to
>>evenly space.
>>
>> 
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> 
>>
>> Is there a better way of doing this?
>>
>> Thanks,
>> Justin
>>
>

RE: git commit: [flex-asjs] [refs/heads/develop] - Parallel is now derived from CompoundEffect

[Yishay Weiss]

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Tuesday, January 31, 2017 9:38 AM
To: Piotr Zarzycki<mailto:piotrzarzyck...@gmail.com>
Subject: RE: git commit: [flex-asjs] [refs/heads/develop] - Parallel is now 
derived from CompoundEffect


There are 2 stages:

  1.  Populate the beads array, which can be done in a derived class, or in the 
mxml.
  2.  Go over the beads array and call addBead() one after the other. This also 
sets the strand on each bead.



If you up go to the Strand class you’ll see that there are 2 collections: 
beads:Array which is populated at the initialization stage (1), and 
_beads:Vector which holds the collection of beads that were actually added.

Each strand implementation decides when stage (2) happens according to what 
makes sense. UIBase, for instance, does it when addedToParent() is called. In 
CompundEffect I do it as soon as the document is ready (setDocument()).

Hope that explains it.



From: Piotr Zarzycki<mailto:piotrzarzyck...@gmail.com>
Sent: Tuesday, January 31, 2017 9:19 AM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>
Subject: Re: git commit: [flex-asjs] [refs/heads/develop] - Parallel is now 
derived from CompoundEffect



Hi Yishay,

Maybe in that case would be better use addBead method instead create
manually this array ?

Piotr

2017-01-29 16:15 GMT+01:00 <yish...@apache.org>:

> Repository: flex-asjs
> Updated Branches:
>   refs/heads/develop 2cc5ca1a7 -> ee4fa779d
>
>
> Parallel is now derived from CompoundEffect
>
>
> Project: http://git-wip-us.apache.org/repos/asf/flex-asjs/repo
> Commit: http://git-wip-us.apache.org/repos/asf/flex-asjs/commit/ee4fa779
> Tree: http://git-wip-us.apache.org/repos/asf/flex-asjs/tree/ee4fa779
> Diff: http://git-wip-us.apache.org/repos/asf/flex-asjs/diff/ee4fa779
>
> Branch: refs/heads/develop
> Commit: ee4fa779d504e7e471a28b133a2a2ad94f5c9891
> Parents: 2cc5ca1
> Author: yishayw <yishayj...@hotmail.com>
> Authored: Sun Jan 29 17:15:05 2017 +0200
> Committer: yishayw <yishayj...@hotmail.com>
> Committed: Sun Jan 29 17:15:05 2017 +0200
>
> --
>  .../flex/org/apache/flex/effects/Parallel.as| 153 ---
>  1 file changed, 29 insertions(+), 124 deletions(-)
> --
>
>
> http://git-wip-us.apache.org/repos/asf/flex-asjs/blob/
> ee4fa779/frameworks/projects/Effects/src/main/flex/org/
> apache/flex/effects/Parallel.as
> --
> diff --git 
> a/frameworks/projects/Effects/src/main/flex/org/apache/flex/effects/Parallel.as
> b/frameworks/projects/Effects/src/main/flex/org/apache/flex/
> effects/Parallel.as
> index ea68f2d..57e63d3 100644
> --- a/frameworks/projects/Effects/src/main/flex/org/apache/flex/
> effects/Parallel.as
> +++ b/frameworks/projects/Effects/src/main/flex/org/apache/flex/
> effects/Parallel.as
> @@ -19,134 +19,39 @@
>
>  package org.apache.flex.effects
>  {
> -
> -import org.apache.flex.core.IDocument;
> -import org.apache.flex.core.IUIBase;
> -import org.apache.flex.events.Event;
> -
> -[DefaultProperty("children")]
> -
> -/**
> - *  The Parallel effect animates set of effects at the
> - *  same time.
> - *
> - *  @langversion 3.0
> - *  @playerversion Flash 10.2
> - *  @playerversion AIR 2.6
> - *  @productversion FlexJS 0.0
> - */
> -public class Parallel extends Effect implements IDocument
> -{
> -
> -//--
> 
> -//
> -//  Constructor
> -//
> -//--
> 
> -
> -/**
> - *  Constructor.
> - *
> - *  @langversion 3.0
> - *  @playerversion Flash 9
> - *  @playerversion AIR 1.1
> - *  @productversion Flex 3
> - */
> -public function Parallel()
> -{
> -super();
> -}
> -
> -//--
> 
> -//
> -//  Variables
> -//
> -//--
> 
> -
> -   /**
> -*  @private
> -*  The document.
> -*/
> -   private var document:Object;
> -
> -   /**
> -*  @private
> -*  The target.
> -*/
> -   private var target:IUIBase;
> -
> -   /**
> -*  The children.
> -*/
> -   public var children:Array;
> +   import org.apache.flex.effects.beads.ParallelPlayBead;
>
>
>

RE: [FlexJS] "MDL + VS Code" ready to go?

[Yishay Weiss]

It sounds like you’ve got your expectations levels right. It’s not at 1.0, but 
it should be good enough for a simple project. The community here has been very 
responsive when we’ve encountered problems (and we have), which to some degree 
makes the bet safer.



From: OK
Sent: Monday, January 30, 2017 1:43 PM
To: dev@flex.apache.org
Subject: [FlexJS] "MDL + VS Code" ready to go?



Hi guys,
first thanks again to all of you for all the efforts to push FlexJS in the
right direction!

For an upcoming simple project I maybe have the chance to choose FlexJS.
Going with FlexJS would be great cause the best way to legitimate any kind
of effort regarding the FlexJS framework within the scope of my daily job is
to have at least an FlexJS app in production.

The main purpose of the upcoming project/app is to just to collect some data
by providing some material design based forms. My Idea is to build the
"consumer UI" with FlexJS and the probably more complex "admin UI" with the
standard Flex SDK.

Cause I've not followed the complete discusson here in the past I wonder if
the current code base is stable and complete enough to realize such an app
with FlexJS.
I understand 1.0 is not reality yet and I don't expect a perfect working
framework but if I suggest FlexJS as a potential candiate for us I'd like to
make sure not to spend too much time with framework issues.

Could anybody share his expericance?

Thanks,
Olaf










--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-VS-Code-ready-to-go-tp58795.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

RE: [FlexJS] Parallel Effect

[Yishay Weiss]

Thanks Piotr and Alex. It’ll be an interesting exercise to see if this can be 
made into  a strand. My issue with ParallelWithReverse is that Parallel already 
implements IEffect which has reverse(). What does that say about Parallel? Does 
it or does it not implement reverse()? If there were a way in AS3 to create an 
interface that extends multiple parents I would opt for having IEffect extends 
IReversible, IPausible, etc. and then creating classes that pick the interfaces 
they actually implement. As things stand, nothing seems like a clean 
implementation.



In a similar way, making Parallel a strand would probably mean that it doesn’t 
implement IEffect because we don’t know in advance whether it actually 
implements reverse(), pause(), etc.



From: Alex Harui
Sent: Sunday, January 22, 2017 5:16 PM
To: dev@flex.apache.org
Subject: Re: [FlexJS] Parallel Effect




On 1/22/17, 5:05 AM, "piotrz"  wrote:

>Hi Yishay,
>
>Personally I'm always for as small class as we can. My +1 for
>ParallelWithReverse

I agree.

It might be worth considering making a subclass of Parallel that is a
Strand so the reverse, pause and stop can be beads.  Are there more than
one way to do reverse, stop, pause, like play non-linear tweens backwards
or just play the timeline backwards?

My 2 cents,
-Alex

RE: [FlexJS] Some things still missing ni FlexJS

[Yishay Weiss]

We’re using PureMVC with FlexJS.



From: Vincent
Sent: Wednesday, January 11, 2017 12:04 PM
To: dev@flex.apache.org
Subject: Re: [FlexJS] Some things still missing ni FlexJS



Hi Carlos,

I agree with you. AMF support is essential for us to start thinking
porting our Flex apps to FlexJS.

I use MVC architecture with the support of Parsley 3 for :

- Dependency Injection
- Messaging
- Managed command (synchronous and asynchronous)

Is there an equivalent of this tools in the current version of FlexJS ?

Cheers.

Vincent.


Le 11/01/2017 à 10:43, Carlos Rovira a écrit :
> Hi Alex,
>
> I think many people in this thread are saying "No, we'll not go to
> production without AMF and basic module support". IMHO, it would be very
> difficult to say we have 1.0 without that, since AMF/RemoteObject was in
> almost 99% of old Flex SDK, with some HTTPServices and almost no
> WebServices (I mean the MXML object).
>
> As well, for a basic experiment, people could go without modules, but for a
> producction App, a basic load of modules is needed.
>
> Then, i18n, Routing, Unit and Functionality testing and so on should come,
> but for me (If I must to choose) that could come after 1.0
>
> For example, in my own company, without AMF and Modules I don't have enough
> to put FlexJS over React to ask people to use it over the other... (and I
> know that we'll find many other little things we need in the road)
>
> Just my 2ctns
>
>
> 2017-01-10 18:11 GMT+01:00 Alex Harui :
>
>> In my mind, there is little doubt that someone will someday implement AMF
>> and not-unloadable modules.  The question is when?  IMO, as soon as
>> someone can tell us they've gone to production with the code we have, I'm
>> willing to call that 1.0, and the people who wrote that app probably
>> migrated a single SWF, single-language, XML or REST app.  Regular Flex
>> grew just fine and it didn’t support modules in 1.0.
>>
>> For sure, as we add modules, AMF, I18N, we'll gain more customers, but I
>> am hesitant to say these are all 1.0 required features.
>>
>> Thoughts?
>> -Alex
>>
>> On 1/10/17, 6:28 AM, "Dev LFM"  wrote:
>>
>>> +1
>>>
>>> 2017-01-10 14:09 GMT+00:00 Fréderic Cox :
>>>
 AMF is also essential for us to take FlexJS serious as a replacement to
 Flex

 On Tue, Jan 10, 2017 at 2:41 PM, Vincent  wrote:

> Hello,
>
> Same points than Christopher : AMF and modules.
> The first is essential for us.
>
> Vincent.
>
>
>
> Le 10/01/2017 à 13:07, Christofer Dutz a écrit :
>
>> +1 for the AMF and +1 for not-unloadable modules.
>>
>> I see it the same way as Carlos. At the moment I see FlexJS as an
>> opportunity for companies to get out of the dilemma of being stuck
 in a
>> dead end with their existing Flex applications.
>> Supporting things like modules and AMF will ease the migration costs
>> dramatically. Even if AMF might be a touch slower than JSON I still
 think
>> it’s worth being supported.
>>
>> Chris
>>
>> Am 10.01.17, 12:14 schrieb "carlos.rov...@gmail.com im Auftrag von
>> Carlos Rovira" > carlos.rov...@codeoscopic.com>:
>>
>>   "IMO, this has two halves:  non-unloadable modules is relatively
>> straight
>>   forward to do.  Unloadable modules will be a ton of work.  IIRC,
>> Flex 1.0
>>   and I think even Flex 2.x grew its customer base without
 unloadable
>>   modules."
>>If non-unloadable modules is easy to implement, I think it
>> should go ASAP.
>>   Then we could left unloadable modules por the future...
>>For me, AMF is a must, since many companies are using it,
 and
 I
>> expect many
>>   of them switch from old Flex to FlexJS if it's as easy as change
>> only the
>>   frontend. Change server code means no easy way to change, so
 stick
>> in old
>>   code
>>Thanks
>>  2017-01-08 9:52 GMT+01:00 Harbs <
>> harbs.li...@gmail.com>:
>>> I agree that skinning is harder than it should be.
>>   >
>>   > For one thing: There’s too many attributes which are set
 directly.
>> More
>>   > extensive use of CSS would make skinning easier.
>>   >
>>   > On Jan 8, 2017, at 10:49 AM, Christofer Dutz <
>> christofer.d...@c-ware.de>
>>   > wrote:
>>   >
>>   > > From my side I’m missing skinnable components. I really
 loved
>> the way I
>>   > could create applications with skinning.
>>   >
>>   >
>> --
>>Carlos Rovira
>>   Director General
>>   M: +34 607 22 60 05
>>   

FW: [FlexJS, MDL] Questions on Slider

[Yishay Weiss]

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Tuesday, January 10, 2017 12:32 PM
To: Carlos Rovira<mailto:carlos.rov...@codeoscopic.com>
Subject: RE: [FlexJS, MDL] Questions on Slider


My question is when CHANGE is dispatched. Is it on MOUSE_MOVE or on MOUSE_UP? 
Thanks.







From: Carlos Rovira<mailto:carlos.rov...@codeoscopic.com>
Sent: Tuesday, January 10, 2017 12:30 PM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>
Subject: Re: [FlexJS, MDL] Questions on Slider



Hi Yishayw,

I follow the js:Slider guidelines to get mdl:Slider to work. Take into
account that mdl:Slider is only JS, although there are some SWF code due to
the initial copy/paste. We'll have to clean code as we get to a final
release. The events assigned in the strand are:

goog.events.listen(UIBase(_strand).element, goog.events.EventType.CHANGE,
handleChange, false, this);
goog.events.listen(UIBase(_strand).element,
goog.events.EventType.INPUT, handleInput, false, this);

What are the events MDL Slider throws, then we route it through FlexJS
events.



2017-01-09 12:06 GMT+01:00 yishayw <yishayj...@hotmail.com>:

> I noticed there were some differences between the MDL and the basic version
> regarding events. One difference is the name: 'change', the other is that
> 'change' is thrown on MOUSE_UP but not on MOUSE_MOVE.
>
> Are these differences by design?
>
>
>
> --
> View this message in context: http://apache-flex-
> development.247.n4.nabble.com/FlexJS-MDL-Questions-on-
> Slider-tp58041.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>



--

Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
http://www.avant2.es

Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.

De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.

RE: [FlexJS] Selenium Webdriver Integrationtests

[Yishay Weiss]

Whichever path is taken I’d like to see more testing on the swf side. It seems 
there’s little community interest now in making flash objects, which is inline 
with the general public’s perception of flash as a thing from the past. Still, 
my experience with working with FlexJS has been that the flash workflow is 
still much faster than the HTML one. If we can keep functional parity between 
flash and JS components, I think developers would benefit significantly.





From: Christofer Dutz
Sent: Tuesday, January 10, 2017 11:40 AM
To: dev@flex.apache.org
Subject: Re: [FlexJS] Selenium Webdriver Integrationtests



Yeah exactly: Leave things the way they are with the old SDK, but build up a 
proper unit-test and integration-test suite for FlexJS using FlexUnit for 
Unit-Tests (located in the modules they test) and Integration-Tests using 
Selenium (usually in dedicated testsuite modules).

I would rather invest time in getting FlexUnit to work with FlexJS than to 
spend time fixing Mustella … Was the next thing on my list after finishing 
ASDoc static html generation … really have to continue working on that :-(

Chris

Am 10.01.17, 10:31 schrieb "carlos.rov...@gmail.com im Auftrag von Carlos 
Rovira" :

Hi,

just to be sure we are talking about the same. The discussion is about to
left Mustella for old Flex SDK and go with Selenium for new FlexJS?

I did some work in the past fixing Mustella and I must to say that is a
real pain, but I'm ok to not spend more time on it and Flex SDK but for
fixing purposes.

Regarding new FlexJS, my vote is clear to go with Selenium. Although I have
little experience with that I think something that is more standard,
integrates well with Maven and has a workflow that the community likes, is
a better way since we are making it from Zero.

Thanks Chris for working on this.

Carlos


2017-01-09 23:22 GMT+01:00 Christofer Dutz :

> Hi Alex,
>
> first of all I think we Need to distinguish between unit-tests and
> functional-tests.
>
> For Unit-Tests I think FlexUnit should be the way to go. Ideally runnable
> in both SWF and JS. Here writing Tests in Flex(JS) is a good Thing.
>
> For Functional-Tests, pure frontend Tests are usually only one of the
> cases. I previously used JUnit-based Tests to Setup the backend and run 
the
> frontend Tests against a well prepared backend. Also do Frameworks like
> JUnit and even more TestNG provide great Support asynchron testing and for
> data-driven Tests. And I would like to mention that I used Tools like
> selenium to test Flex applications by utilizing the Flex Automation API,
> which worked like a charm. Ok … guess we would need something like that.
>
> I would rather go down the path of well established and stable tools
> instead of putting the burdon of learning yet another tool to provide
> functionality on people.
>
> Have any others had a look at the one Test I created? Would be interested
> in some more oppinions.
>
> Chris
>
>
> Von meinem Samsung Galaxy Smartphone gesendet.
>
>
>  Ursprüngliche Nachricht 
> Von: Alex Harui 
> Datum: 09.01.17 19:47 (GMT+01:00)
> An: dev@flex.apache.org
> Betreff: Re: [FlexJS] Selenium Webdriver Integrationtests
>
> The goal of Mustella was to write tests in a declarative language, in this
> case, MXML.  That way, the test could be "interpreted" instead of just
> run, so the test harness could have control over timing and some other
> things that are really tricky in Flash like script timeouts and needing to
> allow the player to render.
>
> MXML would theoretically make tests shorter to write for the same reasons
> folks like declarative languages in general.  And reduce errors, possibly
> allow automated test generation, etc.
>
> So maybe the first question is:  Do we want to write tests that run on
> both SWF and JS?  I think we should since that reduces time to create
> tests for both platforms and potentially add some third platform in the
> future.  But if you are only interested in one platform, then sure, go
> ahead and leverage what is popular and available for that one platform.
>
> And yes, it could be easier to take what is available for JS and back port
> it to SWF.  I was just trying to leverage what we (Apache and not Adobe)
> have in our repos.  There are a lot of existing tests for the regular Flex
> SDK that could potentially be used as is or with small modifications.
>
> Is Mustella/Marmotinni buggy, poorly documented, in need of improvement?
> Yes.  It was never production-grade but was used to help us ship