<?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: Make the Status Toolbar Work for You</title>
	<atom:link href="http://sixfriedrice.com/wp/make-the-status-toolbar-work-for-you/feed/" rel="self" type="application/rss+xml" />
	<link>http://sixfriedrice.com/wp/make-the-status-toolbar-work-for-you/</link>
	<description>smart business solutions</description>
	<lastBuildDate>Mon, 01 Mar 2010 04:42:36 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Frank</title>
		<link>http://sixfriedrice.com/wp/make-the-status-toolbar-work-for-you/comment-page-1/#comment-1830</link>
		<dc:creator>Frank</dc:creator>
		<pubDate>Fri, 07 Aug 2009 03:43:45 +0000</pubDate>
		<guid isPermaLink="false">http://sixfriedrice.com/wp/make-the-status-toolbar-work-for-you/#comment-1830</guid>
		<description>I find the new status tool bar a BIG disappointment!   It is only half baked.  If I upgrade to FM10, then I have to redesign all my layouts.  Filemaker should have given developers the option to keep the status bar on the left side or the top.  This way we could slowly integrate the new design into older layouts.  Furthermore, we should the ability to add custom buttons with scripts to the status bar.  Makes more real estate available in the layout.</description>
		<content:encoded><![CDATA[<p>I find the new status tool bar a BIG disappointment!   It is only half baked.  If I upgrade to FM10, then I have to redesign all my layouts.  Filemaker should have given developers the option to keep the status bar on the left side or the top.  This way we could slowly integrate the new design into older layouts.  Furthermore, we should the ability to add custom buttons with scripts to the status bar.  Makes more real estate available in the layout.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hans J. Gunnarsson</title>
		<link>http://sixfriedrice.com/wp/make-the-status-toolbar-work-for-you/comment-page-1/#comment-1734</link>
		<dc:creator>Hans J. Gunnarsson</dc:creator>
		<pubDate>Fri, 20 Mar 2009 21:17:34 +0000</pubDate>
		<guid isPermaLink="false">http://sixfriedrice.com/wp/make-the-status-toolbar-work-for-you/#comment-1734</guid>
		<description>For deployment of solutions this is not totally bad. But a great number of the windows I create are to narrow to make any use of the new position.

And during development while creating customized solutions I&#039;d rather prefer a floating palette a la Word and Omnigraffle. It is about time that FMI delivers a unified UI for FM Advanced.</description>
		<content:encoded><![CDATA[<p>For deployment of solutions this is not totally bad. But a great number of the windows I create are to narrow to make any use of the new position.</p>
<p>And during development while creating customized solutions I&#8217;d rather prefer a floating palette a la Word and Omnigraffle. It is about time that FMI delivers a unified UI for FM Advanced.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Rosen</title>
		<link>http://sixfriedrice.com/wp/make-the-status-toolbar-work-for-you/comment-page-1/#comment-1674</link>
		<dc:creator>Jon Rosen</dc:creator>
		<pubDate>Wed, 11 Feb 2009 19:22:35 +0000</pubDate>
		<guid isPermaLink="false">http://sixfriedrice.com/wp/make-the-status-toolbar-work-for-you/#comment-1674</guid>
		<description>You are correct that through custom menus we can prevent damage from use of buttons on the status bar. It&#039;s still close to useless, in my opinion. I wish that FMI left it alone until they were ready to deploy useful changes. It&#039;s user-definable, so the developer can&#039;t even present a consistent view. The new record selector uses up a lot of space and is less elegant than the old &quot;rolodex&quot; style selector. The only thing I might want to use it for in its current incarnation is for report printing (Continue button), but I might switch to a different approach. I consider this feature change a total failure until FMI does a lot more work on it.</description>
		<content:encoded><![CDATA[<p>You are correct that through custom menus we can prevent damage from use of buttons on the status bar. It&#8217;s still close to useless, in my opinion. I wish that FMI left it alone until they were ready to deploy useful changes. It&#8217;s user-definable, so the developer can&#8217;t even present a consistent view. The new record selector uses up a lot of space and is less elegant than the old &#8220;rolodex&#8221; style selector. The only thing I might want to use it for in its current incarnation is for report printing (Continue button), but I might switch to a different approach. I consider this feature change a total failure until FMI does a lot more work on it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Piers Dunkley</title>
		<link>http://sixfriedrice.com/wp/make-the-status-toolbar-work-for-you/comment-page-1/#comment-1560</link>
		<dc:creator>Piers Dunkley</dc:creator>
		<pubDate>Wed, 21 Jan 2009 23:12:32 +0000</pubDate>
		<guid isPermaLink="false">http://sixfriedrice.com/wp/make-the-status-toolbar-work-for-you/#comment-1560</guid>
		<description>When I first opened FM 10 I was completely lost without the status area.
I clicked the icon to open it and nothing happened, or didn&#039;t appear to happen. And then I raised my eyes. And there it was.
Much better than the old one , and with the tips you have given, much mire flexible</description>
		<content:encoded><![CDATA[<p>When I first opened FM 10 I was completely lost without the status area.<br />
I clicked the icon to open it and nothing happened, or didn&#8217;t appear to happen. And then I raised my eyes. And there it was.<br />
Much better than the old one , and with the tips you have given, much mire flexible</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Denis</title>
		<link>http://sixfriedrice.com/wp/make-the-status-toolbar-work-for-you/comment-page-1/#comment-1553</link>
		<dc:creator>Denis</dc:creator>
		<pubDate>Tue, 20 Jan 2009 14:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://sixfriedrice.com/wp/make-the-status-toolbar-work-for-you/#comment-1553</guid>
		<description>Geoff,  This is a wonderful tip on how to rename some of the Status Toolbar buttons and tie them into the scripted functionality we want.  

The Toolbar is a tremendous move in the right direction but is still only half-baked because it can not be fully modified and gives developers only half of what they have been looking for in terms of a more standard, thus more familiar, centralized way to manage the look, feel, and operation of a database.  Your steps give me some hope on how to redefine my current development style but I still find myself hindered rather than empowered as a developer.  Nonetheless, keep up the great work!</description>
		<content:encoded><![CDATA[<p>Geoff,  This is a wonderful tip on how to rename some of the Status Toolbar buttons and tie them into the scripted functionality we want.  </p>
<p>The Toolbar is a tremendous move in the right direction but is still only half-baked because it can not be fully modified and gives developers only half of what they have been looking for in terms of a more standard, thus more familiar, centralized way to manage the look, feel, and operation of a database.  Your steps give me some hope on how to redefine my current development style but I still find myself hindered rather than empowered as a developer.  Nonetheless, keep up the great work!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geoff Coffey</title>
		<link>http://sixfriedrice.com/wp/make-the-status-toolbar-work-for-you/comment-page-1/#comment-1540</link>
		<dc:creator>Geoff Coffey</dc:creator>
		<pubDate>Sat, 17 Jan 2009 15:28:09 +0000</pubDate>
		<guid isPermaLink="false">http://sixfriedrice.com/wp/make-the-status-toolbar-work-for-you/#comment-1540</guid>
		<description>Stephen:

My vague recollection is that this dialog box only shows if the user has permission to edit the layout, so it may not be as bad as it seems. I will test this and report back.

Geoff</description>
		<content:encoded><![CDATA[<p>Stephen:</p>
<p>My vague recollection is that this dialog box only shows if the user has permission to edit the layout, so it may not be as bad as it seems. I will test this and report back.</p>
<p>Geoff</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Dolenski</title>
		<link>http://sixfriedrice.com/wp/make-the-status-toolbar-work-for-you/comment-page-1/#comment-1539</link>
		<dc:creator>Stephen Dolenski</dc:creator>
		<pubDate>Sat, 17 Jan 2009 10:11:04 +0000</pubDate>
		<guid isPermaLink="false">http://sixfriedrice.com/wp/make-the-status-toolbar-work-for-you/#comment-1539</guid>
		<description>Thank you Geoff for your article. Another note to be aware of is now that the view menu (form; list; table) is as you say &quot;front and center&quot; it makes it more critical to disable views on that layout you don&#039;t intend the user to switch, when pressed in a multi-user environment you are presented with a dialog box &quot;Do you wish to save this change with the layout?&quot; 

If the user chooses YES then the setting will be set be accepted as the layout&#039;s default view - and instantly cause all other users currently on that layout to have their screens update to reflect this new setting, if they are in the process of editing a record as soon as they exit it will update.

The layout default should be a check box in the layout setup and the dialog box should be eliminated, it&#039;s a pity there isn&#039;t a trigger that can execute your script on view change, then developers could use the handy buttons instead of adding their own on layouts.</description>
		<content:encoded><![CDATA[<p>Thank you Geoff for your article. Another note to be aware of is now that the view menu (form; list; table) is as you say &#8220;front and center&#8221; it makes it more critical to disable views on that layout you don&#8217;t intend the user to switch, when pressed in a multi-user environment you are presented with a dialog box &#8220;Do you wish to save this change with the layout?&#8221; </p>
<p>If the user chooses YES then the setting will be set be accepted as the layout&#8217;s default view &#8211; and instantly cause all other users currently on that layout to have their screens update to reflect this new setting, if they are in the process of editing a record as soon as they exit it will update.</p>
<p>The layout default should be a check box in the layout setup and the dialog box should be eliminated, it&#8217;s a pity there isn&#8217;t a trigger that can execute your script on view change, then developers could use the handy buttons instead of adding their own on layouts.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
