<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: OT:What makes a good interface? in Modeling</title>
    <link>https://community.graphisoft.com/t5/Modeling/OT-What-makes-a-good-interface/m-p/28610#M14116</link>
    <description>Yeah, you… Big Nose.</description>
    <pubDate>Wed, 12 Jul 2006 05:40:52 GMT</pubDate>
    <dc:creator>Dwight</dc:creator>
    <dc:date>2006-07-12T05:40:52Z</dc:date>
    <item>
      <title>OT:What makes a good interface?</title>
      <link>https://community.graphisoft.com/t5/Modeling/OT-What-makes-a-good-interface/m-p/28603#M14109</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;A good interface is…&lt;BR /&gt;
&lt;BR /&gt;
-- one that responds to the way I think.&lt;BR /&gt;
&lt;BR /&gt;
-- one that makes ANYTHING happen in ONE CLICK &lt;BR /&gt;
[If I can buy a book at amazon with one click…?]&lt;BR /&gt;
&lt;BR /&gt;
-- one that…&lt;BR /&gt;
&lt;BR /&gt;
Your turn.&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 11 Jul 2006 22:26:59 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/OT-What-makes-a-good-interface/m-p/28603#M14109</guid>
      <dc:creator>Dwight</dc:creator>
      <dc:date>2006-07-11T22:26:59Z</dc:date>
    </item>
    <item>
      <title>Re: OT:What makes a good interface?</title>
      <link>https://community.graphisoft.com/t5/Modeling/OT-What-makes-a-good-interface/m-p/28604#M14110</link>
      <description>&lt;BLOCKQUOTE&gt;Dwight wrote:&lt;BR /&gt;-- one that…&lt;/BLOCKQUOTE&gt;
. . . teaches me those aspects of the application that i don't already know by clearly, &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;intuitively&lt;E&gt;&lt;/E&gt; and consistently demonstrating &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;process&lt;E&gt;&lt;/E&gt;.&lt;BR /&gt;
&lt;BR /&gt;
an' it's gotta look good too.&lt;BR /&gt;
&lt;BR /&gt;
~/archiben</description>
      <pubDate>Tue, 11 Jul 2006 22:34:58 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/OT-What-makes-a-good-interface/m-p/28604#M14110</guid>
      <dc:creator>__archiben</dc:creator>
      <dc:date>2006-07-11T22:34:58Z</dc:date>
    </item>
    <item>
      <title>Re: OT:What makes a good interface?</title>
      <link>https://community.graphisoft.com/t5/Modeling/OT-What-makes-a-good-interface/m-p/28605#M14111</link>
      <description>..is not overwhelming, and designed by a team that believes in the beauty of simplicity. (sketchup)&lt;BR /&gt;
&lt;BR /&gt;
..can get out of the way when you need it to(photoshop/indesign)&lt;BR /&gt;
&lt;BR /&gt;
..is 100% customizable (Cinema 4D)</description>
      <pubDate>Wed, 12 Jul 2006 01:13:46 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/OT-What-makes-a-good-interface/m-p/28605#M14111</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2006-07-12T01:13:46Z</dc:date>
    </item>
    <item>
      <title>Re: OT:What makes a good interface?</title>
      <link>https://community.graphisoft.com/t5/Modeling/OT-What-makes-a-good-interface/m-p/28606#M14112</link>
      <description>The common tasks are easy, obvious and immediately available.&lt;BR /&gt;
&lt;BR /&gt;
It is set up to work properly and sensibly out of the box.&lt;BR /&gt;
&lt;BR /&gt;
Less common tasks are made available in a layered and logical structure. That is they may take a little more work but that work is promptly rewarded.&lt;BR /&gt;
&lt;BR /&gt;
Really complex tasks and advanced customization is supported by robust management tools.&lt;BR /&gt;
&lt;BR /&gt;
As much as possible everything is self documented.</description>
      <pubDate>Wed, 12 Jul 2006 05:08:30 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/OT-What-makes-a-good-interface/m-p/28606#M14112</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2006-07-12T05:08:30Z</dc:date>
    </item>
    <item>
      <title>Re: OT:What makes a good interface?</title>
      <link>https://community.graphisoft.com/t5/Modeling/OT-What-makes-a-good-interface/m-p/28607#M14113</link>
      <description>"Robust." &lt;BR /&gt;
&lt;BR /&gt;
That is us.&lt;BR /&gt;
A bunch of sissies at keyboards.</description>
      <pubDate>Wed, 12 Jul 2006 05:21:00 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/OT-What-makes-a-good-interface/m-p/28607#M14113</guid>
      <dc:creator>Dwight</dc:creator>
      <dc:date>2006-07-12T05:21:00Z</dc:date>
    </item>
    <item>
      <title>Re: OT:What makes a good interface?</title>
      <link>https://community.graphisoft.com/t5/Modeling/OT-What-makes-a-good-interface/m-p/28608#M14114</link>
      <description>one that...&lt;BR /&gt;
Maximizes the drawing window and doesn't look like a windshield with a dozen or so parking violations glued to the glass.</description>
      <pubDate>Wed, 12 Jul 2006 05:25:13 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/OT-What-makes-a-good-interface/m-p/28608#M14114</guid>
      <dc:creator>David Collins</dc:creator>
      <dc:date>2006-07-12T05:25:13Z</dc:date>
    </item>
    <item>
      <title>Re: OT:What makes a good interface?</title>
      <link>https://community.graphisoft.com/t5/Modeling/OT-What-makes-a-good-interface/m-p/28609#M14115</link>
      <description>&lt;BLOCKQUOTE&gt;Dwight wrote:&lt;BR /&gt;"Robust." &lt;BR /&gt;
&lt;BR /&gt;
That is us.&lt;BR /&gt;
A bunch of sissies at keyboards.&lt;/BLOCKQUOTE&gt;

Who you callin' a tool?</description>
      <pubDate>Wed, 12 Jul 2006 05:38:46 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/OT-What-makes-a-good-interface/m-p/28609#M14115</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2006-07-12T05:38:46Z</dc:date>
    </item>
    <item>
      <title>Re: OT:What makes a good interface?</title>
      <link>https://community.graphisoft.com/t5/Modeling/OT-What-makes-a-good-interface/m-p/28610#M14116</link>
      <description>Yeah, you… Big Nose.</description>
      <pubDate>Wed, 12 Jul 2006 05:40:52 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/OT-What-makes-a-good-interface/m-p/28610#M14116</guid>
      <dc:creator>Dwight</dc:creator>
      <dc:date>2006-07-12T05:40:52Z</dc:date>
    </item>
    <item>
      <title>Re: OT:What makes a good interface?</title>
      <link>https://community.graphisoft.com/t5/Modeling/OT-What-makes-a-good-interface/m-p/28611#M14117</link>
      <description>one that allows you to get out of the way, once you know your way around the system.&lt;BR /&gt;
&lt;BR /&gt;
--&amp;gt; efficient commands that are attached to a nice set of keyboard shortcuts.&lt;BR /&gt;
&lt;BR /&gt;
--&amp;gt; dock pallettes if you like, float them if you like, hide them if you like. Don't force one GUI system on us.&lt;BR /&gt;
&lt;BR /&gt;
--&amp;gt; no modal dialogs: keep the rest of the application accessible when you are editing items in dialogs&lt;BR /&gt;
&lt;BR /&gt;
--&amp;gt; provide plenty of space for the work area. With the return to lower resolutions (websites, laptops, etc...) we can not work comfortably in 1600x1200 anymore. My old CRT monitor can do this, but not my new and clean flatscreen... (typing on 1280x854 now)&lt;BR /&gt;
&lt;BR /&gt;
--&amp;gt; make the Windows version feel and look like Windows and the Mac version feel and look like a real Mac version</description>
      <pubDate>Wed, 12 Jul 2006 12:15:53 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/OT-What-makes-a-good-interface/m-p/28611#M14117</guid>
      <dc:creator>stefan</dc:creator>
      <dc:date>2006-07-12T12:15:53Z</dc:date>
    </item>
    <item>
      <title>Re: OT:What makes a good interface?</title>
      <link>https://community.graphisoft.com/t5/Modeling/OT-What-makes-a-good-interface/m-p/28612#M14118</link>
      <description>&lt;BLOCKQUOTE&gt;Dwight wrote:&lt;BR /&gt;-- one that…&lt;/BLOCKQUOTE&gt;

is consistent. What works here works there. This Working is a subset of the platform/OS UI. So internally and externally consistent.&lt;BR /&gt;
&lt;BR /&gt;
Nothing OT about it.</description>
      <pubDate>Wed, 12 Jul 2006 12:33:47 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/OT-What-makes-a-good-interface/m-p/28612#M14118</guid>
      <dc:creator>James Murray</dc:creator>
      <dc:date>2006-07-12T12:33:47Z</dc:date>
    </item>
    <item>
      <title>Re: OT:What makes a good interface?</title>
      <link>https://community.graphisoft.com/t5/Modeling/OT-What-makes-a-good-interface/m-p/28613#M14119</link>
      <description>-With all the options text and icons big enough so you can see them, and small enough so you don't have to scroll too much &lt;BR /&gt;
-allowing to create layouts for different tasks that I can switch in a fly (different for DD, CD, presentation, modeling etc, ...)</description>
      <pubDate>Wed, 12 Jul 2006 18:24:21 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/OT-What-makes-a-good-interface/m-p/28613#M14119</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2006-07-12T18:24:21Z</dc:date>
    </item>
  </channel>
</rss>

