<?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/"
		>
<channel>
	<title>Comments for Thoughts On Eclipse UI</title>
	<atom:link href="http://eclipseblog.ostroukhovs.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://eclipseblog.ostroukhovs.com</link>
	<description>Useful bits of code</description>
	<lastBuildDate>Sun, 11 Dec 2011 01:04:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on Release names by Zeshylandon</title>
		<link>http://eclipseblog.ostroukhovs.com/2009/11/17/release-names/comment-page-1/#comment-2325</link>
		<dc:creator>Zeshylandon</dc:creator>
		<pubDate>Sun, 11 Dec 2011 01:04:01 +0000</pubDate>
		<guid isPermaLink="false">http://eclipseblog.ostroukhovs.com/?p=94#comment-2325</guid>
		<description>click  suprisely   online</description>
		<content:encoded><![CDATA[<p>click  suprisely   online</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using expressions in your extension points by Eugene Ostroukhov</title>
		<link>http://eclipseblog.ostroukhovs.com/2010/09/07/using-expressions-in-your-extension-points/comment-page-1/#comment-2314</link>
		<dc:creator>Eugene Ostroukhov</dc:creator>
		<pubDate>Mon, 19 Sep 2011 00:00:18 +0000</pubDate>
		<guid isPermaLink="false">http://eclipseblog.ostroukhovs.com/?p=200#comment-2314</guid>
		<description>Please make sure you have &quot;&lt;include schemaLocation=&quot;schema://org.eclipse.core.expressions/schema/expressionLanguage.exsd&quot;/&gt;&quot; in your extension point schema (exsd) file.</description>
		<content:encoded><![CDATA[<p>Please make sure you have &#8220;&lt;include schemaLocation=&#8221;schema://org.eclipse.core.expressions/schema/expressionLanguage.exsd&#8221;/&gt;&#8221; in your extension point schema (exsd) file.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using expressions in your extension points by antkei</title>
		<link>http://eclipseblog.ostroukhovs.com/2010/09/07/using-expressions-in-your-extension-points/comment-page-1/#comment-2312</link>
		<dc:creator>antkei</dc:creator>
		<pubDate>Thu, 15 Sep 2011 01:11:40 +0000</pubDate>
		<guid isPermaLink="false">http://eclipseblog.ostroukhovs.com/?p=200#comment-2312</guid>
		<description>I have compile error:

Referenced element &#039;enablement&#039; is not defined

at line:

 

Did I missed anything? Thanks.</description>
		<content:encoded><![CDATA[<p>I have compile error:</p>
<p>Referenced element &#8216;enablement&#8217; is not defined</p>
<p>at line:</p>
<p>Did I missed anything? Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Qt is not only styling&#8230; by Left</title>
		<link>http://eclipseblog.ostroukhovs.com/2010/09/22/qt-is-not-only-styling/comment-page-1/#comment-2270</link>
		<dc:creator>Left</dc:creator>
		<pubDate>Thu, 26 May 2011 12:33:14 +0000</pubDate>
		<guid isPermaLink="false">http://eclipseblog.ostroukhovs.com/?p=213#comment-2270</guid>
		<description>Я такую же штуку бросил примерно через пару недель разработки - для того чтобы довести это до ума пришлось бы делать похаченую версию как QT так и SWT, причём хаки должны были быть разными под разные платформы. Вообщем, AWT/SWT бридж показался бы верхом стабильности по сравнению с тем что должно было получиться.</description>
		<content:encoded><![CDATA[<p>Я такую же штуку бросил примерно через пару недель разработки &#8211; для того чтобы довести это до ума пришлось бы делать похаченую версию как QT так и SWT, причём хаки должны были быть разными под разные платформы. Вообщем, AWT/SWT бридж показался бы верхом стабильности по сравнению с тем что должно было получиться.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Qt is not only styling&#8230; by Eugene Ostroukhov</title>
		<link>http://eclipseblog.ostroukhovs.com/2010/09/22/qt-is-not-only-styling/comment-page-1/#comment-1678</link>
		<dc:creator>Eugene Ostroukhov</dc:creator>
		<pubDate>Thu, 23 Sep 2010 14:14:17 +0000</pubDate>
		<guid isPermaLink="false">http://eclipseblog.ostroukhovs.com/?p=213#comment-1678</guid>
		<description>I would like to link statically to make distribution easier and to reduce size. I&#039;m afraid I will not be able to avoid LGPL as I use http://qt.nokia.com/products/appdev/add-on-products/catalog/4/Windows/qtwinmigrate/ to embed QWidgets into SWT/win32.

I would be glad to join forces and I am pushing hard to make the code available ASAP.</description>
		<content:encoded><![CDATA[<p>I would like to link statically to make distribution easier and to reduce size. I&#8217;m afraid I will not be able to avoid LGPL as I use <a href="http://qt.nokia.com/products/appdev/add-on-products/catalog/4/Windows/qtwinmigrate/" rel="nofollow">http://qt.nokia.com/products/appdev/add-on-products/catalog/4/Windows/qtwinmigrate/</a> to embed QWidgets into SWT/win32.</p>
<p>I would be glad to join forces and I am pushing hard to make the code available ASAP.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Qt is not only styling&#8230; by Tom Schindl</title>
		<link>http://eclipseblog.ostroukhovs.com/2010/09/22/qt-is-not-only-styling/comment-page-1/#comment-1669</link>
		<dc:creator>Tom Schindl</dc:creator>
		<pubDate>Thu, 23 Sep 2010 07:45:36 +0000</pubDate>
		<guid isPermaLink="false">http://eclipseblog.ostroukhovs.com/?p=213#comment-1669</guid>
		<description>Why linking statically - I&#039;ve you&#039;d link dynamically you could release under EPL and LGPL, not? I&#039;ve been experimenting my own yesterday while traveling and implement a QtJambi free Java-Qt port (well as a start I wrote a wrapper for QPushButton) seems easier than I thought (I don&#039;t want the advanced features like Subclassing in Java and most important I don&#039;t want to rely on Java-Garbage-Collector).

Maybe we should join forces but for me being able to release the code under EPL to make it hostable on Eclipse is a must!</description>
		<content:encoded><![CDATA[<p>Why linking statically &#8211; I&#8217;ve you&#8217;d link dynamically you could release under EPL and LGPL, not? I&#8217;ve been experimenting my own yesterday while traveling and implement a QtJambi free Java-Qt port (well as a start I wrote a wrapper for QPushButton) seems easier than I thought (I don&#8217;t want the advanced features like Subclassing in Java and most important I don&#8217;t want to rely on Java-Garbage-Collector).</p>
<p>Maybe we should join forces but for me being able to release the code under EPL to make it hostable on Eclipse is a must!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Tools for Mobile Web by A Qt QML/3D Demo and Tutorial - Behold the Monkey God &#124; Tutorialicious.info</title>
		<link>http://eclipseblog.ostroukhovs.com/2010/07/27/tools-for-mobile-web/comment-page-1/#comment-1094</link>
		<dc:creator>A Qt QML/3D Demo and Tutorial - Behold the Monkey God &#124; Tutorialicious.info</dc:creator>
		<pubDate>Fri, 13 Aug 2010 22:40:00 +0000</pubDate>
		<guid isPermaLink="false">http://eclipseblog.ostroukhovs.com/?p=176#comment-1094</guid>
		<description>[...] Tools for Mobile Web [...]</description>
		<content:encoded><![CDATA[<p>[...] Tools for Mobile Web [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using Jetty as an OSGi HTTP Service by Lars Vogel</title>
		<link>http://eclipseblog.ostroukhovs.com/2010/05/19/using-jetty-as-an-osgi-http-service/comment-page-1/#comment-903</link>
		<dc:creator>Lars Vogel</dc:creator>
		<pubDate>Sat, 22 May 2010 05:58:53 +0000</pubDate>
		<guid isPermaLink="false">http://eclipseblog.ostroukhovs.com/?p=147#comment-903</guid>
		<description>I believed I once heard there as plans to use Jetty in the OSGi reference implementation to help support the servlet 3.0 standard in OSGi.</description>
		<content:encoded><![CDATA[<p>I believed I once heard there as plans to use Jetty in the OSGi reference implementation to help support the servlet 3.0 standard in OSGi.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using Jetty as an OSGi HTTP Service by Blog bookmarks 05/21/2010 &#171; My Diigo bookmarks</title>
		<link>http://eclipseblog.ostroukhovs.com/2010/05/19/using-jetty-as-an-osgi-http-service/comment-page-1/#comment-902</link>
		<dc:creator>Blog bookmarks 05/21/2010 &#171; My Diigo bookmarks</dc:creator>
		<pubDate>Fri, 21 May 2010 04:32:20 +0000</pubDate>
		<guid isPermaLink="false">http://eclipseblog.ostroukhovs.com/?p=147#comment-902</guid>
		<description>[...] Thoughts On Eclipse UI » Blog Archive » Using Jetty as an OSGi HTTP Service [...]</description>
		<content:encoded><![CDATA[<p>[...] Thoughts On Eclipse UI » Blog Archive » Using Jetty as an OSGi HTTP Service [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Same Button, Different Meaning by Eugene Ostroukhov</title>
		<link>http://eclipseblog.ostroukhovs.com/2009/08/27/same-button-different-meaning/comment-page-1/#comment-900</link>
		<dc:creator>Eugene Ostroukhov</dc:creator>
		<pubDate>Wed, 19 May 2010 21:12:49 +0000</pubDate>
		<guid isPermaLink="false">http://eclipseblog.ostroukhovs.com/?p=72#comment-900</guid>
		<description>I would not attempt to implement this. This is just too big of a task and it looks like Eclipse does not really need this change. Imagine that there are so many UI elements that rely on this interface - wizard dialog, workbench status bar, progress view, progress dialog, etc. You would have to make a change that spans through several Eclipse components.</description>
		<content:encoded><![CDATA[<p>I would not attempt to implement this. This is just too big of a task and it looks like Eclipse does not really need this change. Imagine that there are so many UI elements that rely on this interface &#8211; wizard dialog, workbench status bar, progress view, progress dialog, etc. You would have to make a change that spans through several Eclipse components.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

