<?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: NEWS: Sorry Freestyle no merge (yet)	</title>
	<atom:link href="https://blendernpr.org/news-sorry-freestyle-no-merge-yet/feed/" rel="self" type="application/rss+xml" />
	<link>https://blendernpr.org/news-sorry-freestyle-no-merge-yet/</link>
	<description>Dedicated to Non-Photorealistic and Expressive Rendering</description>
	<lastBuildDate>Fri, 15 Aug 2014 00:22:40 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Light		</title>
		<link>https://blendernpr.org/news-sorry-freestyle-no-merge-yet/#comment-19</link>

		<dc:creator><![CDATA[Light]]></dc:creator>
		<pubDate>Thu, 24 May 2012 15:32:00 +0000</pubDate>
		<guid isPermaLink="false">http://blendernpr.org/?p=641#comment-19</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://blendernpr.org/news-sorry-freestyle-no-merge-yet/#comment-17&quot;&gt;Thomas Dinges&lt;/a&gt;.

Explanation of how Freestyle works by T.K. and reaction by Ton was published, few hours ago.
http://blendernpr.org/freestyle-status-what-is-it/
It won&#039;t be an issue now.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://blendernpr.org/news-sorry-freestyle-no-merge-yet/#comment-17">Thomas Dinges</a>.</p>
<p>Explanation of how Freestyle works by T.K. and reaction by Ton was published, few hours ago.<br />
<a href="http://blendernpr.org/freestyle-status-what-is-it/" rel="ugc">http://blendernpr.org/freestyle-status-what-is-it/</a><br />
It won&#8217;t be an issue now.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Thomas Dinges		</title>
		<link>https://blendernpr.org/news-sorry-freestyle-no-merge-yet/#comment-18</link>

		<dc:creator><![CDATA[Thomas Dinges]]></dc:creator>
		<pubDate>Thu, 24 May 2012 14:35:00 +0000</pubDate>
		<guid isPermaLink="false">http://blendernpr.org/?p=641#comment-18</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://blendernpr.org/news-sorry-freestyle-no-merge-yet/#comment-12&quot;&gt;ikeahloe&lt;/a&gt;.

See my response above, but to answer to your point: 3 years ago Blender had no Render API, things have changed. Projects that are in development for that long have to adapt if changes are made. But as Freestyle is a BI post process, the issue is gone. :) ]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://blendernpr.org/news-sorry-freestyle-no-merge-yet/#comment-12">ikeahloe</a>.</p>
<p>See my response above, but to answer to your point: 3 years ago Blender had no Render API, things have changed. Projects that are in development for that long have to adapt if changes are made. But as Freestyle is a BI post process, the issue is gone. 🙂 </p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Thomas Dinges		</title>
		<link>https://blendernpr.org/news-sorry-freestyle-no-merge-yet/#comment-17</link>

		<dc:creator><![CDATA[Thomas Dinges]]></dc:creator>
		<pubDate>Thu, 24 May 2012 14:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://blendernpr.org/?p=641#comment-17</guid>

					<description><![CDATA[Hi,
The situation has changed. I had the impression that Freestyle was a standalone Render Engine, but it&#039;s actually a BI post process. 
So my mail is basically invalid, although I would like to check on UI design etc. and other devs will do the usual code review too. 

This means that a few changes need to be done, but Freestyle should be in Trunk soon, maybe not in 2.64, but it&#039;ll be in 2.65 for sure! 

Sorry if my mail caused some bad impression, I am welcoming Freestyle of course and it&#039;s a great addition. But that&#039;s why we have the dev mailing list, to communicate and discuss such things, so we all get the best out of it. :) 
We rushed in features before in the past and sometimes it caused some trouble. That&#039;s why such discussion is necessary, even if it makes the userbase a bit unhappy at first. 

But anyway, issue solved, Freestyle is on it&#039;s way! ]]></description>
			<content:encoded><![CDATA[<p>Hi,<br />
The situation has changed. I had the impression that Freestyle was a standalone Render Engine, but it&#8217;s actually a BI post process.<br />
So my mail is basically invalid, although I would like to check on UI design etc. and other devs will do the usual code review too. </p>
<p>This means that a few changes need to be done, but Freestyle should be in Trunk soon, maybe not in 2.64, but it&#8217;ll be in 2.65 for sure! </p>
<p>Sorry if my mail caused some bad impression, I am welcoming Freestyle of course and it&#8217;s a great addition. But that&#8217;s why we have the dev mailing list, to communicate and discuss such things, so we all get the best out of it. 🙂<br />
We rushed in features before in the past and sometimes it caused some trouble. That&#8217;s why such discussion is necessary, even if it makes the userbase a bit unhappy at first. </p>
<p>But anyway, issue solved, Freestyle is on it&#8217;s way! </p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Folkert de Vries		</title>
		<link>https://blendernpr.org/news-sorry-freestyle-no-merge-yet/#comment-16</link>

		<dc:creator><![CDATA[Folkert de Vries]]></dc:creator>
		<pubDate>Thu, 24 May 2012 13:49:00 +0000</pubDate>
		<guid isPermaLink="false">http://blendernpr.org/?p=641#comment-16</guid>

					<description><![CDATA[the documentation is, 
although a few months old, more or less done in my wiki space:
http://wiki.blender.org/index.php/User:Flokkievids/Freestyle ]]></description>
			<content:encoded><![CDATA[<p>the documentation is, <br />
although a few months old, more or less done in my wiki space:<br />
<a href="http://wiki.blender.org/index.php/User:Flokkievids/Freestyle " rel="nofollow ugc">http://wiki.blender.org/index.php/User:Flokkievids/Freestyle </a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: ikeahloe		</title>
		<link>https://blendernpr.org/news-sorry-freestyle-no-merge-yet/#comment-15</link>

		<dc:creator><![CDATA[ikeahloe]]></dc:creator>
		<pubDate>Thu, 24 May 2012 02:32:00 +0000</pubDate>
		<guid isPermaLink="false">http://blendernpr.org/?p=641#comment-15</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://blendernpr.org/news-sorry-freestyle-no-merge-yet/#comment-13&quot;&gt;Light&lt;/a&gt;.

boooooooo]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://blendernpr.org/news-sorry-freestyle-no-merge-yet/#comment-13">Light</a>.</p>
<p>boooooooo</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Light		</title>
		<link>https://blendernpr.org/news-sorry-freestyle-no-merge-yet/#comment-13</link>

		<dc:creator><![CDATA[Light]]></dc:creator>
		<pubDate>Wed, 23 May 2012 04:38:00 +0000</pubDate>
		<guid isPermaLink="false">http://blendernpr.org/?p=641#comment-13</guid>

					<description><![CDATA[Frankly, I&#039;m thinking the same. It&#039;s like a castle was built and someone came in and said, &quot;Nice castle, I thought you were building a pagoda, that&#039;s what the king wants.&quot; Really irresponsible I think for not checking back and give feedback on the &quot;ideal&quot; specs. Only someone like us who use Freestyle very often (as in using it in small productions) that we know how Freestyle really works by design. The lack of documentation is one. But when Thomas mentioned using rendering API, one thing pops up in my mind, &quot;Didn&#039;t Campbell said that the render API was not up to par yet and not ready&quot; Which BI developer is working on this today? Non. So it is perfectly clogged in the drain.]]></description>
			<content:encoded><![CDATA[<p>Frankly, I&#8217;m thinking the same. It&#8217;s like a castle was built and someone came in and said, &#8220;Nice castle, I thought you were building a pagoda, that&#8217;s what the king wants.&#8221; Really irresponsible I think for not checking back and give feedback on the &#8220;ideal&#8221; specs. Only someone like us who use Freestyle very often (as in using it in small productions) that we know how Freestyle really works by design. The lack of documentation is one. But when Thomas mentioned using rendering API, one thing pops up in my mind, &#8220;Didn&#8217;t Campbell said that the render API was not up to par yet and not ready&#8221; Which BI developer is working on this today? Non. So it is perfectly clogged in the drain.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: ikeahloe		</title>
		<link>https://blendernpr.org/news-sorry-freestyle-no-merge-yet/#comment-12</link>

		<dc:creator><![CDATA[ikeahloe]]></dc:creator>
		<pubDate>Tue, 22 May 2012 22:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://blendernpr.org/?p=641#comment-12</guid>

					<description><![CDATA[you&#039;d think they would let the freestyle team know before now that the blender integration method they&#039;re using wasn&#039;t acceptable to the other blender devs. It seems to me coming from an outside coding view, that it would be a lot of work to change the way freestyle is integrated into blender, considering that&#039;s a large percent of the work that&#039;s been done for 3+ years.... i don&#039;t know it just seems a little inconsiderate this late and this close to a stable merge to pull that out. but maybe i&#039;m looking into it wrong and the changes he&#039;s referring to are not that hard/major.]]></description>
			<content:encoded><![CDATA[<p>you&#8217;d think they would let the freestyle team know before now that the blender integration method they&#8217;re using wasn&#8217;t acceptable to the other blender devs. It seems to me coming from an outside coding view, that it would be a lot of work to change the way freestyle is integrated into blender, considering that&#8217;s a large percent of the work that&#8217;s been done for 3+ years&#8230;. i don&#8217;t know it just seems a little inconsiderate this late and this close to a stable merge to pull that out. but maybe i&#8217;m looking into it wrong and the changes he&#8217;s referring to are not that hard/major.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
