Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
Received-SPF: error (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAHS83K=5ROuwrdhCnTZEmB-QbJyqPQ1f4E7HE7D-ee-qsbDQ9A@mail.gmail.com>
References: <JIRA.12659766.1374748533129@arcas>
	<JIRA.12659766.1374748533129.110762.1374748548866@arcas>
	<CAJs+wW31NQ7vw=uyzNuWnwkbmUEMeZs=i3TEnBug-p3B55nytw@mail.gmail.com>
	<CAHS83KkJTegzY_A_WsEa2T7zCqg_amnJVOzSNb8rSWxJxs3bnQ@mail.gmail.com>
	<CAJs+wW1fFLuC=gj9zPg0s8czc=WxrXYcAnBUq7jKD516yQyc-w@mail.gmail.com>
	<CAHS83K=5ROuwrdhCnTZEmB-QbJyqPQ1f4E7HE7D-ee-qsbDQ9A@mail.gmail.com>
Date: Thu, 25 Jul 2013 23:01:00 +0200
Message-ID: 
 <CAJs+wW3nMazL-3oZ9UeuWf0_99-2mrLxYXCaEqCuQKX=FA6jcw@mail.gmail.com>
Subject: Re: [jira] [Created] (FLEX-33634) Flex-Falcon
From: Erik de Bruin <erik@ixsoftware.nl>
To: "dev@flex.apache.org" <dev@flex.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

Terry,

> A.  Where in the downloadable files is a version of Falcon that can be used
> to compile an mxml file?

I'm not sure what you mean by downloadable files. There hasn't been a
release of Falcon yet, so there are no source or binary releases. You
can get the source from git and build the compiler yourself, there is
even a halfway decent README that should help you get started.

> B.  Where can I register to receive nightly updates showing which tests of
> the Falcon compiler have succeeded and which have failed in compiling an
> mxml file in the appropriate Jenkins runs?

You don't have to register. Like everything else in Open Source and
especially with Apache.org, you can see for yourself, it's all
available publicly:

https://builds.apache.org/job/flex-falcon/

> C.  Where can I register to receive notification of each checkin showing
> changes to the Falcon compiler project.

Again, no registration needed. You can create a clone of the git repo
with this command:

git clone https://git-wip-us.apache.org/repos/asf/flex-falcon.git flex-falcon

This clone will have the full history of the development of the Falcon
and FalconJx compilers readily available for your perusal. Do a simple
git pull when you want to check the most recent updates.

HTH,

EdB


>
> On Thu, Jul 25, 2013 at 1:04 PM, Erik de Bruin <erik@ixsoftware.nl> wrote:
>
>> Terry,
>>
>> I don't see where your fear and anger is coming from. The release
>> we're currently working on is purely the Flex SDK; all the
>> improvements and fixes are for SWF output, JavaScript is not even an
>> option.
>>
>> Meanwhile, the work on FlexJS is a separate stream in the project. And
>> even FlexJS will offer the usual SWF output, while ADDING the extra
>> option of 'web native' output as a release build.
>>
>> The Falcon compiler is a fork of the ASC 2.0 compiler and will,
>> together with FalconJx, one day replace the 'old' compiler. More
>> importantly, and what you apparently haven't realised yet, is that the
>> FalconJx cross compiler that's at the core of FlexJS relies heavily on
>> the Falcon compiler. That means, there will be no full FlexJS release
>> WITHOUT a 'completed' Falcon compiler. So, instead of diverting
>> resources away from the pure SDK, FlexJS is actually helping to move
>> the entire project to meet your 'demands'.
>>
>> Please stop with the FUD and help us make Apache Flex an even greater tool.
>>
>> If you want to contribute to the continued support and improvement of
>> the Flex SDK, you can either use the new version of the Installer
>> (currently a Release Candidate) to download and install the SDK to
>> your IDE, or download one the nightly builds from:
>>
>>
>> https://builds.apache.org/job/flex-sdk_release/lastSuccessfulBuild/artifact/out/
>>
>> and work from the command line. Any input you can give the project is
>> much appreciated!
>>
>> Thanks,
>>
>> EdB
>>
>>
>>
>> On Thu, Jul 25, 2013 at 9:35 PM, Terry Corbet <terry.corbet@gmail.com>
>> wrote:
>> > First, it has only been necessary to make such demands because there has
>> > been no championing of this task amongst the primary movers of the Flex
>> > Apache project.  I applaud every improvement, every success that Alex has
>> > in meeting his objective with his unidentified in house customer who what
>> > been driving the allocation of efforts towards their goal, but their goal
>> > was not the primary goal of picking up the support of Flex by the
>> > community.  If you step back and take a hard, objective look at the very
>> > facts motivated by your marketing person's asking for answers to the
>> > business-making decisions that will be made concerning whether or not to
>> > invest in the framework, you will notice that there really are no strong
>> > motivators amongst the thousands of hours you have all spent in turning
>> out
>> > the remarkable 4.10 release.
>> >
>> > I'm sorry, I know that hurts, but the fact of the matter is that the only
>> > reason I have to deciding to compile with 4.10 plus 3.8 instead of 4.6
>> plus
>> > 3.8 is to help you debug/quality-assure the release.  That's an
>> investment
>> > to help the community, not my in house customers.  For my own set of
>> needs
>> > every single advancement is attributable to enhancements in the
>> underlying
>> > Adobe engines from the time of the Flex divestiture.  It is what is in
>> > 11.6, 11.7, 11.8, what is in 3.6, 3.7, 3.8, that I am able to provide a
>> > richer solution today than a year ago.
>> >
>> > That in no way diminishes the importance of what you have accomplished
>> but
>> > if it does not make the point that moving from an application framework
>> > that runs atop the two Adobe virtual machines of Flash Player and AIR to
>> > one that will run atop whomevers browser is completely uninteresting to
>> > some of us invested in Flex for large, complex, compute-intensive,
>> desktop
>> > applications, I don't know what else to say.  I hope that running in
>> > browsers will make tons of folks happy, all I want is that someone be
>> > concerned about making sure that running on desktops and tablets be the
>> > best that it can be.
>> >
>> > Second, what I will contribute is daily testing of Falcon against the
>> needs
>> > of those kinds of applications.
>> >
>> > Third, since I do not have the resources you have at your disposal,
>> cannot
>> > compile the framework, please instruct me on where I can download
>> whatever
>> > set of binaries and any contingent libraries will allow me, just from
>> some
>> > simple command line environment to invoke the equivalent of amxmlc
>> some.as
>> > or amxmlc some.mxml and get a swf file that can be run with adl to give
>> you
>> > feedback.
>> >
>> > Fourth, I am signed up for all the lists of which I am aware, please tell
>> > me where I can watch the nightly progress of Gordon's latest tests
>> against
>> > whatever set of bugs he is working his way through.  If such a list had
>> > ever been published, it would have been possible to construct some test
>> > cases to go against whatever remaining, corner conditions have prevented
>> > your being able to include the Falcon compiler in your 4.10 release.  It
>> is
>> > clear that you ahve such a prioritized list that has helped the wonderful
>> > progress with FalconJX and the JavaScript world.  With some visibility to
>> > your process we ought to be able to surpass that rate of success in
>> getting
>> > Falcon for Flex out the door.
>> >
>> >
>> > On Thu, Jul 25, 2013 at 5:49 AM, Erik de Bruin <erik@ixsoftware.nl>
>> wrote:
>> >
>> >> Ok, Terry, you made your wishes (dare I say demands?) clear. Now I ask
>> >> you this: how are YOU going to contribute to make this happen?
>> >>
>> >> EdB
>> >>
>> >> PS. the Jenkins 'flex-falcon' job has been running nightly for more
>> >> than 2 months now, successfully building and testing both Falcon and
>> >> FalconJx...
>> >>
>> >>
>> >>
>> >>
>> >> On Thu, Jul 25, 2013 at 12:35 PM, J. Terry Corbet (JIRA)
>> >> <jira@apache.org> wrote:
>> >> > J. Terry Corbet created FLEX-33634:
>> >> > --------------------------------------
>> >> >
>> >> >              Summary: Flex-Falcon
>> >> >                  Key: FLEX-33634
>> >> >                  URL:
>> https://issues.apache.org/jira/browse/FLEX-33634
>> >> >              Project: Apache Flex
>> >> >           Issue Type: Wish
>> >> >           Components: Performance: Compiler
>> >> >     Affects Versions: Apache Flex 4.11.0
>> >> >          Environment: The Desktop and the Tablet.
>> >> >             Reporter: J. Terry Corbet
>> >> >
>> >> >
>> >> > If this is not the right place for this request, please tell me where
>> to
>> >> make it.
>> >> >
>> >> > Alex says that the Falcon Compiler is successfully handling some large
>> >> test case he has.  The notes on the Git page say that it is 'almost
>> >> production worthy'.
>> >> >
>> >> > The notes I find show that Erik expressly turned off the testing of
>> the
>> >> compiler so that Jenkins would be clean.
>> >> >
>> >> > OK, you got 4.10 out the door, great job.  Now since it is a top
>> >> priority, please
>> >> >
>> >> > A.  Turn on the nightly Falcon testing.
>> >> > B.  Provide us with a nightly binary so we can help Alex test against
>> >> our requirements.
>> >> >
>> >> > I know that you are personally very excited about being able to get
>> out
>> >> from under Flex/Flash or any dependency except what a browser will
>> provide,
>> >> but we who have stayed with Flex for all these years are committed to
>> >> making our applications the best possible with the Adobe Integrated
>> >> Runtime.  Every time you successfully compile for the JS environment,
>> >> please give us the same capability to compile for the devices on which
>> we
>> >> run.  If you move one step forward on being able to generate JavaScript,
>> >> please gives us one step forward on being able to compile ActionScript.
>> >> >
>> >> > I think any Flex 4.11 Release Candidate that does not successfully
>> >> compile our applications with the new compiler should be voted down by
>> all
>> >> who own that privilege.  Move to JavaScript as fast as the wind will
>> blow
>> >> you there, but please stop leaving us behind.
>> >> >
>> >> > --
>> >> > 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
>> >>
>> >>
>> >>
>> >> --
>> >> Ix Multimedia Software
>> >>
>> >> Jan Luykenstraat 27
>> >> 3521 VB Utrecht
>> >>
>> >> T. 06-51952295
>> >> I. www.ixsoftware.nl
>> >>
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>>


--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

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