<?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:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Kommentare f&#252;r Martin's Blog</title>
	<atom:link href="http://blog.martin-graesslin.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.martin-graesslin.com/blog</link>
	<description>From the land of wobbly windows</description>
	<lastBuildDate>Thu, 02 Feb 2012 20:52:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>Kommentar zu The Importance of Mentoring von Software ist nicht nur Text im Editor &#187; startafire</title>
		<link>http://blog.martin-graesslin.com/blog/2012/01/the-importance-of-mentoring/comment-page-1/#comment-45810</link>
		<dc:creator>Software ist nicht nur Text im Editor &#187; startafire</dc:creator>
		<pubDate>Thu, 02 Feb 2012 20:52:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.martin-graesslin.com/blog/?p=807#comment-45810</guid>
		<description>[...] Software ist nicht nur Text im Editor  &#160;Persönliches, Software &#160;Add comments   Feb 022012  &#160;    $SUPERAWESOMEFEATURE is just bit crap if it cannot be maintained by your team. -Martin Grässlin (in The Importance of Mentoring) [...]</description>
		<content:encoded><![CDATA[<p>[...] Software ist nicht nur Text im Editor  &nbsp;Persönliches, Software &nbsp;Add comments   Feb 022012  &nbsp;    $SUPERAWESOMEFEATURE is just bit crap if it cannot be maintained by your team. -Martin Grässlin (in The Importance of Mentoring) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Kommentar zu KWin Effects written in JavaScript von Martin Gräßlin</title>
		<link>http://blog.martin-graesslin.com/blog/2012/01/kwin-effects-written-in-javascript/comment-page-1/#comment-45787</link>
		<dc:creator>Martin Gräßlin</dc:creator>
		<pubDate>Mon, 30 Jan 2012 19:17:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.martin-graesslin.com/blog/?p=822#comment-45787</guid>
		<description>This is not yet possible but it is an interesting task, so I will try to design the API to make that possible.</description>
		<content:encoded><![CDATA[<p>This is not yet possible but it is an interesting task, so I will try to design the API to make that possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Kommentar zu KWin Effects written in JavaScript von Tom</title>
		<link>http://blog.martin-graesslin.com/blog/2012/01/kwin-effects-written-in-javascript/comment-page-1/#comment-45786</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Mon, 30 Jan 2012 18:33:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.martin-graesslin.com/blog/?p=822#comment-45786</guid>
		<description>My understanding of how this scripting works and what it can do is very limited, so please forgive me if the following seems like a stupid question to you:
Would it be possible with this scripting engine to automatically activate the zooming lens effect when the mouse cursor enters a certain region of a window? (I&#039;m thinking of this for zooming the snapping icons in inkscape).</description>
		<content:encoded><![CDATA[<p>My understanding of how this scripting works and what it can do is very limited, so please forgive me if the following seems like a stupid question to you:<br />
Would it be possible with this scripting engine to automatically activate the zooming lens effect when the mouse cursor enters a certain region of a window? (I&#8217;m thinking of this for zooming the snapping icons in inkscape).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Kommentar zu KWin Effects written in JavaScript von Martin Gräßlin</title>
		<link>http://blog.martin-graesslin.com/blog/2012/01/kwin-effects-written-in-javascript/comment-page-1/#comment-45780</link>
		<dc:creator>Martin Gräßlin</dc:creator>
		<pubDate>Mon, 30 Jan 2012 05:54:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.martin-graesslin.com/blog/?p=822#comment-45780</guid>
		<description>Well you spotted the problem. So even if we had our own QML parser, we would still be constrained to what we can do with effects. Giving you exactly the same API as what you will be able to do with the JavaScript bindings. Additionally the declarative way does not make much sense, as we don&#039;t have Windows which you can declare, but windows just appear and disappear. And we also cannot add them into a Model - well we could, but QML is not very good with TreeModels and for KWin&#039;s usecases we would need a very complex TreeModel with multiple FilterModels before to have nice wrappers (all windows of a desktop, all windows of a screen, all windows of an activity, etc. etc.). So JS is just the better solution for effects.</description>
		<content:encoded><![CDATA[<p>Well you spotted the problem. So even if we had our own QML parser, we would still be constrained to what we can do with effects. Giving you exactly the same API as what you will be able to do with the JavaScript bindings. Additionally the declarative way does not make much sense, as we don&#8217;t have Windows which you can declare, but windows just appear and disappear. And we also cannot add them into a Model &#8211; well we could, but QML is not very good with TreeModels and for KWin&#8217;s usecases we would need a very complex TreeModel with multiple FilterModels before to have nice wrappers (all windows of a desktop, all windows of a screen, all windows of an activity, etc. etc.). So JS is just the better solution for effects.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Kommentar zu KWin Effects written in JavaScript von markg85</title>
		<link>http://blog.martin-graesslin.com/blog/2012/01/kwin-effects-written-in-javascript/comment-page-1/#comment-45776</link>
		<dc:creator>markg85</dc:creator>
		<pubDate>Sun, 29 Jan 2012 21:46:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.martin-graesslin.com/blog/?p=822#comment-45776</guid>
		<description>I know that - going fully through qml - ain&#039;t gonna happen, but i thought there might be a way to use it&#039;s features without it&#039;s rendering.. I guess that means that KWIN should get some QML parser to make that happen..

-- not gonna happen --

I&#039;m dreaming on :) Good job so far!</description>
		<content:encoded><![CDATA[<p>I know that &#8211; going fully through qml &#8211; ain&#8217;t gonna happen, but i thought there might be a way to use it&#8217;s features without it&#8217;s rendering.. I guess that means that KWIN should get some QML parser to make that happen..</p>
<p>&#8211; not gonna happen &#8211;</p>
<p>I&#8217;m dreaming on <img src='http://blog.martin-graesslin.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  Good job so far!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Kommentar zu KWin Effects written in JavaScript von Martin Gräßlin</title>
		<link>http://blog.martin-graesslin.com/blog/2012/01/kwin-effects-written-in-javascript/comment-page-1/#comment-45775</link>
		<dc:creator>Martin Gräßlin</dc:creator>
		<pubDate>Sun, 29 Jan 2012 21:07:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.martin-graesslin.com/blog/?p=822#comment-45775</guid>
		<description>&lt;blockquote&gt;Is that your end goal? Doing it in full QML like in my above example with Window?&lt;/blockquote&gt;
No, I&#039;m not planning to make normal effects in QML. Doing it in QML requires rendering through QML and as I explained to you more than once, this does not make sense for us.</description>
		<content:encoded><![CDATA[<blockquote><p>Is that your end goal? Doing it in full QML like in my above example with Window?</p></blockquote>
<p>No, I&#8217;m not planning to make normal effects in QML. Doing it in QML requires rendering through QML and as I explained to you more than once, this does not make sense for us.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Kommentar zu KWin Effects written in JavaScript von markg85</title>
		<link>http://blog.martin-graesslin.com/blog/2012/01/kwin-effects-written-in-javascript/comment-page-1/#comment-45774</link>
		<dc:creator>markg85</dc:creator>
		<pubDate>Sun, 29 Jan 2012 20:55:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.martin-graesslin.com/blog/?p=822#comment-45774</guid>
		<description>Oh wow, you&#039;re getting to my request :-)
Just slightly different.. It&#039;s nice to see effects can be done so easily, but looking at your example we&#039;re still bound by the effects that KWIN provides through the API. So still no way for us to make real custom effects other then mixing the provided ones.

What i was suggesting is really using QML for the effects from a - z.
For example this, you example would look somewhat like this in QML:

Window
{
    Behavior on opacity
    {
         NumberAnimation { duration: 1000 }
    }
}

That&#039;s it!.

But more advanced things can also be done by using ShaderEffectItem. That&#039;s the kinda stuff i meant :-)

Yes, there you have to be aware of certain shaders not working on certain crappy hardware (ATI/AMD including the newest cards and drivers). Is that your end goal? Doing it in full QML like in my above example with Window?</description>
		<content:encoded><![CDATA[<p>Oh wow, you&#8217;re getting to my request <img src='http://blog.martin-graesslin.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /><br />
Just slightly different.. It&#8217;s nice to see effects can be done so easily, but looking at your example we&#8217;re still bound by the effects that KWIN provides through the API. So still no way for us to make real custom effects other then mixing the provided ones.</p>
<p>What i was suggesting is really using QML for the effects from a &#8211; z.<br />
For example this, you example would look somewhat like this in QML:</p>
<p>Window<br />
{<br />
    Behavior on opacity<br />
    {<br />
         NumberAnimation { duration: 1000 }<br />
    }<br />
}</p>
<p>That&#8217;s it!.</p>
<p>But more advanced things can also be done by using ShaderEffectItem. That&#8217;s the kinda stuff i meant <img src='http://blog.martin-graesslin.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Yes, there you have to be aware of certain shaders not working on certain crappy hardware (ATI/AMD including the newest cards and drivers). Is that your end goal? Doing it in full QML like in my above example with Window?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Kommentar zu KWin Effects written in JavaScript von mutlu</title>
		<link>http://blog.martin-graesslin.com/blog/2012/01/kwin-effects-written-in-javascript/comment-page-1/#comment-45771</link>
		<dc:creator>mutlu</dc:creator>
		<pubDate>Sun, 29 Jan 2012 18:38:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.martin-graesslin.com/blog/?p=822#comment-45771</guid>
		<description>This is indeed awesome! Congratulations to yet another great achievement. The KWin team rocks!</description>
		<content:encoded><![CDATA[<p>This is indeed awesome! Congratulations to yet another great achievement. The KWin team rocks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Kommentar zu KWin Effects written in JavaScript von Bender</title>
		<link>http://blog.martin-graesslin.com/blog/2012/01/kwin-effects-written-in-javascript/comment-page-1/#comment-45770</link>
		<dc:creator>Bender</dc:creator>
		<pubDate>Sun, 29 Jan 2012 18:12:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.martin-graesslin.com/blog/?p=822#comment-45770</guid>
		<description>Looks to me like kde is becoming more tightly integrated with qt as in using qt and its technologies/ideas directly like using qml instead of building some intermediate libraries etc. 

Makes me feel happy seeing how qt and kde are progressing together.</description>
		<content:encoded><![CDATA[<p>Looks to me like kde is becoming more tightly integrated with qt as in using qt and its technologies/ideas directly like using qml instead of building some intermediate libraries etc. </p>
<p>Makes me feel happy seeing how qt and kde are progressing together.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Kommentar zu KWin Effects written in JavaScript von acidrums4</title>
		<link>http://blog.martin-graesslin.com/blog/2012/01/kwin-effects-written-in-javascript/comment-page-1/#comment-45769</link>
		<dc:creator>acidrums4</dc:creator>
		<pubDate>Sun, 29 Jan 2012 17:48:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.martin-graesslin.com/blog/?p=822#comment-45769</guid>
		<description>You&#039;re right, this is really awesome. KWin is getting really better in short time. Thanks for doing such wonderful things!</description>
		<content:encoded><![CDATA[<p>You&#8217;re right, this is really awesome. KWin is getting really better in short time. Thanks for doing such wonderful things!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

