Any Developer working in the XAML Environment must have stumbled across Microsoft Blend, a.k.a. Expression Blend at some time. Blend is a Software aimed to support developers and designers of XAML based UIs create designs and animations, apply behaviors and so forth. As of 2010 (talking VS Versions), Microsoft has made the licensing of Blend a real mess, if you're a WPF Developer: The only way to purchase Blend is buying the entire Expression Studio Ultimate for somewhere around 500 Euros. Smaller development teams are made to bleed unnecessarily, since the VS 2010 XAML editor had serious issues before SP1. We're talking 2012 now - seems MS have learned their lesson: Blend is free for Windows 8 Store Apps and comes along with the correlating Visual Studio Express Edition. But what about WPF or the already zombified Silverlight? Good news first: Blend will continue to support WPF. But what are the licensing terms? Looking things up on the Blend Insider Blog , I fo...
HLSL is mature language that enables developers to address the graphics hardware in a familiar, C-like way. Next to vertex shaders, you can use it to write pixel shaders, which is what - with .Net version 3.5 SP1 - Microsoft introduced into WPF. What sounds like no big deal at first sight is a major leap towards serius WPF / Silverlight game development and - more generally - graphically intensive UI. That goes hand in hand with the DirectX-powered concepts of WPF, finally giving .net developers a good deal of acceleration without the need for unsafe code. Since we're not doing heavy calculus on our GPU, even decent hardware is sufficient to display manipulated images. Since the death sentence of XNA , hopes were shallow that .Net developers get in touch with this cool technology, but we've always loved the walking dead, haven't we? Quite a few WPF Pixel Shader libraries and tutorials have popped up (Some are linked below), and I really recommend getting in touch with the...
WPF has a lot of advantages, it's perfectly sane data binding mechanism being one of the most outstanding ones.On the flipside, many people (meaning companies, mostly) have refused to switch from WinForms to WPF because of the "blurry" looks of applications written in WPF.
This blurryness goes back to two mechanisms:
1)Text Smoothing
Instead of relying on the system's ClearType mechanism, WPF does it's own thing-a-magic, which is blatantly inferior to the aforesaid. In fact, WPF smoothed fonts are a definite way to headaches, if read for some time.
Note : The image is from a website that compares various Microsoft.Net Font-Smoothing implementations.
They might be useful to integrate text in images, though.For business applications (displaying data grids etc.) this is a K.O. criterion. Nobody wants to have to take their glasses off in order to achieve readability, and nobody wants their software deployed along with a pack of aspirins.
2)SubPix...
Kommentare
Kommentar veröffentlichen