29. August 2011

Pexeso – Flex-like framework for PHP

Switching between different languages during development of server-client application is daunting task.

Jan Volf wrote Pexeso framework. Pexeso is component based, event driven PHP View-Controller framework similar to Adobe Flex framework.

Developer can reuse patterns and Flex style of writing code even when coding in PHP.

You can find this project at SourceForge: pexeso-php.sourceforge.net

17. August 2011

Problem with jQueryMobile application in Internet Explorer

I was building application based on jQueryMobile.

It worked correctly in all modern browsers except Internet Explorer. Application was displayed incorrectly and it was not functioning at all.

Solution to this problem was quite easy. I forgot to specify following line in the beginning of document:

<!DOCTYPE html>

Application started to work correctly also in IE after this small fix.

19. July 2011

Mobile First! Video – aDevCamp Prague

Video recording from my talk about Flex, Flash Builder and Android development is available (only Slovak version).

Slides

18. July 2011

Mobile Summer Challenge for EU developers

Adobe announced contest for developers – Adobe Mobile Challenge.

Create app in Flex, package it for iPhone, BlackBerry and Android. Submit it to contest before 1st September.

4. July 2011

Emglare Mobile 0.1 – available for Android

First testing version of Emglare Mobile 0.1 is available on Android Market.

Functionality of application is quite small. It just allows to search for events. Further features will be added in future.

Feel free to test it and give some feedback to Emglare development team.

You can use application even without having Emglare account.

27. June 2011

The end of RIA era as we know it

RIA erra was annouced several years ago by companies like Adobe, Microsoft and Sun. Those companies had special software “fixtures” that move web behind static HTML. Flash player, Silverlight or JavaFX carried promise of more interactive future.

The only problem was that technologies like Flash Player and Silverlight were under control of companies. Yes, there were a lot of things that you could do with RIA tools. Building video player, complex enterprise apps and so on.

Adobe took even further step and made this technology available for Linux community. Unfortunately some managers took measures and decided that they won’t ship Eclipse based plugin for Linux and as a result this led company to cancelling support for Linux in Adobe AIR. The glorious promise of one code multiple platform was broken.

Flex/Flash/AIR and Silverlight are very advanced technology. They can do a lot. The price for that is hidden in their complexity. The web learned from mistakes of those technologies.

It happens that when you write code for the first time then you make a lot of mistakes. Once you do it again you can make it even more efficient. RIA era was great starting point for open technologies that we have today.

I would like to add further points to Flex, because I invested huge amount of my time into this technology. Flex is great piece of technology art. There is no question about that. Flex is even open source. Unfortunately it is complex. Complexity is good when you want to sell enterprise software. Let me formulate it in other way: It was good when you wanted to sell enterprise software. Complexity of projects were blocking Innovation. Take jQuery do some fancy stuff in 5 minutes and you won’t be able to do it in Flex in 4 days.

The primary trap of Flex was one big untrimmed framework. Adobe found out that Flex 3 is too big to fit on mobile devices and therefore Flex 4.5 has completely different architecture. It is so different that it took several days or weeks to port application. That is expensive and result is questionable. My advice is do not try to port app to Flex 4. Write a new one.

The last hope for Adobe Flash player was to promise something great. They promised wonders of 3D in Flash player “soon” at Adobe MAX 2010. Today is summer 2011. No 3D was launched in official version of Flash Player. Meanwhile WebGL and Canvas took off. Open technologies are taking over the ground of 3D and people are doing real creative stuff with great performance even without Flash.

Adobe focused Flex 4.5 on mobile development. I doubt that it was right step how they did it. In order to meet the promise of mobility they had to broke a lot of backward compatibility stuff and to be honest you have to rebuild apps from the scratch again. Another problem is that many good Flex/RIA developers left Adobe in last months. It’s a big challenge for Flex team to keep the ball rolling. I wish them good luck.

I do not regret time invested into Adobe technologies. It taught me a lot. The only thing that I saw as a weak point of Adobe is communication with community. Voices from Linux community were overlooked for many years. Even minor bugfixes took 2 years to implement. Adobe was not able to off-load this development and testing to community. jQuery and other JavaScript frameworks did this in much better fashion.

As far as I understand actual situation Adobe is now moving toward more “safer” enterprise world. Adobe bought Day software and other companies that are focused on enterprise world. But that is different story.

To tell long story short: This is the end of the RIA era as we know it. There are new challenges :-)

19. June 2011

FlexMojos some useful links

There are a lot of information resources about FlexMojos scattered around the web. FlexMojos is evolving and it is necessary to watch changes.

I really suggest to use IntelliJ Idea for writing pom.xml. Idea will help you by highlighting mistakes and incompatibilities that you have in pom.xml.

I found some useful resources that might help you:

18. June 2011

Structure of Flex project for multi-target development

What I mean by multi-target?

Today it is possible to create Flex project that runs in browser as Flash application. Other option is to create mobile or desktop application using AIR.

The question is how to structure bigger projects that need to target web, mobile and desktop.

Let’s assume that we’re developing multiple applications and therefore it is good to have common library which aggregates common functions.

That is sufficient when you’re targeting just one platform. Once you need to support more projects then one common library is not enough.

It is reasonable to split this library into the main core that is common for all projects and then create specialized libraries for AIR, web and mobile.

On the top of these libraries you can build final applications for desired platform.

Recap:

  • top: applications for mobile, web and desktop
  • middle: specialized libraries that extends functionality for mobile, web, desktop
  • bottom: common library for all platforms

16. June 2011

Emglare opened it’s API

First delivery of open API from Emglare.com is here.

You can find JSON and XML API at: emglare.com/api.

Feel free to test it. It’s open for developers to build new extensions.

14. June 2011

Air 2.7 – performance improvement for iOS apps

AIR 2.7 was released! Many new things and improvements. AIR now supports Mac, Win, Android and Blackberry devices.

You can use JavaScript, ActionScript, HTML, MXML or native code to build your application.

See full article at blogs.adobe.com.

  • Babel fish

      Translate from:

      Translate to:

  • Where’s the fish?

  • Starfish

  • Fish for you

  • Further info

  • Badges

  • Video channel

  • Learning

    Grow your brain.
  • Tags

  • Topics

  •  

    May 2012
    M T W T F S S
    « Apr    
     123456
    78910111213
    14151617181920
    21222324252627
    28293031  
  • Comments