<?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: Randa Meetings 2012: The Future of QGraphicsView in Plasma</title>
	<atom:link href="http://vizZzion.org/blog/2012/09/randa-meetings-2012-the-future-of-qgraphicsview-in-plasma/feed/" rel="self" type="application/rss+xml" />
	<link>http://vizZzion.org/blog/2012/09/randa-meetings-2012-the-future-of-qgraphicsview-in-plasma/</link>
	<description>Sebastian Kügler&#039;s web log</description>
	<lastBuildDate>Wed, 17 Apr 2013 11:42:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: sebas</title>
		<link>http://vizZzion.org/blog/2012/09/randa-meetings-2012-the-future-of-qgraphicsview-in-plasma/comment-page-1/#comment-14653</link>
		<dc:creator>sebas</dc:creator>
		<pubDate>Wed, 03 Oct 2012 13:47:04 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/?p=2038#comment-14653</guid>
		<description><![CDATA[I can&#039;t really say, this is too far in the future, and I&#039;m lacking the insight into these things to comment in a meaningful way. Do not that we&#039;re still quite some time away from this ideal world. Do keep in mind that GNOME is very different from KDE&#039;s architecture, so if it doesn&#039;t work well in GNOME, doesn&#039;t mean it&#039;ll break with Plasma. We&#039;ve seen that multiple times in the past (just keep in mind KWin&#039;s fallback mode to &quot;2d rendering&quot;).]]></description>
		<content:encoded><![CDATA[<p>I can&#8217;t really say, this is too far in the future, and I&#8217;m lacking the insight into these things to comment in a meaningful way. Do not that we&#8217;re still quite some time away from this ideal world. Do keep in mind that GNOME is very different from KDE&#8217;s architecture, so if it doesn&#8217;t work well in GNOME, doesn&#8217;t mean it&#8217;ll break with Plasma. We&#8217;ve seen that multiple times in the past (just keep in mind KWin&#8217;s fallback mode to &#8220;2d rendering&#8221;).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Damian Ivanov</title>
		<link>http://vizZzion.org/blog/2012/09/randa-meetings-2012-the-future-of-qgraphicsview-in-plasma/comment-page-1/#comment-14650</link>
		<dc:creator>Damian Ivanov</dc:creator>
		<pubDate>Wed, 03 Oct 2012 13:35:40 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/?p=2038#comment-14650</guid>
		<description><![CDATA[Yeah, but well this would make KDE 3d only (or requiring 3d acceleration), as we will need for quasi standard plasmoids, the start menu will require it, the taskbar, the clock (?!), they are all plasmoids and as they are rewritten in QML. Kwin will also have QML window decorations...
llvmpipe breaks multiseat technologies, even a quad cpu goes almost down with 3 gnome-shell desktops rendered.
Will KDE also break any possible multiseat setup ( I know GPU offloading is in future xrandr, but e.g if no 3d GPU is available, only diplaylink) and have the same requirements like gnome-shell?]]></description>
		<content:encoded><![CDATA[<p>Yeah, but well this would make KDE 3d only (or requiring 3d acceleration), as we will need for quasi standard plasmoids, the start menu will require it, the taskbar, the clock (?!), they are all plasmoids and as they are rewritten in QML. Kwin will also have QML window decorations&#8230;<br />
llvmpipe breaks multiseat technologies, even a quad cpu goes almost down with 3 gnome-shell desktops rendered.<br />
Will KDE also break any possible multiseat setup ( I know GPU offloading is in future xrandr, but e.g if no 3d GPU is available, only diplaylink) and have the same requirements like gnome-shell?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sebas</title>
		<link>http://vizZzion.org/blog/2012/09/randa-meetings-2012-the-future-of-qgraphicsview-in-plasma/comment-page-1/#comment-14647</link>
		<dc:creator>sebas</dc:creator>
		<pubDate>Wed, 03 Oct 2012 13:21:41 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/?p=2038#comment-14647</guid>
		<description><![CDATA[Well, in the worst case, widgets fall back to CPU rendering (through llvmpipe), which is what we&#039;re doing now. I expect a not worse-than-now worst-case-scenario.]]></description>
		<content:encoded><![CDATA[<p>Well, in the worst case, widgets fall back to CPU rendering (through llvmpipe), which is what we&#8217;re doing now. I expect a not worse-than-now worst-case-scenario.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Damian Ivanov</title>
		<link>http://vizZzion.org/blog/2012/09/randa-meetings-2012-the-future-of-qgraphicsview-in-plasma/comment-page-1/#comment-14642</link>
		<dc:creator>Damian Ivanov</dc:creator>
		<pubDate>Wed, 03 Oct 2012 12:53:37 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/?p=2038#comment-14642</guid>
		<description><![CDATA[But doesn&#039;t that mean the widgets using the openGL scenegraph to require 3d drivers or S/W rendering and will be slower than the QGraphicsWidget if no 3d is available]]></description>
		<content:encoded><![CDATA[<p>But doesn&#8217;t that mean the widgets using the openGL scenegraph to require 3d drivers or S/W rendering and will be slower than the QGraphicsWidget if no 3d is available</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian</title>
		<link>http://vizZzion.org/blog/2012/09/randa-meetings-2012-the-future-of-qgraphicsview-in-plasma/comment-page-1/#comment-14203</link>
		<dc:creator>Ian</dc:creator>
		<pubDate>Sun, 30 Sep 2012 14:08:19 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/?p=2038#comment-14203</guid>
		<description><![CDATA[QML lost its (surprisingly small) Australian dev team, but the scenegraph folks have always been in Oslo iirc. And regardless I&#039;m not worried about the ability of Lars Knoll&#039;s team to pick up maintenance for the stuff done previously in Australia.]]></description>
		<content:encoded><![CDATA[<p>QML lost its (surprisingly small) Australian dev team, but the scenegraph folks have always been in Oslo iirc. And regardless I&#8217;m not worried about the ability of Lars Knoll&#8217;s team to pick up maintenance for the stuff done previously in Australia.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian</title>
		<link>http://vizZzion.org/blog/2012/09/randa-meetings-2012-the-future-of-qgraphicsview-in-plasma/comment-page-1/#comment-14201</link>
		<dc:creator>Ian</dc:creator>
		<pubDate>Sun, 30 Sep 2012 14:02:06 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/?p=2038#comment-14201</guid>
		<description><![CDATA[When you get there you realize Switzerland is actually entirely fictional.]]></description>
		<content:encoded><![CDATA[<p>When you get there you realize Switzerland is actually entirely fictional.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ivan Čukić</title>
		<link>http://vizZzion.org/blog/2012/09/randa-meetings-2012-the-future-of-qgraphicsview-in-plasma/comment-page-1/#comment-14170</link>
		<dc:creator>Ivan Čukić</dc:creator>
		<pubDate>Sun, 30 Sep 2012 06:33:54 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/?p=2038#comment-14170</guid>
		<description><![CDATA[Lets hope this is the last time I need to rewrite Lancelot :]

QGV was ruthless in that regard.

Cheerio!]]></description>
		<content:encoded><![CDATA[<p>Lets hope this is the last time I need to rewrite Lancelot :]</p>
<p>QGV was ruthless in that regard.</p>
<p>Cheerio!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nik</title>
		<link>http://vizZzion.org/blog/2012/09/randa-meetings-2012-the-future-of-qgraphicsview-in-plasma/comment-page-1/#comment-14092</link>
		<dc:creator>nik</dc:creator>
		<pubDate>Sun, 30 Sep 2012 00:24:42 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/?p=2038#comment-14092</guid>
		<description><![CDATA[The photographed scenery is magical. I&#039;ts cool for our coders to work there...  If the next sprint takes place in an abandon castle in transylvania, even I, a greek, will donate for it!]]></description>
		<content:encoded><![CDATA[<p>The photographed scenery is magical. I&#8217;ts cool for our coders to work there&#8230;  If the next sprint takes place in an abandon castle in transylvania, even I, a greek, will donate for it!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Seigo</title>
		<link>http://vizZzion.org/blog/2012/09/randa-meetings-2012-the-future-of-qgraphicsview-in-plasma/comment-page-1/#comment-14068</link>
		<dc:creator>Aaron Seigo</dc:creator>
		<pubDate>Sat, 29 Sep 2012 21:55:30 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/?p=2038#comment-14068</guid>
		<description><![CDATA[QML2 does have a development team (3 people still working on it @ Qt afaik) and it&#039;s already rather performant on a variety of chipsets. go look on youtube for various examples; the live coding on raspberry pie (not the reference platform) is pretty spectacular.

will it be a 100% perfect solution? no, nothing ever is. but it already looks better than QGV which truly does not have a devel team and which has long standing bugs in rather basic things like mouse interaction (due to how mouse input handling is managed in the scene with QGraphicsWidget) that are not going to get fixed (due to no devel team and due to how they relate to the design). there are also inherent performance limitations to things like QGraphicsProxyWidget which we rely on heavily right now since it routes through QWidget classes; it is literally not possible to get instantiation of a single QGPW below 50ms on my laptop here due to the code paths it takes. this is a design limitation which QML removes from us.

and since QMl2 is still being developed, we can meaningfully contribute to it.

but hey ... maybe you&#039;ve done a bunch of work with QML2 and have a diferent experience? if so, please share it with us :)]]></description>
		<content:encoded><![CDATA[<p>QML2 does have a development team (3 people still working on it @ Qt afaik) and it&#8217;s already rather performant on a variety of chipsets. go look on youtube for various examples; the live coding on raspberry pie (not the reference platform) is pretty spectacular.</p>
<p>will it be a 100% perfect solution? no, nothing ever is. but it already looks better than QGV which truly does not have a devel team and which has long standing bugs in rather basic things like mouse interaction (due to how mouse input handling is managed in the scene with QGraphicsWidget) that are not going to get fixed (due to no devel team and due to how they relate to the design). there are also inherent performance limitations to things like QGraphicsProxyWidget which we rely on heavily right now since it routes through QWidget classes; it is literally not possible to get instantiation of a single QGPW below 50ms on my laptop here due to the code paths it takes. this is a design limitation which QML removes from us.</p>
<p>and since QMl2 is still being developed, we can meaningfully contribute to it.</p>
<p>but hey &#8230; maybe you&#8217;ve done a bunch of work with QML2 and have a diferent experience? if so, please share it with us :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sebas</title>
		<link>http://vizZzion.org/blog/2012/09/randa-meetings-2012-the-future-of-qgraphicsview-in-plasma/comment-page-1/#comment-14046</link>
		<dc:creator>sebas</dc:creator>
		<pubDate>Sat, 29 Sep 2012 18:04:06 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/?p=2038#comment-14046</guid>
		<description><![CDATA[The bugs I&#039;m talking about are mainly in the layouting and sizing code, so they&#039;re bugs in QGraphicsWidgets usually, those are being removed from libplasma2. So far we&#039;ve seen very good results whenever we replaced QGraphicsWidget-based UI with QML, so I&#039;m very optimistic.]]></description>
		<content:encoded><![CDATA[<p>The bugs I&#8217;m talking about are mainly in the layouting and sizing code, so they&#8217;re bugs in QGraphicsWidgets usually, those are being removed from libplasma2. So far we&#8217;ve seen very good results whenever we replaced QGraphicsWidget-based UI with QML, so I&#8217;m very optimistic.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
