incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Heidegger>
Subject Re: [RT] Awesome FlexNext User Experience (was: Starting with the Whiteboard code)
Date Sun, 12 Feb 2012 17:19:43 GMT
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 

Just thoughts.



On 13/02/2012 01:57, JP Bader wrote:
> I have never seen, 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
> <>  wrote:
>> does it.
>> On Fri, Feb 10, 2012 at 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?
>>> Ariel Jakobovits
>>> Email:
>>> Phone: 650-690-2213
>>> Fax: 650-641-0031
>>> Cell: 650-823-8699
>>> ________________________________
>>>   From: JP Bader<>
>>> To:
>>> Sent: Friday, February 10, 2012 9:07 AM
>>> Subject: Re: [RT] Awesome FlexNext User Experience (was: Starting with the Whiteboard
>>> 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  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<>  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<>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
>>>>> 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
>>>>> to work within the restrictions of HTML/JS with a optional royal look
>>>>> 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:
>>>>> 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
>>>>> 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
>>>>> 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 |
>>> 608.692.2468

View raw message