Linked by Thom Holwerda on Fri 29th Oct 2010 20:48 UTC
Microsoft Most websites glossed over this, but we didn't. Silverlight, once touted as Microsoft's answer to Adobe's Flash, has been retooled from its original purpose. Microsoft is betting big on HTML5 instead, turning Silverlight into the development platform for Windows Phone, and that's it. So... Silverlight is dead - long live Silerlight?
Thread beginning with comment 447707
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Good news for HTML5 ...
by ephracis on Fri 29th Oct 2010 23:36 UTC in reply to "Good news for HTML5 ..."
Member since:

And getting slightly off-topic, how is WPF coming along? I mean, is it really taking off? I can't recall sampling any apps that use it, unless they're so close to the native Win32 look & feel that I didn't recognize it. I heard they retooled the code editor in VS 2010 to use it, but besides that?

Yeah, VS2010 is WPF.
In my hobby project I use WPF. I know, it's not a big project but you can see for yourself that it looks very native:

Reply Parent Score: 1

RE[2]: Good news for HTML5 ...
by WorknMan on Sat 30th Oct 2010 00:23 in reply to "RE: Good news for HTML5 ..."
WorknMan Member since:

How hard is it to create WPF apps... I mean, the ones that look native? Do you have to be a web/graphics designer to make them look decent, or do they have a 'generic' mode where you can just layout the controls like windows forms?

Reply Parent Score: 2

RE[3]: Good news for HTML5 ...
by Nelson on Sat 30th Oct 2010 04:31 in reply to "RE[2]: Good news for HTML5 ..."
Nelson Member since:

WPF apps have default templating to match OS look and feel. You can even switch resources and use the XP look and feel on Vista/7, or the Vista/7 look and feel on XP or vice versa.

WPF is a complex beast, with 10 ways to do the same thing, but it's the most powerful framework I've ever used.

Silverlight is WPF's less complex distant relative, instead of 10 ways to do something, there's 2-3.

Reply Parent Score: 2

ephracis Member since:

It's pretty easy. Most of my design I do in XAML which is very efficient. But sometimes I need to handle the controls in code which works just as you would expect if you are used to WinForms. You can actually access WinForms from within WPF application _exactly_ as you do in your normal WinForms app. Just be careful what namespaces you include so you don't confuse your compiler. ;)

One thing I love is the ease of modifying controls. You can put a style on it, or completely remake a control just by using templates. This is how I made those playback buttons which were supposed to look somewhat like the buttons in Windows Explorer (in fact I have tried to mimic Explorer pretty much). However, when it's easy to style your app, some people/corporations will abuse that ability and create computer-vomit, but that's life. ;)

I used Glade before when doing GTK+ apps, which I enjoyed, so WPF with XAML felt natural for me.

However, I love the Qt toolkit and how easy and powerful it is. When I port my app to Linux I hope to be able to do a Qt and a GTK+ version (because integration is extremely important IMO), so I hope that WPF can give me that separation that I need as well.

Oops! This seems to have gotten out of hand. I should've stayed on topic... *flees*

Edited 2010-10-30 04:39 UTC

Reply Parent Score: 2