I had a discussion yesterday night in a restaurant with two nerds teasing me about Silverlight. This leads me to think we have to clarify some points... That's the reason why I'm going to try to answer objectively to this obvious question: "Why should YOU use GOA WinForms?"
Well, all of you understood that GOA WinForms was not producing Silverlight apps the way Microsoft would and that we were using the Canvas to host our own container: WinFormHost.
This means that GOA WinForms controls:
- have to be hosted in the WinFormHost,
- cannot overlap other not GOA controls.
These are technical consequences of our strategy, which may look at first sight, quite strange and not compatible with Microsoft's vision. Without any hesitation I answer you that our philosophy is compatible and work hand in hand with Microsoft's strategy of going ahead from WinForms to WPF and from WPF to Silverlight.
This must be clear: we are going to provide WinForms developers an alternative way to start, now, creating RIA targeting Silverlight or Flash. The alternative being: use your already existing - deep & rich - knowledge of WinForms to create, right now, Silverlight/Flash apps with a zero learning path.
That's the main reason why GOA WinForms is an implementation of the standard System.Windows.Form .NET library.
So, will every WinForms developer start using GOA to create beautiful, rich, fast and magnificent RIAs? Well, while it sounds great to my ears, future will not be like that... GOA WinForms convince:
- Developers who don't want to do "one more move in the application development history" and use the full potential of their knowhow.
- Developers who have to provide rapidly a professionnal RIA using Flash or Silverlight, without having to learn WPF/Silverlight/Blend/Orcas, without having to start prototyping, etc.
I hope this "lights up" our strategy and way of thinking the Next Web.
Currently rated 5.0 by 1 people
- Currently 5/5 Stars.
- 1
- 2
- 3
- 4
- 5