<?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:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Using White To Test Kosmos GUI</title>
	<atom:link href="http://igorbrejc.net/development/testing/using-white-to-test-kosmos-gui/feed" rel="self" type="application/rss+xml" />
	<link>http://igorbrejc.net/development/testing/using-white-to-test-kosmos-gui</link>
	<description>Just another developer's weblog</description>
	<lastBuildDate>Thu, 19 Apr 2012 12:15:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: breki</title>
		<link>http://igorbrejc.net/development/testing/using-white-to-test-kosmos-gui/comment-page-1#comment-70307</link>
		<dc:creator>breki</dc:creator>
		<pubDate>Mon, 28 Dec 2009 15:55:42 +0000</pubDate>
		<guid isPermaLink="false">http://igorbrejc.net/uncategorized/using-white-to-test-kosmos-gui#comment-70307</guid>
		<description>&lt;p&gt;@adam,&lt;/p&gt;

&lt;p&gt;Thanks for the info. I actually did test it a long time ago on an openSUSE virt. image and, as you point out, it runs quite slowly. I suspect the biggest problem is Mono&#039;s implementation of GDI+ drawing engine. 
The good news is that I&#039;m in the process of rewriting the Kosmos drawing code and it will be much less reliant on GDI+ (there will be an alternative Cairo mode which I hope will run faster on Mono). So I hope Kosmos v3 will be more portable. Also, I&#039;ve become an (almost) regular user of Linux now, so it will be easier for me to support Kosmos on Linux.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@adam,</p>

<p>Thanks for the info. I actually did test it a long time ago on an openSUSE virt. image and, as you point out, it runs quite slowly. I suspect the biggest problem is Mono&#8217;s implementation of GDI+ drawing engine. 
The good news is that I&#8217;m in the process of rewriting the Kosmos drawing code and it will be much less reliant on GDI+ (there will be an alternative Cairo mode which I hope will run faster on Mono). So I hope Kosmos v3 will be more portable. Also, I&#8217;ve become an (almost) regular user of Linux now, so it will be easier for me to support Kosmos on Linux.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: adam</title>
		<link>http://igorbrejc.net/development/testing/using-white-to-test-kosmos-gui/comment-page-1#comment-70242</link>
		<dc:creator>adam</dc:creator>
		<pubDate>Sun, 27 Dec 2009 22:02:26 +0000</pubDate>
		<guid isPermaLink="false">http://igorbrejc.net/uncategorized/using-white-to-test-kosmos-gui#comment-70242</guid>
		<description>&lt;p&gt;I installed openSUSE on VMWare Player and did a quick test of Kosmos.Gui 
on it. It actually runs without any additional code changes. It does 
sometimes break down on the &quot;Open file&quot; dialog however, but this looks 
like a bug in Mono.
Kosmos.Gui runs quite slowly on my VM, especially on zoomed-in maps when 
it has to draw street names.
Anyway, test it if you want on your Linux machines and let me know about 
your experience.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I installed openSUSE on VMWare Player and did a quick test of Kosmos.Gui 
on it. It actually runs without any additional code changes. It does 
sometimes break down on the &#8220;Open file&#8221; dialog however, but this looks 
like a bug in Mono.
Kosmos.Gui runs quite slowly on my VM, especially on zoomed-in maps when 
it has to draw street names.
Anyway, test it if you want on your Linux machines and let me know about 
your experience.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: igorbrejc.net &#187; White Facade - Fluent Interface For Writing Tests Using White</title>
		<link>http://igorbrejc.net/development/testing/using-white-to-test-kosmos-gui/comment-page-1#comment-228</link>
		<dc:creator>igorbrejc.net &#187; White Facade - Fluent Interface For Writing Tests Using White</dc:creator>
		<pubDate>Mon, 21 Apr 2008 17:06:07 +0000</pubDate>
		<guid isPermaLink="false">http://igorbrejc.net/uncategorized/using-white-to-test-kosmos-gui#comment-228</guid>
		<description>&lt;p&gt;[...] few days ago I wrote about my first experiences in using White. I mentioned I wanted to create a facade around the White API in order to avoid constantly retyping [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] few days ago I wrote about my first experiences in using White. I mentioned I wanted to create a facade around the White API in order to avoid constantly retyping [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: breki</title>
		<link>http://igorbrejc.net/development/testing/using-white-to-test-kosmos-gui/comment-page-1#comment-220</link>
		<dc:creator>breki</dc:creator>
		<pubDate>Sat, 19 Apr 2008 19:18:05 +0000</pubDate>
		<guid isPermaLink="false">http://igorbrejc.net/uncategorized/using-white-to-test-kosmos-gui#comment-220</guid>
		<description>&lt;p&gt;Vivek,&lt;/p&gt;

&lt;p&gt;Thank you for the response. I&#039;ll be sure to check out the documentation in the source code.&lt;/p&gt;

&lt;p&gt;Regarding shortcuts, here&#039;s a simple code to parse WinForms-style shortcuts from the string into a System.Windows.Forms.Keys enumeration (although I suppose you would want something more general, not WinForms, for White):&lt;/p&gt;

&lt;p&gt;try
{
    KeysConverter converter = new KeysConverter ();
    Keys shortcutKeys = (Keys)converter.ConvertFromInvariantString (value);
}
catch (ArgumentException)
{
   throw new ArgumentException(String.Format (System.Globalization.CultureInfo.InvariantCulture, &quot;Illegal hotkey &#039;{0}&#039;.&quot;, value));
}&lt;/p&gt;

&lt;p&gt;Looking forward to the next release of White. And keep up the good work!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Vivek,</p>

<p>Thank you for the response. I&#8217;ll be sure to check out the documentation in the source code.</p>

<p>Regarding shortcuts, here&#8217;s a simple code to parse WinForms-style shortcuts from the string into a System.Windows.Forms.Keys enumeration (although I suppose you would want something more general, not WinForms, for White):</p>

<p>try
{
    KeysConverter converter = new KeysConverter ();
    Keys shortcutKeys = (Keys)converter.ConvertFromInvariantString (value);
}
catch (ArgumentException)
{
   throw new ArgumentException(String.Format (System.Globalization.CultureInfo.InvariantCulture, &#8220;Illegal hotkey &#8216;{0}&#8217;.&#8221;, value));
}</p>

<p>Looking forward to the next release of White. And keep up the good work!</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Vivek Singh</title>
		<link>http://igorbrejc.net/development/testing/using-white-to-test-kosmos-gui/comment-page-1#comment-219</link>
		<dc:creator>Vivek Singh</dc:creator>
		<pubDate>Sat, 19 Apr 2008 19:08:55 +0000</pubDate>
		<guid isPermaLink="false">http://igorbrejc.net/uncategorized/using-white-to-test-kosmos-gui#comment-219</guid>
		<description>&lt;p&gt;I am sorry for your not so good experience. I am making sure the next release, NDoc is much better. As you said, there is lot more documentation in the source which for some reason didnt showup in the NDoc and I didn&#039;t check it. Yes, but the intention is not to leave it undocumented.
There is a release coming up next week. I would try to address some of your concerns.
Also if you face any issue you can raise it is IssueTracker or Discussion List.
I like your idea of Ctrl+O.
Regarding providing a wrapper, the release after next should answer something around this. It ready for use but I havent released it because it isnt documented completely yet.
Sorry again, but your ideas are welcome.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I am sorry for your not so good experience. I am making sure the next release, NDoc is much better. As you said, there is lot more documentation in the source which for some reason didnt showup in the NDoc and I didn&#8217;t check it. Yes, but the intention is not to leave it undocumented.
There is a release coming up next week. I would try to address some of your concerns.
Also if you face any issue you can raise it is IssueTracker or Discussion List.
I like your idea of Ctrl+O.
Regarding providing a wrapper, the release after next should answer something around this. It ready for use but I havent released it because it isnt documented completely yet.
Sorry again, but your ideas are welcome.</p>]]></content:encoded>
	</item>
</channel>
</rss>

