<?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 on: Why preventing Qt4.5 to work fine with KDE4.2 is bad !</title>
	<atom:link href="http://blog.cberger.net/2009/02/09/why-preventing-qt4-5-to-work-fine-with-kde4-2-is-bad/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.cberger.net/2009/02/09/why-preventing-qt4-5-to-work-fine-with-kde4-2-is-bad/</link>
	<description>What I do, where I live, what I think.</description>
	<lastBuildDate>Wed, 16 Jun 2010 13:53:02 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Cyrille Berger</title>
		<link>http://blog.cberger.net/2009/02/09/why-preventing-qt4-5-to-work-fine-with-kde4-2-is-bad/comment-page-1/#comment-225</link>
		<dc:creator>Cyrille Berger</dc:creator>
		<pubDate>Thu, 12 Feb 2009 09:30:00 +0000</pubDate>
		<guid isPermaLink="false">http://cyrilleberger.wordpress.com/2009/02/09/why-preventing-qt4-5-to-work-fine-with-kde4-2-is-bad#comment-225</guid>
		<description>@KAMiKAZOW and Kevin&lt;/&gt;What decide KOffice 2.0 schedule is 2.0 stability.&lt;/&gt;Delaying 2.0 to wait for plasma 4.3 would be silly, since plasma isn&#039;t a dependency of KOffice, nothing prevent you to use KOffice without plasma, while the main userbase of KOffice is KDE users, and it will stay that way for a while, we already have people who test KOffice and use gnome, windows or Mac OSX, those people don&#039;t care about plasma and wether plasma works with 4.5, and among KDE users, there are some people who care more about applications than a few glitches in plasma.&lt;/&gt;An other point to consider is that delaying KOffice to wait for KDE4.3 won&#039;t necesseraly make it better, since when it reaches a reasonnable stable state (the one we would have used to release 2.0), we would probably want to start working on the 2.1 branch, while the 2.0 branch would be left to wait for at least three monthes.&lt;/&gt;And we all hope, in the KOffice community that the release will have a significant impact on our moral (3 years of development without stable release, and more than a year of stabilization has a negative impact on that) and on the visibility of the project, which is also why we want the release sooner than latter.</description>
		<content:encoded><![CDATA[<p>@KAMiKAZOW and KevinWhat decide KOffice 2.0 schedule is 2.0 stability.Delaying 2.0 to wait for plasma 4.3 would be silly, since plasma isn&#8217;t a dependency of KOffice, nothing prevent you to use KOffice without plasma, while the main userbase of KOffice is KDE users, and it will stay that way for a while, we already have people who test KOffice and use gnome, windows or Mac OSX, those people don&#8217;t care about plasma and wether plasma works with 4.5, and among KDE users, there are some people who care more about applications than a few glitches in plasma.An other point to consider is that delaying KOffice to wait for KDE4.3 won&#8217;t necesseraly make it better, since when it reaches a reasonnable stable state (the one we would have used to release 2.0), we would probably want to start working on the 2.1 branch, while the 2.0 branch would be left to wait for at least three monthes.And we all hope, in the KOffice community that the release will have a significant impact on our moral (3 years of development without stable release, and more than a year of stabilization has a negative impact on that) and on the visibility of the project, which is also why we want the release sooner than latter.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Kofler</title>
		<link>http://blog.cberger.net/2009/02/09/why-preventing-qt4-5-to-work-fine-with-kde4-2-is-bad/comment-page-1/#comment-224</link>
		<dc:creator>Kevin Kofler</dc:creator>
		<pubDate>Thu, 12 Feb 2009 02:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://cyrilleberger.wordpress.com/2009/02/09/why-preventing-qt4-5-to-work-fine-with-kde4-2-is-bad#comment-224</guid>
		<description>Unless something really bad happens, Fedora 11 &lt;&gt;will&lt;&gt; ship with Qt 4.5. We will import it into Rawhide soon, so we will be delivering the testing some folks (e.g. Aaron) are asking for. Hopefully we can get the kinks sorted out. Most likely it&#039;ll also hit Fedora 10 and possibly 9 updates before KDE 4.3, maybe even before the Fedora 11 release.&lt;/&gt;&lt;/&gt;And to us, it matters very much when KOffice 2 releases, because we want to ship Fedora 11 with KOffice 2. In fact, Rawhide already has the prereleases. (We even wanted to ship KOffice 2 in Fedora 10, but had to revert to 1.4.) So I hope the KOffice team won&#039;t get pressured into delaying their release.&lt;/&gt;&lt;/&gt;FWIW, I also wouldn&#039;t complain if a later 4.2.x release started requiring Qt 4.5, as long as it fixes the issues with 4.5. We can just push out 4.5 as an update to earlier Fedora releases.</description>
		<content:encoded><![CDATA[<p>Unless something really bad happens, Fedora 11 <>will<> ship with Qt 4.5. We will import it into Rawhide soon, so we will be delivering the testing some folks (e.g. Aaron) are asking for. Hopefully we can get the kinks sorted out. Most likely it&#8217;ll also hit Fedora 10 and possibly 9 updates before KDE 4.3, maybe even before the Fedora 11 release.And to us, it matters very much when KOffice 2 releases, because we want to ship Fedora 11 with KOffice 2. In fact, Rawhide already has the prereleases. (We even wanted to ship KOffice 2 in Fedora 10, but had to revert to 1.4.) So I hope the KOffice team won&#8217;t get pressured into delaying their release.FWIW, I also wouldn&#8217;t complain if a later 4.2.x release started requiring Qt 4.5, as long as it fixes the issues with 4.5. We can just push out 4.5 as an update to earlier Fedora releases.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pan, Shi Zhu</title>
		<link>http://blog.cberger.net/2009/02/09/why-preventing-qt4-5-to-work-fine-with-kde4-2-is-bad/comment-page-1/#comment-223</link>
		<dc:creator>Pan, Shi Zhu</dc:creator>
		<pubDate>Wed, 11 Feb 2009 03:56:00 +0000</pubDate>
		<guid isPermaLink="false">http://cyrilleberger.wordpress.com/2009/02/09/why-preventing-qt4-5-to-work-fine-with-kde4-2-is-bad#comment-223</guid>
		<description>I think the situation is quite clear: Plasma team is in short of human resources and had to focus on KDE 4.3. &lt;/&gt;&lt;/&gt;If distributions want to ship KDE 4.2 with Qt 4.5 they should fix the problems in KDE 4.2 where incompatible with Qt 4.5.&lt;/&gt;&lt;/&gt;No one is baring Qt 4.5, but Plasma team should focus on KDE4.3 so those who want Qt 4.5 with KDE4.2 should co-operate and try to fix the problems, which shouldn&#039;t be very hard and is encouraged.</description>
		<content:encoded><![CDATA[<p>I think the situation is quite clear: Plasma team is in short of human resources and had to focus on KDE 4.3. If distributions want to ship KDE 4.2 with Qt 4.5 they should fix the problems in KDE 4.2 where incompatible with Qt 4.5.No one is baring Qt 4.5, but Plasma team should focus on KDE4.3 so those who want Qt 4.5 with KDE4.2 should co-operate and try to fix the problems, which shouldn&#8217;t be very hard and is encouraged.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pinheiro</title>
		<link>http://blog.cberger.net/2009/02/09/why-preventing-qt4-5-to-work-fine-with-kde4-2-is-bad/comment-page-1/#comment-222</link>
		<dc:creator>Pinheiro</dc:creator>
		<pubDate>Wed, 11 Feb 2009 00:05:00 +0000</pubDate>
		<guid isPermaLink="false">http://cyrilleberger.wordpress.com/2009/02/09/why-preventing-qt4-5-to-work-fine-with-kde4-2-is-bad#comment-222</guid>
		<description>Just to say that Qt4.5 intruduced a problem that did not had in 4.4 it dosent do grouped alpha in svg, this is a important feature in kde and specialy in plasma....&lt;/&gt;Yes we can overcome this issue by redoing the themes, and probaly we will have to do so.&lt;/&gt;But the svg theme was ok and is rendered correctly in most svg renderes Qt4.4 actualy did a beter job at this specific joob.&lt;/&gt;&lt;/&gt;And if you want a correctly rendered plasma themes today you should not use Qt 4.5.&lt;/&gt;&lt;/&gt;Still thank you Qt the windows scale much faster now :) and im sure we can fix this bugs.</description>
		<content:encoded><![CDATA[<p>Just to say that Qt4.5 intruduced a problem that did not had in 4.4 it dosent do grouped alpha in svg, this is a important feature in kde and specialy in plasma&#8230;.Yes we can overcome this issue by redoing the themes, and probaly we will have to do so.But the svg theme was ok and is rendered correctly in most svg renderes Qt4.4 actualy did a beter job at this specific joob.And if you want a correctly rendered plasma themes today you should not use Qt 4.5.Still thank you Qt the windows scale much faster now <img src='http://blog.cberger.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  and im sure we can fix this bugs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fgunni</title>
		<link>http://blog.cberger.net/2009/02/09/why-preventing-qt4-5-to-work-fine-with-kde4-2-is-bad/comment-page-1/#comment-221</link>
		<dc:creator>fgunni</dc:creator>
		<pubDate>Tue, 10 Feb 2009 21:07:00 +0000</pubDate>
		<guid isPermaLink="false">http://cyrilleberger.wordpress.com/2009/02/09/why-preventing-qt4-5-to-work-fine-with-kde4-2-is-bad#comment-221</guid>
		<description>Just the view from a &quot;dumb&quot; user and KDE-Fan:&lt;/&gt;I hope there will be Qt 4.5 for KDE 4.2.x as i hope for more stability.&lt;/&gt;Currently, although i love KDE, there are so many bugs, crashes and more, that Qt 4.5 can hardly make it worse.</description>
		<content:encoded><![CDATA[<p>Just the view from a &#8220;dumb&#8221; user and KDE-Fan:I hope there will be Qt 4.5 for KDE 4.2.x as i hope for more stability.Currently, although i love KDE, there are so many bugs, crashes and more, that Qt 4.5 can hardly make it worse.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kristoffer</title>
		<link>http://blog.cberger.net/2009/02/09/why-preventing-qt4-5-to-work-fine-with-kde4-2-is-bad/comment-page-1/#comment-220</link>
		<dc:creator>Kristoffer</dc:creator>
		<pubDate>Tue, 10 Feb 2009 17:38:00 +0000</pubDate>
		<guid isPermaLink="false">http://cyrilleberger.wordpress.com/2009/02/09/why-preventing-qt4-5-to-work-fine-with-kde4-2-is-bad#comment-220</guid>
		<description>Statement: There is no problem. Kde 4.2 can be used with qt 4.5 with very little effort on the part of the devs, this is because the QT devs have been testing KDE 4.2 with qt 4.5 all along during their development schedule.&lt;/&gt;&lt;/&gt;see: http://labs.trolltech.com/blogs/2009/02/10/why-kde-42-should-use-qt-45/&lt;/&gt;&lt;/&gt;I am running kde 4.2 on qt 4.5, not even with qt-copy, and have /less/ bugs than I had with kde 4.2 on qt 4.4.3. According to the above this is also the case for others. So if distribution ship kde 4.2 with qt 4.5 they will see /less/ bugs, _even_ in current state. If kde devs/qt devs spend one day or two days actively fixing bugs in kde 4.2 pertaining to qt 4.5 they will get a very stable GUI!&lt;/&gt;&lt;/&gt;(relevant or not relevant: i deleted .kde4 and started afresh when i updated the qt version, don&#039;t know if it makes a difference)</description>
		<content:encoded><![CDATA[<p>Statement: There is no problem. Kde 4.2 can be used with qt 4.5 with very little effort on the part of the devs, this is because the QT devs have been testing KDE 4.2 with qt 4.5 all along during their development schedule.see: <a href="http://labs.trolltech.com/blogs/2009/02/10/why-kde-42-should-use-qt-45/" rel="nofollow">http://labs.trolltech.com/blogs/2009/02/10/why-kde-42-should-use-qt-45/</a>I am running kde 4.2 on qt 4.5, not even with qt-copy, and have /less/ bugs than I had with kde 4.2 on qt 4.4.3. According to the above this is also the case for others. So if distribution ship kde 4.2 with qt 4.5 they will see /less/ bugs, _even_ in current state. If kde devs/qt devs spend one day or two days actively fixing bugs in kde 4.2 pertaining to qt 4.5 they will get a very stable GUI!(relevant or not relevant: i deleted .kde4 and started afresh when i updated the qt version, don&#8217;t know if it makes a difference)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jake Sallee</title>
		<link>http://blog.cberger.net/2009/02/09/why-preventing-qt4-5-to-work-fine-with-kde4-2-is-bad/comment-page-1/#comment-219</link>
		<dc:creator>Jake Sallee</dc:creator>
		<pubDate>Tue, 10 Feb 2009 16:45:00 +0000</pubDate>
		<guid isPermaLink="false">http://cyrilleberger.wordpress.com/2009/02/09/why-preventing-qt4-5-to-work-fine-with-kde4-2-is-bad#comment-219</guid>
		<description>Yet another reason why KOffice, Plasma, KDE, and major KDE projects should align their release schedules.&lt;/&gt;&lt;/&gt;It&#039;s not that hard people.  Schedule.  Communicate.&lt;/&gt;&lt;/&gt;&quot;Assuming&quot; that the &quot;plasma devs&quot; are going to have everything worked out of plasma so everyone can write programs with Qt4.5 (release candidate) is not a good practice.&lt;/&gt;&lt;/&gt;&quot;If the Plasma team did not discuss this with other teams, I think that holding their position is untenable from the point of view that they bar progress in other parts of KDE.&quot;&lt;/&gt;&lt;/&gt;In that same thought, why couldn&#039;t the &quot;other teams&quot; communicate with the plasma devs?&lt;/&gt;&lt;/&gt;Sorry, but the plasma devs are held more responsible for things not working than most other KDE teams.  I don&#039;t necessarily think that the Plasma team should be held responsible for fixing plasma to work with Qt4.5 which has been in beta and RC form for quite some time.</description>
		<content:encoded><![CDATA[<p>Yet another reason why KOffice, Plasma, KDE, and major KDE projects should align their release schedules.It&#8217;s not that hard people.  Schedule.  Communicate.&#8220;Assuming&#8221; that the &#8220;plasma devs&#8221; are going to have everything worked out of plasma so everyone can write programs with Qt4.5 (release candidate) is not a good practice.&#8220;If the Plasma team did not discuss this with other teams, I think that holding their position is untenable from the point of view that they bar progress in other parts of KDE.&#8221;In that same thought, why couldn&#8217;t the &#8220;other teams&#8221; communicate with the plasma devs?Sorry, but the plasma devs are held more responsible for things not working than most other KDE teams.  I don&#8217;t necessarily think that the Plasma team should be held responsible for fixing plasma to work with Qt4.5 which has been in beta and RC form for quite some time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KAMiKAZOW</title>
		<link>http://blog.cberger.net/2009/02/09/why-preventing-qt4-5-to-work-fine-with-kde4-2-is-bad/comment-page-1/#comment-218</link>
		<dc:creator>KAMiKAZOW</dc:creator>
		<pubDate>Tue, 10 Feb 2009 11:53:00 +0000</pubDate>
		<guid isPermaLink="false">http://cyrilleberger.wordpress.com/2009/02/09/why-preventing-qt4-5-to-work-fine-with-kde4-2-is-bad#comment-218</guid>
		<description>OK, then I&#039;m positively surprised that you plan to release KOffice 2.0 before KDE 4.3. But when KOffice 2.0 relies on Qt 4.5 anyway, why don&#039;t you just postpone the KOffice release a bit to be simultaneously with KDE 4.3? It&#039;s in pre-release state for 1.5 years -- a few weeks later won&#039;t make any difference.</description>
		<content:encoded><![CDATA[<p>OK, then I&#8217;m positively surprised that you plan to release KOffice 2.0 before KDE 4.3. But when KOffice 2.0 relies on Qt 4.5 anyway, why don&#8217;t you just postpone the KOffice release a bit to be simultaneously with KDE 4.3? It&#8217;s in pre-release state for 1.5 years &#8212; a few weeks later won&#8217;t make any difference.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cyrille Berger</title>
		<link>http://blog.cberger.net/2009/02/09/why-preventing-qt4-5-to-work-fine-with-kde4-2-is-bad/comment-page-1/#comment-217</link>
		<dc:creator>Cyrille Berger</dc:creator>
		<pubDate>Tue, 10 Feb 2009 10:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://cyrilleberger.wordpress.com/2009/02/09/why-preventing-qt4-5-to-work-fine-with-kde4-2-is-bad#comment-217</guid>
		<description>@David, Shi Zhu&lt;/&gt;You are missing the point, I don&#039;t care that plasma use Qt4.5 or Qt4.4, but by preventing plasma to use Qt4.5, it&#039;s blocking the use of 4.5 by other projects. When KOffice 2.0 is released it&#039;s going to be dependent on 4.5, because 4.5 includes important bug/crash fixes. And whatever people like KAMiKAZOW think it&#039;s going to happen before 4.3. And KOffice 2.0 isn&#039;t the only project outside KDE4.2 that use Qt as a library, there are countless open source project that depend on it and might want to use Qt4.5 before KDE4.3 is out, which is going to become a problem if distributions can&#039;t ship Qt4.5.&lt;/&gt;&lt;/&gt;@jos, yes you are right, the issue is a difference of behavior from Qt4.4 to Qt4.5, this is something that happen on a regular basis, especially for newly introduced features. Yet, sebas mention hacks and workarounds, and if there is something to know about hacks and workarounds, they are always going to backfire on you.</description>
		<content:encoded><![CDATA[<p>@David, Shi ZhuYou are missing the point, I don&#8217;t care that plasma use Qt4.5 or Qt4.4, but by preventing plasma to use Qt4.5, it&#8217;s blocking the use of 4.5 by other projects. When KOffice 2.0 is released it&#8217;s going to be dependent on 4.5, because 4.5 includes important bug/crash fixes. And whatever people like KAMiKAZOW think it&#8217;s going to happen before 4.3. And KOffice 2.0 isn&#8217;t the only project outside KDE4.2 that use Qt as a library, there are countless open source project that depend on it and might want to use Qt4.5 before KDE4.3 is out, which is going to become a problem if distributions can&#8217;t ship Qt4.5.@jos, yes you are right, the issue is a difference of behavior from Qt4.4 to Qt4.5, this is something that happen on a regular basis, especially for newly introduced features. Yet, sebas mention hacks and workarounds, and if there is something to know about hacks and workarounds, they are always going to backfire on you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jospoortvliet</title>
		<link>http://blog.cberger.net/2009/02/09/why-preventing-qt4-5-to-work-fine-with-kde4-2-is-bad/comment-page-1/#comment-216</link>
		<dc:creator>jospoortvliet</dc:creator>
		<pubDate>Tue, 10 Feb 2009 09:20:00 +0000</pubDate>
		<guid isPermaLink="false">http://cyrilleberger.wordpress.com/2009/02/09/why-preventing-qt4-5-to-work-fine-with-kde4-2-is-bad#comment-216</guid>
		<description>To be fair to the Plasma developers, Qt is supposed to be backwards compatible - and cleary 4.4/4.5 failed at this.&lt;/&gt;&lt;/&gt;Any KDE app which uses normal, available Qt features should work fine on any version equal or later than the one it was developed on. So we can&#039;t blame the plasmadevelopers for having to work around bugs in Qt...&lt;/&gt;&lt;/&gt;Nonetheless, it would be great if it were possible to use KDE 4.2 with Qt 4.5, as that version introduces bugfixes and performance improvements.</description>
		<content:encoded><![CDATA[<p>To be fair to the Plasma developers, Qt is supposed to be backwards compatible &#8211; and cleary 4.4/4.5 failed at this.Any KDE app which uses normal, available Qt features should work fine on any version equal or later than the one it was developed on. So we can&#8217;t blame the plasmadevelopers for having to work around bugs in Qt&#8230;Nonetheless, it would be great if it were possible to use KDE 4.2 with Qt 4.5, as that version introduces bugfixes and performance improvements.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
