https://my.adobeconnect.com/_a295153/p89f97u8cph/?launcher=false&fcsContent=true&pbMode=normal

… instead it is the fault of Adobe, which was constantly delaying the release of a fully featured Designer/Developer workflow which was finally introduced with Flash Catalyst CS5.5 and Flash Builder 4.5 this year. And Flash Catalyst is still not the way it should be … for more information listen to this audio podcast (16m:30s):

http://blog.nerdradio.com/post/14180140595/after-the-first-day-of-the-flex-community-summit

Just to recap: Flash Catalyst (formally codenamed “Thermo”) was announced in early 2007 on Adobe Labs:

http://franto.com/thermo-on-adobe-labs/

Discontinuing Flash Catalyst and removing it from the Creative Suite of Adobe means:

• This is bad news for all people who prefer to design and think visually: http://en.wikipedia.org/wiki/Visual_learning
• This is bad news for all Flex developers which have to navigate and code large-scale Flex apps.
• This is bad news for all Flex designers that need to interact with Flex developers.
• This is bad news for all Flex beginners because it adds another barrier while learning Flex development … and this is bad again because we need more highly skilled Flex developers around.

Please:

1) Sign this petition: http://www.change.org/petitions/adobe-systems-flash-catalyst-must-survive

2) Vote on these questions for the past Flex summit (Dec 12th – 13th, 2011) to show your affords:

• http://openspoon.uservoice.com/forums/142644-future-of-flex-questions-for-adobe/suggestions/2447111-flash-catalyst-
• http://openspoon.uservoice.com/forums/142644-future-of-flex-questions-for-adobe/suggestions/2450508-how-much-is-the-flashcatalyst-source-code-
• http://openspoon.uservoice.com/forums/142644-future-of-flex-questions-for-adobe/suggestions/2449494-how-can-we-make-skin-components-of-flex-4-x-withou
• http://openspoon.uservoice.com/forums/142644-future-of-flex-questions-for-adobe/suggestions/2450042-is-it-true-that-design-view-will-not-exist-in-new-

3) Buy Flash Catalyst CS5.5 to show respect to Adobe’s pioneering work in the last years.

4) Buy the Flash Catalyst source code or lets start building our own Open Source Flash Catalyst for Flex developers.

1. The W3C and ECMA Int will implement their standards

Flash- and Flex-Coding would still be relevant in 2050 unless the W3C and ECMA Int will decide that it is not just enough to define a standard for the web – and HTML and Javascript in particular. Instead, they would also take care of its implementation of a freely available and open WWW with a _SINGLE_ HTML/Javascript engine (or web browser). Still having so many versions of web browsers out there could mean: the WWW is still very new and we (including the W3C and ECMA Int) probably don’t know yet where it should lead us to.

Benefits:

• HTML/Javascript documents look and behave the same EVERYWHERE!

Risks:

• The risk grows that the development of a single web browser inside the W3C and ECMA Int could be misused in favor to a certain involved company.
• Different web browser stay in competition in growing features, performance and their user community. Removing this competition could result into a weaker WWW.

2. HTML/Javascript will go RIA

Flash- and Flex-Coding would still be relevant in 2050 unless the W3C and ECMA Int does not combine SVG, WebGL, HTML, CSS & Javascript … etc. into a single Rich Internet Application (RIA) document specification – hereby called “RIA-HTML”. For the moment the W3C still considers HTML to be a “text document with additional multimedia features”, whereas, a Flash document can be considered as a “pure multimedia document” (Audio, Video, 3D, Text … etc).

Benefits:

• A “pure multimedia document” similar to MXML/FXG (Flex) or XAML (Silverlight) would be way more expressive

3. HTML/Javascript will be binary with a Semantic Webservice API

Flash- and Flex-Coding would still be relevant in 2050 unless HTML/Javascript cannot be compiled into binary code so that search engines, crawlers and web bots will be restricted to only communicate to the “RIA-HTML” document via a certain separated Semantic Webservices API … for more information read Semantic Web and RDF, OWL … etc.

Benefits:

• Compiled binary HTML/Javascript could significantly be transfered much faster between client and server
• Users don’t have to run through any human-prove task in the web anymore … e.g. “Prove you are human while typing in the letters below: k2eMSlo rUs4Kin”
• Search engines, crawlers or any type of web bots only get the information which is intended for them

Risks:

• Users don’t see what is inside a binary HTML/Javascript anymore (unless there is a “View Sourcecode API” included)

4. Javascript will become a type-safe OOP-language

Flash- and Flex-Coding would still be relevant in 2050 unless Javascript will become a type-safe OOP-language … which means: introducing castable typed objects and more powerful OOP features into the language.

Benefits:

• Faster Javascript code execution
• Better tooling-support for Javascript

Conclusion

We should “occupy” W3C and ECMA Int … because then there wouldn’t be the need to “occupy” Flash … http://www.occupyflash.org/

http://www.riagora.com/2011/11/flex-is-open/

http://blogs.adobe.com/flex/2011/11/your-questions-about-flex.html

http://www.mikechambers.com/blog/2011/11/11/clarifications-on-flash-player-for-mobile-browsers-the-flash-platform-and-the-future-of-flash/

I think, for the moment, we all should calm down and watch these two videos first:

http://zaa.tv/2011/04/360flex-denver-2011–day-2-keynote-spoon/
http://tv.adobe.com/watch/max-2011-develop/open-source-flex-what-the-spoon-project-means-to-you/

… and participate in the Open Spoon Project. Adobe tries to involve the Flex community into the development and bugfixing process of the Flex SDK. Some might say that Adobe just tries to benefit from cheap developers to develop their Flex SDK. Others might say that we will all benefit from this community work in future.

I guess, Adobe is only trying to restructure their capacities (around 6000 employers worldwide, maximum of 50 Adobe developers work on the Flex SDK). They will refocus on building tools (Flash Pro CS6 and later, Flash Builder 5 and later, Flash Catalyst CS6 and later) and providing services (Flash Media Gateway, Cirrus, LiveCycle Collaboration Service … etc.) which will surround the Flashplayer. Furthermore, they will continue to constantly release new Flashplayer versions with more and more missing “Java Virtual Machine” (JVM) respectively “Java Applet” features on a yearly basis (Flashplayer 12, 13, 14, 15, 16 … etc). And they will invest into HTML5 – Tools, too (Muse, Edge) … because it is of need to the evolution of the WWW.

AND … I strongly believe that there will be:

- Flex 5 with Flashplayer 11 Stage3D (Molehill)
- Flex 6 with Flashplayer 12 Multithreading … and maybe with a single embedded MVC framework (similiar to Parsley, Swiz, Spring AS, Robotlegs, Mate … and such) and Flex 6 MVC code generation wizards in Flash Builder 6
- Flex 7 with Flashplayer 13 …

I still remain optimistic regarding the future of the Flash Platform, and I really hope that Adobe’s pocket-money hasn’t been consumed before Flex 7 will be released in 2014 …

“Over the coming weeks Adobe and the Spoon Foundation will be working together to donate the Flex SDK to an established open source foundation.

The project will be jointly led by developers from the Flex SDK team, members of the Spoon Project, key developers from the community and contributors from enterprise companies using Flex.

Continued development will happen under this new governance model.

The Open Spoon Foundation board and officers are excited by these continued developments and looking forward to the collaboration. Details will be evolving rapidly, check back here for continued updates.”

see announcement of the Open Spoon Project:

http://www.spoon.as/2011/adobe-announces-intention-to-donate-flex-sdk/

I expected that this day would come in future, but, I did not expect it to come so soon. I hope that this decision will bring a positive new responsibility to this new growing Flex community and will hopefully be as effective as the Java open source community became in November 13, 2006:

http://en.wikipedia.org/wiki/Java_(programming_language)

If not, then I am seeing the risk that all Flash- and Flex-Developers have to go back to the past web browser war years which most of them hated and hoped they never have to go back again:

http://en.wikipedia.org/wiki/Browser_wars

If yes, I am very curious about the future of the Flash Platform. Is the complete Flash Platform (Flash Player, Flash Pro, Flash Builder, Flash Catalyst) going to be open sourced within the next 10 years, too? What about Flex 5 running on Stage3D (Molehill)? What about Flash Catalyst CS6 or even later? Who will be responsible for the development of the Flashplayer, Flash Pro, Flash Builder and Flash Catalyst for the next 10 years?

For my Flex 4 code examples I also created an additional Flex 4 Coding Conventions wiki page into Google Code, see:

http://code.google.com/p/masuland/wiki/Flex4CodingConventions

Hope this helps!

Wanted to let you know that I was able to add Flex 4.5 (Hero) for Mobile examples to my “Login Example”. The following IoC Microarchitectures are supported so far:

- Mate 0.9.1
- Robotlegs 1.4 / AS3-Signals 0.8
- Parsley 2.4.0
- Spring AS 1.1
- Swiz 1.1

The source code can be found at Google Code:
http://code.google.com/p/masuland/wiki/LoginExample

Hope this helps. Feedback for improvements would be great!

When thinking about the implications of the Open Screen Project I started thinking how I can write a single Flex application for different devices. Therefore, I created an application called “Login Example” which can be found at Google Code:

http://code.google.com/p/masuland/wiki/LoginExample

Implementations for different Flex versions and MVC frameworks like Cairngorm 2.2.1, Cairngorm 3, Swiz 1.0, Parsley 2.2.2, Spring AS 1.0 … etc. will be discussed as well. Please feel free to give comments or suggestions because the code is still work in progress.

Thank you,
masu

just added my additional Flex 3 Coding Conventions into the Google Code Wiki, see:

http://code.google.com/p/masuland/wiki/Flex3CodingConventions

Hope this helps,
masu

Adobe® Flash® Builder™  4 Beta 1: http://labs.adobe.com/technologies/flashbuilder4/

http://www.myspace.com/hirnsaeule

• Heiko (Singer)
• Steffen (Guitar)
• Digger (Guitar)
• Thomas (Bass guitar)
• Masu (Drums)

We’ll see how far this rabbit goes!