On Tue, Dec 4, 2012 at 6:53 PM, Michael Schmalle wrote:
>
> Quoting Alex Harui :
>
> If you have the time and interest, you are certainly welcome to see if you
>>
> can implement a different strategy to generate the JS straight from the
>> AST.
>>
>
> I hear you Alex, the interest is 110%, the tim
[
https://issues.apache.org/jira/browse/FLEX-33286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cyrill Zadra resolved FLEX-33286.
-
Resolution: Fixed
Fix Version/s: Apache Flex Next
Assignee: Cyrill Zadra
Thank yo
If Apache doesn't care about that we should just drop it. It seems strange to
have it in some SWCs and not others.
- Gordon
-Original Message-
From: Gordon Smith [mailto:gosm...@adobe.com]
Sent: Tuesday, December 04, 2012 6:21 PM
To: flex-dev@incubator.apache.org
Subject: RE: Falcon SDK
We found some tests. They should be arriving in SVN shortly.
On 12/4/12 5:19 PM, "Om" wrote:
> On Tue, Dec 4, 2012 at 5:08 PM, Justin Mclean wrote:
>
>> HI,
>>
>>> The reason is that we dont have any Mustella tests for Charts and this
>> code
>>> change could potentially affect how charts re
I think Adobe's build machines had some scripts that set build.number to the
Perforce revision number that it was building.
- Gordon
-Original Message-
From: Chema Balsas [mailto:jbal...@gmail.com]
Sent: Tuesday, December 04, 2012 6:08 PM
To: flex-dev@incubator.apache.org
Subject: Re: F
Ok, I've submitted a patch for that (
https://issues.apache.org/jira/browse/FLEX-33286). I've checked and those
were the only projects including that file.
I've also checked, and the content of version.properties always seems to be
"build=0". I've even compiled without including the file and every
[
https://issues.apache.org/jira/browse/FLEX-33286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chema Balsas updated FLEX-33286:
Attachment: version-properties-fix.diff
Fix for projects rpc, spark and spark_dmv
Chema Balsas created FLEX-33286:
---
Summary: Fix version.properties for several compile-config files
Key: FLEX-33286
URL: https://issues.apache.org/jira/browse/FLEX-33286
Project: Apache Flex
Iss
In that case, let's move -include-file option for version.properties back out
of compile-config.xml and into the task.
- Gordon
-Original Message-
From: Chema Balsas [mailto:jbal...@gmail.com]
Sent: Tuesday, December 04, 2012 5:22 PM
To: flex-dev@incubator.apache.org
Subject: Re: Falco
Hi Cyril,
The version.properties file is created and removed inside the compile
target for those projects.
It is generated at the beginning of the target by:
build=${build.number}
And then removed at the end by:
which is why you shouldn't find it ;)
2012/12/5 Cyrill Zadra
> Hey Chema
>
> In
On Tue, Dec 4, 2012 at 5:08 PM, Justin Mclean wrote:
> HI,
>
> > The reason is that we dont have any Mustella tests for Charts and this
> code
> > change could potentially affect how charts render.
> If we didn't have any tests (ie they might already render differently)
> before is it an issue?
>
HI,
> The reason is that we dont have any Mustella tests for Charts and this code
> change could potentially affect how charts render.
If we didn't have any tests (ie they might already render differently) before
is it an issue?
Thanks,
Justin
Hi,
> It appears to be empty, but was it ever decided that this "experimental"
> project should be left in here:
> http://svn.apache.org/viewvc/incubator/flex/sdk/branches/develop/frameworks/projects/experimental/
I believe that is a place holder package for experimental components to add to
th
Hi,
There are 388 odd resolved issues in JIRA - obviously not all of these (IMO)
are need to be in the release notes.
Here a rough query that will get them (may miss a couple)
project = Flex and status = resolved and updatedDate > '2011/1/1'
Someone what to take a look and see which one are wor
I'm planning on fixing these things in the next couple days. Let me
know if that was your plan and I will stay out of the way otherwise
they are on my list.
I'm going to start testing the others SWCs as well.
Mike
Quoting "Cyrill Zadra (JIRA)" :
[
https://issues.apache.org/jira/b
Hey Chema
In the follwing compile-config.xml is the version.properties included.
rpc
spark
spark_dmv
version.properties
../../version.properties
In my builded flex sdk it does not exists. Is that part really used or
can it be removed? Or does anyone know how this versi
[
https://issues.apache.org/jira/browse/FLEX-33285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cyrill Zadra updated FLEX-33285:
Component/s: (was: Collections)
RPC: RemoteObject
Description:
C:\dev\apac
We might want to pull this revision out:
http://svn.apache.org/viewvc?view=revision&revision=1408058
The reason is that we dont have any Mustella tests for Charts and this code
change could potentially affect how charts render.
The two issues are tracked here:
https://issues.apache.org/jira/brows
Cyrill Zadra created FLEX-33285:
---
Summary: unmarshall( ... ) uses duplicate value declarations
Key: FLEX-33285
URL: https://issues.apache.org/jira/browse/FLEX-33285
Project: Apache Flex
Issue
Hi,
Ok as the first step I created a release branch:
https://svn.apache.org/repos/asf/incubator/flex/sdk/branches/release4.9
This was a copy of head from:
https://svn.apache.org/repos/asf/incubator/flex/sdk/branches/develop
Thanks,
Justin
Quoting Alex Harui :
On 12/4/12 10:54 AM, "Michael Schmalle" wrote:
Ok, I get what you are saying but that is like buying a car with no
mechanic within 3000 miles.
That is true for a significant portion of the AS code as well, not just
FalconJS. Carol, Gordon and I didn't write every li
I'm trying to stay out of FalconJS, but I will ask Bernd P about this.
- Gordon
-Original Message-
From: Michael Schmalle [mailto:apa...@teotigraphix.com]
Sent: Tuesday, December 04, 2012 2:53 PM
To: flex-dev@incubator.apache.org
Subject: RE: ABC -> JS
The JSEmitter is littered with the
It appears to be empty, but was it ever decided that this "experimental"
project should be left in here:
http://svn.apache.org/viewvc/incubator/flex/sdk/branches/develop/frameworks/projects/experimental/
--Dasa
On Dec 4, 2012, at 3:23 PM, Justin Mclean wrote:
> Hi,
>
> Does anyone know of an
Hi,
Does anyone know of any changes that have been checked into develop (since we
made the parity release) that we don't want to release?
Thanks,
Justin
On 12/4/12 2:41 PM, "Justin Mclean" wrote:
> Hi,
>
>> This sounds reasonable to me. All we need is a volunteer to be the release
>> manager.
>
>
> I'm willing to give it a go. (I have keys for signing the binaries etc etc)
> My time is a little bit limited at the moment so would appreciate
Hi,
>> I wish it was that easy. You mean 'build yourself a kit from the develop
>> branch'. But remember, we are going to cherry pick changes from develop
>> into a release branch before I can make a kit for myself.
I believe that is the process as voted on but the actually implications fro
cr
The JSEmitter is littered with the whole;
import org.apache.flex.abc.graph.IBasicBlock;
import org.apache.flex.abc.semantics.ClassInfo;
import org.apache.flex.abc.semantics.ExceptionInfo;
import org.apache.flex.abc.semantics.InstanceInfo;
import org.apache.flex.abc.semantics.Instruction;
import o
On 12/4/12 5 :34PM, "Om" wrote:
>On Tue, Dec 4, 2012 at 1:51 PM, Carol Frampton wrote:
>
>>
>>
>>
>> On 12/4/12 3 :01PM, "Om" wrote:
>>
>> >On Tue, Dec 4, 2012 at 11:51 AM, Carol Frampton
>> >wrote:
>> >
>> >> As far as the installer goes, that work should be done now/soon
>>since I
>> >> th
Hi,
> This sounds reasonable to me. All we need is a volunteer to be the release
> manager.
I'm willing to give it a go. (I have keys for signing the binaries etc etc) My
time is a little bit limited at the moment so would appreciate some help.
Thanks,
Justin
On Tue, Dec 4, 2012 at 1:51 PM, Carol Frampton wrote:
>
>
>
> On 12/4/12 3 :01PM, "Om" wrote:
>
> >On Tue, Dec 4, 2012 at 11:51 AM, Carol Frampton
> >wrote:
> >
> >> As far as the installer goes, that work should be done now/soon since I
> >> think we can/should release in January and it would
This sounds reasonable to me. All we need is a volunteer to be the release
manager. I would rather not be it.
On 12/4/12 12:26 PM, "Greg Reddin" wrote:
> On Tue, Dec 4, 2012 at 12:27 PM, Alex Harui wrote:
>
>> I¹m leaning towards waiting, but I feel bad for folks who are waiting to
>> see t
> Hi,
> Release early and often should be the case, we are way overdue for a release
> IMO.
> Justin
Justin is correct. Part of the graduation criteria is to be a self-sustaining
community. Concerning ourselves with whether mentors approve or disapprove of
our project provides evidence that we a
Interesting. I don't understand why it is doing anything with Traits. Alex, you
might want to ask Bernd P.
- Gordon
-Original Message-
From: Michael Schmalle [mailto:apa...@teotigraphix.com]
Sent: Tuesday, December 04, 2012 1:50 PM
To: flex-dev@incubator.apache.org
Subject: Re: ABC -> J
On 12/4/12 3 :01PM, "Om" wrote:
>On Tue, Dec 4, 2012 at 11:51 AM, Carol Frampton
>wrote:
>
>> As far as the installer goes, that work should be done now/soon since I
>> think we can/should release in January and it would be great if the
>> installer was ready with the SDK.
>>
>
>I agree that
Quoting Alex Harui :
On 12/4/12 12:37 PM, "Gordon Smith" wrote:
SO I will say to anybody, in the current state of the FalconJS
compiler, you
NEED to know opcdes to be able to fix anything.
I don't know much about FalconJS but I would be very surprised if this is
true. Can you show me one
On 12/4/12 3 :03PM, "Om" wrote:
>On Tue, Dec 4, 2012 at 12:01 PM, Justin Mclean
>wrote:
>
>> Hi,
>>
>> > I don't disagree but I think a release without "-incubating" in the
>>title
>> > would be a good thing.
>> Nothing stopping us from making another release after graduation and
>>it's
>> not
Hi,
> In jira you'll find falcon tasks and bugs here ->
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+12313521+AND+labels+%3D+Falcon
I've just assed a "Flex Falcon Open Issues" filter to JIRA.
Justin
On 12/4/12 12:37 PM, "Gordon Smith" wrote:
>> SO I will say to anybody, in the current state of the FalconJS compiler, you
>> NEED to know opcdes to be able to fix anything.
>
> I don't know much about FalconJS but I would be very surprised if this is
> true. Can you show me one method of Fal
In jira you'll find falcon tasks and bugs here ->
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+12313521+AND+labels+%3D+Falcon
Am 04.12.2012 um 12:56 schrieb vineet sood :
> Can you give me the bug base link if any.
>
> On Wed, Dec 5, 2012 at 2:25 AM
> Can you give me the bug base link if any.
Click the "Jira" link on the main Apache Flex page at
http://incubator.apache.org/flex/.
- Gordon
-Original Message-
From: vineet sood [mailto:vineette...@gmail.com]
Sent: Tuesday, December 04, 2012 12:56 PM
To: flex-dev@incubator.apache.org
Can you give me the bug base link if any.
On Wed, Dec 5, 2012 at 2:25 AM, vineet sood wrote:
> Ok, makes sense
>
>
> On Wed, Dec 5, 2012 at 2:19 AM, Gordon Smith wrote:
>
>> I work on Falcon, so I'll address that area.
>>
>> We are working on building a test suite to determine what works and wh
Ok, makes sense
On Wed, Dec 5, 2012 at 2:19 AM, Gordon Smith wrote:
> I work on Falcon, so I'll address that area.
>
> We are working on building a test suite to determine what works and what
> doesn't work in Falcon, and to provide a suite that will keep us from
> introducing regressions. We ar
I work on Falcon, so I'll address that area.
We are working on building a test suite to determine what works and what
doesn't work in Falcon, and to provide a suite that will keep us from
introducing regressions. We are creating low-level unit tests at the lexer and
parser level, mid-level feat
> SO I will say to anybody, in the current state of the FalconJS compiler, you
> NEED to know opcdes to be able to fix anything.
I don't know much about FalconJS but I would be very surprised if this is true.
Can you show me one method of FalconJS that actually writes out an ABC opcode?
There a
On Tue, Dec 4, 2012 at 12:27 PM, Alex Harui wrote:
> I’m leaning towards waiting, but I feel bad for folks who are waiting to
> see their work get out the door. This will truly separate the Apache Flex
> SDK from the Adobe Flex SDK because non-Adobe code will finally be released!
>
I think we s
[
https://issues.apache.org/jira/browse/FLEX-33279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carol Frampton resolved FLEX-33279.
---
Resolution: Fixed
Assignee: Carol Frampton
Author: cframpton
Date: Tue Dec 4 19:58:21
Hi,
> I was expecting they would probably just move our existing repository as is
> to an SVN url that is not incubating.
I can't see that should cause too many issues as the release branch we're
working on would also be moved over.
Thanks,
Justin
On Tue, Dec 4, 2012 at 12:01 PM, Justin Mclean wrote:
> Hi,
>
> > I don't disagree but I think a release without "-incubating" in the title
> > would be a good thing.
> Nothing stopping us from making another release after graduation and it's
> not certain that we will graduate at the next board m
[
https://issues.apache.org/jira/browse/FLEX-33156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carol Frampton resolved FLEX-33156.
---
Resolution: Fixed
Author: cframpton
Date: Tue Dec 4 15:30:50 2012
New Revision: 1416993
URL
Hi,
> I don't disagree but I think a release without "-incubating" in the title
> would be a good thing.
Nothing stopping us from making another release after graduation and it's not
certain that we will graduate at the next board meeting (although I hope we do).
Does anything here need to be up
On Tue, Dec 4, 2012 at 11:49 AM, Justin Mclean wrote:
> Hi,
>
> > Given the pending graduation
> Which we'll find out about 19th Dec at minimum.
>
> > and moving of repositories
> Which as far as I can see still up in the air and there's several
> unanswered questions about and may be at a minimum
On Tue, Dec 4, 2012 at 11:49 AM, Justin Mclean wrote:
> Hi,
>
> > Given the pending graduation
> Which we'll find out about 19th Dec at minimum.
>
> > and moving of repositories
> Which as far as I can see still up in the air and there's several
> unanswered questions about and may be at a minimum
On 12/4/12 2 :32PM, "Justin Mclean" wrote:
>Hi,
>
>Release early and often should be the case, we are way overdue for a
>release IMO.
I don't disagree but I think a release without "-incubating" in the title
would be a good thing. I also don't think we can pull off a release in
the next two w
That said, there is nothing stopping us from preparing for a release before
we graduate. The major difference would be the "incubating" tag for the
release and an additional 72 hour (minimum) voting period in the IPMC. If
folks feel like we can pull it off, they should take it on.
Lets also keep
Hi,
> Given the pending graduation
Which we'll find out about 19th Dec at minimum.
> and moving of repositories
Which as far as I can see still up in the air and there's several unanswered
questions about and may be at a minimum a few months off. (Unless I've missed
some news here)
Do we reall
On Tue, Dec 4, 2012 at 11:32 AM, Justin Mclean wrote:
> Hi,
>
> Release early and often should be the case, we are way overdue for a
> release IMO.
>
> Justin
While I generally agree with this statement it is predicated on the
assumption that releasing often can happen in an efficient and timely
Hi,
Release early and often should be the case, we are way overdue for a release
IMO.
Justin
I think is better to wait.
just my 2ctns :)
2012/12/4 Jun Heider
>
> On Dec 4, 2012, at 11:27 AM, Alex Harui wrote:
> > I’m leaning towards waiting, but I feel bad for folks who are waiting to
> see their work get out the door. This will truly separate the Apache Flex
> SDK from the Adobe Flex
My guess is that it will take at least a month to sort out the code, build,
test and have the artifacts prepared for a release. Also, we want to make
changes to the Installer (ex. removing download of TLF since it is part of
the SDK now)
I think it would be better if we wait instead of trying to
On 12/4/12 10:54 AM, "Michael Schmalle" wrote:
> Ok, I get what you are saying but that is like buying a car with no
> mechanic within 3000 miles.
That is true for a significant portion of the AS code as well, not just
FalconJS. Carol, Gordon and I didn't write every line. And many of the
fo
Quoting Alex Harui :
On 12/4/12 9:53 AM, "Michael Schmalle" wrote:
Quoting Alex Harui :
On 12/4/12 2:24 AM, "Michael Schmalle" wrote:
What makes that code REALLY confusing is although you say he is using
AS, there is a huge amount of ABC opcode in that code he wrote.
Are you talk
On Dec 4, 2012, at 11:27 AM, Alex Harui wrote:
> I’m leaning towards waiting, but I feel bad for folks who are waiting to see
> their work get out the door. This will truly separate the Apache Flex SDK
> from the Adobe Flex SDK because non-Adobe code will finally be released!
>
> Thoughts?
Go
On 12/4/12 9:53 AM, "Michael Schmalle" wrote:
>
> Quoting Alex Harui :
>
>>
>>
>>
>> On 12/4/12 2:24 AM, "Michael Schmalle" wrote:
>>> What makes that code REALLY confusing is although you say he is using
>>> AS, there is a huge amount of ABC opcode in that code he wrote.
>> Are you talk
Hi,
We’ve had a couple of new locales and many bug fixes submitted that have been
sitting around for a while now. It would be great to get them out the door,
but with the impending graduation (we hope), the timing becomes tricky.
I’m not sure we can get it together to get packages approved by
On 12/3/12 12:32 AM, "Bertrand Delacretaz" wrote:
> Hi,
>
> FYI, this month's board meeting (where Flex graduation should be
> ratified) is on December 19th, in the meantime the podling board
> report is due at http://wiki.apache.org/incubator/December2012
>
> As I'll soon be retiring from Fl
I have interest, but like you my problem is time.
I'm in the last sprint of a big project and I'm hoping my schedule frees up
as we head into the new year. Lots of things on my todo list right now. :/
-omar
On Tuesday, December 4, 2012, Michael Schmalle wrote:
>
> Quoting Alex Harui :
>
>
>>
>>
Quoting Alex Harui :
On 12/4/12 2:24 AM, "Michael Schmalle" wrote:
What makes that code REALLY confusing is although you say he is using
AS, there is a huge amount of ABC opcode in that code he wrote.
Are you talking about JSEmmitter?
I'm talking about the classes in general. My questio
@Alex: no, not yet checked in, I don't like to check in code that
doesn't 'compile' ;-) A couple of days more...
@Omar: no, I didn't. The original FalconJS POC and demonstration code
already have a great deal of Closure annotation in it, so I figured
the compiler was geared towards that already. A
Did you check this in? I'm not seeing any commit emails from you.
On 12/4/12 7:50 AM, "Erik de Bruin" wrote:
> Hi,
>
> After a lot of reading, trying and testing, as well as looking at the
> current code and compiler output, I think the project is best of using
> the Google Closure Tools. Bot
On 12/4/12 2:24 AM, "Michael Schmalle" wrote:
> What makes that code REALLY confusing is although you say he is using
> AS, there is a huge amount of ABC opcode in that code he wrote.
Are you talking about JSEmmitter?
>
> SO I will say to anybody, in the current state of the FalconJS
> compile
Did you try Uglify.js? It has about the same compression results as GCC but
runs a lot faster. There's also an Uglify 2.0 that's supposed to be even
faster than 1.x.
-omar
On Tuesday, December 4, 2012, Erik de Bruin wrote:
> Hi,
>
> After a lot of reading, trying and testing, as well as looking
Hi,
After a lot of reading, trying and testing, as well as looking at the
current code and compiler output, I think the project is best of using
the Google Closure Tools. Both for developing and deploying FlexJS
components and applications. I've implemented them into the FlexJS
workflow, and provi
Quoting Michael Schmalle :
One advantage of ABC -> JS is that it solves the problem of having
a 3rd party SWC that you don't have source code for but want to
transcode to JS.
Couldn't we write an intermediary SWC parsing tool that could create
classes with native stubs (by parsing the A
Quoting Gordon Smith :
The possibility of transcoding ABC -> JS (rather than AS -> JS, MXML
-> JS, CSS -> JS, and .properties -> JS) has come up on another
thread. I should mention that this approach is the one that the
architect of the Falcon compiler (Chris Brichford, who recently left
Thanks Gordon, let me know which one I can start to work on with,
whichever of the below are on priority,I can take on any of them. I would
love to have my hands on Falcon as well as writing components or JS cross
compilation, am fine with any of them.
On Tue, Dec 4, 2012 at 4:58 AM, Gordon Smit
OK, I think I fixed this. Works for me on Windows now.
On 12/3/12 1:21 PM, "João Fernandes"
wrote:
> Hi,
>
> I'm trying to run Mustella tests to check if my proposed patch for spark
> Datagrid didn't break anything but no tests are run.
>
> I've run the full test suite first, then used the uti
76 matches
Mail list logo
