You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Martin Heidegger <mh...@leichtgewicht.at> on 2012/02/10 17:00:16 UTC
[RT] Awesome FlexNext User Experience (was: Starting with the Whiteboard
code)
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
to 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:
*) _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 and feel when being built for Flash without breaking the system.
*) _Flash super-powered:_ Systems that leverage the power of the
current version of the Flash Player without thinking for a second about
HTML: Stage 3D / HD videos / JPEG XR / Slick custom fonts / Pixelbender
effects / (generated audio) / ...
*) _Touch centric:_ Focussing on the fingers:
Swipe/Zoom/Rotate/Expand/Swoosh/... These concepts don't need to care
about a mouse or keyboard.
*) _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:
* Responsiveness is key: The more stuff that has to run at a time
the less likely it will rock.
* 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.
[RT] Awesome FlexNext End-User Experience
Posted by Martin Heidegger <mh...@leichtgewicht.at>.
Just because it seemed to created some misunderstanding.
The post was intended to focus on the _design_ aspect of
end-user-experiences. The stuff that we do with Flex.
yours
Martin.
On 11/02/2012 01:00, Martin Heidegger wrote:
> 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
> to 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:
>
> *) _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 and feel when being built for Flash without breaking the system.
>
> *) _Flash super-powered:_ Systems that leverage the power of the
> current version of the Flash Player without thinking for a second
> about HTML: Stage 3D / HD videos / JPEG XR / Slick custom fonts /
> Pixelbender effects / (generated audio) / ...
>
> *) _Touch centric:_ Focussing on the fingers:
> Swipe/Zoom/Rotate/Expand/Swoosh/... These concepts don't need to care
> about a mouse or keyboard.
>
> *) _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:
>
> * Responsiveness is key: The more stuff that has to run at a time
> the less likely it will rock.
> * 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.
>
>
Re: [RT] Awesome FlexNext User Experience (was: Starting with the Whiteboard code)
Posted by Bryan Hunt <br...@sentimentmetrics.com>.
> I mean add-on / extension. https://addons.mozilla.org/en-US/firefox/
>
> Not every browser supports add-ons either tho. What I was thinking was a
> sidebar that showed something like the package explorer or even an
> extension that took, "http://localhost/my_application.mxml" and ran mxmlc
> on it (which then redirected to the generated html wrapper page).
>
> You would have to install the extension and also download the SDK for it to
> point to it but then you'd have the same ability to interpret a page on the
> fly (sic) that HTML developers have.
IMHO, this sounds like an elephant trying to pass itself off as a
butterfly.
Flash/Flex and HTML/JavaScript have completely different rationalle and
Use-Case; just as PHP/Drupal, Python/Django, and Scala/MongoDB have
theirs.
In my Yoga class last night, Yogi told us 'the essence of being is just
to be, regardless'. Perhaps he was on to something.
Regards,
Bryan Hunt
Re: [RT] Awesome FlexNext User Experience (was: Starting with the
Whiteboard code)
Posted by jude <fl...@gmail.com>.
I mean add-on / extension. https://addons.mozilla.org/en-US/firefox/
Not every browser supports add-ons either tho. What I was thinking was a
sidebar that showed something like the package explorer or even an
extension that took, "http://localhost/my_application.mxml" and ran mxmlc
on it (which then redirected to the generated html wrapper page).
You would have to install the extension and also download the SDK for it to
point to it but then you'd have the same ability to interpret a page on the
fly (sic) that HTML developers have.
On Mon, Feb 20, 2012 at 12:57 PM, Alex Harui <ah...@adobe.com> wrote:
>
>
>
> On 2/20/12 1:09 AM, "jude" <fl...@gmail.com> wrote:
>
> > What about a browser plug in that would handle .mxml files? Then you'd
> just
> > drag and drop an MXML file to the browser and it would render?
> It is the fact that certain browsers don't support plug-ins that put us in
> this situation in the first place.
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
Re: [RT] Awesome FlexNext User Experience (was: Starting with the
Whiteboard code)
Posted by Alex Harui <ah...@adobe.com>.
On 2/20/12 1:09 AM, "jude" <fl...@gmail.com> wrote:
> What about a browser plug in that would handle .mxml files? Then you'd just
> drag and drop an MXML file to the browser and it would render?
It is the fact that certain browsers don't support plug-ins that put us in
this situation in the first place.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: [RT] Awesome FlexNext User Experience (was: Starting with the
Whiteboard code)
Posted by Martin Heidegger <mh...@leichtgewicht.at>.
On 21/02/2012 01:52, David Francis Buhler wrote:
> Google's Dart is gaining traction and is now offered as a browser plug-in
> (for Chrome).
>
> [1]
> http://news.cnet.com/8301-30685_3-57380050-264/googles-dart-language-arrives-in-chrome-test-version/
There are strong discussions against dart in a release version of chrome
as it will clutter the rest of the system.
It speaks against the nature of Chrome that aims on supporting w3c
standards.
yours
Martin.
<https://lists.webkit.org/pipermail/webkit-dev/2011-December/018820.html>
Re: [RT] Awesome FlexNext User Experience (was: Starting with the
Whiteboard code)
Posted by David Francis Buhler <da...@gmail.com>.
Google's Dart is gaining traction and is now offered as a browser plug-in
(for Chrome).
[1]
http://news.cnet.com/8301-30685_3-57380050-264/googles-dart-language-arrives-in-chrome-test-version/
On Mon, Feb 20, 2012 at 4:42 AM, ganaraj p r <ga...@gmail.com> wrote:
> If browser plugins were a future we would be worrying quite a bit about
> releasing Flex 4.7 or Flex 5. The problem is, the most popular plugin in
> the world seems to have a hazy future, which is probably the reason for all
> the discussion about moving away from Flash.
>
>
> On Mon, Feb 20, 2012 at 9:09 AM, jude <fl...@gmail.com> wrote:
>
> > The ease of making HTML pages was partly what hooked me so long ago. I
> > could type something in a text editor and it would show up rendered in
> the
> > browser.
> >
> > What about a browser plug in that would handle .mxml files? Then you'd
> just
> > drag and drop an MXML file to the browser and it would render?
> >
> > Judah
> >
> > On Sun, Feb 12, 2012 at 11:19 AM, Martin Heidegger <mh@leichtgewicht.at
> > >wrote:
> >
> > > The differences to languages like Python is that AS3 requires a
> compiler,
> > > and unlike - for example - haXe the compiler for AS3 is not written in
> > AS3.
> > >
> > > One option is to implement that nice functionality would be a compiler
> in
> > > AS3. There is rudimentary ActionScript 3 evaluator called "Eval"
> > available
> > > [1].
> > > The other option would be to "call" the Compiler using a Java
> > executable.
> > > [2] That will work "perfectly" but requires the java plugin to be
> > installed.
> > > The third option would be to compile it on a server which well ...
> would
> > > require a server. Wonderfl is nice but highly proprietary. And we could
> > not
> > > use
> > > those examples offline.
> > >
> > > A completely different approach would be to implement a "IDE" tutorial.
> > To
> > > be used with all AS3 ide's out there. You download the IDE and there
> you
> > > have access to documentation from Apache. This way all the IDE's could
> > > provide the same Flex documentation that "interacts" with their editor.
> > >
> > > Just thoughts.
> > >
> > > yours
> > > Martin.
> > >
> > > [1] http://eval.hurlant.com/
> > > [2] http://www.victordramba.com/?p=31
> > >
> >
>
>
>
> --
> Regards,
> Ganaraj P R
>
Re: [RT] Awesome FlexNext User Experience (was: Starting with the
Whiteboard code)
Posted by jude <fl...@gmail.com>.
Let me rephrase, I mean Firefox Add-on.
On Mon, Feb 20, 2012 at 3:42 AM, ganaraj p r <ga...@gmail.com> wrote:
> If browser plugins were a future we would be worrying quite a bit about
> releasing Flex 4.7 or Flex 5. The problem is, the most popular plugin in
> the world seems to have a hazy future, which is probably the reason for all
> the discussion about moving away from Flash.
>
>
> On Mon, Feb 20, 2012 at 9:09 AM, jude <fl...@gmail.com> wrote:
>
> > The ease of making HTML pages was partly what hooked me so long ago. I
> > could type something in a text editor and it would show up rendered in
> the
> > browser.
> >
> > What about a browser plug in that would handle .mxml files? Then you'd
> just
> > drag and drop an MXML file to the browser and it would render?
> >
> > Judah
> >
> > On Sun, Feb 12, 2012 at 11:19 AM, Martin Heidegger <mh@leichtgewicht.at
> > >wrote:
> >
> > > The differences to languages like Python is that AS3 requires a
> compiler,
> > > and unlike - for example - haXe the compiler for AS3 is not written in
> > AS3.
> > >
> > > One option is to implement that nice functionality would be a compiler
> in
> > > AS3. There is rudimentary ActionScript 3 evaluator called "Eval"
> > available
> > > [1].
> > > The other option would be to "call" the Compiler using a Java
> > executable.
> > > [2] That will work "perfectly" but requires the java plugin to be
> > installed.
> > > The third option would be to compile it on a server which well ...
> would
> > > require a server. Wonderfl is nice but highly proprietary. And we could
> > not
> > > use
> > > those examples offline.
> > >
> > > A completely different approach would be to implement a "IDE" tutorial.
> > To
> > > be used with all AS3 ide's out there. You download the IDE and there
> you
> > > have access to documentation from Apache. This way all the IDE's could
> > > provide the same Flex documentation that "interacts" with their editor.
> > >
> > > Just thoughts.
> > >
> > > yours
> > > Martin.
> > >
> > > [1] http://eval.hurlant.com/
> > > [2] http://www.victordramba.com/?p=31
> > >
> >
>
>
>
> --
> Regards,
> Ganaraj P R
>
Re: [RT] Awesome FlexNext User Experience (was: Starting with the
Whiteboard code)
Posted by ganaraj p r <ga...@gmail.com>.
If browser plugins were a future we would be worrying quite a bit about
releasing Flex 4.7 or Flex 5. The problem is, the most popular plugin in
the world seems to have a hazy future, which is probably the reason for all
the discussion about moving away from Flash.
On Mon, Feb 20, 2012 at 9:09 AM, jude <fl...@gmail.com> wrote:
> The ease of making HTML pages was partly what hooked me so long ago. I
> could type something in a text editor and it would show up rendered in the
> browser.
>
> What about a browser plug in that would handle .mxml files? Then you'd just
> drag and drop an MXML file to the browser and it would render?
>
> Judah
>
> On Sun, Feb 12, 2012 at 11:19 AM, Martin Heidegger <mh@leichtgewicht.at
> >wrote:
>
> > The differences to languages like Python is that AS3 requires a compiler,
> > and unlike - for example - haXe the compiler for AS3 is not written in
> AS3.
> >
> > One option is to implement that nice functionality would be a compiler in
> > AS3. There is rudimentary ActionScript 3 evaluator called "Eval"
> available
> > [1].
> > The other option would be to "call" the Compiler using a Java
> executable.
> > [2] That will work "perfectly" but requires the java plugin to be
> installed.
> > The third option would be to compile it on a server which well ... would
> > require a server. Wonderfl is nice but highly proprietary. And we could
> not
> > use
> > those examples offline.
> >
> > A completely different approach would be to implement a "IDE" tutorial.
> To
> > be used with all AS3 ide's out there. You download the IDE and there you
> > have access to documentation from Apache. This way all the IDE's could
> > provide the same Flex documentation that "interacts" with their editor.
> >
> > Just thoughts.
> >
> > yours
> > Martin.
> >
> > [1] http://eval.hurlant.com/
> > [2] http://www.victordramba.com/?p=31
> >
>
--
Regards,
Ganaraj P R
Re: [RT] Awesome FlexNext User Experience (was: Starting with the
Whiteboard code)
Posted by jude <fl...@gmail.com>.
The ease of making HTML pages was partly what hooked me so long ago. I
could type something in a text editor and it would show up rendered in the
browser.
What about a browser plug in that would handle .mxml files? Then you'd just
drag and drop an MXML file to the browser and it would render?
Judah
On Sun, Feb 12, 2012 at 11:19 AM, Martin Heidegger <mh...@leichtgewicht.at>wrote:
> The differences to languages like Python is that AS3 requires a compiler,
> and unlike - for example - haXe the compiler for AS3 is not written in AS3.
>
> One option is to implement that nice functionality would be a compiler in
> AS3. There is rudimentary ActionScript 3 evaluator called "Eval" available
> [1].
> The other option would be to "call" the Compiler using a Java executable.
> [2] That will work "perfectly" but requires the java plugin to be installed.
> The third option would be to compile it on a server which well ... would
> require a server. Wonderfl is nice but highly proprietary. And we could not
> use
> those examples offline.
>
> A completely different approach would be to implement a "IDE" tutorial. To
> be used with all AS3 ide's out there. You download the IDE and there you
> have access to documentation from Apache. This way all the IDE's could
> provide the same Flex documentation that "interacts" with their editor.
>
> Just thoughts.
>
> yours
> Martin.
>
> [1] http://eval.hurlant.com/
> [2] http://www.victordramba.com/?p=31
>
Re: [RT] Awesome FlexNext User Experience (was: Starting with the
Whiteboard code)
Posted by Martin Heidegger <mh...@leichtgewicht.at>.
The differences to languages like Python is that AS3 requires a
compiler, and unlike - for example - haXe the compiler for AS3 is not
written in AS3.
One option is to implement that nice functionality would be a compiler
in AS3. There is rudimentary ActionScript 3 evaluator called "Eval"
available [1].
The other option would be to "call" the Compiler using a Java
executable. [2] That will work "perfectly" but requires the java plugin
to be installed.
The third option would be to compile it on a server which well ... would
require a server. Wonderfl is nice but highly proprietary. And we could
not use
those examples offline.
A completely different approach would be to implement a "IDE" tutorial.
To be used with all AS3 ide's out there. You download the IDE and there
you have access to documentation from Apache. This way all the IDE's
could provide the same Flex documentation that "interacts" with their
editor.
Just thoughts.
yours
Martin.
[1] http://eval.hurlant.com/
[2] http://www.victordramba.com/?p=31
On 13/02/2012 01:57, JP Bader wrote:
> I have never seen wonderfl.net, but that is exactly the idea of what
> we can build, however I am envisioning something more like rails for
> zombies, or learn Python the hard way, which actually can take you
> through a series of tutorials that will help you experience some of
> the more basic aspects of Flex (and AS3), and then delve into some of
> the more complex aspects, leaving the ending open for users to go
> explore.
>
> On Fri, Feb 10, 2012 at 5:10 PM, David Francis Buhler
> <da...@gmail.com> wrote:
>> http://wonderfl.net/ does it.
>>
>> On Fri, Feb 10, 2012 at 5:04 PM, Ariel Jakobovits<ar...@yahoo.com> wrote:
>>>> An interactive tutorial
>>> Would it be a lot of work for us to set up a server that could compile Flex code and return a compiled swf for a beginner to see as they follow a lesson plan and learn to program Flex?
>>>
>>> Ariel Jakobovits
>>> Email: arieljake@yahoo.com
>>> Phone: 650-690-2213
>>> Fax: 650-641-0031
>>> Cell: 650-823-8699
>>>
>>>
>>> ________________________________
>>> From: JP Bader<jp...@zavteq.com>
>>> To: flex-dev@incubator.apache.org
>>> Sent: Friday, February 10, 2012 9:07 AM
>>> Subject: Re: [RT] Awesome FlexNext User Experience (was: Starting with the Whiteboard code)
>>>
>>> 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<gl...@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 applications
>>>> 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>wrote:
>>>>
>>>>> 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 to
>>>>> 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:
>>>>>
>>>>> *) _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 and
>>>>> feel when being built for Flash without breaking the system.
>>>>>
>>>>> *) _Flash super-powered:_ Systems that leverage the power of the current
>>>>> version of the Flash Player without thinking for a second about HTML: Stage
>>>>> 3D / HD videos / JPEG XR / Slick custom fonts / Pixelbender effects /
>>>>> (generated audio) / ...
>>>>>
>>>>> *) _Touch centric:_ Focussing on the fingers: Swipe/Zoom/Rotate/Expand/**Swoosh/...
>>>>> These concepts don't need to care about a mouse or keyboard.
>>>>>
>>>>> *) _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:
>>>>>
>>>>> * Responsiveness is key: The more stuff that has to run at a time the
>>>>> less likely it will rock.
>>>>> * 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.
>>>>>
>>>>>
>>>
>>>
>>> --
>>> JP Bader
>>> Principal
>>> Zavteq, Inc.
>>> @lordB8r | jp@zavteq.com
>>> 608.692.2468
>
>
Re: [RT] Awesome FlexNext User Experience (was: Starting with the
Whiteboard code)
Posted by JP Bader <jp...@zavteq.com>.
I have never seen wonderfl.net, but that is exactly the idea of what
we can build, however I am envisioning something more like rails for
zombies, or learn Python the hard way, which actually can take you
through a series of tutorials that will help you experience some of
the more basic aspects of Flex (and AS3), and then delve into some of
the more complex aspects, leaving the ending open for users to go
explore.
On Fri, Feb 10, 2012 at 5:10 PM, David Francis Buhler
<da...@gmail.com> wrote:
> http://wonderfl.net/ does it.
>
> On Fri, Feb 10, 2012 at 5:04 PM, Ariel Jakobovits <ar...@yahoo.com> wrote:
>>> An interactive tutorial
>> Would it be a lot of work for us to set up a server that could compile Flex code and return a compiled swf for a beginner to see as they follow a lesson plan and learn to program Flex?
>>
>> Ariel Jakobovits
>> Email: arieljake@yahoo.com
>> Phone: 650-690-2213
>> Fax: 650-641-0031
>> Cell: 650-823-8699
>>
>>
>> ________________________________
>> From: JP Bader <jp...@zavteq.com>
>> To: flex-dev@incubator.apache.org
>> Sent: Friday, February 10, 2012 9:07 AM
>> Subject: Re: [RT] Awesome FlexNext User Experience (was: Starting with the Whiteboard code)
>>
>> 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 <gl...@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 applications
>>> 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>wrote:
>>>
>>>> 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 to
>>>> 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:
>>>>
>>>> *) _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 and
>>>> feel when being built for Flash without breaking the system.
>>>>
>>>> *) _Flash super-powered:_ Systems that leverage the power of the current
>>>> version of the Flash Player without thinking for a second about HTML: Stage
>>>> 3D / HD videos / JPEG XR / Slick custom fonts / Pixelbender effects /
>>>> (generated audio) / ...
>>>>
>>>> *) _Touch centric:_ Focussing on the fingers: Swipe/Zoom/Rotate/Expand/**Swoosh/...
>>>> These concepts don't need to care about a mouse or keyboard.
>>>>
>>>> *) _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:
>>>>
>>>> * Responsiveness is key: The more stuff that has to run at a time the
>>>> less likely it will rock.
>>>> * 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.
>>>>
>>>>
>>
>>
>>
>> --
>> JP Bader
>> Principal
>> Zavteq, Inc.
>> @lordB8r | jp@zavteq.com
>> 608.692.2468
--
JP Bader
Principal
Zavteq, Inc.
@lordB8r | jp@zavteq.com
608.692.2468
Re: [RT] Awesome FlexNext User Experience (was: Starting with the
Whiteboard code)
Posted by David Francis Buhler <da...@gmail.com>.
http://wonderfl.net/ does it.
On Fri, Feb 10, 2012 at 5:04 PM, Ariel Jakobovits <ar...@yahoo.com> wrote:
>> An interactive tutorial
> Would it be a lot of work for us to set up a server that could compile Flex code and return a compiled swf for a beginner to see as they follow a lesson plan and learn to program Flex?
>
> Ariel Jakobovits
> Email: arieljake@yahoo.com
> Phone: 650-690-2213
> Fax: 650-641-0031
> Cell: 650-823-8699
>
>
> ________________________________
> From: JP Bader <jp...@zavteq.com>
> To: flex-dev@incubator.apache.org
> Sent: Friday, February 10, 2012 9:07 AM
> Subject: Re: [RT] Awesome FlexNext User Experience (was: Starting with the Whiteboard code)
>
> 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 <gl...@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 applications
>> 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>wrote:
>>
>>> 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 to
>>> 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:
>>>
>>> *) _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 and
>>> feel when being built for Flash without breaking the system.
>>>
>>> *) _Flash super-powered:_ Systems that leverage the power of the current
>>> version of the Flash Player without thinking for a second about HTML: Stage
>>> 3D / HD videos / JPEG XR / Slick custom fonts / Pixelbender effects /
>>> (generated audio) / ...
>>>
>>> *) _Touch centric:_ Focussing on the fingers: Swipe/Zoom/Rotate/Expand/**Swoosh/...
>>> These concepts don't need to care about a mouse or keyboard.
>>>
>>> *) _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:
>>>
>>> * Responsiveness is key: The more stuff that has to run at a time the
>>> less likely it will rock.
>>> * 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.
>>>
>>>
>
>
>
> --
> JP Bader
> Principal
> Zavteq, Inc.
> @lordB8r | jp@zavteq.com
> 608.692.2468
Re: [RT] Awesome FlexNext User Experience
Posted by Martin Heidegger <mh...@leichtgewicht.at>.
On 11/02/2012 08:10, David Francis Buhler wrote:
> http://wonderfl.net/ does it.
wonderfl.net is awesome but does not harmonize with the Apache process.
Imagine we create tons of docs and Kayac decides to just shut down the
server. Or if we introduce a new library and its not being included into
kayac due to a lack of administration. Both very unfortunate yet likely
cases.
Something like this would be more appropriate I guess:
http://www.victordramba.com/?p=31
It could be improved using the opensource editor that wonderfl provides!
yours
Martin.
Re: [RT] Awesome FlexNext User Experience
Posted by David Francis Buhler <da...@gmail.com>.
http://wonderfl.net/
On Fri, Feb 10, 2012 at 5:09 PM, Jeffry Houser <je...@dot-com-it.com> wrote:
>
> Adobe had one of those sites; but it's no longer up. Maybe it was
> tryflex.com ? I think that was in the Flex 2 days. I always assumed it got
> no traction.
>
> --
Re: [RT] Awesome FlexNext User Experience
Posted by Om <bi...@gmail.com>.
On Fri, Feb 10, 2012 at 2:09 PM, Jeffry Houser <je...@dot-com-it.com>wrote:
> On 2/10/2012 5:04 PM, Ariel Jakobovits wrote:
>
>> An interactive tutorial
>>>
>> Would it be a lot of work for us to set up a server that could compile
>> Flex code and return a compiled swf for a beginner to see as they follow a
>> lesson plan and learn to program Flex?
>>
>
> Adobe had one of those sites; but it's no longer up. Maybe it was
> tryflex.com ? I think that was in the Flex 2 days. I always assumed it
> got no traction.
>
>
It was try.flex.org. This was pretty cool to try out when they launched
it. But I believe it was decommissioned because there was no traction, as
you say.
But it would cool if we can set up something like this for Apache Flex.
Om
Re: [RT] Awesome FlexNext User Experience
Posted by Jeffry Houser <je...@dot-com-it.com>.
On 2/10/2012 5:04 PM, Ariel Jakobovits wrote:
>> An interactive tutorial
> Would it be a lot of work for us to set up a server that could compile Flex code and return a compiled swf for a beginner to see as they follow a lesson plan and learn to program Flex?
Adobe had one of those sites; but it's no longer up. Maybe it was
tryflex.com ? I think that was in the Flex 2 days. I always assumed it
got no traction.
--
Jeffry Houser
Technical Entrepreneur
203-379-0773
--
http://www.flextras.com?c=104
UI Flex Components: Tested! Supported! Ready!
--
http://www.theflexshow.com
http://www.jeffryhouser.com
http://www.asktheflexpert.com
--
Part of the DotComIt Brain Trust
Re: [RT] Awesome FlexNext User Experience (was: Starting with the Whiteboard code)
Posted by Ariel Jakobovits <ar...@yahoo.com>.
> An interactive tutorial
Would it be a lot of work for us to set up a server that could compile Flex code and return a compiled swf for a beginner to see as they follow a lesson plan and learn to program Flex?
Ariel Jakobovits
Email: arieljake@yahoo.com
Phone: 650-690-2213
Fax: 650-641-0031
Cell: 650-823-8699
________________________________
From: JP Bader <jp...@zavteq.com>
To: flex-dev@incubator.apache.org
Sent: Friday, February 10, 2012 9:07 AM
Subject: Re: [RT] Awesome FlexNext User Experience (was: Starting with the Whiteboard code)
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 <gl...@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 applications
> 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>wrote:
>
>> 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 to
>> 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:
>>
>> *) _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 and
>> feel when being built for Flash without breaking the system.
>>
>> *) _Flash super-powered:_ Systems that leverage the power of the current
>> version of the Flash Player without thinking for a second about HTML: Stage
>> 3D / HD videos / JPEG XR / Slick custom fonts / Pixelbender effects /
>> (generated audio) / ...
>>
>> *) _Touch centric:_ Focussing on the fingers: Swipe/Zoom/Rotate/Expand/**Swoosh/...
>> These concepts don't need to care about a mouse or keyboard.
>>
>> *) _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:
>>
>> * Responsiveness is key: The more stuff that has to run at a time the
>> less likely it will rock.
>> * 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.
>>
>>
--
JP Bader
Principal
Zavteq, Inc.
@lordB8r | jp@zavteq.com
608.692.2468
Re: [RT] Awesome FlexNext User Experience (was: Starting with the
Whiteboard code)
Posted by JP Bader <jp...@zavteq.com>.
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 <gl...@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 applications
> 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>wrote:
>
>> 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 to
>> 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:
>>
>> *) _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 and
>> feel when being built for Flash without breaking the system.
>>
>> *) _Flash super-powered:_ Systems that leverage the power of the current
>> version of the Flash Player without thinking for a second about HTML: Stage
>> 3D / HD videos / JPEG XR / Slick custom fonts / Pixelbender effects /
>> (generated audio) / ...
>>
>> *) _Touch centric:_ Focussing on the fingers: Swipe/Zoom/Rotate/Expand/**Swoosh/...
>> These concepts don't need to care about a mouse or keyboard.
>>
>> *) _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:
>>
>> * Responsiveness is key: The more stuff that has to run at a time the
>> less likely it will rock.
>> * 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.
>>
>>
--
JP Bader
Principal
Zavteq, Inc.
@lordB8r | jp@zavteq.com
608.692.2468
Re: [RT] Awesome FlexNext User Experience (was: Starting with the Whiteboard code)
Posted by Ariel Jakobovits <ar...@yahoo.com>.
> a showcase of applications
this could be done as a fun community space of custom layouts, components, visualizations, skins, etc.
Ariel Jakobovits
Email: arieljake@yahoo.com
Phone: 650-690-2213
Fax: 650-641-0031
Cell: 650-823-8699
________________________________
From: Greg Lafrance <gl...@ipass.com>
To: flex-dev@incubator.apache.org
Sent: Friday, February 10, 2012 9:02 AM
Subject: Re: [RT] Awesome FlexNext User Experience (was: Starting with the Whiteboard code)
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 applications
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>wrote:
> 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 to
> 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:
>
> *) _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 and
> feel when being built for Flash without breaking the system.
>
> *) _Flash super-powered:_ Systems that leverage the power of the current
> version of the Flash Player without thinking for a second about HTML: Stage
> 3D / HD videos / JPEG XR / Slick custom fonts / Pixelbender effects /
> (generated audio) / ...
>
> *) _Touch centric:_ Focussing on the fingers: Swipe/Zoom/Rotate/Expand/**Swoosh/...
> These concepts don't need to care about a mouse or keyboard.
>
> *) _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:
>
> * Responsiveness is key: The more stuff that has to run at a time the
> less likely it will rock.
> * 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.
>
>
Re: [RT] Awesome FlexNext User Experience (was: Starting with the
Whiteboard code)
Posted by Greg Lafrance <gl...@ipass.com>.
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 applications
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>wrote:
> 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 to
> 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:
>
> *) _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 and
> feel when being built for Flash without breaking the system.
>
> *) _Flash super-powered:_ Systems that leverage the power of the current
> version of the Flash Player without thinking for a second about HTML: Stage
> 3D / HD videos / JPEG XR / Slick custom fonts / Pixelbender effects /
> (generated audio) / ...
>
> *) _Touch centric:_ Focussing on the fingers: Swipe/Zoom/Rotate/Expand/**Swoosh/...
> These concepts don't need to care about a mouse or keyboard.
>
> *) _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:
>
> * Responsiveness is key: The more stuff that has to run at a time the
> less likely it will rock.
> * 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.
>
>
RE: [RT] Awesome FlexNext User Experience (was: Starting with the
Whiteboard code)
Posted by FRANKLIN GARZON <fg...@hotmail.com>.
> Date: Sat, 11 Feb 2012 01:00:16 +0900
> From: mh@leichtgewicht.at
> To: flex-dev@incubator.apache.org
> Subject: [RT] Awesome FlexNext User Experience (was: Starting with the Whiteboard code)
>
> 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
> to 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:
>
> *) _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 and feel when being built for Flash without breaking the system. Will be great if in the same project we can build for HTML5 too.
>
> *) _Flash super-powered:_ Systems that leverage the power of the
> current version of the Flash Player without thinking for a second about
> HTML: Stage 3D / HD videos / JPEG XR / Slick custom fonts / Pixelbender
> effects / (generated audio) / ...
> *) _Touch centric:_ Focussing on the fingers:
> Swipe/Zoom/Rotate/Expand/Swoosh/... These concepts don't need to care
> about a mouse or keyboard. Great if ApacheFlex will talk the finggers languaje.
> *) _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.
Nice
> Some rule-of-thumbs I can think of:
>
> * Responsiveness is key: The more stuff that has to run at a time
> the less likely it will rock.
> * 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.
Re: [RT] Documentation (split from: Awesome User Experience)
Posted by Martin Heidegger <mh...@leichtgewicht.at>.
On 11/02/2012 07:00, Ariel Jakobovits wrote:
> Regarding asdocs, will we be able to reliably point users to the Flash Player AS3 documentation from our imported Flex doc site?
Of course not. The Flash Player as well as the AS3 Language are not
planned to be submitted to Apache.
However: I, personally, see the possibility that Adobe might change its
mind if we really "hit it off" as they say.
yours
Martin.
Re: [RT] Documentation (split from: Awesome User Experience)
Posted by Ariel Jakobovits <ar...@yahoo.com>.
Regarding asdocs, will we be able to reliably point users to the Flash Player AS3 documentation from our imported Flex doc site?
Ariel Jakobovits
Email: arieljake@yahoo.com
Phone: 650-690-2213
Fax: 650-641-0031
Cell: 650-823-8699
________________________________
From: Martin Heidegger <mh...@leichtgewicht.at>
To: flex-dev@incubator.apache.org
Sent: Friday, February 10, 2012 8:43 AM
Subject: [RT] Documentation (split from: Awesome User Experience)
Hello Francis
I think you are talking more about developer experience than end-user experience.
The wiki seems a good start for documentation to me but I agree that it has some serious drawbacks.
For example: we can not easily include swf's and AS3 code formatting is sub-par. But i think if those requests are
raised to the infrastructure team then they will be dealt with. This would result in following documentation locations:
*) Wiki: edited documentation, documentation about concepts with example section
*) Blog: Time-related documentation: Changes/News
*) API-Docs: Generated API documentation
It would be not so hard to provide something like the PHP Ninja manual [1] that sets up on the online data.
The only problem I see with the wiki solution is the translation. I personally think "just english" is enough. However: For some reason japanese developers (as a example) seem to be really trying to translate everything and I am not yet sure how this could be done with the wiki.
However: this raises another question:
@Adobe: I assume that the Flash Player AS3 documentation will stay at the Adobe site:
Do you plan to submit the Flex documentation (not just api docs) to apache?
Might that include Tour De Flex?
What system/format does it use?
Can the community help with that?
yours
Martin.
[1] https://chrome.google.com/webstore/detail/clbhjjdhmgeibgdccjfoliooccomjcab
On 11/02/2012 01:23, David Francis Buhler wrote:
> I'd like to see the examples and documentation be part of an improved,
> cohesive 'brand' outlined. The rest of the outline I agree with.
>
> Someone else had suggested the idea of emulating the
> examples/documentation Sencha/JQuery use, which I second. Likewise,
> Google does an excellent job with http://tour.golang.org/
>
> I always found Adobe to offer too many alternatives to finding information.
>
> Examples:
> -Adobe offered too many Flex examples in the help.adobe.com site made
> accessing the information slow and painful. Future hiding of the
> Examples until the user clicked a button made 'seeing' the examples
> more involved.
> -The Help Docs had poor SEO. Questions asked about technical problems
> have a certain language, and the page-titles needed to reflect the
> language developers use to search out solutions to problems.
> -The Help Docs were longer than necessary.
> -Tour De Flex's User Experience did not reflect how people seek out
> information. It did not offer a linear evolution of 'challenges' or
> 'difficulty'. Examples often error out.
> -Adobe Community Help provided too many search options, that did not
> reflect an understanding of how people look for information.
>
> -Buhler
>
Re: [RT] Documentation (split from: Awesome User Experience)
Posted by Alain Ekambi <ja...@googlemail.com>.
@Martin
Unfortunately the code of that application wont help much i think.
Simply because the application was not written in AS3/MXML but in Java
using GWT.
I was talking more about the structure of the app which was inspired from
the Ext-GWT explorer.
2012/2/10 Martin Heidegger <mh...@leichtgewicht.at>
> On 11/02/2012 01:55, Alain Ekambi wrote:
>
>> We have create something similar to the EXT-GWT explorer for our product
>> Gwt4Flex. ( http://www.gwt4air.appspot.**com/<http://www.gwt4air.appspot.com/>)
>>
>> Something in that direction would definitly be usefull.
>>
> It would be awesome if you could publish the code under a APL compatible
> license under github so it could be improved.
>
> yours
> Martin.
>
Re: [RT] Documentation (split from: Awesome User Experience)
Posted by Martin Heidegger <mh...@leichtgewicht.at>.
On 11/02/2012 01:55, Alain Ekambi wrote:
> We have create something similar to the EXT-GWT explorer for our product
> Gwt4Flex. ( http://www.gwt4air.appspot.com/ )
>
> Something in that direction would definitly be usefull.
It would be awesome if you could publish the code under a APL compatible
license under github so it could be improved.
yours
Martin.
RE: [RT] Documentation (split from: Awesome User Experience)
Posted by "Michael A. Labriola" <la...@digitalprimates.net>.
>>I'm curious how Open-Source projects handle the localization of documentation.
Before Adobe started the process of donating Flex to Apache, Spoon was working with them to open the localization of the framework and eventually docs to the community. We can see if Adobe is willing to donate any of the work done so far.
Mike
Notice: This transmission is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. Any dissemination, distribution or copying of this transmission by anyone other than the intended recipient is strictly prohibited. If you have received this transmission in error, please notify the sender immediately by e-mail or telephone and delete the original transmission. Thank you.
Re: [RT] Documentation (split from: Awesome User Experience)
Posted by Martin Heidegger <mh...@leichtgewicht.at>.
On 11/02/2012 02:56, David Francis Buhler wrote:
> I'm curious how Open-Source projects handle the localization of documentation.
- Every system does it differently, this can be handled in a lot of ways.
I structure it for me like that:
- If documentation is deployed with the release of a project then every
"localization team" has time
to the release to add documentation and either they deploy with
untranslated parts or deploy
the translated parts once each translation is done.
- If the documentation is on a global service (homepage) then usually
the english page is first there
and the translators translate as they pass by. (See php documentation).
- Projects that do not change over a long time due to their simplicity
(small JavaScript projects) usually
can have one documentation and the documentation gets a version related
to but not similar to the
project.
API-doc translation is something that is missing in the FLEX SDK for
years now - I had particular difficult discussions about that in the
Java Community.
I have two concepts for that lying around somewhere.
If we have wiki it would work like:
> ...ng Tour de Flex, I'm not sure how effective it is.
I am not saying that we should continue it, I have certainly not used it ...
> If people have found the application to be helpful, I'd be interested in hearing more.
Me too.
yours
Martin.
Re: [RT] Documentation (split from: Awesome User Experience)
Posted by David Francis Buhler <da...@gmail.com>.
Martin,
My apologies for thread-hijacking.
I'm curious how Open-Source projects handle the localization of documentation.
My understanding is that Adobe intends to donate the Tour de Flex
application, per another thread. With all due-respect to the efforts
of those involved with developing Tour de Flex, I'm not sure how
effective it is. If people have found the application to be helpful,
I'd be interested in hearing more.
@Alain,
Your explorer is excellent for providing examples. The hierarchy, I
think if effective.
On Fri, Feb 10, 2012 at 12:10 PM, Alain Ekambi
<ja...@googlemail.com> wrote:
> Looks like my post did not get through ....
>
> 2012/2/10 Alain Ekambi <ja...@googlemail.com>
>
>> We have create something similar to the EXT-GWT explorer for our product
>> Gwt4Flex. ( http://www.gwt4air.appspot.com/ )
>>
>> Something in that direction would definitly be usefull.
>>
>>
>>
>> 2012/2/10 Martin Heidegger <mh...@leichtgewicht.at>
>>
>>> Hello Francis
>>>
>>> I think you are talking more about developer experience than end-user
>>> experience.
>>>
>>> The wiki seems a good start for documentation to me but I agree that it
>>> has some serious drawbacks.
>>> For example: we can not easily include swf's and AS3 code formatting is
>>> sub-par. But i think if those requests are
>>> raised to the infrastructure team then they will be dealt with. This
>>> would result in following documentation locations:
>>>
>>> *) Wiki: edited documentation, documentation about concepts with example
>>> section
>>> *) Blog: Time-related documentation: Changes/News
>>> *) API-Docs: Generated API documentation
>>>
>>> It would be not so hard to provide something like the PHP Ninja manual
>>> [1] that sets up on the online data.
>>>
>>> The only problem I see with the wiki solution is the translation. I
>>> personally think "just english" is enough. However: For some reason
>>> japanese developers (as a example) seem to be really trying to translate
>>> everything and I am not yet sure how this could be done with the wiki.
>>>
>>> However: this raises another question:
>>>
>>> @Adobe: I assume that the Flash Player AS3 documentation will stay at the
>>> Adobe site:
>>> Do you plan to submit the Flex documentation (not just api docs) to
>>> apache?
>>> Might that include Tour De Flex?
>>> What system/format does it use?
>>> Can the community help with that?
>>>
>>> yours
>>> Martin.
>>>
>>> [1] https://chrome.google.com/**webstore/detail/**
>>> clbhjjdhmgeibgdccjfoliooccomjc**ab<https://chrome.google.com/webstore/detail/clbhjjdhmgeibgdccjfoliooccomjcab>
>>>
>>> On 11/02/2012 01:23, David Francis Buhler wrote:
>>>
>>>> I'd like to see the examples and documentation be part of an improved,
>>>> cohesive 'brand' outlined. The rest of the outline I agree with.
>>>>
>>>> Someone else had suggested the idea of emulating the
>>>> examples/documentation Sencha/JQuery use, which I second. Likewise,
>>>> Google does an excellent job with http://tour.golang.org/
>>>>
>>>> I always found Adobe to offer too many alternatives to finding
>>>> information.
>>>>
>>>> Examples:
>>>> -Adobe offered too many Flex examples in the help.adobe.com site made
>>>> accessing the information slow and painful. Future hiding of the
>>>> Examples until the user clicked a button made 'seeing' the examples
>>>> more involved.
>>>> -The Help Docs had poor SEO. Questions asked about technical problems
>>>> have a certain language, and the page-titles needed to reflect the
>>>> language developers use to search out solutions to problems.
>>>> -The Help Docs were longer than necessary.
>>>> -Tour De Flex's User Experience did not reflect how people seek out
>>>> information. It did not offer a linear evolution of 'challenges' or
>>>> 'difficulty'. Examples often error out.
>>>> -Adobe Community Help provided too many search options, that did not
>>>> reflect an understanding of how people look for information.
>>>>
>>>> -Buhler
>>>>
>>>>
>>
Re: [RT] Documentation (split from: Awesome User Experience)
Posted by Alain Ekambi <ja...@googlemail.com>.
Looks like my post did not get through ....
2012/2/10 Alain Ekambi <ja...@googlemail.com>
> We have create something similar to the EXT-GWT explorer for our product
> Gwt4Flex. ( http://www.gwt4air.appspot.com/ )
>
> Something in that direction would definitly be usefull.
>
>
>
> 2012/2/10 Martin Heidegger <mh...@leichtgewicht.at>
>
>> Hello Francis
>>
>> I think you are talking more about developer experience than end-user
>> experience.
>>
>> The wiki seems a good start for documentation to me but I agree that it
>> has some serious drawbacks.
>> For example: we can not easily include swf's and AS3 code formatting is
>> sub-par. But i think if those requests are
>> raised to the infrastructure team then they will be dealt with. This
>> would result in following documentation locations:
>>
>> *) Wiki: edited documentation, documentation about concepts with example
>> section
>> *) Blog: Time-related documentation: Changes/News
>> *) API-Docs: Generated API documentation
>>
>> It would be not so hard to provide something like the PHP Ninja manual
>> [1] that sets up on the online data.
>>
>> The only problem I see with the wiki solution is the translation. I
>> personally think "just english" is enough. However: For some reason
>> japanese developers (as a example) seem to be really trying to translate
>> everything and I am not yet sure how this could be done with the wiki.
>>
>> However: this raises another question:
>>
>> @Adobe: I assume that the Flash Player AS3 documentation will stay at the
>> Adobe site:
>> Do you plan to submit the Flex documentation (not just api docs) to
>> apache?
>> Might that include Tour De Flex?
>> What system/format does it use?
>> Can the community help with that?
>>
>> yours
>> Martin.
>>
>> [1] https://chrome.google.com/**webstore/detail/**
>> clbhjjdhmgeibgdccjfoliooccomjc**ab<https://chrome.google.com/webstore/detail/clbhjjdhmgeibgdccjfoliooccomjcab>
>>
>> On 11/02/2012 01:23, David Francis Buhler wrote:
>>
>>> I'd like to see the examples and documentation be part of an improved,
>>> cohesive 'brand' outlined. The rest of the outline I agree with.
>>>
>>> Someone else had suggested the idea of emulating the
>>> examples/documentation Sencha/JQuery use, which I second. Likewise,
>>> Google does an excellent job with http://tour.golang.org/
>>>
>>> I always found Adobe to offer too many alternatives to finding
>>> information.
>>>
>>> Examples:
>>> -Adobe offered too many Flex examples in the help.adobe.com site made
>>> accessing the information slow and painful. Future hiding of the
>>> Examples until the user clicked a button made 'seeing' the examples
>>> more involved.
>>> -The Help Docs had poor SEO. Questions asked about technical problems
>>> have a certain language, and the page-titles needed to reflect the
>>> language developers use to search out solutions to problems.
>>> -The Help Docs were longer than necessary.
>>> -Tour De Flex's User Experience did not reflect how people seek out
>>> information. It did not offer a linear evolution of 'challenges' or
>>> 'difficulty'. Examples often error out.
>>> -Adobe Community Help provided too many search options, that did not
>>> reflect an understanding of how people look for information.
>>>
>>> -Buhler
>>>
>>>
>
Re: [RT] Documentation (split from: Awesome User Experience)
Posted by Alain Ekambi <ja...@googlemail.com>.
We have create something similar to the EXT-GWT explorer for our product
Gwt4Flex. ( http://www.gwt4air.appspot.com/ )
Something in that direction would definitly be usefull.
2012/2/10 Martin Heidegger <mh...@leichtgewicht.at>
> Hello Francis
>
> I think you are talking more about developer experience than end-user
> experience.
>
> The wiki seems a good start for documentation to me but I agree that it
> has some serious drawbacks.
> For example: we can not easily include swf's and AS3 code formatting is
> sub-par. But i think if those requests are
> raised to the infrastructure team then they will be dealt with. This would
> result in following documentation locations:
>
> *) Wiki: edited documentation, documentation about concepts with example
> section
> *) Blog: Time-related documentation: Changes/News
> *) API-Docs: Generated API documentation
>
> It would be not so hard to provide something like the PHP Ninja manual [1]
> that sets up on the online data.
>
> The only problem I see with the wiki solution is the translation. I
> personally think "just english" is enough. However: For some reason
> japanese developers (as a example) seem to be really trying to translate
> everything and I am not yet sure how this could be done with the wiki.
>
> However: this raises another question:
>
> @Adobe: I assume that the Flash Player AS3 documentation will stay at the
> Adobe site:
> Do you plan to submit the Flex documentation (not just api docs) to apache?
> Might that include Tour De Flex?
> What system/format does it use?
> Can the community help with that?
>
> yours
> Martin.
>
> [1] https://chrome.google.com/**webstore/detail/**
> clbhjjdhmgeibgdccjfoliooccomjc**ab<https://chrome.google.com/webstore/detail/clbhjjdhmgeibgdccjfoliooccomjcab>
>
> On 11/02/2012 01:23, David Francis Buhler wrote:
>
>> I'd like to see the examples and documentation be part of an improved,
>> cohesive 'brand' outlined. The rest of the outline I agree with.
>>
>> Someone else had suggested the idea of emulating the
>> examples/documentation Sencha/JQuery use, which I second. Likewise,
>> Google does an excellent job with http://tour.golang.org/
>>
>> I always found Adobe to offer too many alternatives to finding
>> information.
>>
>> Examples:
>> -Adobe offered too many Flex examples in the help.adobe.com site made
>> accessing the information slow and painful. Future hiding of the
>> Examples until the user clicked a button made 'seeing' the examples
>> more involved.
>> -The Help Docs had poor SEO. Questions asked about technical problems
>> have a certain language, and the page-titles needed to reflect the
>> language developers use to search out solutions to problems.
>> -The Help Docs were longer than necessary.
>> -Tour De Flex's User Experience did not reflect how people seek out
>> information. It did not offer a linear evolution of 'challenges' or
>> 'difficulty'. Examples often error out.
>> -Adobe Community Help provided too many search options, that did not
>> reflect an understanding of how people look for information.
>>
>> -Buhler
>>
>>
[RT] Documentation (split from: Awesome User Experience)
Posted by Martin Heidegger <mh...@leichtgewicht.at>.
Hello Francis
I think you are talking more about developer experience than end-user
experience.
The wiki seems a good start for documentation to me but I agree that it
has some serious drawbacks.
For example: we can not easily include swf's and AS3 code formatting is
sub-par. But i think if those requests are
raised to the infrastructure team then they will be dealt with. This
would result in following documentation locations:
*) Wiki: edited documentation, documentation about concepts with example
section
*) Blog: Time-related documentation: Changes/News
*) API-Docs: Generated API documentation
It would be not so hard to provide something like the PHP Ninja manual
[1] that sets up on the online data.
The only problem I see with the wiki solution is the translation. I
personally think "just english" is enough. However: For some reason
japanese developers (as a example) seem to be really trying to translate
everything and I am not yet sure how this could be done with the wiki.
However: this raises another question:
@Adobe: I assume that the Flash Player AS3 documentation will stay at
the Adobe site:
Do you plan to submit the Flex documentation (not just api docs) to apache?
Might that include Tour De Flex?
What system/format does it use?
Can the community help with that?
yours
Martin.
[1]
https://chrome.google.com/webstore/detail/clbhjjdhmgeibgdccjfoliooccomjcab
On 11/02/2012 01:23, David Francis Buhler wrote:
> I'd like to see the examples and documentation be part of an improved,
> cohesive 'brand' outlined. The rest of the outline I agree with.
>
> Someone else had suggested the idea of emulating the
> examples/documentation Sencha/JQuery use, which I second. Likewise,
> Google does an excellent job with http://tour.golang.org/
>
> I always found Adobe to offer too many alternatives to finding information.
>
> Examples:
> -Adobe offered too many Flex examples in the help.adobe.com site made
> accessing the information slow and painful. Future hiding of the
> Examples until the user clicked a button made 'seeing' the examples
> more involved.
> -The Help Docs had poor SEO. Questions asked about technical problems
> have a certain language, and the page-titles needed to reflect the
> language developers use to search out solutions to problems.
> -The Help Docs were longer than necessary.
> -Tour De Flex's User Experience did not reflect how people seek out
> information. It did not offer a linear evolution of 'challenges' or
> 'difficulty'. Examples often error out.
> -Adobe Community Help provided too many search options, that did not
> reflect an understanding of how people look for information.
>
> -Buhler
>
Re: [RT] Awesome FlexNext User Experience (was: Starting with the Whiteboard code)
Posted by Ariel Jakobovits <ar...@yahoo.com>.
> offered too many Flex examples
never
> Future hiding of the examples until the user clicked a button made 'seeing'
> the examples more involved.
is 'involved' good or bad, i can't tell from the context?
> The Help Docs were longer than necessary.
i like long help docs, means there is a good chance something is there to help
> Tour De Flex's User Experience did not reflect how people seek out information.
what if we improve our docs to communicate to Tour de Flex over local connection to "tune" the app to examples specific to the doc being viewed?
> Adobe Community Help provided too many search options
Agree.
Ariel Jakobovits
Email: arieljake@yahoo.com
Phone: 650-690-2213
Fax: 650-641-0031
Cell: 650-823-8699
________________________________
From: David Francis Buhler <da...@gmail.com>
To: flex-dev@incubator.apache.org
Sent: Friday, February 10, 2012 8:23 AM
Subject: Re: [RT] Awesome FlexNext User Experience (was: Starting with the Whiteboard code)
I'd like to see the examples and documentation be part of an improved,
cohesive 'brand' outlined. The rest of the outline I agree with.
Someone else had suggested the idea of emulating the
examples/documentation Sencha/JQuery use, which I second. Likewise,
Google does an excellent job with http://tour.golang.org/
I always found Adobe to offer too many alternatives to finding information.
Examples:
-Adobe offered too many Flex examples in the help.adobe.com site made
accessing the information slow and painful. Future hiding of the
Examples until the user clicked a button made 'seeing' the examples
more involved.
-The Help Docs had poor SEO. Questions asked about technical problems
have a certain language, and the page-titles needed to reflect the
language developers use to search out solutions to problems.
-The Help Docs were longer than necessary.
-Tour De Flex's User Experience did not reflect how people seek out
information. It did not offer a linear evolution of 'challenges' or
'difficulty'. Examples often error out.
-Adobe Community Help provided too many search options, that did not
reflect an understanding of how people look for information.
-Buhler
On Fri, Feb 10, 2012 at 11:10 AM, ganaraj p r <ga...@gmail.com> wrote:
> I am completely up for this. I vote for doing something along this line...
>
> On Fri, Feb 10, 2012 at 4:00 PM, Martin Heidegger <mh...@leichtgewicht.at>wrote:
>
>> 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 to
>> 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:
>>
>> *) _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 and
>> feel when being built for Flash without breaking the system.
>>
>> *) _Flash super-powered:_ Systems that leverage the power of the current
>> version of the Flash Player without thinking for a second about HTML: Stage
>> 3D / HD videos / JPEG XR / Slick custom fonts / Pixelbender effects /
>> (generated audio) / ...
>>
>> *) _Touch centric:_ Focussing on the fingers: Swipe/Zoom/Rotate/Expand/**Swoosh/...
>> These concepts don't need to care about a mouse or keyboard.
>>
>> *) _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:
>>
>> * Responsiveness is key: The more stuff that has to run at a time the
>> less likely it will rock.
>> * 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.
>>
>
>
>
> --
> Regards,
> Ganaraj P R
Re: [RT] Awesome FlexNext User Experience (was: Starting with the
Whiteboard code)
Posted by David Francis Buhler <da...@gmail.com>.
I'd like to see the examples and documentation be part of an improved,
cohesive 'brand' outlined. The rest of the outline I agree with.
Someone else had suggested the idea of emulating the
examples/documentation Sencha/JQuery use, which I second. Likewise,
Google does an excellent job with http://tour.golang.org/
I always found Adobe to offer too many alternatives to finding information.
Examples:
-Adobe offered too many Flex examples in the help.adobe.com site made
accessing the information slow and painful. Future hiding of the
Examples until the user clicked a button made 'seeing' the examples
more involved.
-The Help Docs had poor SEO. Questions asked about technical problems
have a certain language, and the page-titles needed to reflect the
language developers use to search out solutions to problems.
-The Help Docs were longer than necessary.
-Tour De Flex's User Experience did not reflect how people seek out
information. It did not offer a linear evolution of 'challenges' or
'difficulty'. Examples often error out.
-Adobe Community Help provided too many search options, that did not
reflect an understanding of how people look for information.
-Buhler
On Fri, Feb 10, 2012 at 11:10 AM, ganaraj p r <ga...@gmail.com> wrote:
> I am completely up for this. I vote for doing something along this line...
>
> On Fri, Feb 10, 2012 at 4:00 PM, Martin Heidegger <mh...@leichtgewicht.at>wrote:
>
>> 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 to
>> 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:
>>
>> *) _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 and
>> feel when being built for Flash without breaking the system.
>>
>> *) _Flash super-powered:_ Systems that leverage the power of the current
>> version of the Flash Player without thinking for a second about HTML: Stage
>> 3D / HD videos / JPEG XR / Slick custom fonts / Pixelbender effects /
>> (generated audio) / ...
>>
>> *) _Touch centric:_ Focussing on the fingers: Swipe/Zoom/Rotate/Expand/**Swoosh/...
>> These concepts don't need to care about a mouse or keyboard.
>>
>> *) _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:
>>
>> * Responsiveness is key: The more stuff that has to run at a time the
>> less likely it will rock.
>> * 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.
>>
>
>
>
> --
> Regards,
> Ganaraj P R
Re: [RT] Awesome FlexNext User Experience (was: Starting with the
Whiteboard code)
Posted by ganaraj p r <ga...@gmail.com>.
I am completely up for this. I vote for doing something along this line...
On Fri, Feb 10, 2012 at 4:00 PM, Martin Heidegger <mh...@leichtgewicht.at>wrote:
> 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 to
> 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:
>
> *) _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 and
> feel when being built for Flash without breaking the system.
>
> *) _Flash super-powered:_ Systems that leverage the power of the current
> version of the Flash Player without thinking for a second about HTML: Stage
> 3D / HD videos / JPEG XR / Slick custom fonts / Pixelbender effects /
> (generated audio) / ...
>
> *) _Touch centric:_ Focussing on the fingers: Swipe/Zoom/Rotate/Expand/**Swoosh/...
> These concepts don't need to care about a mouse or keyboard.
>
> *) _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:
>
> * Responsiveness is key: The more stuff that has to run at a time the
> less likely it will rock.
> * 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.
>
--
Regards,
Ganaraj P R
Re: [RT] Awesome FlexNext User Experience (was: Starting with the
Whiteboard code)
Posted by Martin Heidegger <mh...@leichtgewicht.at>.
On 11/02/2012 01:56, Haykel BEN JEMIA wrote:
> Nice proposal Mike. Regarding 'Fully portable', is that not just a matter
> of skinning or are you thinking about more?
>
> Haykel
The word "Skin" has certain restrictions in the current Flex model which
is why I tried to avoid it.
I am talking about rule-based-translatable designs.
The "rule" as to how-the-data-is-mapped to the various versions and at
which level the "skinning" starts
should be freely definable by the one who has the idea.
PS.: Its "Martin" :)
Re: [RT] Awesome FlexNext User Experience (was: Starting with the
Whiteboard code)
Posted by Haykel BEN JEMIA <ha...@gmail.com>.
Nice proposal Mike. Regarding 'Fully portable', is that not just a matter
of skinning or are you thinking about more?
Haykel
On 10 February 2012 17:00, Martin Heidegger <mh...@leichtgewicht.at> wrote:
> 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 to
> 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:
>
> *) _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 and
> feel when being built for Flash without breaking the system.
>
> *) _Flash super-powered:_ Systems that leverage the power of the current
> version of the Flash Player without thinking for a second about HTML: Stage
> 3D / HD videos / JPEG XR / Slick custom fonts / Pixelbender effects /
> (generated audio) / ...
>
> *) _Touch centric:_ Focussing on the fingers: Swipe/Zoom/Rotate/Expand/**Swoosh/...
> These concepts don't need to care about a mouse or keyboard.
>
> *) _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:
>
> * Responsiveness is key: The more stuff that has to run at a time the
> less likely it will rock.
> * 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.
>