Login Example for Apache Flex (was: [Website] Learning content)

[Sebastian Mohr <fl...@gmail.com>]

@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 <bi...@gmail.com> wrote:

> On Fri, Feb 1, 2013 at 7:26 PM, Nicholas Kwiatkowski <nicholas@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 users@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
>

RE: Login Example for Apache Flex (was: [Website] Learning content)

[Mark Fuqua <ma...@availdata.com>]

As a newbie, I think a good discussion of Flex would include the following:
custom components, suggested folder structure, event bubbling, setting event
listeners, removing event listeners, item renderers and maybe even item
renderers for mobile (I think they are suggested to be actionscript only).

Mark

-----Original Message-----
From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of Om
Sent: Monday, February 04, 2013 1:52 PM
To: dev@flex.apache.org
Subject: Re: Login Example for Apache Flex (was: [Website] Learning content)

On Mon, Feb 4, 2013 at 9:20 AM, Nicholas Kwiatkowski
<ni...@spoon.as>wrote:

> Sebastian,
>
> I'm not sure that talking about frameworks is the best way to attract 
> new developers.  I think some code samples that show how easy it is to 
> do fairly complicated tasks may be better.  Think of what the Adobe 
> Evangelists have shown in the past (demoware).  Flex is pretty awesome 
> in the fact that you don't really need a framework to do most basic 
> functions -- it is a framework in itself (and it allows the developer 
> to explore the framework without having to worry about the black-magic 
> that is Framework X vs. Framework Y).
>
> Showing new users code patterns without involving frameworks would be 
> very useful.  For example, showing how certain code patterns can help 
> leverage Events properly, etc.
>
> -Nick
>


Right.  The only framework we need to talk about is the Flex framework.
 Examples for integrating it with other microarchitectures can be taken care
of those respective projects.  By talking about third-party
microarchitectures we would seem like we prefer any particular one(s)  Our
examples should talk in terms of just ActionScript and MXML.  You can
implement MVC in Flex without having to use any other framework.

Thanks,
Om

Re: Login Example for Apache Flex (was: [Website] Learning content)

[Om <bi...@gmail.com>]

On Mon, Feb 4, 2013 at 9:20 AM, Nicholas Kwiatkowski <ni...@spoon.as>wrote:

> Sebastian,
>
> I'm not sure that talking about frameworks is the best way to attract new
> developers.  I think some code samples that show how easy it is to do
> fairly complicated tasks may be better.  Think of what the
> Adobe Evangelists have shown in the past (demoware).  Flex is pretty
> awesome in the fact that you don't really need a framework to do most basic
> functions -- it is a framework in itself (and it allows the developer to
> explore the framework without having to worry about the black-magic that is
> Framework X vs. Framework Y).
>
> Showing new users code patterns without involving frameworks would be very
> useful.  For example, showing how certain code patterns can help leverage
> Events properly, etc.
>
> -Nick
>


Right.  The only framework we need to talk about is the Flex framework.
 Examples for integrating it with other microarchitectures can be taken
care of those respective projects.  By talking about third-party
microarchitectures we would seem like we prefer any particular one(s)  Our
examples should talk in terms of just ActionScript and MXML.  You can
implement MVC in Flex without having to use any other framework.

Thanks,
Om

Re: Login Example for Apache Flex (was: [Website] Learning content)

[Hans | dotdotcommadot <ha...@dotdotcommadot.com>]

Dart seems to be doing some kind of 5 minute video instructions.
I think this would be a great idea: make tutorials that won't take longer than 5 minutes (video or text.. whatever).
Or some kind of 'gotoandlearn.com' for flex would be awesome as well of course.
IF somebody would have the time to do this stuff that is.


Hans Van den Keybus | dotdotcommadot.com
Mail: hans@dotdotcommadot.com
Phone: 0032 (0) 486 16 30 69

On 4-feb.-2013, at 18:20, Nicholas Kwiatkowski <ni...@spoon.as> wrote:

> Sebastian,
> 
> I'm not sure that talking about frameworks is the best way to attract new
> developers.  I think some code samples that show how easy it is to do
> fairly complicated tasks may be better.  Think of what the
> Adobe Evangelists have shown in the past (demoware).  Flex is pretty
> awesome in the fact that you don't really need a framework to do most basic
> functions -- it is a framework in itself (and it allows the developer to
> explore the framework without having to worry about the black-magic that is
> Framework X vs. Framework Y).
> 
> Showing new users code patterns without involving frameworks would be very
> useful.  For example, showing how certain code patterns can help leverage
> Events properly, etc.
> 
> -Nick
> 
> On Mon, Feb 4, 2013 at 5:41 AM, Sebastian Mohr <fl...@gmail.com>wrote:
> 
>> @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 <bi...@gmail.com> wrote:
>> 
>>> On Fri, Feb 1, 2013 at 7:26 PM, Nicholas Kwiatkowski <nicholas@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 users@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
>>> 
>> 

Re: Login Example for Apache Flex (was: [Website] Learning content)

[Nicholas Kwiatkowski <ni...@spoon.as>]

Sebastian,

I'm not sure that talking about frameworks is the best way to attract new
developers.  I think some code samples that show how easy it is to do
fairly complicated tasks may be better.  Think of what the
Adobe Evangelists have shown in the past (demoware).  Flex is pretty
awesome in the fact that you don't really need a framework to do most basic
functions -- it is a framework in itself (and it allows the developer to
explore the framework without having to worry about the black-magic that is
Framework X vs. Framework Y).

Showing new users code patterns without involving frameworks would be very
useful.  For example, showing how certain code patterns can help leverage
Events properly, etc.

-Nick

On Mon, Feb 4, 2013 at 5:41 AM, Sebastian Mohr <fl...@gmail.com>wrote:

> @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 <bi...@gmail.com> wrote:
>
> > On Fri, Feb 1, 2013 at 7:26 PM, Nicholas Kwiatkowski <nicholas@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 users@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
> >
>