Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CA+GLYmNHkrrP-7mrfsChPSyrFWtFr3EL4YHNxQJD1Qz4DBZj1A@mail.gmail.com>
References: <4F353F10.6090700@leichtgewicht.at>
	<CA+GLYmNHkrrP-7mrfsChPSyrFWtFr3EL4YHNxQJD1Qz4DBZj1A@mail.gmail.com>
Date: Fri, 10 Feb 2012 11:07:37 -0600
Message-ID: 
 <CAOL2cRSL8H+eExQf3_7v1YAX6LX0-=38ypbgMxV=P-s1rt=JXg@mail.gmail.com>
Subject: Re: [RT] Awesome FlexNext User Experience (was: Starting with the
 Whiteboard code)
From: JP Bader <jp@zavteq.com>
To: flex-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Agreed.  One of the things we need to also demonstrate is the ease of
development concept, something that David pointed out with Sencha, Go
and even tryruby.org.  An interactive tutorial would be great for
getting Apache Flex out to the masses for ease of use, and examples
should be focused on current-day use cases.

I have tons of examples that are useful in my bookmark bar, and those
range from Flash IDE to Flashbuilder IDE, all using actionscript, but
not necessarily the same codebase nor framework.  Should we suggest a
page added to the wiki for creating/displaying/cataloguing these
learning experiences?

JP

On Fri, Feb 10, 2012 at 11:02 AM, Greg Lafrance <glafrance@ipass.com> wrote=
:
> I'd also like to see a showcase of applications developed that not only
> inspire developers as to what's possible, but provide useful code either
> for developers creating proof or concepts for internal approval or as
> starting code for actual projects.
>
> This would not be a tour de flex, but rather a number of basic applicatio=
ns
> for various industries. So for example basic apps for:
>
> - allowing users to manage images they have gathered (possibly an AIR app=
)
> - showing financial data for some stocks, with charts based on financial
> data
> - a shopping cart
> - managing one's social networks (Twitter, Facebook, LinkedIn, etc)
> - mobile AIR apps that offer an appropriate subset of each app
>
> This would not be done quickly or easily, but if such apps are planned
> well, and created, and offered as open source code (with whatever is the
> appropriate license), developers from a variety of industries can more
> quickly jump into using Flex.
>
> One thing I was amazed at is that Adobe never (and most tech companies
> never do) created such multi-industry sample apps, which over time could
> include sample backend code, and become more complex sample apps.
>
> Not easy, but along with stunningly excellent documentation, can get
> developers swarming to Apache Flex.
>
> BTW, I really love the new logo. Very kool!
> Greg
>
> On Fri, Feb 10, 2012 at 8:00 AM, Martin Heidegger <mh@leichtgewicht.at>wr=
ote:
>
>> Dear List,
>>
>> it can be hard to find a vision for the next version of Flex. Developers
>> like us like discussions about technical details and they are boring.
>>
>> I think that is not enough! I think we need something that inspires us t=
o
>> create something new - something that makes us believe that the things
>> created with Apache Flex are awesome.
>>
>> We can make awesome things!
>>
>> I propose following: Lets ask everyone who listens for user experience
>> concepts - full or partial. Things that they could see Flex is going to =
so
>> the PPMC get a better feeling how awesome they could be.
>>
>> The proposals should be split in a few categories:
>>
>> =A0*) _HTML/JS compatible:_ To compile mxmlc/AS3 -> html/js the concept =
has
>> to work within the restrictions of HTML/JS with a optional royal look an=
d
>> feel when being built for Flash without breaking the system.
>>
>> =A0*) _Flash super-powered:_ Systems that leverage the power of the curr=
ent
>> version of the Flash Player without thinking for a second about HTML: St=
age
>> 3D / HD videos / JPEG XR / Slick custom fonts / Pixelbender effects /
>> (generated audio) / ...
>>
>> =A0*) _Touch centric:_ Focussing on the fingers: Swipe/Zoom/Rotate/Expan=
d/**Swoosh/...
>> These concepts don't need to care about a mouse or keyboard.
>>
>> =A0*) _Fully portable:_ Interfaces flexible enough to be represented in =
the
>> style of various Operation systems without neglecting our need for style=
.
>> Awesome on Mac/iOS/Windows/Android with few adaptations.
>>
>> Some rule-of-thumbs I can think of:
>>
>> =A0 * Responsiveness is key: The more stuff that has to run at a time th=
e
>> less likely it will rock.
>> =A0 * All assets should be open-source: Don't build on royal fonts or
>> imagery.
>>
>> What would you think of such a request? Is that something that the PPMC
>> think is useful? Should we rock that?
>>
>> Note: The various concepts should be presented in the Wiki.
>>
>> yours
>> Martin.
>>
>>


--=20
JP Bader
Principal
Zavteq, Inc.
@lordB8r | jp@zavteq.com
608.692.2468