As it is said here:
http://houseofbilz.com/archives/2010/12/29/cross-training-in-silverlight-flexmvvm-vs-presentation-model/
\"If you do a Google search today fo
What prevents Silverlight MVVM to be implemented like Flex ?
in .net silverlight/wpf everything should transparent. Binding is notification mechanism so, it should act "at least" like event base system.
If yes why does Silverlight do things more complicated what's the advantages then ?
for me, it is about mindset, if i know it is an event base system, then i should carefully use it. do not over use it, etc.
cases: Binding converter, easily implemented in flex, not in silverlight.
in flex: text="{getColor(pm.customerName)}" yes it is amazing simple, but the question is are you sure your PM will be released correctly by garbage collection, because it is an event base system, who responsible to observe the change? getColor method? or text property? or both? really hard to know that.
in silverlight: text="{Binding CustmerName, Converter={StaticResources nameToColorConverter}}" i don't need to ask who is responsible to observe, because colorConverter is only a converter supported by binding. i don't need to worry about memory leak.
so, for me its all about the mindset.