Re: [FLEXJS] ASDoc App

[Alex Harui]

On 12/16/16, 11:28 PM, "omup...@gmail.com on behalf of OmPrakash
Muppirala"  wrote:

>On Fri, Dec 16, 2016 at 9:45 PM, Alex Harui  wrote:
>
>>
>>
>> On 12/16/16, 7:05 PM, "omup...@gmail.com on behalf of OmPrakash
>>Muppirala"
>>  wrote:
>>
>> >On Dec 16, 2016 3:15 PM, "Alex Harui"  wrote:
>> >
>> >Or could our framework dump out the resulting DOM and generate the
>>static
>> >HTML that way?
>> >
>> >
>> >You are probably the only person who could build and maintain this :-)
>> >I would say,  XSLT sounds easier than this.
>> >
>>
>> Maybe I'm not understanding something, but IMO, XSLT is an alternative
>>for
>> ASDoc, but isn't an alternative for all other FlexJS applications.
>
>
>XSLT is a tool/language to modify the generated AsDoc into HTML.  As I
>said
>earlier, we could also build the docs as an interactive web app.  One does
>not have to necessarily replace another.
>

Maybe I'm too idealistic, but IMO, since we are project for RIAs, it bugs
me every time our web presence displays data without using Flex or FlexJS.
 That's why Peter is trying to build out the team page as a FlexJS app.
So my line of thinking is: folks have limited time to contribute, so
spending that limited resource on static site generation of data is a bit
contradictory.  We should spend that limited time on making sure that
FlexJS apps don't have limitations that make even us choose not to use our
own product.


>
>>   Is the
>> only way FlexJS apps can work with search engines going to be to use
>> PhantomJS or can we and should make something better?
>>
>> Thinking about static generation from a FlexJS app, it seems to be there
>> are several pieces:
>> 1) when is all data loaded and JS run so we can start the dump?
>> 2) the dump is a simple DOM tree walk
>> 3) how do we save the dump?
>>
>
>I don't understand your proposal.  We have javascript, css and json as
>separate entities.  You need to have a (headless) browser running the code
>and consuming the json to generate the HTML.  Are you proposing that a DOM
>is created without a browser?

Sort of.  This is a totally new idea to me, so I haven't spent too much
time thinking about it, but last night I had the idea of using AIR.  Maybe
we can build an AIR app that loads the output from FlexJS, and basically
crawls it, but saves out the DOM tree as HTML.  Of course, I could just be
dreaming...

Thoughts?
-Alex

Re: [DISCUSS] Apache Flex SDK 4.16 RC1 release

[Justin Mclean]

Hi

> I will be able to test around 4 hours from now.

Thanks much appreciated.

Once we had a couple of people test the CI artefact (which I assume may take a 
day or so) I’ll create the official RC and call for a vote.

Justin

[4.16.0] # Apache Flex SDK 4.16.0 nightly build 168: Successful

[flex . ci . builds]

flex-sdk_release-candidate - Build #168 - Successful

Changes since last build:
[jmclean] Changed saxon download link to one that works


For more information, check the console output at 
http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_release-candidate/168/.

Re: [DISCUSS] Apache Flex SDK 4.16 RC1 release

[OmPrakash Muppirala]

I will be able to test around 4 hours from now.

Thanks,
Om


On Dec 17, 2016 4:55 PM, "Justin Mclean"  wrote:

> Hi,
>
> OK I found a saxon mirror URL that works (but it may of course break
> again) and can now make a release candidate. Before I do can people please
> check out the build on the CI box.
>
> Also be aware that I will have extremely limited internet access (no
> phone, some access via satellite) from Friday my time (GMT +10) onwards and
> it’s unlikely that I'll have the bandwidth to upload any further RCs for
> several weeks after that date.
>
> Thanks,
> Justin

Re: [DISCUSS] Apache Flex SDK 4.16 RC1 release

[Justin Mclean]

Hi,

OK I found a saxon mirror URL that works (but it may of course break again) and 
can now make a release candidate. Before I do can people please check out the 
build on the CI box. 

Also be aware that I will have extremely limited internet access (no phone, 
some access via satellite) from Friday my time (GMT +10) onwards and it’s 
unlikely that I'll have the bandwidth to upload any further RCs for several 
weeks after that date.

Thanks,
Justin

[4.16.0] # Apache Flex SDK 4.16.0 nightly build 167: Successful

[flex . ci . builds]

flex-sdk_release-candidate - Build #167 - Successful

Changes since last build:
No changes

For more information, check the console output at 
http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_release-candidate/167/.

How to register a list of classes to be able to parse an MXML document that uses namespaces

[flex capacitor]

I'm parsing an MXML document and then creating the elements. This would
allow me to show a live preview of an MXML document at runtime. So far what
I have is based using my own XML document that has a list of components in
where the node name was a one to one match with a qualified class name.





And I have been, for the time being, mostly ignoring the namespace and just
using the Spark component set.

But now it's necessary to support separate namespaces and each namespace
can have it's own user defined prefix. So my goal now is to parse an MXML
document and get the correct class for the XML node.

I'm having difficulty with this. Mainly there are four parts that are
interrelated: the prefix, the namespace, the node name and the definition.

I've found a few things to help though. SimpleXMLEncoder, XMLEncoder,
XMLDecoder, SchemaTypeRegistry, SchemaManager. These are all Flex excluded
classes.

I have something working but it's hacky, and it feels like something is
missing so I don't want to start off on that and it's fragile since it
doesn't handle certain scenarios. Before I post any of the code I've been
working on can someone suggest how they'd do it?

Plus, using the classes above, like SchemaManager and SchemaTypeRegistry
etc, it seems they expect an XSD for the object definitions (like Button).
I couldn't find and XSD for the Adobe or Apache Flex component set. Up
until now I've been able to parse MXML using the information in the
metadata of the classes and that seems to work fine for the most part but
again I wouldn't mind hearing suggestions on that as well.

Also, I'm attempting to parse an MXML document at *runtime*, not compile
time.

PS. Some research has lead me to ~FlexSDK/frameworks/flex-config.xml. That
file lists namespaces and manifests that list the classes in those
namespaces.

Re: AW: [FlexJS] Updated Closure compiler from v20151015 to v20161201

[Alex Harui]

I don't think closure compiler is involved in a library build.

Sent from my LG G3, an AT 4G LTE smartphone

-- Original message--
From: Christofer Dutz
Date: Sat, Dec 17, 2016 2:21 PM
To: dev@flex.apache.org;
Subject:AW: [FlexJS] Updated Closure compiler from v20151015 to v20161201

It doesn't report errors, because I had to disable that because there we always 
closure errors in normal execution :-(





Von meinem Samsung Galaxy Smartphone gesendet.


 Ursprüngliche Nachricht 
Von: Alex Harui 
Datum: 17.12.16 21:08 (GMT+01:00)
An: joshtynj...@gmail.com, dev@flex.apache.org
Betreff: Re: [FlexJS] Updated Closure compiler from v20151015 to v20161201

For some reason the maven build did not report failure.  Errors were in the 
console log.  I plan to look into that tonight.

The ci maven build is failing in the distribution step.  Hopefully Chris can 
help.

Sent from my LG G3, an AT 4G LTE smartphone

-- Original message--
From: Josh Tynjala
Date: Sat, Dec 17, 2016 8:15 AM
To: dev@flex.apache.org;
Subject:Re: [FlexJS] Updated Closure compiler from v20151015 to v20161201

Oh, right, I forgot that Maven doesn't use the compiler's config files, for
some reason. I wish it would so that we could keep the builds in sync
easier. Oh well. Thanks, Alex!

- Josh

On Dec 16, 2016 10:41 PM, "Alex Harui"  wrote:

> Thanks Josh!  I had to make one fix for Maven in flex-typedefs, but your
> changes build with Ant and Maven locally for me.
>
> -Alex
>
> On 12/16/16, 3:42 PM, "Josh Tynjala"  wrote:
>
> >Hey folks,
> >
> >I updated flex-falcon to use a newer build of Closure compiler,
> >specifically v20161201. This also required an update of the Guava
> >dependency from v17.0 to v20.0. I have made the required changes to the
> >dependencies for both Ant and Maven builds.
> >
> >An update to Closure compiler means that we have the latest features and
> >bug fixes from Google for optimizing our JS release builds. For instance,
> >one new feature that prompted my desire to update should allow us to
> >improve JS source maps for release builds (to step through the original
> >ActionScript instead of the generated js-debug JavaScript). It also means
> >updated externs with the newest JavaScript browser APIs becoming exposed
> >to
> >ActionScript. Finally, the v20151015 build is getting to be over a year
> >old
> >now, and the longer we wait to update, the harder it will become!
> >
> >This change also affected the flex-typedefs and flex-asjs repositories a
> >bit. I had to make a few tweaks here and there because Closure compiler or
> >the externs became a little more strict, and some APIs were renamed. I
> >think I got everything running properly because the DataBindingExample
> >works correctly, but I encourage you to test more examples to be sure that
> >I didn't miss anything.
> >
> >If you're using the Ant build, you need to be sure to wipe before building
> >each of the repositories after you pull the latest changes. Be sure to
> >pull
> >from all three repos! This will ensure that the new dependencies are
> >downloaded to replace the old ones, and everything will be in sync.
> >
> >flex-falcon:
> >ant wipe-all
> >
> >flex-typedefs:
> >ant wipe
> >
> >flex-asjs:
> >ant super-clean
> >
> >I ran all of these on the Ant CI server, and I'll make tweaks as needed if
> >anything appears to break.
> >
> >- Josh
>
>

AW: Unable to check out source repo - URL down or moved?

[Christofer Dutz]

All services were out because of a network outage for about two hours, but ask 
working again :-)



Von meinem Samsung Galaxy Smartphone gesendet.


 Ursprüngliche Nachricht 
Von: Justin Mclean 
Datum: 17.12.16 23:14 (GMT+01:00)
An: dev@flex.apache.org
Betreff: Re: Unable to check out source repo - URL down or moved?

Hi,

BTW it does look like there was an outage a few hours ago and that it is now 
fixed.

Thanks,
Justin

AW: [FlexJS] Updated Closure compiler from v20151015 to v20161201

[Christofer Dutz]

It doesn't report errors, because I had to disable that because there we always 
closure errors in normal execution :-(





Von meinem Samsung Galaxy Smartphone gesendet.


 Ursprüngliche Nachricht 
Von: Alex Harui 
Datum: 17.12.16 21:08 (GMT+01:00)
An: joshtynj...@gmail.com, dev@flex.apache.org
Betreff: Re: [FlexJS] Updated Closure compiler from v20151015 to v20161201

For some reason the maven build did not report failure.  Errors were in the 
console log.  I plan to look into that tonight.

The ci maven build is failing in the distribution step.  Hopefully Chris can 
help.

Sent from my LG G3, an AT 4G LTE smartphone

-- Original message--
From: Josh Tynjala
Date: Sat, Dec 17, 2016 8:15 AM
To: dev@flex.apache.org;
Subject:Re: [FlexJS] Updated Closure compiler from v20151015 to v20161201

Oh, right, I forgot that Maven doesn't use the compiler's config files, for
some reason. I wish it would so that we could keep the builds in sync
easier. Oh well. Thanks, Alex!

- Josh

On Dec 16, 2016 10:41 PM, "Alex Harui"  wrote:

> Thanks Josh!  I had to make one fix for Maven in flex-typedefs, but your
> changes build with Ant and Maven locally for me.
>
> -Alex
>
> On 12/16/16, 3:42 PM, "Josh Tynjala"  wrote:
>
> >Hey folks,
> >
> >I updated flex-falcon to use a newer build of Closure compiler,
> >specifically v20161201. This also required an update of the Guava
> >dependency from v17.0 to v20.0. I have made the required changes to the
> >dependencies for both Ant and Maven builds.
> >
> >An update to Closure compiler means that we have the latest features and
> >bug fixes from Google for optimizing our JS release builds. For instance,
> >one new feature that prompted my desire to update should allow us to
> >improve JS source maps for release builds (to step through the original
> >ActionScript instead of the generated js-debug JavaScript). It also means
> >updated externs with the newest JavaScript browser APIs becoming exposed
> >to
> >ActionScript. Finally, the v20151015 build is getting to be over a year
> >old
> >now, and the longer we wait to update, the harder it will become!
> >
> >This change also affected the flex-typedefs and flex-asjs repositories a
> >bit. I had to make a few tweaks here and there because Closure compiler or
> >the externs became a little more strict, and some APIs were renamed. I
> >think I got everything running properly because the DataBindingExample
> >works correctly, but I encourage you to test more examples to be sure that
> >I didn't miss anything.
> >
> >If you're using the Ant build, you need to be sure to wipe before building
> >each of the repositories after you pull the latest changes. Be sure to
> >pull
> >from all three repos! This will ensure that the new dependencies are
> >downloaded to replace the old ones, and everything will be in sync.
> >
> >flex-falcon:
> >ant wipe-all
> >
> >flex-typedefs:
> >ant wipe
> >
> >flex-asjs:
> >ant super-clean
> >
> >I ran all of these on the Ant CI server, and I'll make tweaks as needed if
> >anything appears to break.
> >
> >- Josh
>
>

Re: Unable to check out source repo - URL down or moved?

[Justin Mclean]

Hi,

BTW it does look like there was an outage a few hours ago and that it is now 
fixed.

Thanks,
Justin

Re: Unable to check out source repo - URL down or moved?

[Justin Mclean]

Hi,

BTW it does look like there was an outage a few hours ago and that it is now 
fixed.

Thanks,
Justin

Re: Unable to check out source repo - URL down or moved?

[OmPrakash Muppirala]

If you are simply checking out the code, you can try the github mirror as
well:
https://github.com/apache/flex-sdk
https://github.com/apache/flex-asjs

Hope that helps for now.

Thanks,
Om

On Sat, Dec 17, 2016 at 1:11 PM, Justin Mclean 
wrote:

> Hi,
>
> > Hi everyone, I'm trying to check out the sources for Flex SDK and FLex JS
> > from the repos on this page:
>
> The URLs are correct and I’m not seeing any issues at [1]. Perhaps just
> try again?
>
> Thanks,
> Justin
>
> 1. http://status.apache.org

Re: Unable to check out source repo - URL down or moved?

[Justin Mclean]

Hi,

> Hi everyone, I'm trying to check out the sources for Flex SDK and FLex JS
> from the repos on this page:

The URLs are correct and I’m not seeing any issues at [1]. Perhaps just try 
again?

Thanks,
Justin

1. http://status.apache.org

Re: [FlexJS] Updated Closure compiler from v20151015 to v20161201

[OmPrakash Muppirala]

Josh, will this affect the npm flexjs installer?  What are the changes I
need to make?

Thanks,
Om

On Sat, Dec 17, 2016 at 9:40 AM, Alex Harui  wrote:

> For some reason the maven build did not report failure.  Errors were in
> the console log.  I plan to look into that tonight.
>
> The ci maven build is failing in the distribution step.  Hopefully Chris
> can help.
>
> Sent from my LG G3, an AT 4G LTE smartphone
>
> -- Original message--
> From: Josh Tynjala
> Date: Sat, Dec 17, 2016 8:15 AM
> To: dev@flex.apache.org;
> Subject:Re: [FlexJS] Updated Closure compiler from v20151015 to v20161201
>
> Oh, right, I forgot that Maven doesn't use the compiler's config files, for
> some reason. I wish it would so that we could keep the builds in sync
> easier. Oh well. Thanks, Alex!
>
> - Josh
>
> On Dec 16, 2016 10:41 PM, "Alex Harui"  wrote:
>
> > Thanks Josh!  I had to make one fix for Maven in flex-typedefs, but your
> > changes build with Ant and Maven locally for me.
> >
> > -Alex
> >
> > On 12/16/16, 3:42 PM, "Josh Tynjala"  wrote:
> >
> > >Hey folks,
> > >
> > >I updated flex-falcon to use a newer build of Closure compiler,
> > >specifically v20161201. This also required an update of the Guava
> > >dependency from v17.0 to v20.0. I have made the required changes to the
> > >dependencies for both Ant and Maven builds.
> > >
> > >An update to Closure compiler means that we have the latest features and
> > >bug fixes from Google for optimizing our JS release builds. For
> instance,
> > >one new feature that prompted my desire to update should allow us to
> > >improve JS source maps for release builds (to step through the original
> > >ActionScript instead of the generated js-debug JavaScript). It also
> means
> > >updated externs with the newest JavaScript browser APIs becoming exposed
> > >to
> > >ActionScript. Finally, the v20151015 build is getting to be over a year
> > >old
> > >now, and the longer we wait to update, the harder it will become!
> > >
> > >This change also affected the flex-typedefs and flex-asjs repositories a
> > >bit. I had to make a few tweaks here and there because Closure compiler
> or
> > >the externs became a little more strict, and some APIs were renamed. I
> > >think I got everything running properly because the DataBindingExample
> > >works correctly, but I encourage you to test more examples to be sure
> that
> > >I didn't miss anything.
> > >
> > >If you're using the Ant build, you need to be sure to wipe before
> building
> > >each of the repositories after you pull the latest changes. Be sure to
> > >pull
> > >from all three repos! This will ensure that the new dependencies are
> > >downloaded to replace the old ones, and everything will be in sync.
> > >
> > >flex-falcon:
> > >ant wipe-all
> > >
> > >flex-typedefs:
> > >ant wipe
> > >
> > >flex-asjs:
> > >ant super-clean
> > >
> > >I ran all of these on the Ant CI server, and I'll make tweaks as needed
> if
> > >anything appears to break.
> > >
> > >- Josh
> >
> >
>

Re: [FlexJS] Updated Closure compiler from v20151015 to v20161201

[Alex Harui]

For some reason the maven build did not report failure.  Errors were in the 
console log.  I plan to look into that tonight.

The ci maven build is failing in the distribution step.  Hopefully Chris can 
help.

Sent from my LG G3, an AT 4G LTE smartphone

-- Original message--
From: Josh Tynjala
Date: Sat, Dec 17, 2016 8:15 AM
To: dev@flex.apache.org;
Subject:Re: [FlexJS] Updated Closure compiler from v20151015 to v20161201

Oh, right, I forgot that Maven doesn't use the compiler's config files, for
some reason. I wish it would so that we could keep the builds in sync
easier. Oh well. Thanks, Alex!

- Josh

On Dec 16, 2016 10:41 PM, "Alex Harui"  wrote:

> Thanks Josh!  I had to make one fix for Maven in flex-typedefs, but your
> changes build with Ant and Maven locally for me.
>
> -Alex
>
> On 12/16/16, 3:42 PM, "Josh Tynjala"  wrote:
>
> >Hey folks,
> >
> >I updated flex-falcon to use a newer build of Closure compiler,
> >specifically v20161201. This also required an update of the Guava
> >dependency from v17.0 to v20.0. I have made the required changes to the
> >dependencies for both Ant and Maven builds.
> >
> >An update to Closure compiler means that we have the latest features and
> >bug fixes from Google for optimizing our JS release builds. For instance,
> >one new feature that prompted my desire to update should allow us to
> >improve JS source maps for release builds (to step through the original
> >ActionScript instead of the generated js-debug JavaScript). It also means
> >updated externs with the newest JavaScript browser APIs becoming exposed
> >to
> >ActionScript. Finally, the v20151015 build is getting to be over a year
> >old
> >now, and the longer we wait to update, the harder it will become!
> >
> >This change also affected the flex-typedefs and flex-asjs repositories a
> >bit. I had to make a few tweaks here and there because Closure compiler or
> >the externs became a little more strict, and some APIs were renamed. I
> >think I got everything running properly because the DataBindingExample
> >works correctly, but I encourage you to test more examples to be sure that
> >I didn't miss anything.
> >
> >If you're using the Ant build, you need to be sure to wipe before building
> >each of the repositories after you pull the latest changes. Be sure to
> >pull
> >from all three repos! This will ensure that the new dependencies are
> >downloaded to replace the old ones, and everything will be in sync.
> >
> >flex-falcon:
> >ant wipe-all
> >
> >flex-typedefs:
> >ant wipe
> >
> >flex-asjs:
> >ant super-clean
> >
> >I ran all of these on the Ant CI server, and I'll make tweaks as needed if
> >anything appears to break.
> >
> >- Josh
>
>

Unable to check out source repo - URL down or moved?

[Tim Diggle]

Hi everyone, I'm trying to check out the sources for Flex SDK and FLex JS
from the repos on this page:

http://flex.apache.org/dev-sourcecode.html

Requests are timing out - is the server down or are these URLs out of date?

Re: [FlexJS] Updated Closure compiler from v20151015 to v20161201

[Josh Tynjala]

Oh, right, I forgot that Maven doesn't use the compiler's config files, for
some reason. I wish it would so that we could keep the builds in sync
easier. Oh well. Thanks, Alex!

- Josh

On Dec 16, 2016 10:41 PM, "Alex Harui"  wrote:

> Thanks Josh!  I had to make one fix for Maven in flex-typedefs, but your
> changes build with Ant and Maven locally for me.
>
> -Alex
>
> On 12/16/16, 3:42 PM, "Josh Tynjala"  wrote:
>
> >Hey folks,
> >
> >I updated flex-falcon to use a newer build of Closure compiler,
> >specifically v20161201. This also required an update of the Guava
> >dependency from v17.0 to v20.0. I have made the required changes to the
> >dependencies for both Ant and Maven builds.
> >
> >An update to Closure compiler means that we have the latest features and
> >bug fixes from Google for optimizing our JS release builds. For instance,
> >one new feature that prompted my desire to update should allow us to
> >improve JS source maps for release builds (to step through the original
> >ActionScript instead of the generated js-debug JavaScript). It also means
> >updated externs with the newest JavaScript browser APIs becoming exposed
> >to
> >ActionScript. Finally, the v20151015 build is getting to be over a year
> >old
> >now, and the longer we wait to update, the harder it will become!
> >
> >This change also affected the flex-typedefs and flex-asjs repositories a
> >bit. I had to make a few tweaks here and there because Closure compiler or
> >the externs became a little more strict, and some APIs were renamed. I
> >think I got everything running properly because the DataBindingExample
> >works correctly, but I encourage you to test more examples to be sure that
> >I didn't miss anything.
> >
> >If you're using the Ant build, you need to be sure to wipe before building
> >each of the repositories after you pull the latest changes. Be sure to
> >pull
> >from all three repos! This will ensure that the new dependencies are
> >downloaded to replace the old ones, and everything will be in sync.
> >
> >flex-falcon:
> >ant wipe-all
> >
> >flex-typedefs:
> >ant wipe
> >
> >flex-asjs:
> >ant super-clean
> >
> >I ran all of these on the Ant CI server, and I'll make tweaks as needed if
> >anything appears to break.
> >
> >- Josh
>
>

RE: [FlexJS] Image on JS platform

[Yishay Weiss]

This [1] works for me



[1] https://paste.apache.org/61AK



From: Peter Ent
Sent: Friday, December 16, 2016 11:19 PM
To: dev@flex.apache.org
Subject: Re: [FlexJS] Image on JS platform



I meant url. I did not use src.

On 12/16/16, 2:39 PM, "Yishay Weiss"  wrote:

>Have you tried url instead of src?
>
>
>
>From: Peter Ent
>Sent: Friday, December 16, 2016 9:23 PM
>To: dev@flex.apache.org
>Subject: [FlexJS] Image on JS platform
>
>
>
>I'm trying to use  and no image is being
>loaded. Looking at the ImageBase.as code, I don't see how the image src
>is making it to the  element that has been created. Is there a part
>I'm missing or is something disconnected? I'm happy to fix it, I just
>didn't want to undo something that should be working.
>
>-peter

Flex SDK Installer AIR 24 & FP 24

[Ghazi Triki]

Hello,

Flash Player 24 and AIR 24 have been released, however they can't be
installed using Flex SDK Installer. Can anyone update the application files?


-- 
Thanks,
Ghazi Triki