|
|
Friday, March 16, 2007 - Posts
-
-
Siguiendo con el éxito de la Academia Latinoamericana de Seguridad Informática y la Academia Latinoamericana de Management , la gente de TechNet Latam ha comenzado el pre registro para el lanzamiento el próximo lunes de su nuevo programa de entrenamiento, la Academia Latinoamericana de Business Intelligence . Las tecnologías relacionadas con BI están teniendo un fuerte auge así que tanto Developers como IT Pros debemos estar preparados por si debemos implementar estas tecnologías en un futuro proyecto, a continuación les dejo el enlace para registrarse, el del webcasts de presentación y otros relacionados con el tema. Pre Registo a la Academia Latinoamericana de Business Intelligence Academia Latinoamericana de Business Intelligence; presentación y lanzamiento oficial Introducción a SQL Server 2005 Analysis Services El aspecto técnico de Datawarehousing en el mundo real – Parte 1 El aspecto técnico de Datawarehousing en el mundo real – Parte 2 El aspecto técnico de Datawarehousing en el Read More...
|
-
TextEffects is a poorly-documented property that allows you to apply an effect to a portion of text. It’s not the best of name for the property (at least in this first version of WPF), because the only “effects” supported in the current version are Clip, Foreground, and Transform.
There are four important things to know about [...] Read More...
|
-
After I posted my previous feasibility study on doing shadows in WPF 3D , I received helpful emails from Larry O'Brien and WPF 3D Blogger Jordan Parker , both of whom induced me to think of the problem in another way. Thank you! I am happy to report that this morning I implemented an approach I'm quite happy with. The "chopper" is animated, of course. Besides actually having good performance without jaggies on the shadow, what makes this especially cool is that it happens to be an all-XAML solution: ShadowsFeasibilityStudy2.xaml This comes under the category of "putting the API to work." Basically, the cyan "ground" or "floor" is covered by a second material which is based on a VisualBrush , the visual being basically another Viewport3D that views the figures from the perspective of the DirectionalLight . This brush is the shadows. This is certainly not a generalized scheme for 3D shadows. First, the scene must be divided into figures that throw shadows and figures that display shadows. Read More...
|
-
The April 2007 issue of MSDN Magazine is online now, so if you're one of those rare programmers who don't subscribe to the print edition, you can now check out my article on strategies for developing WPF 3D triangle meshes . In each of my WPF articles for MSDN Magazine I've been trying to create at least one program that does something visually I've never seen before, and which causes me to giggle in delight. In this article, that would be the ImageOnCylinder program, which wraps a photo of my head around a cylinder and then animates the lenth of the cylinder and the radii of the cylinder ends. Except for one standalone XAML file, all the sample code is part of one Visual Studio solution named MeshGeometries, which contains a DLL project used by the other four programs. Read More...
|
-
I've been nagging my friend Dave to set up a blog for ages, so now that he's finally got around to it , the least I can do is link to him. Dave is an author with APress. He's written two books on Hibernate. (Yes, Hibernate, not NHibernate - he's mostly a Java guy. With some occasional Forth.) These are Beginning Hibernate and Pro Hibernate 3 . He also wrote Building Portlets with the Java Portlet API , a book which inexplicably has a Foreword written by me. Dave's truly evil implementation of continuations for Java is a kind of car crash for language geeks, and shows a combination of technical insight and a twisted sense of humour that I confidently expect to become a theme. Either that or he'll get bored of it in 2 months and stop posting entirely. Dave's blog is here , and his RSS feed is here . Read More...
|
-
-
Developers new to WPF are sometimes a little confused when the Width and Height properties of elements report as ‘NaN’ (Not a Number) in code, when these very same elements are clearly visible and do have a width and height. What’s going on? The short answer is you can interpret ‘NaN’ to mean “not set”. The Width and Height properties of Buttons, TextBoxes and most other controls are inherited from the FrameworkElement superclass. These normal .NET properties in turn backs on to a DependencyProperty (the WidthProperty in the case of Width) that has been registered for FrameworkElement in the class constructor with a default value of ‘NaN’. Until you set that WidthProperty to something, or set the Width .NET property in code or Xaml the Width will stay as ‘NaN’. If you wish to know what the on-screen size for an object is you should instead consult the ActualWidth and ActualHeight properties, which always reflects the actual width and height of the object on screen. These properties are Read More...
|
|
|
|