@Om ... in regards to code examples, I have already added Apache Flex code examples to my Login Example [1]. Sure, the Login Example is not a fancy app, but, it shows Flex newbies how they could structure the Flex code with the MVC pattern. I am not sure if this code would be of interest to the Apache Flex codebase because these code example rely on Microarchitectures like Cairngorm 3, Mate, Robotlegs, Parsley, Spring AS and Swiz. As you probably have noticed, after the anxiety and depression phase of the Flex market in 2012, the development of these Microarchitectures has mostly been stopped, and, the founders of Parsley and Swiz have left the Flex market. This brings the Login Example into the need to change, but, for the moment, it is not clear to me into which direction. I also would like to add that, for Flex newbies, I wouldn't suggest any Apache Flex newbie to start building a Flex application without a Microarchitecture ... Reasons IMHO: 1) Shorter development time, 2) Less bad coding practises 3) Better structured modular code.
So ... what do you think? Would it be of interest for you put the Login Example into the Apache Flex codebase? Do you have any recommendations for Flex newbies how they should build Flex apps? How should Flex newbies build Flex apps without the use of existing Microarchitectures? Thank you ... -- Sebastian (PPMC) Interaction Designer [1] http://code.google.com/p/masuland/wiki/LoginExample#Apache_Flex_4.8_(Spark) Looking for a Login Example with Apache Flex? Please check out this code: http://code.google.com/p/masuland/wiki/LoginExample On Sun, Feb 3, 2013 at 4:59 AM, Om <bigosma...@gmail.com> wrote: > On Fri, Feb 1, 2013 at 7:26 PM, Nicholas Kwiatkowski <nicho...@spoon.as > >wrote: > > > It's been blowing me away too. I can't imagine the impact we could have > > made if the timing would have worked better between the press releases > and > > the new website. > > > > Either way, If anybody wants to help me keep the content fresh that would > > rock too. In particular we still need to do some scrubbing of the > external > > content links -- like the videos and how-to stuff. Looking at the stats > > coming back from the goog it seems people are looking to learn. Right > now, > > we quickly being the only source for this type of content (as Adobe goes > > down the road of dropping content from the ADC). > > > > -Nick > > > > I agree that this would be key to keeping Apache Flex relevant. A lot of > people (committers as well) had expressed interest in contributing learning > materials to Apache Flex. I hope they would step up now and deliver. A > few things that we could right away are: > > 1. Create more how-to videos > 2. Create tutorials and working examples for the new features we have > added > 3. Get more and more people to subscribe to us...@flex.apache.org (any > ideas how to do that?) > 4. Figure out more ways to engage the community. We started with a few > google hangouts, townhalls, etc. Can those folks start doing it more > regularly? > 5. Create a brand new Flex component explorer or a Tour de Flex like app. > We dont need to wait for stuff to be donated. These projects should be > straightforward to create ourselves. > > Any other ideas? > > Thanks, > Om >
