Hi,
I just checked in (to patches branch) changes to the build script for a new
apache sub project that produces an apache.swc and apache_rb.swc. (Anyone feel
the swc should have a different name?) This gives a clean separation between
the current swc namespaces and the apache one.
This is wer
Agree with that!
Good job Tink!
On Tue, Mar 13, 2012 at 12:56 PM, Arnoud Bos wrote:
>
> Hi Tink,
>
> Your layouts / navigators are of great value! So consider this as interest
> :-)
> Maybe because they just work and people can grab them from the whiteboard
> there is not much feedback.
>
>
Hi everyone,
I saw the discussions regarding SDK inclusion process. In my case, it's
true that I cannot improve any component without having requests for that.
The submitted components reflects exactly what I needed them to do at the
time they were created.
In Alert's case, it's written in the sa
It will be ideal if there a way to interface any DLL from as3 code when
cross compile to c or cpp, this will attract developers who are using QT
On Mar 14, 2012 6:42 AM, "Arnoud Bos" wrote:
>
> On Mar 13, 2012, at 10:07 PM, Niel Drummond wrote:
>
> >
> > Regarding Arnoud Bos' suggestion of using
>Many folks want to see all the mustella tests in before making changes to the
>SDK which is another reason why I've been trying to do it in all one shot.
Just thinking it would give people a way to start writing tests in this
supported way so that we are getting coverage on new code. I might pu
On Mar 13, 2012, at 4:17 PM, Alex Harui wrote:
> The tool currently pulls one Adobe issue and creates a new issue in the
> destination instance, then goes on to the next. I could slow it down if we
> have to.
Ask Infrastructure what rate is too fast, or if there are times when you should
stop.
On 3/13/12 11:52 AM, "Michael A. Labriola"
wrote:
>> The real #2 has a bunch of optional parameters and doesn't rely on
>> flashlog.txt
>
> Just wondering if the fake #2 still gets us started for now.
Well, there really isn't anything in a fake #2. It is just a matter of
compiling an MXML fi
The tool currently pulls one Adobe issue and creates a new issue in the
destination instance, then goes on to the next. I could slow it down if we
have to.
On 3/13/12 4:12 PM, "Dave Fisher" wrote:
>
> On Mar 13, 2012, at 1:18 PM, Alex Harui wrote:
>
>>
>>
>>
>> On 3/13/12 1:13 PM, "Carol
On Mar 13, 2012, at 1:18 PM, Alex Harui wrote:
>
>
>
> On 3/13/12 1:13 PM, "Carol Frampton" wrote:
>
>> I know Alex considered this option several weeks ago. I believe he was
>> told by Apache infrastructure not to do this but he can correct me if I am
>> wrong.
>>
> I already have this to
On 14/03/2012 03:07, Michael A. Labriola wrote:
The AIR stuff has some of its own complexity too. Ideally we would like to test
things in Flash Player and in AIR, not just one or the othe
My thinking is following: Right now X images are compressed into &
decompressed from PNG. I assume the Flex
On Mar 13, 2012, at 10:07 PM, Niel Drummond wrote:
>
> Regarding Arnoud Bos' suggestion of using as3hx, this might be a solution,
> if (and only if) it's desired to keep as3 as-is, but I doubt it will be a
> satisfactory solution, because I suspect eventually flex will want to
> migrate some of
Niel,
I've tried to bootstrap the framework once, but I've reduced it to the
minimum required to support MXML (so no visual components, collections
etc), only bindings + some other stuff I wasn't able to remove. It would be
all in all about 30 classes. So, if you are interested, I could give it a
I think if some work were to go into this, it would be a great primer for
the issues around targeting javascript/HTML regardless of which compiler is
used. Many issues that were raised in the "porting to haxe" threads
revolved around generic issues that would need to be dealt with regardless
of whe
Hi,
> I don't agree. If you don't have an IOS device, that shouldn't be a
> blocker. If you don't have a Mac, that shouldn't matter either. That is the
> advantage of community. Folks help each other by contributing their
> expertise.
Perhaps I wasn't clean that exactly what I was saying. I ag
On 3/13/12 1:13 PM, "Carol Frampton" wrote:
> I know Alex considered this option several weeks ago. I believe he was
> told by Apache infrastructure not to do this but he can correct me if I am
> wrong.
>
I already have this tool written. That's how I was able to convert from the
Adobe vers
I know Alex considered this option several weeks ago. I believe he was
told by Apache infrastructure not to do this but he can correct me if I am
wrong.
Carol
On 3/13/12 4 :05PM, "Omar Gonzalez" wrote:
>On Tue, Mar 13, 2012 at 12:42 PM, Carol Frampton
>wrote:
>
>> >
>> >
>> >
>> >If you take
On Tue, Mar 13, 2012 at 12:42 PM, Carol Frampton wrote:
> >
> >
> >
> >If you take this road you could also argue that Apache is deliberately
> >delaying because we we're waiting long for the Jira import. And that is
> >of course ridiculous.
>
> Apache infrastructure ended up filing a support iss
>
>
>
>If you take this road you could also argue that Apache is deliberately
>delaying because we we're waiting long for the Jira import. And that is
>of course ridiculous.
Apache infrastructure ended up filing a support issue at Atlassian so they
are waiting for support from them. Our bug is
ht
Alex has said this before but I'll remind people. I think he/we are
proposing that there be 2 or 3 branches with the final branch being trunk.
Trunk becomes the next release of the SDK. So, for example, code could
move from the whiteboard or, or some external source, to the "not quite
polished"
On Mar 13, 2012, at 5:54 PM, JP Bader wrote:
> Every time we want a little progress, Adobe makes sure their "legal"
> has some more wrangling to do, so we fall a little further
> behind...Does anyone else sense that maybe Adobe is intentionally
> sabotaging any of our progress? That's just the
>The real #2 has a bunch of optional parameters and doesn't rely on flashlog.txt
Just wondering if the fake #2 still gets us started for now.
On 3/13/12 11:09 AM, "Michael A. Labriola"
wrote:
>
>> 1) A SWC of test steps that are tags in MXML used to define the script.
>> 2) A Java engine that runs tests based on command line input
>
> Isn't some version of #1 and #2 in the check in tests?
#2 is not in the checkintests. The build.
>1) A SWC of test steps that are tags in MXML used to define the script.
>2) A Java engine that runs tests based on command line input
Isn't some version of #1 and #2 in the check in tests?
>Yeah, maybe someday we can rewrite the engine to use AIR instead of Java, but
>mustella was around long before ANEs.
The AIR stuff has some of its own complexity too. Ideally we would like to test
things in Flash Player and in AIR, not just one or the other.
On 3/13/12 10:52 AM, "Martin Heidegger" wrote:
> Just out of curiosity: It would be no problem to run a test in adl an
> capture the output there using a native extension, would it?
> I am not sure how the tests are built but making a screenshot is of a
> application is not "high science" and
On 3/13/12 10:42 AM, "Omar Gonzalez" wrote:
> There's an awful lot of process described in your response. This is exactly
> what I'm saying we need to come to an agreement on, finalize a decision and
> publish this process on the wiki.
Yes, there is a sequence, but I think it is the same short
On 14/03/2012 02:46, Alex Harui wrote:
Well, sarcastic or not, it is a good question.
Here's my latest thinking: There are several pieces to mustella.
1) A SWC of test steps that are tags in MXML used to define the script.
2) A Java engine that runs tests based on command line input
3) An htt
On 3/13/12 9:40 AM, "Michael A. Labriola"
wrote:
>> Adobe probably won't go after folks who have legal copies of mustella.swc and
>> guess how it works and write and
> run tests on their computers, but I don't mustella.swc can get checked into
> Apache without Adobe's approval.
>
> Okay, so i
On 3/13/12 10:12 AM, "Omar Gonzalez" wrote:
>
> As an example, Tink has his layouts and containers in whiteboard. What now?
As the unit test thread is saying, we're a bit stuck right now. What should
be happening is that Tink and others write some tests to validate that it
works and folks w
On Tue, Mar 13, 2012 at 10:37 AM, Alex Harui wrote:
>
>
>
> On 3/13/12 10:12 AM, "Omar Gonzalez" wrote:
>
>
> >
> > As an example, Tink has his layouts and containers in whiteboard. What
> now?
> As the unit test thread is saying, we're a bit stuck right now. What
> should
> be happening is tha
I concede, it's my own paranoia...
I am stoked, love Tink's and Justin's contributions, and look forward
to committing shortly.
On Tue, Mar 13, 2012 at 12:24 PM, Michael A. Labriola
wrote:
>>Every time we want a little progress, Adobe makes sure their "legal"
>>has some more wrangling to do, so
>Every time we want a little progress, Adobe makes sure their "legal"
>has some more wrangling to do, so we fall a little further behind...Does
>anyone else sense that maybe Adobe is intentionally sabotaging any of our
>progress? That's just the conspiracy-theorist in me...
Not with you there.
On Tue, Mar 13, 2012 at 9:54 AM, JP Bader wrote:
> Every time we want a little progress, Adobe makes sure their "legal"
> has some more wrangling to do, so we fall a little further
> behind...Does anyone else sense that maybe Adobe is intentionally
> sabotaging any of our progress? That's just t
On Tue, Mar 13, 2012 at 10:04 AM, Alex Harui wrote:
>
>
>
> On 3/13/12 12:24 AM, "Justin Mclean" wrote:
>
> > Hi,
> >
> >> I may change my mind about this in the morning, but this is just too
> much
> >> process.
> > I see it as more of a list of what you may need to think about/get other
> > pe
On 13 March 2012 16:54, JP Bader
>
> behind...Does anyone else sense that maybe Adobe is intentionally
> sabotaging any of our progress? That's just the conspiracy-theorist
> in me...
>
>
Clearly conspiracy-theory. They are trying hard to get everything donated
and if you look in the archives, yo
On 3/13/12 12:24 AM, "Justin Mclean" wrote:
> Hi,
>
>> I may change my mind about this in the morning, but this is just too much
>> process.
> I see it as more of a list of what you may need to think about/get other
> people to help you out along the way with rather than a step by step proces
Every time we want a little progress, Adobe makes sure their "legal"
has some more wrangling to do, so we fall a little further
behind...Does anyone else sense that maybe Adobe is intentionally
sabotaging any of our progress? That's just the conspiracy-theorist
in me...
On Tue, Mar 13, 2012 at 11
>Adobe probably won't go after folks who have legal copies of mustella.swc and
>guess how it works and write and
run tests on their computers, but I don't mustella.swc can get checked into
Apache without Adobe's approval.
Okay, so if I post a decompiled version of the SWC on github with comment
On 3/13/12 6:35 AM, "Michael A. Labriola"
wrote:
>
> Alex,
>
> Let's just say I happen to have an older version of the source... If I was
> willing to support this on my own and deal with questions, do you have any
> problem with people writing tests against mustella. We cant write unit tests
>Hasn't the MXMLC Flex compiler been open source since version 3?
No, not really. If you look at the licenses (which are contradictory in some
cases) the modules directory containing the compiler source *may* have been
Adobe license and not Mozilla so we may not have the right to redistribute.
On 3/13/2012 10:22 AM, James Cowan wrote:
that is a good summary and yes it sounds like a massive amount of work.
I have never seen an open source MXML compiler but I have seen XAML
open source compilers.
Hasn't the MXMLC Flex compiler been open source since version 3?
--
Jeffry Houser
T
On 3/13/12 3 :24AM, "Justin Mclean" wrote:
>
>We could actually use apache.flex (or org.apache.flex) as the intern
>package in the patches branch?
Based on mail I got from Bertrand about a question I asked about code
donation I think he would say org.apache.flex
Carol
that is a good summary and yes it sounds like a massive amount of work.
I have never seen an open source MXML compiler but I have seen XAML open
source compilers.
extras/mxml.xsd seems to have disappeared but this project
(http://code.google.com/p/xsd4mxml/) seems to be useful.
James
On 13
Ok, just looked it up. I was wrong.
If the various branches of an if/else statement involve single statements,
don't make them into blocks.
But if any branch has multiple statements, make all of them into blocks.
ref:
http://opensource.adobe.com/wiki/display/flexsdk/Coding+Conventions#CodingC
On Mar 13, 2012, at 1:17 PM, James Cowan wrote:
>
> MXML/AS3/Flex are conceptually identical to XAML/C#/WPF. They borrow a lot of
> ideas from previous XML UI technologies.
> MXML/haXe/Flex does sound quite viable.
Sure, it could be done. But i guess someone should be willing to port the
acti
On Tue, Mar 13, 2012 at 8:31 AM, Rui Silva wrote:
> Let's be patient and trust that every possible effort is being made by the
> people in charge to bring this to fruition as soon as possible. Then, it's
> on to a first release and on to the path out of incubation!
For now, I think that's a fine
Hi,
> I made a couple of changes to your PostCodeValidator class in order for it
> to "understand" Portuguese postcodes.
Great send me the patches.
> Do you want me to send in a patch or is it OK if I just commit the code to
> your whiteboard?
And that is fine by me as well.
> I also wanted to
Hi Tink
markmail is not as easy to search as a google group! I read what posts I
could find but it was not clear
whether the only way of interacting with the haXe environment was via a
port of AS3 source to haXe
or whether there was some other approach. I did not see a post from
Nicholas on t
Hi Justin,
I made a couple of changes to your PostCodeValidator class in order for it
to "understand" Portuguese postcodes. I've also updated the unit tests to
include Portuguese postcode.
Do you want me to send in a patch or is it OK if I just commit the code to
your whiteboard?
I also wante
The topic was discussed a little, but it seemed to me that the general
feeling was "as3 is not haxe", and "let's wait and see what adobe
hands us on a plate".
I am definitely interested in such a project, but it's still an idea
that needs some traction in the community, or it will have some
diffic
>I think it is better to wait. Folks could probably play around on their own
>with the Adobe mustella.swc, but I don't want to take the time to deal with
>questions and doc and bugs right now.
Alex,
Let's just say I happen to have an older version of the source... If I was
willing to support
Hi James
Hope all is well mate.
Try searching the archives as this has been discussed previously on the list
and Nicholas took part in the discussion.
Tink
James Cowan wrote:
>
>MXML/AS3/Flex are conceptually identical to XAML/C#/WPF. They borrow a
>lot of ideas from previous XML UI technol
Original Message
> From: "Bertrand Delacretaz"
>
> I agree that these delays are not good, but I don't think we can do
> much about them. Either wait, or rewrite the missing parts.
>
As do I, but if you look around at other Apache project that were donated
in a mature state
Original Message
> From: "Bertrand Delacretaz"
>
> I don't think this has been mentioned on this list yet:
>
> http://incubator.apache.org/learn/rules-for-revolutionaries.html
>
> "Any committer has the right to go start a revolution" - and if you're
> not a committer yet, s
Hi Igor,
On Mon, Mar 12, 2012 at 6:17 PM, Igor Costa wrote:
> ...I'm only wondering and we should let people know, why is taking so long to
> donate the source code base to Apache...
Don't you think Alex and Carol have provided sufficient info as to why
this is taking longer than expected?
I ag
I don't think this has been mentioned on this list yet:
http://incubator.apache.org/learn/rules-for-revolutionaries.html
"Any committer has the right to go start a revolution" - and if you're
not a committer yet, starting a revolution in your own corner of
github (or any other suitable place) mig
Hi,
On Tue, Mar 13, 2012 at 8:03 AM, Alex Harui wrote:
> ...I think the ASF has a process for checking the legality of all of our code
> before we graduate. But when donating, I believe it is up to you to follow
> the rules. Large donations require a software grant stating you have
> permission
MXML/AS3/Flex are conceptually identical to XAML/C#/WPF. They borrow a
lot of ideas from previous XML UI technologies.
MXML/haXe/Flex does sound quite viable.
The issue is that both Silverlight and Flash are dieing and haXe
represents a future for Flex because it is clever cross compiler
tech
Original Message
> From: "Arnoud Bos"
>
> Hi Tink,
>
> Your layouts / navigators are of great value! So consider this as interest :-)
> Maybe because they just work and people can grab them from the whiteboard
> there is not much feedback.
Interesting you mention this as I've ju
Tink,
Love your stuff as well.
I'm working on a respons to your idea about step-scrolling-layouts. Just trying
to find the time (and the brains) to do it in code.
Keep up the good work!
/E
I know this has nothing to do with the original
discussion, which actually summed my position
quite well too
Every time there is a new component or code from
Tink, I ALWAYs just add it to my sdk base as start
using it right away. I trust it that much.
The process we are at the beginning of is goi
>
> Hi Tink,
>
> Your layouts / navigators are of great value! So consider this as interest
> :-)
> Maybe because they just work and people can grab them from the whiteboard
> there is not much feedback.
>
> Looks to me like some really well architectured code with good
> documentation and
> exampl
Hi Tink,
Your layouts / navigators are of great value! So consider this as interest :-)
Maybe because they just work and people can grab them from the whiteboard
there is not much feedback.
Looks to me like some really well architectured code with good documentation and
examples and definitely d
On 13/03/2012 08:16, Om wrote:
Is there an effort to start writing unit tests for the Flex SDK? I know
that the Mustella suite is coming, but I have heard calls for a real unit
test suite. I would love to contribute by writing as many unit tests as
possible for the existing SDK code. I realize
Existing validator and formatter classes only validate US and Canadian postcodes
Key: FLEX-29
URL: https://issues.apache.org/jira/browse/FLEX-29
Project: Apache Flex
Hi,
> I may change my mind about this in the morning, but this is just too much
> process.
I see it as more of a list of what you may need to think about/get other people
to help you out along the way with rather than a step by step process. Perhaps
I should of left off the numbers? I certainly
On 3/12/12 6:09 PM, "jude" wrote:
> We need the guys from Adobe to chime in and share their process, the goals,
> constraints and principles of Flex SDK development and requirements. As
> much of what they do, why they do it and how would ease the transition.
IMHO, the old Adobe process, goals
67 matches
Mail list logo
