<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Finding a WDK Component to customize</title>
	<atom:link href="http://vermarohit.wordpress.com/2009/01/14/finding-a-wdk-component-to-customize/feed/" rel="self" type="application/rss+xml" />
	<link>http://vermarohit.wordpress.com/2009/01/14/finding-a-wdk-component-to-customize/</link>
	<description>Just another WordPress.com weblog</description>
	<lastBuildDate>Thu, 05 Feb 2009 16:23:43 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: vermarohit</title>
		<link>http://vermarohit.wordpress.com/2009/01/14/finding-a-wdk-component-to-customize/#comment-4</link>
		<dc:creator>vermarohit</dc:creator>
		<pubDate>Thu, 05 Feb 2009 16:23:43 +0000</pubDate>
		<guid isPermaLink="false">http://vermarohit.wordpress.com/?p=7#comment-4</guid>
		<description>Deepak 

You are right that DOM is more useful for tracking CSS and images. Other very easy way for finding the components is  to configure iTrace tool available on EMC developer network.


Thanks

</description>
		<content:encoded><![CDATA[<p>Deepak </p>
<p>You are right that DOM is more useful for tracking CSS and images. Other very easy way for finding the components is  to configure iTrace tool available on EMC developer network.</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deepak Apte</title>
		<link>http://vermarohit.wordpress.com/2009/01/14/finding-a-wdk-component-to-customize/#comment-3</link>
		<dc:creator>Deepak Apte</dc:creator>
		<pubDate>Thu, 05 Feb 2009 12:48:40 +0000</pubDate>
		<guid isPermaLink="false">http://vermarohit.wordpress.com/?p=7#comment-3</guid>
		<description>lotsa typo there!! 
what i meant was ....
Thought the way you suggest is ok, normally we trace the component details by turning WDK tracing on for the session and checking the FORM related traces, you get the component details in the html source.</description>
		<content:encoded><![CDATA[<p>lotsa typo there!!<br />
what i meant was &#8230;.<br />
Thought the way you suggest is ok, normally we trace the component details by turning WDK tracing on for the session and checking the FORM related traces, you get the component details in the html source.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deepak Apte</title>
		<link>http://vermarohit.wordpress.com/2009/01/14/finding-a-wdk-component-to-customize/#comment-2</link>
		<dc:creator>Deepak Apte</dc:creator>
		<pubDate>Thu, 05 Feb 2009 12:45:51 +0000</pubDate>
		<guid isPermaLink="false">http://vermarohit.wordpress.com/?p=7#comment-2</guid>
		<description>Hello Rohit,
Thought the way you suggest is ok, normally trace the component details but turn WDK tracing on for the seesion and checking the FORM related traces, you get the component details in the html source.

I think the Document (DOM) Inspector available in Firefox is more useful for tracking the css and images, It really is very useful for WDK Theme customization.</description>
		<content:encoded><![CDATA[<p>Hello Rohit,<br />
Thought the way you suggest is ok, normally trace the component details but turn WDK tracing on for the seesion and checking the FORM related traces, you get the component details in the html source.</p>
<p>I think the Document (DOM) Inspector available in Firefox is more useful for tracking the css and images, It really is very useful for WDK Theme customization.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
