Goodbye and thank you, Flash Player, for all that jazz

July 27th, 2017

My adventure with Flash Player had started back in 2002 when I’ve explored the capabilities of this platform for the User Interface prototyping at Philips Research using Flash MX components and ActionScript 2.



One of my first commercial work was games development together with Sean Wood using Flash lite development for one Japanese mobile operator, later we’ve done together interactive maps app for Ayuquila river basin area for United Nations University.

My interest into the development of UI components using Flash platform had led to my collaboration with Judah Frangipane on Tree component with Drag and drop support.

Later I worked with Dmitry Leader on Re:mark application to be used by mentors for adding remarks to the reviewed documents, early days of the company that is now known as Grammarly.

Then we played with an idea on building audio player in Flash for ukrainian mobile operator Kyivstar and Anton Antropov.

In 2005 a group of ex-employees from Macromedia and Microsoft had established an startup in intriguing Ukraine to build on Web an user customized application built in Macromedia Flex 1.5 and later Adobe Flex 2, that’s how I did open an new chapter in my life with Flex UI framework.

I’ve spent with Flex UI framework almost 10 years of my development career, did a few talks at Ukrainian Flash User group, open-sourced InputAssist component, but after Adobe decision in 2011 to abandon the future development of Flex framework it become obvious that sooner or later every seasoned Flex developer has to move on.

Nowdays my choice of technologies for modern web application is React and Redux state container, Javascript with Ecmascript 6 touch, npm and many more.

Yes, we will say the final goodbye to Flash player runtime in 2020, but Web and UI interfaces will remain with us till the very end of our professional life.

mx:HTTPService calls are cached in IE 6 unnecessary

November 23rd, 2006

Usually, mx:HTTPService is defined in MXML in the following way:

<mx:HTTPService id="accountsRequest"
      method="POST" url="accounts.php"
      result="assignUsersData(event)" fault="onErrorLoad(event)">

Such a HTTP request works flawlessly in Firefox browser, but in IE6 after first call the results of HTTP get cached and a new call to the remote destination never occur. The same issue is discussed at Adobe Flash Player 9 forums.My solution to prevent caching of HTTP requests in IE is to add foo variable to the url of HTTP Service that equals to the random value.

private function changePage(pageIdValue : Number) : void 
      var rnd : Number = Math.round(Math.random()*1000);
      accountsRequest.url = "accounts.php?foo=" + rnd;
      pageId = pageIdValue; 

Macromedia will preserve its name forever in MXML abbreviation

May 11th, 2006

I feel kinda blue, when I see more and more signs that Macromedia brand and Macromedia name will slowly dissappear from the Internet, and only historians and Internet WayBack machine will remember what Macromedia name standed for.

But today, I kinda feel happy again, because Macromedia FleX Markup Language (MXML for short) – a markup language for rich internet applications created by Macromedia back at 2003 and now intelectual property of Adobe will hold the the glory Macromedia name inside MXML abbreviation for ever, I guess.

I think it is very unlikely, that MXML will change its name to AXML (Adobe FleX Markup Language) some day.

John Dowdell, please, do not prove, that I am wrong in my statement!

Cool audio/video player built in Laszlo

March 30th, 2006

I got to know today, that there are at least 5 cool Laszlo developers in Berlin, Germany and most of them are employed in Yokai studios ( site done by help of Laszlo technology).

I am not sceptical here, there are currently only 5 good ( not equal to cool :)) Adobe Flex developers ( me included) in Kyiv, Ukraine ( yep, I am located here 🙂 that I currently aware of.

Yokai studios had delivered quite cool web-site for regional radio-station 104. 6 RTL. Yokai studios developers had applied ColdFusion, Laszlo and some common sense to create an smooth and appealing experience for the visitors of radiostation’s web-site.

Most of all, I liked audio/video player built by the help of Laszlo. Audio/video playback capability – is something that Flash player doing extremely well and no wonder more and more web-sites are supporting Flash video FLV format as a main file format for the video content to be displayed at the web.

Jukebox player

After Pandora’s jukebox, it is a second attempt I saw to create a multimedia player online in Laszlo and both attempts rocks! in my mind.

IMHO, In the battle of commercially deployed audio/video players
Laszlo : Adobe Flex 2:0

Why Flex is more superior over open-sourced Laszlo? Here is my take

November 21st, 2005

   While there is quite a number of technoolgies aiming to ease the life of modern RIA developer ( Droplets, Xamalon/XAML/Sparkle, Laszlo, JSF, XUI, XUL based stuff, SwixML, Thinlets, XSWT, Luxor, Keystone, Jazilla, Vexi, Ajax, etc… thanks for this list Tariq Ahmed from Flexcoders mailing list we the three contenders for the final choice as main technology to deliver RIA applicatiion at client.

   The conteders are: Flash, Flex and Laszlo. No surprise, here.

   We selected Macromedia Flex as our initial choice in summer 2005 and we do not yet regret about it.

   The selection creterea were: the exisitng developer base, the innovation development done with this technology, the solid widget library, AMF binary protocol support, final download size of SWF, final time of the development to name a few.

   I would like to hear more both from strong opponnnets of Flash and Laszlo technologies how those technologies can be superior over Macromedia Flex to deliver enterprise level RIA in web-browser.