Linked by Thom Holwerda on Thu 22nd Dec 2005 07:43 UTC, submitted by jonsmirl
"The current Win32-based Windows UI graphics subsystem, found in Windows XP, has been around for nearly 20 years. It's aging and limited, and as a result, user interface development has been somewhat, well, constrained at best. The Windows Presentation Foundation, which is built on the .NET Framework, provides new techniques for developing applications, and makes better use of current hardware and technologies. In this article, we'll show you 10 of the most significant advances that make WPF superior to its Win32 forebears." In related news, here are shots of Vista server.
Thread beginning with comment 77323
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[7]: Yay, they discovered fire
by on Thu 22nd Dec 2005 21:50
in reply to "RE[6]: Yay, they discovered fire"
Member since:Do I need to spell out that having a layout engine allow to solve these in a way that also makes the developer's life easier ?
So what you meant to say was that a layout engine is just a tool that may help a developer with enhancing usability (or just help him fill the screen with a mass of incoherent widgets). And according to you this is the only feature being listed in the article that can help the developer when dealing with usability in an application. And this is somehow bad because other systems have had this tool for a while now. So the addition of this one feature to WPF means that it is hopelessly out of date and behind the times.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-07-06
You consider a layout engine to be a usability feature. You really are a Linux zealot, aren't you?
Fixed-size dialog are a usability problem.
Dialogs that can't resize properly to use a bigger font are a usability problem.
Dialogs that can't adapt their size properly to the length of translations into other languages are a usability problem.
Do I need to spell out that having a layout engine allow to solve these in a way that also makes the developer's life easier ?
I'm sorry to be upset to have to scroll horizontally most configuration dialogs trees when I'm using a french version of visual .net, and a million other similar annoyances.