comparison

Flex 3 SDK Vs. Flex 4 SDK – Part 5 – View States

In previous posts in the series we discussed new features in Flex 4 that are basic in nature (namespaces, an introduction to the new Spark components architecture and the new mxml tags to name a few).

In the next few posts we will discuss the more interesting stuff new with Flex 4 like FXG, states, layouts, effects and skinning.
So, without further ado, View States!

 

sefi 29/06/2010 - 08:56
comparison, currentState, excludeFrom, flex, Flex, flex 3 sdk, Flex 4 SDK, includeIn, view states, Flex
Flex 3 SDK Vs. Flex 4 SDK

Now that Flex SDK 4 was released, I thought I'd do a series of posts on the differences between Flex 3 and Flex 4 SDKs that will hopefully help migrate your Flex 3 app to Flex 4 or make the transition from SDK 3 to SDK 4 easier. I will be assuming you already know Flex 3 and will concentrate on the new in Flex 4 compared to Flex 3.

This post will serve as the index of the series, and I will be adding links to the different posts to this one as they become available, so come back from time to time to get updated.

 

sefi 21/04/2010 - 07:33
comparison, flex, Flex, flex 3, flex 4, MX, namespace, sdk 3, sdk 4, Spark
Nice comparison of Django, Rails & Grails

 Check out this quick & to-the-point comparison of the leading RAD web frameworks:

 http://prezi.com/n9re7-x9guah/django-and-rails-and-grails-oh-my/

 

 

 

 

udib 29/11/2010 - 16:06
comparison, Django, Django, frameworks, Python, Rails
Flex 3 SDK Vs. Flex 4 SDK – Part 4 – Two-way data binding

In previous posts in the series we discussed namespaces, an introduction to the new Spark components architecture and the new mxml tags introduced with Flex 4.
This post is all about data binding, and two-way data binding new to Flex 4 specifically.

Basically, data binding is like taking a piece of string and tying each end to an object, so that when the data in one object is modified, the modified data also applies to the other object. The benefits are obvious – an easy way to pass data between different layers of the application or an easy way to catch an event with a single handler and have that handler update more than one object are a few examples.

sefi 30/05/2010 - 23:07
bidirectional, binding, comparison, data binding, Flex, flex 3 sdk, Flex 4 SDK, two-way
Flex SDK 3 Vs. 4 - Part 1 - Namespaces

Flex 4 added some namespaces, while it still supports the Flex 3 namespaces. This can cause some confusion, more so since some classes are part of two namespaces.

 

While Flex3 used only one namespace (xmlns:mx="http://www.adobe.com/2006/mxml"), Flex4 uses 3 namespaces:
xmlns:fx="http://ns.adobe.com/mxml/2009"
xmlns:s="library://ns.adobe.com/flex/spark"
xmlns:mx="library://ns.adobe.com/flex/mx"
Note, that while there's still a mx namespace, the URI is different.

 

Each namespaces defines a component set. The old Flex3 mx namespace is still active but if you use it Flex 4 features will not be available.

 

The fx:namespace includes top-level AS building blocks such as Object, Array etc. but does not include any of the mx or spark component sets. It also includes some mxml tags, like <fx:script>, <fx:style> and <fx:declarations>.

sefi 21/04/2010 - 07:35
comparison, flex, Flex, flex 3, flex 4, MX, namespace, Spark
Study compares productivity levels of Python+Django vs. C#+ASP.NET

 A recent study measured the productivity of using Python+Django vs. C#+ASP.NET, in terms of user-stories per week. The results are that 1 Django developer is equivalent to 2 ASP.NET developers, productivity-wise:

http://kurtgrandis.com/blog/2010/02/24/python-django-vs-c-asp-net-produc...

 

The Django team that participated in the benchmark, BTW, had no prior experience with Django, which probably implies that the difference can be even higher.

 

 

udib 25/02/2010 - 13:34
ASP.NET, comparison, Django, Django, Productivity, Python, Python
iBATIS, Hibernate, and JPA: Which is right for you?

This article introduces and compares two of the most popular open source persistence frameworks, iBATIS and Hibernate. It also discusses the Java Persistence API (JPA). It introduces each solution and discusses its defining qualities, as well as its individual strengths and weaknesses in broad application scenarios. It then then compares iBATIS, Hibernate, and JPA based on factors such as performance, portability, complexity, and adaptability to data model changes.

yanai 19/07/2008 - 19:30
Article, comparison, Hibernate, ibatis
Syndicate content