Ted Patrick - Demos & MAX @ Adobe Systems
Note: This is the personal blog of Ted Patrick. The opinions and statements voiced here are my own.
Flex Component Activity +10
DIGG IT!
2
Comments
Published
Thursday, March 01, 2007
at
10:58 AM
.
There has been a huge uptick in activity in the Flex Component space. It seems that many developers are making components and extending Flex in unique ways. Four projects to highlight are FlexLib, FlexBox, FlexComponents List, and Flex Exchange.FlexLib
FlexLib is a source code repository for Flex components under an MIT license. The repository contains there open source components: ConvertibleTreeList, Draggable Slider, PromptingTextInput, Scrollable Menu Controls, SuperTabNavigator, Alternative Scrolling Canvases, Horizontal Accordion
FlexBox
FlexBox is a directory of 101 Flex components in a Flex RIA. It is a great source for locating various Flex components scattered all over the Internet.
FlexComponents Discussion List
If you are making components or extending Flex this is the mother of all lists. Backed by some of the framework engineers and packed with great devs, FlexComponents is a great resource.
Flex Exchange
Flex Exchange at Adobe.com is a directory of Flex components submitted by developers.
Cheers,
Ted :)
2 Responses to “Flex Component Activity +10”
Post a CommentWhere to find me:
Ted on Twitter - @AdobeTed
Ted on Adobe Groups
Ted on LinkedIn
Ted on Facebook
Ted at Adobe
Latest
- First day of work at Yahoo!
- Adobe Engage Thoughts
- Tour of California - LIVE - Part 2
- Tour of California - LIVE
- Ready for Apollo? Sign up for ApolloCamp NOW!!!
- FlexApps Component - Version 0.9
- Flipper (FlexApps Viewer) by Cynergy Systems
- Code-Behind in Flex 2
- FlexJobs - 100 Jobs in 20 Days
- Flex Instantiation Life Cycle and Event Flow
Lists
Links
Jobs
Flex JobsArchives
- May 2003
- June 2003
- July 2003
- August 2003
- September 2003
- October 2003
- November 2003
- December 2003
- January 2004
- February 2004
- March 2004
- April 2004
- May 2004
- June 2004
- July 2004
- August 2004
- September 2004
- October 2004
- November 2004
- December 2004
- January 2005
- February 2005
- March 2005
- April 2005
- May 2005
- June 2005
- July 2005
- August 2005
- September 2005
- October 2005
- November 2005
- December 2005
- January 2006
- February 2006
- March 2006
- April 2006
- May 2006
- June 2006
- July 2006
- August 2006
- September 2006
- October 2006
- November 2006
- December 2006
- January 2007
- February 2007
- March 2007
- April 2007
- May 2007
- June 2007
- July 2007
- August 2007
- September 2007
- October 2007
- November 2007
- December 2007
- January 2008
- February 2008
- March 2008
- April 2008
- May 2008
- June 2008
- July 2008
- August 2008
- September 2008
- October 2008
- November 2008
- December 2008
- January 2009
- February 2009
- March 2009
- April 2009
- May 2009
- June 2009
- July 2009
- August 2009
- September 2009
- October 2009
- November 2009
Hi Ted,
Just thought I'd point out to your readers that although FlexBox right now has 101 Components, the idea is to get as many as we can find in there. The current set of components that you see in FlexBox came from the bookmarks that I collected in my 8-9 months spent with Flex. Surely there are others who have been collecting similar bookmarks and may have pointers to components that are not yet in FlexBox ... If you do know of any such components leave me a link/other details on my blog entry introducing FlexBox or contact me using these details.
Note: FlexBox right now is FlexBox 0.01 and hence we do not have an inbuilt form for adding components, I will try and add that soon.
Ted,
At some point in time, sooner than one might think, there will be a need for a central component repository in which developers can both publish, query and retrieve versioned components (.as, .mxml, .swc, .swf). For comparison, both the Java and Ruby community have well-known and cleaver solutions to this. Look at Maven (Java) or RubyGems and read about their features. Both implementations are completely open-source driven. One particular common aspect is the notion of component dependency stored in meta-data. This way a component developer can define exactly what other versioned components are required for the user of this version. Both Maven and RubyGems provide tools to access those components and store them in a local repository for use in projects.