<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Super Apps Series (Java): Running in the Background Part Four</title>
	<atom:link href="http://devblog.blackberry.com/2010/09/running-in-the-background-part-4/feed/" rel="self" type="application/rss+xml" />
	<link>http://devblog.blackberry.com/2010/09/running-in-the-background-part-4/</link>
	<description></description>
	<lastBuildDate>Tue, 29 Jan 2013 20:13:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Ke</title>
		<link>http://devblog.blackberry.com/2010/09/running-in-the-background-part-4/#comment-627</link>
		<dc:creator><![CDATA[Ke]]></dc:creator>
		<pubDate>Tue, 07 Sep 2010 21:03:58 +0000</pubDate>
		<guid isPermaLink="false">http://devblog.blackberry.com/?p=2122#comment-627</guid>
		<description><![CDATA[These tips are all good but very generic. We would like to see some &quot;lesson learned&quot; in real life projects. We look forward to seeing some of this in the Developer conference. One tip we would like to provide here: the fact that we are not able to show/hide (set visible/invisible) a filed force us to add and delete fields to and from the screen (to show/hide it), each add/delete will trigger sublayout(). As a result, when we are refreshing UI, layout become the bottleneck. One way we solve this problem is to not doing sublayout() before everything is ready (all the fields are added/deleted), then do a updateLayout(). We use this tip to fix a performance issue right before we submit our app to the Super App Challenge.]]></description>
		<content:encoded><![CDATA[<p>These tips are all good but very generic. We would like to see some &#8220;lesson learned&#8221; in real life projects. We look forward to seeing some of this in the Developer conference. One tip we would like to provide here: the fact that we are not able to show/hide (set visible/invisible) a filed force us to add and delete fields to and from the screen (to show/hide it), each add/delete will trigger sublayout(). As a result, when we are refreshing UI, layout become the bottleneck. One way we solve this problem is to not doing sublayout() before everything is ready (all the fields are added/deleted), then do a updateLayout(). We use this tip to fix a performance issue right before we submit our app to the Super App Challenge.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
