On 8/1/12 11:23 PM, "ranboleelan" wrote:
> not all mx components have their spark equivalent ones, so i guess more spark
> components in future version would be nice.
>
The prototypes we have are waiting VP signature then they will be checked
in.
--
Alex Harui
Flex SDK Team
Adobe Systems, I
not all mx components have their spark equivalent ones, so i guess more spark
components in future version would be nice.
ranboleelan
From: Alex Harui
Date: 2012-08-02 14:14
To: flex-dev@incubator.apache.org
Subject: Re: [ROADMAP] Apache Flex Steering Survey
On 8/1/12 10:25 PM, "Erik de Br
On 8/1/12 10:25 PM, "Erik de Bruin" wrote:
>> next. No consensus has to be reached on what will be worked on. Folks are
>> free to do what they want.
>
> Free to create a roadmap and try to give some direction to people
> looking to contribute, but not sure where to begin, or which
> featur
Keith,
I'm sorry I did not respond to your first roadmap email. Honestly, I
stopped reading after your first bullet point raising FUD about whether
Adobe would live up to its commitments without any quoting of the statements
behind your logic. I almost responded, but when nobody else did, I just
The component list was developed reviewing the emails on the mailing
list as we as the Flex White Paper. The component list was provided
earlier with the request for corrections but none were forthcoming.
Given that Adobe's resource commitment is not indefinite it would be
most appropriate to d
> next. No consensus has to be reached on what will be worked on. Folks are
> free to do what they want.
Free to create a roadmap and try to give some direction to people
looking to contribute, but not sure where to begin, or which
features/bug fixes would benefit the end users the most, like my
On 8/1/2012 8:22 PM, Alex Harui wrote:
Keith,
I appreciate the effort, and more data is welcome, but I don't think Apache
projects have roadmaps or make commitments on what is going to be delivered
next. No consensus has to be reached on what will be worked on. Folks are
free to do what they w
Keith,
I appreciate the effort, and more data is welcome, but I don't think Apache
projects have roadmaps or make commitments on what is going to be delivered
next. No consensus has to be reached on what will be worked on. Folks are
free to do what they want.
I also don't understand the items o
All,
Some of you may have seen tweets and emails concerning a Apache Flex
Steering Survey which currently has more than 375 respondents since July
26th.
With the successful release of Apache Flex 4.8.0-incubating (previously
announced below) it is timely to have a discussion/consensus around
[
https://issues.apache.org/jira/browse/FLEX-33149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426879#comment-13426879
]
Alex Harui commented on FLEX-33149:
---
I don't know how close Nick is to getting this done
[
https://issues.apache.org/jira/browse/FLEX-33149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426853#comment-13426853
]
OmPrakash Muppirala commented on FLEX-33149:
I am still waiting for Nick to im
[
https://issues.apache.org/jira/browse/FLEX-33150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426835#comment-13426835
]
OmPrakash Muppirala commented on FLEX-33150:
Erik,
Thanks a lot for working o
[
https://issues.apache.org/jira/browse/FLEX-33143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426801#comment-13426801
]
Emmanuel Jacquier commented on FLEX-33143:
--
I had lot of weird bug with TextInput
[
https://issues.apache.org/jira/browse/FLEX-33143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426762#comment-13426762
]
Emmanuel Jacquier commented on FLEX-33143:
--
By default, its the StageTextInputSki
Hi Joris,
If you downloaded the 'raw' binaries from the Apache site, did you
check out the README [1] that goes with it? It notes several
installation requirements and dependencies.
You might also consider using Om's SDK install app, which handles
these details for you. You can find it at [2].
I
[
https://issues.apache.org/jira/browse/FLEX-33150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik de Bruin updated FLEX-33150:
-
Attachment: InstallApacheFlex_Patch_EdB_MD5_2012-08-01.txt
I've created a utility class that read
[
https://issues.apache.org/jira/browse/FLEX-33155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426626#comment-13426626
]
Carol Frampton commented on FLEX-33155:
---
Java 1.7 is not yet supported by Apache Fle
I tried it out today, and I was able to successfully update it to 0.7.13 on
Windows. Thanks Om!
How can I keep a track of what changes are going into the newer revisions of
this tool. Why I am asking this is because I have logged a bug
https://issues.apache.org/jira/browse/FLEX-33145 which is re
[
https://issues.apache.org/jira/browse/FLEX-33155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudhir updated FLEX-33155:
--
Attachment: UncaughtException_Compiler.log
Attaching the error log
> Uncaught exception in com
[
https://issues.apache.org/jira/browse/FLEX-33155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudhir updated FLEX-33155:
--
Priority: Major (was: Minor)
Summary: Uncaught exception in compiler, when JRE 1.7 is used (was:
Uncaugh
Sudhir created FLEX-33155:
-
Summary: Uncaught exception in compiler, when used with JRE 1.7
Key: FLEX-33155
URL: https://issues.apache.org/jira/browse/FLEX-33155
Project: Apache Flex
Issue Type: Bug
[
https://issues.apache.org/jira/browse/FLEX-33149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426352#comment-13426352
]
Erik de Bruin commented on FLEX-33149:
--
Om, you might want to include the change to t
22 matches
Mail list logo
