<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" 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" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>Trog, The Blog</title>
	
	<link>http://www.priacta.com/trogblog</link>
	<description>Development Blog for Priacta's Trog Bar</description>
	<pubDate>Mon, 29 Sep 2008 14:20:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<creativeCommons:license>http://creativecommons.org/licenses/by-nd/2.0/</creativeCommons:license><image><link>http://www.priacta.com/trogblog</link><url>http://www.priacta.com/images/feed_header_trog.jpg</url><title>Trog, The Blog</title></image><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/TrogTheBlog" type="application/rss+xml" /><feedburner:emailServiceId>TrogTheBlog</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><item>
		<title>What’s Cooking</title>
		<link>http://feedproxy.google.com/~r/TrogTheBlog/~3/Ei4cclbBWOg/</link>
		<comments>http://www.priacta.com/trogblog/2008/07/16/whats-cooking/#comments</comments>
		<pubDate>Wed, 16 Jul 2008 23:02:26 +0000</pubDate>
		<dc:creator>Bug Slayer</dc:creator>
		
		<category><![CDATA[Beta and Preview Features]]></category>

		<category><![CDATA[Development]]></category>

		<category><![CDATA[Trog Bar]]></category>

		<category><![CDATA[MAPI]]></category>

		<category><![CDATA[Outlook]]></category>

		<category><![CDATA[RTM]]></category>

		<category><![CDATA[synchronization]]></category>

		<category><![CDATA[Thunderbird]]></category>

		<category><![CDATA[TRO]]></category>

		<guid isPermaLink="false">http://www.priacta.com/trogblog/?p=8</guid>
		<description><![CDATA[What does it mean when the development blog is quiet for awhile? Are the programmers soaking in sun on a Hawaiian beach, or are they chained to their desks beside a pile of pizza?

Here is the inside scoop. Over the last 3 months we've been working feverishly on radical changes that will make Trog Bar even faster and more flexible with a smaller memory footprint.

[<a title="Trog Bar Development Status and Roadmap" href="http://www.priacta.com/trogblog/2008/07/16/yes-were-alive/">Click here to read more...</a>]]]></description>
			<content:encoded><![CDATA[<p>What does it mean when the development blog is quiet for awhile? Are the programmers soaking in sun on a Hawaiian beach, or are they chained to their desks beside a pile of pizza?</p>
<p>Here is the inside scoop. Over the last 3 months we&#8217;ve been working feverishly on radical changes that will make Trog Bar even faster and more flexible with a smaller memory footprint.</p>
<h3>The Road MAP(I) and Syncing</h3>
<p>We began to notice that our data storage system (MAPI + Outlook) was limiting Trog&#8217;s performance and our development options, including how well TaskSense does its job. It was also preventing us from adding the most requested feature: compatibility with Thunderbird and other email clients. By mid-April we were ready to launch into a new architecture.</p>
<p>One of our primary concerns was maintaining the real time binding with Outlook. In other words, when you make a change in the Trog Bar or Outlook, it needs to appear in the other immediately. Until now this was automatic since we stored everything in Outlook&#8217;s database. Now, however, <em>in addition</em> to storing data in Outlook (for Outlook to use directly) we needed a second, much faster database (for Trog Bar to use). Programmers reading this will recognize that this requires a robust synchronization system.</p>
<p>Syncing requires caution. If you do it wrong, you can duplicate data or worse. It can be slow enough that you don&#8217;t want to do it in real time with every little change. Even worse, the patent landscape is littered with syncing algorithms owned by big names like Microsoft. (Interestingly, they published one algorithm to the world while not mentioning that they had it patented!) One false syncing step could turn into a nightmare.</p>
<p>Needless to say, we moved very carefully. Still, we are pleased to announce that we have developed a safe, proprietary syncing approach that allows Trog to remain responsive. The new sync approach and database are now largely in place and very exciting.</p>
<h3>Please, Predict the Future</h3>
<p>1. While much of the new approach has been coded, much has yet to be tested, and the size and scope of the conversion demand careful quality assurance. Things look good, but we don&#8217;t have a projected release date yet.</p>
<p>2. When we do release, the first benefits will be improved performance in nearly every area. Trog will load faster, use less memory, respond faster, search faster, handle huge task lists without blinking, and do everything else faster. (Size on the hard drive will increase a bit; that is the only impact.)</p>
<p>3. We will be integrating Trog Bar with more tools besides Outlook. We are also expanding our coaching offerings, and a <a title="Remember the Milk" href="http://www.rememberthemilk.com" target="_blank">Remember the Milk</a> version of the <a href="http://www.priacta.com/Training/Field_Guide.shtml">TRO Field Guide</a> is nearing completion. The goal is to make Trog Bar and the <a title="Self Training: Total, Relaxed Organization" href="http://www.priacta.com/Training/Self_Training.shtml">TRO Self Training System</a> available to a wider audience, including folks needing shared or online access to their tasks lists. (Don&#8217;t panic, we&#8217;re not abandoning Trog Bar! We&#8217;re actually allowing Trog Bar and TRO Self Training to embrace additional tools people already love.)</p>
<p>4. We&#8217;ve started a Trog Bar documentation/help project in response to user demand. This appears to be progressing quickly. We&#8217;ll be sure to announce when this is ready.</p>
<p>5. Usability and interface enhancements are planned to make Trog even more intuitive and stress-relieving.</p>
<p>6. We will, of course, fix the bugs that have been reported. Some bugs take longer than others, but as always we intend to zap them just as fast as we can hunt them down.</p>
<p>7. We&#8217;ve received very valuable feedback on the new Projects feature while it was in preview, and we will use what we learned to complete the feature with a dramatic boost in usability. Thank you to all who provided feedback, asked for clarification, or reported bugs!</p>
<h3>Getting the Updates</h3>
<p>The best way to get the updates is to get a <a title="Premium Registration for Trog Bar" href="http://www.priacta.com/catalog/product_info.php?products_id=40">Trog Bar Premium Registration</a>, which includes all feature upgrades for one year.</p>
<p>How will you know when we release? Keep Trog Bar configured for Automatic Updates, and you&#8217;ll always get the latest changes at the right time. New features will be released in Beta mode, so anyone running in Release mode will not be affected until the Trogger community gives its final stamp of approval.</p>
<p>You can check your Automatic Update settings by going to Windows Start &gt; Programs &gt; Trog Bar &gt; Configure Trog Bar Automatic Update. We recommend configuring it to check for updates daily.</p>
<p>Also, subscribe to this blog by clicking at top left for further announcements.</p>
<p>Stay tuned&#8230;</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/TrogTheBlog?a=Ei4cclbBWOg:51XDZMLjawg:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/TrogTheBlog?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/TrogTheBlog/~4/Ei4cclbBWOg" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.priacta.com/trogblog/2008/07/16/whats-cooking/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.priacta.com/trogblog/2008/07/16/whats-cooking/</feedburner:origLink></item>
		<item>
		<title>Getting Started with Natural Project Management</title>
		<link>http://feedproxy.google.com/~r/TrogTheBlog/~3/xP6RvMBn79E/</link>
		<comments>http://www.priacta.com/trogblog/2008/04/12/getting-started-with-natural-project-management/#comments</comments>
		<pubDate>Sat, 12 Apr 2008 23:22:25 +0000</pubDate>
		<dc:creator>Bug Slayer</dc:creator>
		
		<category><![CDATA[Beta and Preview Features]]></category>

		<category><![CDATA[Natural Project Management]]></category>

		<category><![CDATA[Trog Bar]]></category>

		<guid isPermaLink="false">http://www.priacta.com/trogblog/?p=5</guid>
		<description><![CDATA[<p><img style="float: right;" src="http://www.priacta.com/images/samplesteps.jpg" alt="Example of Steps in a Project" />The latest <a title="What is a Preview Feature?" href="http://www.priacta.com/trogblog/preview-and-beta-features/" target="_blank">Preview feature</a> in the Trog Bar is Natural Project Management. This slick tool will let you organize arbitrarily complex projects in bite sized pieces. Here is a brief overview that will get you started with this powerful new feature.</p>
<h4>It&#8217;s&#8230;</h4>]]></description>
			<content:encoded><![CDATA[<p><img style="float: right;" src="http://www.priacta.com/images/samplesteps.jpg" alt="Example of Steps in a Project" />The latest <a title="What is a Preview Feature?" href="http://www.priacta.com/trogblog/preview-and-beta-features/" target="_blank">Preview feature</a> in the Trog Bar is Natural Project Management. This slick tool will let you organize arbitrarily complex projects in bite sized pieces. Here is a brief overview that will get you started with this powerful new feature.</p>
<h4>It&#8217;s a Project!</h4>
<p>Your unprocessed list meets with numerous new arrivals every day. If you are among the blessed few, this number has only one digit, but if you are like me, or countless others, you net 20-100, maybe more. One of the basic tenets of GTD is the processing system, and one of the first questions you ask yourself when processing is &#8220;Is it a project?&#8221; Now, with the <a title="Description of the Trog Bar" href="http://www.priacta.com/trog">Trog Bar</a>, you can handle these projects better than ever.</p>
<p>When you meet one of these projects, flip open the &#8220;Steps&#8221; tab, and type in the next step, easy as that. Now for the awesome part: it works with emails too. When you get that email, just add a next step, and voilà! It&#8217;s a project!</p>
<h4>It&#8217;s a BIG Project!</h4>
<p>Every project should have one next action, and you should work only that action until it is done, so says GTD. Unfortunately, the reality on the ground is a little different. Especially in large projects, there may be many steps in a project that you <em>can</em> do, so there is no solid &#8220;next&#8221; step. There are in fact many possible next steps. Natural Project Management allows you to specify multiple steps as they occur to you. Any steps with no remaining prerequisites can be marked as &#8220;Ready&#8221; and will show a green circle next to them. These steps will appear in the various lists in the Trog Bar. The remainder should be left on hold, and will be hidden from your lists.</p>
<p>With Natural Project Management the &#8220;one project has one step&#8221; philosophy changes slightly. Each project must have <em>at least</em> one step, and at least one must be &#8220;Ready.&#8221; If a project has no remaining Ready steps, it will show in your unprocessed list.</p>
<h4>It Belongs to a New Project</h4>
<p>Even cooler, Natural Project Management has the ability to attach a task to a project that doesn&#8217;t exist yet. This works the same way as with categories. Just type in the name of the project, and when you save the task, the project will be created. This is an extremely powerful feature, and allows a new project to be created on the fly when you encounter a task that belongs to it.</p>
<h4>It Belongs to That One Project</h4>
<p>Believe it or not, adding a task to an existing project is even easier than adding it to a new project. As you type in the Projects field, Trog will match what you type against the list of known projects. If any possible matches are found, a list is presented, just like Outlook does with email addresses. When you see the project you want, hit enter and it will be selected. If that isn&#8217;t easy enough, you can hit the &#8220;Projects&#8221; button and select the project you want from a checklist of all your current projects.</p>
<h4>What else?</h4>
<p>There is much more that you can do with Natural Project Management, but this should be enough to get you started. Subscribe to the feed to be notified when we post more.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/TrogTheBlog?a=xP6RvMBn79E:8PjNSKxwYq8:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/TrogTheBlog?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/TrogTheBlog/~4/xP6RvMBn79E" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.priacta.com/trogblog/2008/04/12/getting-started-with-natural-project-management/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.priacta.com/trogblog/2008/04/12/getting-started-with-natural-project-management/</feedburner:origLink></item>
		<item>
		<title>Use New Features…Even Before the Beta</title>
		<link>http://feedproxy.google.com/~r/TrogTheBlog/~3/fzuwr52I2RQ/</link>
		<comments>http://www.priacta.com/trogblog/2008/04/10/use-new-featureseven-before-the-beta/#comments</comments>
		<pubDate>Fri, 11 Apr 2008 01:21:48 +0000</pubDate>
		<dc:creator>Bug Slayer</dc:creator>
		
		<category><![CDATA[Beta and Preview Features]]></category>

		<category><![CDATA[Development]]></category>

		<category><![CDATA[Trog Bar]]></category>

		<guid isPermaLink="false">http://www.priacta.com/trogblog/2008/04/10/use-new-featureseven-before-the-beta/</guid>
		<description><![CDATA[<p align="justify"><img style="margin-left: 10px; margin-bottom: 5px; float: right" src="http://www.priacta.com/images/enablebeta.jpg" border="0" alt="example of one of Google's features with a \" />A lot of software companies maintain development blogs. In fact, I'd venture to say that over 50% of GTD-related software providers have blogs. Until now, Priacta stubbornly ignored this trend, and for good reason. Why <strong>talk</strong> about the features, when we can let you <strong>use</strong> them? Maintaining a blog consumes time that could be spent creating features instead.</p>
<p align="justify">So why the change of heart? Ironically, it was a new feature!</p>]]></description>
			<content:encoded><![CDATA[<p align="justify"><img style="margin-left: 10px; margin-bottom: 5px; float: right" src="http://www.priacta.com/images/enablebeta.jpg" border="0" alt="example of one of Google's features with a \" />A lot of software companies maintain development blogs. In fact, I&#8217;d venture to say that over 50% of GTD-related software providers have blogs. Until now, Priacta stubbornly ignored this trend, and for a good reason. Why <strong>talk</strong> about the features, when we can let you <strong>use</strong> them? Maintaining a blog consumes time that could be spent creating features instead.</p>
<p align="justify">So why the change of heart? Ironically, it was a new feature!</p>
<p align="justify">We have been developing support for projects, which is no small task when you are bound to Outlook&#8217;s database. On the one hand, the project support works, and we are starting to use it internally. The feature is very useful, and we have received emails from many customers begging us to get it out there so they can use it. On the other hand, it is missing important functionality, has a number of known bugs that we aren&#8217;t really proud of, and we&#8217;re not sure we like the way it works in some places. In short, we do not think it is done, but folks are asking for it anyway. What do we do?</p>
<p align="justify">For a while it has been possible to dynamically enable &#8220;Beta Features.&#8221; This allows users to get access to new features and bug fixes while they are still in beta testing. Beta Features can be enabled on a whim from the options screen, and turned off without having to re-install. We recently realized however that we could do one better.</p>
<p align="justify">We&#8217;ve extended our existing Beta Features functionality to allow for &#8220;Preview Features.&#8221; Just as with Beta Features you can turn on these Preview Features at runtime. Unlike Beta Features, these are cutting edge, definitely <strong>not</strong> complete, and have a number of known unresolved issues; however, they are probably still very useful. Everything about a Preview Feature is a work in progress, and is highly negotiable. This means that Preview Features can change significantly and users can easily mold it by sharing their wants and needs with the developers. It also means that they don&#8217;t have to wait for the features to be released &#8220;someday.&#8221;</p>
<p align="justify"><img style="margin-left: 10px; margin-bottom: 5px; float: right" src="http://www.priacta.com/images/googlebeta.jpg" border="0" alt="example of one of Google's features with a \" />The concept of releasing functionality in early previews and betas is not new. Microsoft has done this with many of their products, most notably Vista and Orcas. Google allows you to turn on &#8220;experimental&#8221; search features, or occasionally tags functionality in their tools as &#8220;Beta.&#8221; Open source projects typically allow people to download the absolute latest code and build it themselves.</p>
<p align="justify">Each of these systems has its faults though. Microsoft requires you to download massive installers, and installing beta versions of Microsoft products usually causes problems when you get the real one, costing hours or days of time just to use the features early. Google makes it easy and seamless, but sometimes there is no way to &#8220;opt out&#8221; if the changes are giving you trouble, meaning it is really a released feature, with enough known bugs to put a &#8220;beta&#8221; tag on it. The SVN repository used by open source projects is so technical, that even hardened programmers will avoid it.</p>
<p align="justify">What we&#8217;ve done with the Trog Bar is combine the best of it all. The beta features come as easily and seamlessly as with Google&#8217;s variety. Like with Microsoft&#8217;s system, you can opt in or out, but unlike the Microsoft approach, this doesn&#8217;t require you to uninstall the beta version, and reinstall the normal one.</p>
<p align="justify">So we can deliver Previews Features with all the geeky benefits, congratulations to us, but why does this change the blog situation? It changes because now we don&#8217;t have to blog about the development of great new stuff we will give you <strong>someday</strong>. Instead we can blog about the development of great new stuff that you can <strong>already</strong> try. The blog ceases to be a hole to throw valuable development time into, and becomes a communication medium for discussing development of the latest thing in Trog.  So give it a shot, turn on Preview Features and take a look at our first one: Natural Project Management. Tell us what you like, and what you hate, what you want, and what you&#8217;d rather not have. Your feedback will shape the development of this, and other features.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/TrogTheBlog?a=fzuwr52I2RQ:HY2IGHZpB98:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/TrogTheBlog?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/TrogTheBlog/~4/fzuwr52I2RQ" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.priacta.com/trogblog/2008/04/10/use-new-featureseven-before-the-beta/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.priacta.com/trogblog/2008/04/10/use-new-featureseven-before-the-beta/</feedburner:origLink></item>
	</channel>
</rss>
