You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Keith Sutton <ke...@spoon.as> on 2012/08/03 17:51:00 UTC
Re: [ROADMAP] Apache Flex Steering Survey - Revised component status
Based on Alex's email this is a revise component list to go into survey
(PLEASE identify anything missing or in wrong place):
Available in 4.8
4.6 automation libraries
4.6 fabridge
4.6 flash-integration
4.6 samples
Flex MXML compiler source code
Yet to be donated
? 4.6 missing embedded font support
4.6 ViewStack (listed in Flex White Paper - protoype)
4.6 Accordion (listed in Flex White Paper but does not exist)
4.6 DateField (listed in Flex White Paper - protoype)
4.6 DataChooser (listed in Flex White Paper - protoype)
4.6 Enhanced DataGrid (listed in Flex White Paper - protoype)
BlazeDS/BlazeDS.NET
3.x Flex SDK
TLF
Gravity
FXG - will this continue to be supported beyond CS6?
Squiggly
OSMF
Falcon (2012 Q4)
Re: [ROADMAP] Apache Flex Steering Survey - Squiggly and Gravity
Posted by jude <fl...@gmail.com>.
Yeah, it's Monocle. OK I just saw the your post on Gravity further down. I
could use something like this on a project I'm working on now.
On Sun, Aug 5, 2012 at 11:36 AM, Keith Sutton <ke...@spoon.as> wrote:
> Good on Squiggly Jude, Gravity below, can't find anything on Telemetry -
> did this become Monocle?
>
> On 8/5/2012 1:27 AM, jude wrote:
>
>> Squiggly is an Action Script spell checking library for developers who
>> work
>> in Adobe® Flash® Professional, Adobe Flex® Builder™, or other IDEs that
>> support ActionScript. The Squiggly package contains six .swc files – three
>> of which integration convenience classes called SpellUI, one for Flex 3,
>> another for Flex 4, and a third one for TLF. [0]
>>
>> I don't know what Gravity is either. Is it Telemetry? BTW What happened to
>> Telemetry?
>>
> Gravity
>
> "The ADEP Client Component Framework (codename Gravity) is an ActionScript
> library that takes the concepts of OSGi and applies them to ActionScript.
> It provides a module and/or plugin architecture in which individual pieces
> can be added and removed seamlessly. The Gravity SDK comes with the es-sdk
> package for Experience Services. The parts become much more independent of
> each other allowing easier integration of content from different teams or
> repurposing of existing content. It makes it easier to have a library of
> parts that are put together as needed for applications."
> http://blogs.adobe.com/**dekesmith/2011/10/17/**deconstructing-experience-
> **services-client-component-**framework-gravity/<http://blogs.adobe.com/dekesmith/2011/10/17/deconstructing-experience-services-client-component-framework-gravity/>
>
> HelloGravity Sample Application: http://blogs.adobe.com/**
> gravity/2011/09/09/**hellogravity-sample-**application/<http://blogs.adobe.com/gravity/2011/09/09/hellogravity-sample-application/>
>
> Video tutorials:
> http://www.youtube.com/watch?**v=NxLnnPm-84g&list=UU3x6nH-**
> 4vot_ipxZ7CBJutw&index=7&**feature=plcp<http://www.youtube.com/watch?v=NxLnnPm-84g&list=UU3x6nH-4vot_ipxZ7CBJutw&index=7&feature=plcp>
> http://www.youtube.com/watch?**v=Dn7R7W8QaIU&list=UU3x6nH-**
> 4vot_ipxZ7CBJutw&index=6&**feature=plcp<http://www.youtube.com/watch?v=Dn7R7W8QaIU&list=UU3x6nH-4vot_ipxZ7CBJutw&index=6&feature=plcp>
> http://www.youtube.com/watch?**v=PTEVNudQLWk&list=UU3x6nH-**
> 4vot_ipxZ7CBJutw&index=5&**feature=plcp<http://www.youtube.com/watch?v=PTEVNudQLWk&list=UU3x6nH-4vot_ipxZ7CBJutw&index=5&feature=plcp>
>
> A similar framework is Potomac: http://www.potomacframework.**org/<http://www.potomacframework.org/>
> The Potomac Framework for Flex is:
>
> A modularity framework inspired by OSGi
> A UI composition framework that pulls user interface ‘parts’ together
> to form applications
> A general purpose business application framework (providing reusable
> features for business applications)
> A dependency injection framework
> An extensible metadata processor with reflection support
>
>
Re: [ROADMAP] Apache Flex Steering Survey - Squiggly and Gravity
Posted by Keith Sutton <ke...@spoon.as>.
Good on Squiggly Jude, Gravity below, can't find anything on Telemetry -
did this become Monocle?
On 8/5/2012 1:27 AM, jude wrote:
> Squiggly is an Action Script spell checking library for developers who work
> in Adobe® Flash® Professional, Adobe Flex® Builder™, or other IDEs that
> support ActionScript. The Squiggly package contains six .swc files – three
> of which integration convenience classes called SpellUI, one for Flex 3,
> another for Flex 4, and a third one for TLF. [0]
>
> I don't know what Gravity is either. Is it Telemetry? BTW What happened to
> Telemetry?
Gravity
"The ADEP Client Component Framework (codename Gravity) is an
ActionScript library that takes the concepts of OSGi and applies them to
ActionScript. It provides a module and/or plugin architecture in which
individual pieces can be added and removed seamlessly. The Gravity SDK
comes with the es-sdk package for Experience Services. The parts become
much more independent of each other allowing easier integration of
content from different teams or repurposing of existing content. It
makes it easier to have a library of parts that are put together as
needed for applications."
http://blogs.adobe.com/dekesmith/2011/10/17/deconstructing-experience-services-client-component-framework-gravity/
HelloGravity Sample Application:
http://blogs.adobe.com/gravity/2011/09/09/hellogravity-sample-application/
Video tutorials:
http://www.youtube.com/watch?v=NxLnnPm-84g&list=UU3x6nH-4vot_ipxZ7CBJutw&index=7&feature=plcp
http://www.youtube.com/watch?v=Dn7R7W8QaIU&list=UU3x6nH-4vot_ipxZ7CBJutw&index=6&feature=plcp
http://www.youtube.com/watch?v=PTEVNudQLWk&list=UU3x6nH-4vot_ipxZ7CBJutw&index=5&feature=plcp
A similar framework is Potomac: http://www.potomacframework.org/
The Potomac Framework for Flex is:
A modularity framework inspired by OSGi
A UI composition framework that pulls user interface ‘parts’
together to form applications
A general purpose business application framework (providing
reusable features for business applications)
A dependency injection framework
An extensible metadata processor with reflection support
RE: [ROADMAP] Apache Flex Steering Survey
Posted by "Guthmann, Scott" <sg...@on3solutions.com>.
> Although the survey attempts to get to the bottom of feature priorities, I can't help feeling that we should be including parties other than this mailing list to take part in the survey. Although many of this list's participants including myself have an exposure > to a subset of the corporate users requirements, does anyone have any ideas how we could ( and if we should ) be trying to include the high paying end customers in our surveys ? i.e. the big corporations that were (and in some cases are) spending
> money on Flex development ? Is this information Spoon can get access to through their network?
Daniel - the survey is not part of the Apache Flex project. The survey is currently live and will be open until Aug 21st, 2012 and the survey link is here: http://www.surveymonkey.com/s/TWTJ2VS. The survey is meant to generate interest, recruit help & engagement, and isn't limited to those participating in the project or restricted in some other way. If you wish to distribute the survey, you may. If you wish to take the survey, please do. The Apache Way allows those who wish to participate to do so without anybody's permission or guidance. Each person can scratch their own itch. My itch was facilitating a conversation around development priorities & preferences of Flex community members.
> Obviously I appreciate that some of these large spending corporations will have members monitoring this list, but some may not as they probably relied on Adobe (and partners) sales & marketing effort to keep them posted.
IMO, a very good way to access the sales and marketing resources available for Apache Flex is to join the Spoon mailing list today http://www.spoon.as/contact-spoon/. Flex ecosystem partners, Flex user groups, Flex service provider directories, Flex conference speakers, Flex evangelism resources, Spoon monthly newsletter archives, and other authoritative information is posted for all to consume, enjoy, and distribute. Please encourage those who need help to ask for what they need! Spoon will get your colleagues the help they need.
> As much as I appreciate the effort which has been put into the survey, I can't help feeling it is a little bit leaning towards some kind of 'progress report' on Adobe donations rather than a focus on whats next.
You're welcome! The power of the Apache Way is that participation is not limited or directed by the Spoon survey. The results are a Flex community conversation starter, do not have any official weight with commenters, contributors, committers, or users of the Flex SDK. We also look forward to imagining the possibilities, too. There will probably be new powerful features that haven't been conceived yet, spontaneous discussions of future project direction, and a completely unknowable future for Flex as part of the ASF. It is an exciting time!
Re: [ROADMAP] Apache Flex Steering Survey
Posted by Keith Sutton <ke...@spoon.as>.
below
On 8/7/2012 8:52 AM, Daniel Harfleet wrote:
> Mike's statement "I am sure there are customers using it" has reminded me a thought I had about the 'survey' which I wanted to share...
>
> Many members on this list have probably felt an impact on their livelihood as a result of the changes relating to Adobe's actions around Flex. My primary motivation in committing to work in my spare time on Apache Flex would be to help ensure the longevity of Flex and hence my livelihood (although I recognize and respect for some it may be more oriented towards hobby/interest/other).
>
> Although the survey attempts to get to the bottom of feature priorities, I can't help feeling that we should be including parties other than this mailing list to take part in the survey. Although many of this list's participants including myself have an exposure to a subset of the corporate users requirements, does anyone have any ideas how we could ( and if we should ) be trying to include the high paying end customers in our surveys ? i.e. the big corporations that were (and in some cases are) spending money on Flex development ? Is this information Spoon can get access to through their network?
>> I couldn't agree more with this but, I think Apache Flex has to get
to a point where it has something to offer those corporate users over
and above 4.6. With the release of 4.8.-incubating we are definitely
closer to that point and will likely get there in the next release. At
that point (and working up to it) we should be able to go out to those
corporate users with not just a message but a product. Fundamentally, Q1
in the survey is about digging out what is "essential to commercial /
economic success for Apache Flex within the next 6-12 months".
>> I believe there are lines of communication to 'corporate users' from
within the network of Spoon, 3rd party product vendors, service
providers and people on this list which we can follow but this needs to
be done in an organized fashion. Typically with successful open source
initiatives this is undertaken by a commercial entity associated with
the project that builds offerings on top of the project (ex hadoop >>
cloudera, spring >> springsource). This is something Spoon is thinking
about how to get started.
>
> For example only, I personally can see a big benefit to putting effort into FalconJS, but it may be that 9 out 10 large spenders in Flex development may actually not care about HTML/JS and are more concerned about performance increases/additional components/bug fixes, etc ?
>> Agree, no technology is good at everything, with FalconJS we could
offer a path from Flex for those things that HTML5/JS does better. I
can't think of a better bunch of people to define/adopt a JS framework
than the people on this list.
>
> Obviously I appreciate that some of these large spending corporations will have members monitoring this list, but some may not as they probably relied on Adobe (and partners) sales & marketing effort to keep them posted.
>> Agree, AF is in a unique situation, it has an established
user-based, we just need to get organized to access and inform it.
>
> I am not saying I like the idea of a 'roadmap', but I do like the idea of a 'picklist' of features that paying organizations have stated an interest in.
>
> As much as I appreciate the effort which has been put into the survey, I can't help feeling it is a little bit leaning towards some kind of 'progress report' on Adobe donations rather than a focus on whats next.
>> Agreed, but it is a good place to start/clarify. One of the things
coming out of the survey is the 'other' things people think are
important and that is going to be a good basis for discussion on what is
next for non-Adobe people to work on.
>
>
> dan
Re: [ROADMAP] Apache Flex Steering Survey
Posted by Daniel Harfleet <dh...@yahoo.com>.
Mike's statement "I am sure there are customers using it" has reminded me a thought I had about the 'survey' which I wanted to share...
Many members on this list have probably felt an impact on their livelihood as a result of the changes relating to Adobe's actions around Flex. My primary motivation in committing to work in my spare time on Apache Flex would be to help ensure the longevity of Flex and hence my livelihood (although I recognize and respect for some it may be more oriented towards hobby/interest/other).
Although the survey attempts to get to the bottom of feature priorities, I can't help feeling that we should be including parties other than this mailing list to take part in the survey. Although many of this list's participants including myself have an exposure to a subset of the corporate users requirements, does anyone have any ideas how we could ( and if we should ) be trying to include the high paying end customers in our surveys ? i.e. the big corporations that were (and in some cases are) spending money on Flex development ? Is this information Spoon can get access to through their network?
For example only, I personally can see a big benefit to putting effort into FalconJS, but it may be that 9 out 10 large spenders in Flex development may actually not care about HTML/JS and are more concerned about performance increases/additional components/bug fixes, etc ?
Obviously I appreciate that some of these large spending corporations will have members monitoring this list, but some may not as they probably relied on Adobe (and partners) sales & marketing effort to keep them posted.
I am not saying I like the idea of a 'roadmap', but I do like the idea of a 'picklist' of features that paying organizations have stated an interest in.
As much as I appreciate the effort which has been put into the survey, I can't help feeling it is a little bit leaning towards some kind of 'progress report' on Adobe donations rather than a focus on whats next.
dan
RE: [ROADMAP] Apache Flex Steering Survey - Revised component status
Posted by "Michael A. Labriola" <la...@digitalprimates.net>.
>I don't know what Gravity is either. Is it Telemetry? BTW What happened to Telemetry?
Gravity is a framework which, in theory, solves the problems associated with multiple domain applications using the Marshall plan by providing a structure to work within. While my opinion may be somewhat controversial on this, I see Gravity as a work around to the problems created through a work around.
I am sure there are customers using it, and if it helps them we should pursue it... however, I would put it somewhere around the 101st priority of our top 100 in my mind.
Mike
Re: [ROADMAP] Apache Flex Steering Survey - Revised component status
Posted by jude <fl...@gmail.com>.
Squiggly is an Action Script spell checking library for developers who work
in Adobe® Flash® Professional, Adobe Flex® Builder™, or other IDEs that
support ActionScript. The Squiggly package contains six .swc files – three
of which integration convenience classes called SpellUI, one for Flex 3,
another for Flex 4, and a third one for TLF. [0]
I don't know what Gravity is either. Is it Telemetry? BTW What happened to
Telemetry?
[0] http://labs.adobe.com/technologies/squiggly/releasenotes.html
On Fri, Aug 3, 2012 at 11:04 AM, Carol Frampton <cf...@adobe.com> wrote:
>
>
> On 8/3/12 11 :51AM, "Keith Sutton" <ke...@spoon.as> wrote:
>
> >Based on Alex's email this is a revise component list to go into survey
> >(PLEASE identify anything missing or in wrong place):
> >
> >Available in 4.8
> > 4.6 automation libraries
> > 4.6 fabridge
> > 4.6 flash-integration
> > 4.6 samples
> > Flex MXML compiler source code
> >
> >Yet to be donated
> > ? 4.6 missing embedded font support
> 4.8.0 has embedded font support if you're willing to use
> the Adobe jars
> with the Adobe license which isn't compatible with the Apache license
> source won't be donated - it is Adobe proprietary
> Apache Flex would have to implement the support
>
> 4.6 DateField (listed in Flex White Paper - protoype)
> nothing to donate - work wasn't started
>
>
> > 4.6 ViewStack (listed in Flex White Paper - protoype)
> > 4.6 Accordion (listed in Flex White Paper but does not exist)
> > 4.6 DataChooser (listed in Flex White Paper - protoype
> > 4.6 Enhanced DataGrid (listed in Flex White Paper - protoype)
>
> both ViewStack and Accordion are just about done and some
> testing has
> been done
> several DG features were completed and tested inc locked
> rows and
> columns
> DataChooser is more than prototype but has a fair amount
> of remaining
> work
>
>
> I'll check it all into whiteboard/cframpton/adobe.next as
> soon as we get
> the VP signature - paperwork on his desk
>
> > BlazeDS/BlazeDS.NET
> > 3.x Flex SDK
> Peter will start this process as soon as mustella gets in
> - will have to
> spend a fair amount of time cleaning before donation as we did for 4.6
>
> > TLF
> donation in the works - already thru Adobe legal and some
> signatures
> have already been gotten
>
> Falcon (2012 Q4)
>
> Alex and Gordon working on this now
>
> > Gravity
> > FXG - will this continue to be supported beyond CS6?
> > Squiggly
> > OSMF
> don't know but never heard of Gravity or Squiggly before
> this list
> >
>
>
Re: [ROADMAP] Apache Flex Steering Survey - Revised component status
Posted by Alex Harui <ah...@adobe.com>.
On 8/7/12 8:24 AM, "dharfleet@yahoo.com" <dh...@yahoo.com> wrote:
> Alex,
>
> with respect to Gravity, when you say "won't happen unless .... " is the
> reasoning behind this related to the amount of effort involved in
> 're-packaging' for Apache and legal compliance ?
>
>
> dan
Yes. I think Adobe's resources should be elsewhere, including changes to
the framework that would make Gravity much less needed.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: [ROADMAP] Apache Flex Steering Survey - Revised component status
Posted by Daniel Harfleet <dh...@yahoo.com>.
Alex,
with respect to Gravity, when you say "won't happen unless .... " is the reasoning behind this related to the amount of effort involved in 're-packaging' for Apache and legal compliance ?
dan
________________________________
From: Alex Harui <ah...@adobe.com>
To: "flex-dev@incubator.apache.org" <fl...@incubator.apache.org>
Sent: Friday, 3 August 2012, 17:09
Subject: Re: [ROADMAP] Apache Flex Steering Survey - Revised component status
On 8/3/12 8:51 AM, "Keith Sutton" <ke...@spoon.as> wrote:
> Based on Alex's email this is a revise component list to go into survey
> (PLEASE identify anything missing or in wrong place):
>
> Available in 4.8
> 4.6 automation libraries
> 4.6 fabridge
> 4.6 flash-integration
> 4.6 samples
> Flex MXML compiler source code
>
> Yet to be donated
> ? 4.6 missing embedded font support
Probably won't be donated, but in theory the one part we need (CFF
Embedding) is not too hard for us to re-write in Apache.
> 4.6 ViewStack (listed in Flex White Paper - protoype)
> 4.6 Accordion (listed in Flex White Paper but does not exist)
> 4.6 DateField (listed in Flex White Paper - protoype)
> 4.6 DataChooser (listed in Flex White Paper - protoype)
> 4.6 Enhanced DataGrid (listed in Flex White Paper - protoype)
These just got signed off yesterday.
> BlazeDS/BlazeDS.NET
> 3.x Flex SDK
> TLF
All are in progress, TLF will probably be next.
> Squiggly
> OSMF
> Gravity
Won't happen unless we hear lots of people want it.
> FXG - will this continue to be supported beyond CS6?
Support is in the compiler, but there is no guarantee that Adobe apps will
continue to export it.
> Falcon (2012 Q4)
In legal audit now.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
[DISCUSS] Navigators (was [ROADMAP] Apache Flex Steering Survey - Revised component status)
Posted by Tink <fl...@tink.ws>.
Hey Alex
Have the navigators been committed to a whiteboard anywhere?
I like to open up some discussion about navigators, but thought I'd wait for these to be committed first.
cheers
Tink
On 3 Aug 2012, at 17:09, Alex Harui wrote:
>> 4.6 ViewStack (listed in Flex White Paper - protoype)
>> 4.6 Accordion (listed in Flex White Paper but does not exist)
>> 4.6 DateField (listed in Flex White Paper - protoype)
>> 4.6 DataChooser (listed in Flex White Paper - protoype)
>> 4.6 Enhanced DataGrid (listed in Flex White Paper - protoype)
> These just got signed off yesterday.
Re: [ROADMAP] Apache Flex Steering Survey - Revised component status
Posted by superabe superabe <su...@gmail.com>.
Ok thanks for the info
It's a relief to know at least somebody is maintaining and advancing it :)
It's a rather crucial piece for most video related apps.
On Fri, Aug 3, 2012 at 1:24 PM, Michael A. Labriola <
labriola@digitalprimates.net> wrote:
> >About OSMF. What is the status of OSMF? Is it being actively maintained
> and developed by Adobe?
>
> OSMF is still being actively maintained and expanded by Adobe, that is
> probably part of the reason we won't see it soon/ever without some work on
> our part.
>
>
>
RE: [ROADMAP] Apache Flex Steering Survey - Revised component status
Posted by "Michael A. Labriola" <la...@digitalprimates.net>.
>About OSMF. What is the status of OSMF? Is it being actively maintained and developed by Adobe?
OSMF is still being actively maintained and expanded by Adobe, that is probably part of the reason we won't see it soon/ever without some work on our part.
Re: [ROADMAP] Apache Flex Steering Survey - Revised component status
Posted by superabe superabe <su...@gmail.com>.
>
>
>>> All are in progress, TLF will probably be next.
>>
>> Squiggly
>>> * OSMF*
>>> Gravity
>>>
>> Won't happen unless we hear lots of people want it.
>>
>>
>>
>>
About OSMF. What is the status of OSMF? Is it being actively maintained and
developed by Adobe?
By "Won't happen..." do you mean OSMF won't get donated to Apache or that
it won't be maintained at all even by Adobe.
Thx,
-superabe
Re: [ROADMAP] Apache Flex Steering Survey - Revised component status
Posted by Keith Sutton <ke...@spoon.as>.
Alex/Carol,
Awesome, thanks
We will role that back into the survey
On 8/3/2012 9:09 AM, Alex Harui wrote:
>
>
> On 8/3/12 8:51 AM, "Keith Sutton" <ke...@spoon.as> wrote:
>
>> Based on Alex's email this is a revise component list to go into survey
>> (PLEASE identify anything missing or in wrong place):
>>
>> Available in 4.8
>> 4.6 automation libraries
>> 4.6 fabridge
>> 4.6 flash-integration
>> 4.6 samples
>> Flex MXML compiler source code
>>
>> Yet to be donated
>> ? 4.6 missing embedded font support
> Probably won't be donated, but in theory the one part we need (CFF
> Embedding) is not too hard for us to re-write in Apache.
>> 4.6 ViewStack (listed in Flex White Paper - protoype)
>> 4.6 Accordion (listed in Flex White Paper but does not exist)
>> 4.6 DateField (listed in Flex White Paper - protoype)
>> 4.6 DataChooser (listed in Flex White Paper - protoype)
>> 4.6 Enhanced DataGrid (listed in Flex White Paper - protoype)
> These just got signed off yesterday.
>
>> BlazeDS/BlazeDS.NET
>> 3.x Flex SDK
>> TLF
> All are in progress, TLF will probably be next.
>
>> Squiggly
>> OSMF
>> Gravity
> Won't happen unless we hear lots of people want it.
>
>> FXG - will this continue to be supported beyond CS6?
> Support is in the compiler, but there is no guarantee that Adobe apps will
> continue to export it.
>
>> Falcon (2012 Q4)
> In legal audit now.
>
Re: [ROADMAP] Apache Flex Steering Survey - Revised component status
Posted by Alex Harui <ah...@adobe.com>.
On 8/3/12 8:51 AM, "Keith Sutton" <ke...@spoon.as> wrote:
> Based on Alex's email this is a revise component list to go into survey
> (PLEASE identify anything missing or in wrong place):
>
> Available in 4.8
> 4.6 automation libraries
> 4.6 fabridge
> 4.6 flash-integration
> 4.6 samples
> Flex MXML compiler source code
>
> Yet to be donated
> ? 4.6 missing embedded font support
Probably won't be donated, but in theory the one part we need (CFF
Embedding) is not too hard for us to re-write in Apache.
> 4.6 ViewStack (listed in Flex White Paper - protoype)
> 4.6 Accordion (listed in Flex White Paper but does not exist)
> 4.6 DateField (listed in Flex White Paper - protoype)
> 4.6 DataChooser (listed in Flex White Paper - protoype)
> 4.6 Enhanced DataGrid (listed in Flex White Paper - protoype)
These just got signed off yesterday.
> BlazeDS/BlazeDS.NET
> 3.x Flex SDK
> TLF
All are in progress, TLF will probably be next.
> Squiggly
> OSMF
> Gravity
Won't happen unless we hear lots of people want it.
> FXG - will this continue to be supported beyond CS6?
Support is in the compiler, but there is no guarantee that Adobe apps will
continue to export it.
> Falcon (2012 Q4)
In legal audit now.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: [ROADMAP] Apache Flex Steering Survey - Revised component status
Posted by Carol Frampton <cf...@adobe.com>.
On 8/3/12 11 :51AM, "Keith Sutton" <ke...@spoon.as> wrote:
>Based on Alex's email this is a revise component list to go into survey
>(PLEASE identify anything missing or in wrong place):
>
>Available in 4.8
> 4.6 automation libraries
> 4.6 fabridge
> 4.6 flash-integration
> 4.6 samples
> Flex MXML compiler source code
>
>Yet to be donated
> ? 4.6 missing embedded font support
4.8.0 has embedded font support if you're willing to use the Adobe jars
with the Adobe license which isn't compatible with the Apache license
source won't be donated - it is Adobe proprietary
Apache Flex would have to implement the support
4.6 DateField (listed in Flex White Paper - protoype)
nothing to donate - work wasn't started
> 4.6 ViewStack (listed in Flex White Paper - protoype)
> 4.6 Accordion (listed in Flex White Paper but does not exist)
> 4.6 DataChooser (listed in Flex White Paper - protoype
> 4.6 Enhanced DataGrid (listed in Flex White Paper - protoype)
both ViewStack and Accordion are just about done and some testing has
been done
several DG features were completed and tested inc locked rows and
columns
DataChooser is more than prototype but has a fair amount of remaining
work
I'll check it all into whiteboard/cframpton/adobe.next as soon as we get
the VP signature - paperwork on his desk
> BlazeDS/BlazeDS.NET
> 3.x Flex SDK
Peter will start this process as soon as mustella gets in - will have to
spend a fair amount of time cleaning before donation as we did for 4.6
> TLF
donation in the works - already thru Adobe legal and some signatures
have already been gotten
Falcon (2012 Q4)
Alex and Gordon working on this now
> Gravity
> FXG - will this continue to be supported beyond CS6?
> Squiggly
> OSMF
don't know but never heard of Gravity or Squiggly before this list
>