<?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"
	>
<channel>
	<title>Comments on: Viewports etc.</title>
	<atom:link href="http://chrisjs.com/viewports-etc/feed/" rel="self" type="application/rss+xml" />
	<link>http://chrisjs.com/viewports-etc/</link>
	<description>Chrisjs Rockbox Branch</description>
	<pubDate>Tue, 06 Jan 2009 03:22:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: chrisjs169</title>
		<link>http://chrisjs.com/viewports-etc/#comment-330</link>
		<dc:creator>chrisjs169</dc:creator>
		<pubDate>Sun, 06 Jan 2008 22:42:43 +0000</pubDate>
		<guid isPermaLink="false">http://chrisjs.com/viewports-etc/#comment-330</guid>
		<description>If anyone wants to see an example of a theme with viewports, KratoJet has been ported, and can be found at http://chrisjs.com/upload/viewport/KratoJetVP-v8.zip</description>
		<content:encoded><![CDATA[<p>If anyone wants to see an example of a theme with viewports, KratoJet has been ported, and can be found at <a href='http://chrisjs.com/upload/viewport/KratoJetVP-v8.zip'>http://chrisjs.com/upload/viewport/KratoJetVP-v8.zip</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chrisjs169</title>
		<link>http://chrisjs.com/viewports-etc/#comment-329</link>
		<dc:creator>chrisjs169</dc:creator>
		<pubDate>Sun, 06 Jan 2008 22:40:32 +0000</pubDate>
		<guid isPermaLink="false">http://chrisjs.com/viewports-etc/#comment-329</guid>
		<description>From ABi:

Old: %e&#124;x&#124;y&#124;width&#124;fontnumber&#124;fontcolor&#124;
New: %V&#124;x&#124;y&#124;width&#124;height&#124;font&#124;fgcolor&#124;bgcolor&#124;

From [fs]8385[/fs]:


Specifying "0" for font means that that viewport draws text using the built-in (6x8) system font (FONT_SYSFIXED). Note that this font only includes ASCII characters, so isn't suitable for displaying information from tags.

Specifying "1" for font will use the currently selected user font (FONT_UI).</description>
		<content:encoded><![CDATA[<p>From ABi:</p>
<p>Old: %e|x|y|width|fontnumber|fontcolor|<br />
New: %V|x|y|width|height|font|fgcolor|bgcolor|</p>
<p>From <a href='http://rockbox.org/tracker/task/8385'>FS#8385</a>:</p>
<p>Specifying "0" for font means that that viewport draws text using the built-in (6x8) system font (FONT_SYSFIXED). Note that this font only includes ASCII characters, so isn't suitable for displaying information from tags.</p>
<p>Specifying "1" for font will use the currently selected user font (FONT_UI).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zim</title>
		<link>http://chrisjs.com/viewports-etc/#comment-328</link>
		<dc:creator>Zim</dc:creator>
		<pubDate>Sun, 06 Jan 2008 16:34:59 +0000</pubDate>
		<guid isPermaLink="false">http://chrisjs.com/viewports-etc/#comment-328</guid>
		<description>Ok, so how exactly can you port themes?</description>
		<content:encoded><![CDATA[<p>Ok, so how exactly can you port themes?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chrisjs169</title>
		<link>http://chrisjs.com/viewports-etc/#comment-327</link>
		<dc:creator>chrisjs169</dc:creator>
		<pubDate>Sun, 06 Jan 2008 04:11:28 +0000</pubDate>
		<guid isPermaLink="false">http://chrisjs.com/viewports-etc/#comment-327</guid>
		<description>Yeah, with 50+ failed hunks, there's no way I'm making it run parallel with viewports.

Zim - that's what I said back in the "warning about wps patches" post - once viewports are accepted* those patches will be closed.
* There was discussion about whether to close them earlier or wait until viewports were committed.  Either way, once viewports is in SVN, those patches will be closed.  I think the patches that are definitely going to be closed are [fs]2954[/fs] and [fs]5900[/fs], though I think others might be as well.

major_works - I agree, one advantage to going to viewports is it will be a lot easier to sync patches, at the expense of having quite a few themes not work until converted.  Zim, that means your themes can still work, you just need to port them.  Seeing that somehow the build updated while I was rebuilding, I can really say that the build uses viewports, along with Digi's.  Kugel has told me that his next build will be using viewports as well, meaning that current themes will only work with old builds and cpchan's build.</description>
		<content:encoded><![CDATA[<p>Yeah, with 50+ failed hunks, there's no way I'm making it run parallel with viewports.</p>
<p>Zim - that's what I said back in the "warning about wps patches" post - once viewports are accepted* those patches will be closed.<br />
* There was discussion about whether to close them earlier or wait until viewports were committed.  Either way, once viewports is in SVN, those patches will be closed.  I think the patches that are definitely going to be closed are <a href='http://rockbox.org/tracker/task/2954'>FS#2954</a> and <a href='http://rockbox.org/tracker/task/5900'>FS#5900</a>, though I think others might be as well.</p>
<p>major_works - I agree, one advantage to going to viewports is it will be a lot easier to sync patches, at the expense of having quite a few themes not work until converted.  Zim, that means your themes can still work, you just need to port them.  Seeing that somehow the build updated while I was rebuilding, I can really say that the build uses viewports, along with Digi's.  Kugel has told me that his next build will be using viewports as well, meaning that current themes will only work with old builds and cpchan's build.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: major_works</title>
		<link>http://chrisjs.com/viewports-etc/#comment-326</link>
		<dc:creator>major_works</dc:creator>
		<pubDate>Sun, 06 Jan 2008 03:50:12 +0000</pubDate>
		<guid isPermaLink="false">http://chrisjs.com/viewports-etc/#comment-326</guid>
		<description>Ooohh... ouch on that pastebin link. Going to Viewports will make your life much easier. The big thing now is converting all the themes that relied on the WPS patches.</description>
		<content:encoded><![CDATA[<p>Ooohh... ouch on that pastebin link. Going to Viewports will make your life much easier. The big thing now is converting all the themes that relied on the WPS patches.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zim</title>
		<link>http://chrisjs.com/viewports-etc/#comment-325</link>
		<dc:creator>Zim</dc:creator>
		<pubDate>Sun, 06 Jan 2008 02:29:19 +0000</pubDate>
		<guid isPermaLink="false">http://chrisjs.com/viewports-etc/#comment-325</guid>
		<description>So what you're saying is, once they get these View-ports all figured out, they'll close all of the old WPS patches. And that means that many (if not all) themes that rely on those patches, including my super awesome theme;{ , will die.</description>
		<content:encoded><![CDATA[<p>So what you're saying is, once they get these View-ports all figured out, they'll close all of the old WPS patches. And that means that many (if not all) themes that rely on those patches, including my super awesome theme;{ , will die.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

