On Fri, 2012-02-17 at 10:25 +0100, Roland Zwaga wrote:
> By the way,
>
> here is the Java port of the goldparser engine:
>
> https://github.com/ridencww/goldengine
>
> it might be an idea to try out both ANTLR and goldparser
> and compare the results, I'd say the fastest one we'd take ;)
How abo
>
> Michael Schmalle already created jasblocks, a Java port of his asblocks
> engine
> which is able to parse AS3.
> https://github.com/teotigraphix/as3-commons-jasblocks/
> Since he's already created grammars for AS3, E4X, regex and ASDoc we might
> be able to stand on the shoulders of giants :)
>
>
> By the way,
>
> here is the Java port of the goldparser engine:
>
> https://github.com/ridencww/goldengine
>
> it might be an idea to try out both ANTLR and goldparser
> and compare the results, I'd say the fastest one we'd take ;)
>
Michael Schmalle already created jasblocks, a Java port of h
By the way,
here is the Java port of the goldparser engine:
https://github.com/ridencww/goldengine
it might be an idea to try out both ANTLR and goldparser
and compare the results, I'd say the fastest one we'd take ;)
cheers,
Roland
> If a 3rd party really needs to release a new .swc, then t
, Falcon team
>
>
> -Original Message-
> From: David Arno [mailto:da...@davidarno.org]
> Sent: Thursday, February 16, 2012 2:39 AM
> To: flex-dev@incubator.apache.org
> Subject: Time for an Apache Flex compiler.
>
> Yesterday Adobe published their "whitepaper&
I really like the ideas being forth here. I still want to continue to push
Adobe to finish Falcon work in an open development model, and I hope they
respond as such. However, assuming not only that Falcon will retain its closed
development model, but also that it is likely to slip past the end
Very nice. Have you considered RST [1] (or another markup language)
for the design document formatting? It's readable as plain text,
github displays some of these natively (I think at least RST and
Markdown), and RST can be "compiled" to PDF or HTML (e.g., Python uses
it for their documentation and
>
> If a 3rd party really needs to release a new .swc, then they can still
> use the compc compiler as I think we are supposed to be getting that
> too. By requiring them to use compc, we make it clear that they are
> using old technology to do things the old way.
>
> Of course, having said all tha
On Thu, 2012-02-16 at 12:10 -0800, Om wrote:
> David, from your pdf (yeah, I read it ;-) )
> This sounds like a serious limitation - especially for Flex based library
> projects which is a pretty important feature. Can you please elaborate on
> the workaround you hinted in your doc?
What I was thi
>
> "To facilitate supporting multiple targets, Goshawk will not generate SWC
> library files as
> they can only be used by a compiler targetting SWFs. Instead, the
> language-agnostic parsetree
> generated by the ANTLR front-end will be used as a library file format.
> This may be
> stored in XML,
David, from your pdf (yeah, I read it ;-) )
"To facilitate supporting multiple targets, Goshawk will not generate SWC
library files as
they can only be used by a compiler targetting SWFs. Instead, the
language-agnostic parsetree
generated by the ANTLR front-end will be used as a library file forma
On Thu, 2012-02-16 at 20:48 +0100, Roland Zwaga wrote:
> not to throw a spanner in the works immediately but I was wondering if you
> could
> consider a different parser from ANTLR. There is a project called
> Goldparser:
> http://goldparser.org/
> From what I understand this thing is the fastest o
On 17/02/2012 03:01, David Arno wrote:
Obviously, as per the mentors' request recently, whilst it makes sense
to experiment with this compiler on Github, we need to keep discussions
happening here. Perhaps we could prefix topics with [Goshawk]? That way
those that wish to concentrate on making th
>
> As there was some positive feedback to the idea of creating our own
> compiler, I have gone ahead and started a new project on Github and
> created an initial design document on how I think it might work. I've
> taken the liberty of giving it the code name "Goshawk." If you are
> curious as to
On Feb 16, 2012, at 8:52 AM, Jeffry Houser wrote:
> On 2/16/2012 11:47 AM, Omar Gonzalez wrote:
>> On Thursday, February 16, 2012, David Arno wrote:
>>> On Thu, 2012-02-16 at 05:34 -0800, Carol Frampton wrote:
Adobe's fiscal year starts in Dec so Q4 is Sept-Nov.
>>> Not wishing to shoot the
On Thursday, February 16, 2012, David Arno wrote:
...
> Obviously, as per the mentors' request recently, whilst it makes sense
> to experiment with this compiler on Github, we need to keep discussions
> happening here...
Yes, that would be great.
> ..Perhaps we could prefix topics with [Goshawk]
On 2/16/2012 1:00 PM, Gordon Smith wrote:
Falcon ... will support AS3 only, with no support for MXML.
This is incorrect.
Falcon *already* supports enough of MXML to compile a correctly-running version
of Checkinapp, the test app that is part of the SDK. Falcon's support for
.mxml, .css, and .
As there was some positive feedback to the idea of creating our own
compiler, I have gone ahead and started a new project on Github and
created an initial design document on how I think it might work. I've
taken the liberty of giving it the code name "Goshawk." If you are
curious as to why, google
on Smith, Falcon team
-Original Message-
From: David Arno [mailto:da...@davidarno.org]
Sent: Thursday, February 16, 2012 2:39 AM
To: flex-dev@incubator.apache.org
Subject: Time for an Apache Flex compiler.
Yesterday Adobe published their "whitepaper" on the future of Flex. In it
On Thu, 2012-02-16 at 08:47 -0800, Omar Gonzalez wrote:
> Mind communicating that last thought in a clear fashion? :P I don't
> understand what your complaint is, Carol is simply explaining Adobe's time
> frame, what problem so you see in such a simple statement?
If one uses the abbreviation "Q4" w
On 2/16/2012 11:47 AM, Omar Gonzalez wrote:
On Thursday, February 16, 2012, David Arno wrote:
On Thu, 2012-02-16 at 05:34 -0800, Carol Frampton wrote:
Adobe's fiscal year starts in Dec so Q4 is Sept-Nov.
Not wishing to shoot the messenger here, but this really does sum up
Adobe's inability to
On 17/02/2012 01:47, Omar Gonzalez wrote:
P I don't
understand what your complaint is, Carol is simply explaining Adobe's time
frame, what problem so you see in such a simple statem
I think he is saying that its marketing-wise not a great idea to use Q4
which is usually interpreted as OCT-DEC.
On Thursday, February 16, 2012, David Arno wrote:
> On Thu, 2012-02-16 at 05:34 -0800, Carol Frampton wrote:
>> Adobe's fiscal year starts in Dec so Q4 is Sept-Nov.
> Not wishing to shoot the messenger here, but this really does sum up
> Adobe's inability to think and communicate in a clear fashio
On Thu, 2012-02-16 at 05:34 -0800, Carol Frampton wrote:
> Adobe's fiscal year starts in Dec so Q4 is Sept-Nov.
Not wishing to shoot the messenger here, but this really does sum up
Adobe's inability to think and communicate in a clear fashion... :(
David.
I believe Google plans to offer Brightly as a cloud-based IDE, which may be
one of the reasons the compiler also exists in the Cloud. It's rather neat,
if I may say so.
On Thu, Feb 16, 2012 at 7:55 AM, Martin Heidegger wrote:
> On 16/02/2012 21:49, Jarosław Szczepankiewicz wrote:
>
>> Also Dart -
> From: "Carol Frampton"
> The compiler team had absolutely no cuts last November. It was a
separate
> team from the Flex frameworks team.
>
> Carol
>
I stand corrected. Thanks for clarifying Carol.
Rui
Two clarifications. Adobe's fiscal year starts in Dec so Q4 is Sept-Nov.
The compiler team had absolutely no cuts last November. It was a separate
team from the Flex frameworks team.
Carol
On 2/16/12 7 :25AM, "Rui Silva" wrote:
>
>> From: "David Arno"
>>
>> This is not a viable timescale fo
On 16/02/2012 22:00, Roland Zwaga wrote:
he libraries needed to create an AS3 based compiler are already available,
there is as3commons-asblock
as3commons-asblocks is interesting but not a bit optimized and consumes
a lot of memory.
yours
Martin.
On 16 February 2012 13:55, Martin Heidegger wrote:
> On 16/02/2012 21:49, Jarosław Szczepankiewicz wrote:
>
>> this is my personal opinion, but what's the purpose of another flex
>> compiler from open source, especially written in as3?
>>
>
> The purpose of a compiler written in AS3 is that we ca
On 16/02/2012 21:55, Martin Heidegger wrote:
..instead of whenever necessary...
"instead of" should read "or" ...
On 16/02/2012 21:49, Jarosław Szczepankiewicz wrote:
this is my personal opinion, but what's the purpose of another flex
compiler from open source, especially written in as3?
The purpose of a compiler written in AS3 is that we can compile code on
the fly instead of whenever necessary. This abi
i'm definitely in.
as3 and mxml to swf is a must, compile to js would be great for webapps,
but I'd like to see this
multitarget approach targeting other platforms too, expecially c\c++.
if flash\air doesn't run in the platform my project is targeting i would be
enabled to reuse my code and
convert
this is my personal opinion, but what's the purpose of another flex
compiler from open source, especially written in as3?
- will it be faster than mxmlc / fcsh / falcon?
- will it better support multicore architectures / really big projects?
- will it produce better / optimised optocode than mxmlc
Also: There is the haXe compiler that already compiles a AS3 like
language to swf and javascript.
I guess it would be possible in less than 5 months to add AS3, metadata
and xml support in that mix.
yours
Martin.
On 16/02/2012 21:25, Rui Silva wrote:
From: "David Arno"
This is not a viable t
I really agree with Rui. I believe it will be a waste of time, because even
if Adobe will donate it at the beginning of 2013, I'm pretty sure that when
they will have a stable solution it will be provided to all developers,
even if is only AS3 and not MXML.
And if your target is mobile or web, you
On 16/02/2012 21:25, Rui Silva wrote:
Though I'm generally available for any work that this group decides to
undertake, I really do not see this as a viable solution. Do you truly
believe that we (considering most of us are Flex developers with
little or no expertise in compiler development) co
> From: "David Arno"
>
> This is not a viable timescale for Apache Flex in my opinion. Therefore
> I feel we have no choice but to ignore Falcon and to start developing
> our own compiler with immediate effect. I therefore want to get an idea
> as to who, if anyone, here is interested in getting
Today I played around with a AS3 As3 compiler
yours
Martin.
>
> > This is not a viable timescale for Apache Flex in my opinion. Therefore
> > I feel we have no choice but to ignore Falcon and to start developing
> > our own compiler with immediate effect. I therefore want to get an idea
> > as to who, if anyone, here is interested in getting involved in thi
2012/2/16 David Arno :
> Yesterday Adobe published their "whitepaper" on the future of Flex. In
> it, they state that they'll be contributing the Falcon compiler to
> Apache sometime between October and December. This compiler will support
> AS3 only, with no support for MXML. So when we get the co
Yesterday Adobe published their "whitepaper" on the future of Flex. In
it, they state that they'll be contributing the Falcon compiler to
Apache sometime between October and December. This compiler will support
AS3 only, with no support for MXML. So when we get the compiler (which
as already slippe
41 matches
Mail list logo
