<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>fortes.com - Latest Comments in Creating WPF Text Layouts is Hard</title><link>http://fortes.disqus.com/</link><description></description><atom:link href="https://fortes.disqus.com/creating_wpf_text_layouts_is_hard/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Thu, 29 Mar 2007 11:40:58 -0000</lastBuildDate><item><title>Re: Creating WPF Text Layouts is Hard</title><link>http://fortes.com/2007/03/creating-wpf-text-layouts-is-hard/#comment-1208162</link><description>&lt;p&gt;Tanveer -- You're absolutely correct, Reflector is indispensible (especially with the BAML Viewer add-in). However, many designers (Blend users) don't use the tool. Also, real WPF apps can be hard to understand due to all the indirection and abstraction that happens through templating and styling, although AJAX-based websites also have much greater complexity than the old days of HTML 1.0 :)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Fortes</dc:creator><pubDate>Thu, 29 Mar 2007 11:40:58 -0000</pubDate></item><item><title>Re: Creating WPF Text Layouts is Hard</title><link>http://fortes.com/2007/03/creating-wpf-text-layouts-is-hard/#comment-1208161</link><description>&lt;p&gt;Every programmer worth his/her salt has a copy of .Net reflector somewhere close. It is way better than having a peek by "View source".&lt;/p&gt;&lt;p&gt;In case someone points out about an xbap, you only have to search in your application data and local settings\application directories to find the assemblies for an xbap application.&lt;/p&gt;&lt;p&gt;Most people don't do any kind of obfuscation on their code and it is still possible to guess something from obfuscated code.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tanveer Badar</dc:creator><pubDate>Thu, 29 Mar 2007 02:22:07 -0000</pubDate></item></channel></rss>