RE: Question: Current state of Flacon to build Flex projects

[Glenn Williams]

Thanks as always for this extensive answer

I'll let you all know how I get on

Regards

glenn

-Original Message-
From: Alex Harui [mailto:aha...@adobe.com] 
Sent: 20 April 2016 17:33
To: dev@flex.apache.org
Subject: Re: Question: Current state of Flacon to build Flex projects



On 4/20/16, 8:47 AM, "Glenn Williams" <i...@tinylion.co.uk> wrote:

>Hi folks,
>
> 
>
>Sorry to bring this up again but im still not sure of the current state 
>of the Falcon compiler regarding straight Flex applications.

Good question.  I honestly don't know, because I haven't not taken the time to 
try it.  Volunteers like yourself are welcome to try it out, report bugs, 
hopefully even fix bugs.  The simplest way to do that would be to install 
FlexJS, then run the bin/mxmlc against an existing Flex project.

I will say that a couple of years ago, I got Falcon to compile a large existing 
Flex project into a SWF and got the SWF to run as far as its initial screen, 
and compile time was only about 10% faster.  And I'm pretty sure any bugs we've 
fixed since then have only made compile time slower instead of faster.  I think 
that's the reason there hasn't been more of a push to swap Falcon in for MXMLC. 
 There was hope that Falcon could deliver 2x or better speed in compiling.  Now 
it might be worth trying this again on a 4+ core SSD machine to see how 
performance currently compares.

If you dig into it, be aware that there are two different MXMLC code-generation 
code paths in Falcon.  FlexJS uses the mxml-children-as-data code path because 
it does a better job of separating out framework dependencies from the 
compiler.  Apache versions of the Flex SDK have the code to support 
mxml-children-as-data compiled output, but it is likely to be buggy.  However, 
if you use the other code path to get output more similar to what MXMLC does, 
Falcon might have more bugs in that output because we haven't exercised those 
code paths when we use FlexJS.  If you need Falcon to work against the Adobe 
Flex SDKs then you have to not use the mxml-children-as-data output.

You probably don't have to know much about compilers to help fix the bugs to 
make Falcon work with an Apache Flex SDK.  If you gamble on using the 
mxml-children-as-data code path, the output from the compiler should be in 
pretty good shape, so any bug fixes would be in the ActionScript in the 
flex-sdk repo.  You should be able to copy lots of code from the FlexJS repo to 
fix most bugs.  The other bugs will be about configuration: making sure the 
-config.xml files and other files are in the right places with the right 
contents.  And if you think the compiler isn't outputting the right code, 
create a test case with FlexJS and if it fails there, then I'll be more 
motivated to look.

Also, as progress is made on making a MX-like and Spark-like component set for 
FlexJS, lots of these bugs in Flex code handling the mxml-children-as-data 
output will have to be fixed.  So, while you could just wait for me to fix it, 
it sure would be nice to have other people helping out.

Thanks,
-Alex

Question: Current state of Flacon to build Flex projects

[Glenn Williams]

Hi folks,

 

Sorry to bring this up again but im still not sure of the current state of
the Falcon compiler regarding straight Flex applications.

 

I've tried to follow posts here as much as possible but I admit to being
slightly confused still.

 

While reading the 'FlexJS identity crisis' thread I noticed Alex saying
'Adobe already used ASC2.0, plus our version of Falcon handles MXML. '

 

I know this was regarding a talk about using falcon to  cross-compile but
does it also mean that Falcon can now replace mxmlc and is able to replace
the old compiler for my Flex projects (I still have several applications
that I have to maintain and build upon. Im also still using flash-builder
for these projects (mainly because that's how they were developed and
despite the slowness and limited features I haven't had time to move the
projects to intellij so if there is any advantage I could get from using
this compiler I'd really like to know.

 

It does sometimes feel a little lonely out here working on what feels like a
technology given early retirement. :)

 

So, if there is anyone on here who knows the current state of Falcon could
you message me. 

 

I seem to remember Adobe promising some continued development of falcon by
whoever was working on it at adobe before they threw the baby away with the
bath water :)

 

I'd also like to take this time to say thanks to all you folks who've made
my life easier with bug fixes etc. 

 

Regards

 

glenn

RE: [DISCUSS] How about bringing Falcon and ASJS together?

[Glenn Williams]

Hi all

As a sub-question:

What's the current state of Falcon for compiling Flex SDK apps?

I've not been able to keep up to date here as much as I'd like to. The last 
time I looked Falcon was not anywhere near complete enough to be used. Is this 
still the case?

Thanks folks

Glenn
tinylion


-Original Message-
From: Alex Harui [mailto:aha...@adobe.com] 
Sent: 27 March 2016 15:31
To: dev@flex.apache.org
Subject: Re: [DISCUSS] How about bringing Falcon and ASJS together?

We've had this discussion before.  Falcon was also intended to be the 
next-generation compiler for the regular Flex SDK, and FalconJX is being 
considered for other non-Apache frameworks like Feathers.

Is it really true that no Maven projects have validation suites against 
downstream projects?  Maybe the integration tests need to be in a different 
repo or something?

-Alex

On 3/27/16, 2:38 AM, "Christofer Dutz"  wrote:

>Hi,
>
>
>I don't know if we had this discussion recently, but I would like to 
>propose to bring together the two sub-projects Falcon and ASJS. The 
>reason for this is that they are naturally tightly connected, which 
>becomes obvious every time a release is coming and internally a lot of 
>tests depend on ASJS and ASJS needs Falcon to be built. This 
>entanglement makes it hard do releases Maven-style. Bringing both 
>together should make a lot of things easier.
>
>
>If the problem is adjusting the build for the merged project, I could 
>disable the cross-cutting tests (as I already have) and do the same 
>Maven conversion for ASJS. As soon as that's done it should be easy to 
>merge both parts.
>
>
>And I would propose to name the project "FlexJS".
>
>
>What do you think?
>
>
>Chris

RE: [jira] [Commented] (FLEX-33083) Flash builder report An internal build error has occurred. See the error log for more information.

[Glenn Williams]

Ive also had this happen with builder 4.7

I actually assumed it was some problem of mine until reading this post

I changed back to sdk 4.7 and all was fine again

I will look into it my end 

-Original Message-
From: Alex Harui (JIRA) [mailto:j...@apache.org] 
Sent: Wednesday, June 05, 2013 10:15 PM
To: dev@flex.apache.org
Subject: [jira] [Commented] (FLEX-33083) Flash builder report An internal 
build error has occurred. See the error log for more information.


[ 
https://issues.apache.org/jira/browse/FLEX-33083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13676359#comment-13676359
 ] 

Alex Harui commented on FLEX-33083:
---

Well, technically, Flash Builder 4.5 isn't supported for Apache Flex, but it 
shouldn't be a factor for this scenario.  I updated mxmlc to show more 
information for this exception.  I've attached an updated mxmlc.jar which you 
can use to replace the one in the lib folder of your Apache Flex SDK.  If you 
compile the app from the command line you should see a better error message. I 
couldn't find an easy way to get that better information into the console, log, 
or problems pane.

When I compile your project from the command line, I now get: 
flex.messaging.config.ConfigurationException: channel not found for reference 
'weborb-rtmp-messaging' in destination 'SampleRTMPDestination'.

You didn't mention if you are using Blaze or DataServices and which version.  
I'm not sure why with Adobe Flex 4.6 you aren't seeing this same problem, but 
it could be that I still don't have your test case set up properly.  I only set 
up to use Blaze 4, not DataServices or whatever Adobe calls it these days.


 Flash builder report An internal build error has occurred. See the error log 
 for more information. 
 --
 ---

 Key: FLEX-33083
 URL: https://issues.apache.org/jira/browse/FLEX-33083
 Project: Apache Flex
  Issue Type: Bug
  Components: Project Management
 Environment: Flash builder 4.6  , sdk 4.8.0  
Reporter: Alex Harui
Assignee: Alex Harui
  Labels: easyfix
 Attachments: mxmlc.jar, weborb.codegen.test.zip


 1. download the source kit from 
 https://svn.apache.org/repos/asf/incubator/flex/trunk
 2. run ant release
 3. extract apache-flex-sdk-4.8.0-incubating-bin.zip to new folder 4. 
 extract AIR Integration Kit.zip to folder
 5 copy additional files for Flash Ide ( frameworks/libs\player\* and 
 frameworks\*-config.xm) 6.create a simple project with reference to 
 RemoteObject private var remote:RemoteObject; remote = new 
 RemoteObject; flash builder log file :
 !ENTRY com.adobe.flexbuilder.project 4 43 2012-06-08 18:27:39.112 
 !MESSAGE Uncaught exception in compiler !STACK 0 
 java.lang.NullPointerException
   at flex2.compiler.CompilerAPI.getMessagingClasses(CompilerAPI.java:1730)
   at flex2.compiler.CompilerAPI.compile(CompilerAPI.java:1538)
   at flex2.tools.oem.Application.compile(Application.java:1357)
   at flex2.tools.oem.Application.recompile(Application.java:1295)
   at flex2.tools.oem.Application.compile(Application.java:894)
   at 
 flex2.tools.flexbuilder.BuilderApplication.compile(BuilderApplication.java:367)
   at 
 com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder$MyBuilder.mybuild(ASApplicationBuilder.java:319)
   at 
 com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder.build(ASApplicationBuilder.java:129)
   at 
 com.adobe.flexbuilder.multisdk.compiler.internal.ASBuilder.build(ASBuilder.java:198)
   at 
 com.adobe.flexbuilder.multisdk.compiler.internal.ASItemBuilder.build(ASItemBuilder.java:70)
   at 
 com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.buildItem(FlexProjectBuilder.java:607)
   at 
 com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.build(FlexProjectBuilder.java:382)
   at 
 com.adobe.flexbuilder.project.compiler.internal.FlexIncrementalBuilder.build(FlexIncrementalBuilder.java:187)
   at 
 org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728)
   at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
   at 
 org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
   at 
 org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
   at 
 org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
   at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
   at 
 org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
   at 
 org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351)
   at 
 

RE: SDK Nightly builds?

[Glenn Williams]

I used to test against Adobe nightly builds all the time when they still did
that

Think it would be a good idea as long as it wasn't causing someone a real
headache

-Original Message-
From: Erik de Bruin [mailto:e...@ixsoftware.nl] 
Sent: Monday, June 03, 2013 10:29 AM
To: dev@flex.apache.org
Subject: Re: SDK Nightly builds?

I can do that, where would we want to 'publish' the nightly builds and what
would we include in them?

EdB



On Mon, Jun 3, 2013 at 10:47 AM, Justin Mclean jus...@classsoftware.com
wrote:
 Hi,

 My thinking was the more people that use it the more likely we are to pick
up any issues before making an official release.

 Justin



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

[jira] [Commented] (FLEX-33562) There is no option to change color of selected item text from Dropdownlist. you can only change background color but not selected text color.

[Glenn Williams (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLEX-33562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13659481#comment-13659481
 ] 

Glenn Williams commented on FLEX-33562:
---

the text colour is changed in the actual renderer attached to the list and not 
the droplist itself. I suppose if background colour changes are there as 
properties then maybe the text colour should be too. I like the way the 
components don't have lots of properties but rely on you making a custom skin.

I don't think this is a bug, just another way in which the spark and halo 
models differ

this is another issue where some like the new way spark works and some don't. 

 There is no option to change color of selected item text from Dropdownlist. 
 you can only change background color but not selected text color. 
 --

 Key: FLEX-33562
 URL: https://issues.apache.org/jira/browse/FLEX-33562
 Project: Apache Flex
  Issue Type: Bug
  Components: Spark: DropDownList
Affects Versions: Adobe Flex SDK 4.6 (Release)
 Environment: Windows 7.
Reporter: usman ashraf
  Labels: patch
   Original Estimate: 2h
  Remaining Estimate: 2h

 I was using flex 3.5 . Here I used combobox but when I applied customFont  
 family then data was not showing in list. Then I used spark combobox but 
 there rowcount, prompt issue were facing. Then I decided to use 
 s:dropdownlist and changed flash version 4.6 by applying custom skin. here  
 everything was working fine  but one issue faced again, I am unable to change 
 the selected item text color. there is only property selectionColor or 
 rollOverColor that change the selection color but not text color. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira