<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Selenium UI-Element Locator</title>
	<link>http://ttwhy.org/home/blog/2007/05/12/selenium-ui-element-locator/</link>
	<description>from the seeds of gyrm</description>
	<pubDate>Thu, 04 Dec 2008 03:20:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3</generator>
		<item>
		<title>By: chinese characters support</title>
		<link>http://ttwhy.org/home/blog/2007/05/12/selenium-ui-element-locator/#comment-8560</link>
		<dc:creator>chinese characters support</dc:creator>
		<pubDate>Tue, 11 Nov 2008 01:12:16 +0000</pubDate>
		<guid>http://ttwhy.org/home/blog/2007/05/12/selenium-ui-element-locator/#comment-8560</guid>
		<description>hi,i only use gbk unicode to have a transfer.The good thing is that it can support directly input in javascript.
Thanks</description>
		<content:encoded><![CDATA[<p>hi,i only use gbk unicode to have a transfer.The good thing is that it can support directly input in javascript.<br />
Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gyrm</title>
		<link>http://ttwhy.org/home/blog/2007/05/12/selenium-ui-element-locator/#comment-8559</link>
		<dc:creator>gyrm</dc:creator>
		<pubDate>Mon, 10 Nov 2008 16:03:23 +0000</pubDate>
		<guid>http://ttwhy.org/home/blog/2007/05/12/selenium-ui-element-locator/#comment-8559</guid>
		<description>@chinese characters support:

Very good question! I'll have to look into this. I've never used multibyte characters directly in javascript files, so I'm not sure exactly how it works.</description>
		<content:encoded><![CDATA[<p>@chinese characters support:</p>
<p>Very good question! I&#8217;ll have to look into this. I&#8217;ve never used multibyte characters directly in javascript files, so I&#8217;m not sure exactly how it works.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chinese characters support</title>
		<link>http://ttwhy.org/home/blog/2007/05/12/selenium-ui-element-locator/#comment-8558</link>
		<dc:creator>chinese characters support</dc:creator>
		<pubDate>Mon, 10 Nov 2008 08:28:37 +0000</pubDate>
		<guid>http://ttwhy.org/home/blog/2007/05/12/selenium-ui-element-locator/#comment-8558</guid>
		<description>hi,
thanks for your hard work.
but I have one problem is that I could not use Chinese characters in ui-element.js
when i locator one element using chinese ui link,but I could not write the Chinse characters into ui-element.js.It show irrecognizable.
How to do it?</description>
		<content:encoded><![CDATA[<p>hi,<br />
thanks for your hard work.<br />
but I have one problem is that I could not use Chinese characters in ui-element.js<br />
when i locator one element using chinese ui link,but I could not write the Chinse characters into ui-element.js.It show irrecognizable.<br />
How to do it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gyrm</title>
		<link>http://ttwhy.org/home/blog/2007/05/12/selenium-ui-element-locator/#comment-8547</link>
		<dc:creator>gyrm</dc:creator>
		<pubDate>Sat, 27 Sep 2008 03:48:10 +0000</pubDate>
		<guid>http://ttwhy.org/home/blog/2007/05/12/selenium-ui-element-locator/#comment-8547</guid>
		<description>@Todd: I'm not sure what you mean by "rebuilding the extension every time" - do you mean when preparing them for use by the RC? You could use the technique described here to &lt;a href="http://ttwhy.org/home/blog/2008/05/14/selenium-rc-per-session-extension-javascript/" rel="nofollow"&gt;specify per-session javascript&lt;/a&gt;.

I've had similar ideas for making it easier to construct a map file - here's a &lt;a href="http://docs.google.com/View?docid=dhjhrf9w_7cqq3xz" rel="nofollow"&gt;dump of some earlier thoughts on the subject&lt;/a&gt;. Would definitely be useful, but I haven't had a chance to invest any effort into it. I think it would make sense to add as a feature of the Selenium IDE.

A similar effort called &lt;a href="http://code.google.com/p/fireelement/" rel="nofollow"&gt;fireelement&lt;/a&gt; is staged on Google Code (just stumbled across this today), but I'm not sure where the author intends to go with it.</description>
		<content:encoded><![CDATA[<p>@Todd: I&#8217;m not sure what you mean by &#8220;rebuilding the extension every time&#8221; - do you mean when preparing them for use by the RC? You could use the technique described here to <a href="http://ttwhy.org/home/blog/2008/05/14/selenium-rc-per-session-extension-javascript/" rel="nofollow">specify per-session javascript</a>.</p>
<p>I&#8217;ve had similar ideas for making it easier to construct a map file - here&#8217;s a <a href="http://docs.google.com/View?docid=dhjhrf9w_7cqq3xz" rel="nofollow">dump of some earlier thoughts on the subject</a>. Would definitely be useful, but I haven&#8217;t had a chance to invest any effort into it. I think it would make sense to add as a feature of the Selenium IDE.</p>
<p>A similar effort called <a href="http://code.google.com/p/fireelement/" rel="nofollow">fireelement</a> is staged on Google Code (just stumbled across this today), but I&#8217;m not sure where the author intends to go with it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Todd Andrew</title>
		<link>http://ttwhy.org/home/blog/2007/05/12/selenium-ui-element-locator/#comment-8546</link>
		<dc:creator>Todd Andrew</dc:creator>
		<pubDate>Fri, 26 Sep 2008 13:45:34 +0000</pubDate>
		<guid>http://ttwhy.org/home/blog/2007/05/12/selenium-ui-element-locator/#comment-8546</guid>
		<description>Thanks for making UI-Element.  It makes my life much easier.  Are there any future enhancements planned?  One of the things that I did was to export the Pageset definitions to an XML file so that I could update them without rebuilding the extension every time.  I was thinking that an extension of this idea could be to have a page recording utility that would create an XML file that contains the objects on a page.  Once the page is recorded, a developer could then go in and remove undesired objects and do some reorganization.  If it was done well, it would really take UI-Element to the next level.</description>
		<content:encoded><![CDATA[<p>Thanks for making UI-Element.  It makes my life much easier.  Are there any future enhancements planned?  One of the things that I did was to export the Pageset definitions to an XML file so that I could update them without rebuilding the extension every time.  I was thinking that an extension of this idea could be to have a page recording utility that would create an XML file that contains the objects on a page.  Once the page is recorded, a developer could then go in and remove undesired objects and do some reorganization.  If it was done well, it would really take UI-Element to the next level.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
