<?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: Major bitch Robert</title>
	<atom:link href="http://habitablezone.com/2012/05/02/major-bitch-robert/feed/" rel="self" type="application/rss+xml" />
	<link>https://habitablezone.com/2012/05/02/major-bitch-robert/</link>
	<description></description>
	<lastBuildDate>Fri, 03 Apr 2026 22:41:18 -0700</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Robert</title>
		<link>https://habitablezone.com/2012/05/02/major-bitch-robert/#comment-14652</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Wed, 02 May 2012 18:45:39 +0000</pubDate>
		<guid isPermaLink="false">http://habitablezone.net/?p=14568#comment-14652</guid>
		<description>For want of a comma...

I understand your complaint, though. This software is heavily adapted from WordPress, and the most awkward part of the adaptation is continuing to use admin pages from the WordPress dashboard for ordinary poster tasks like composing and editing. Sucks big time, on that we can agree.

You can make the cramped overlay window a little roomier, if you haven&#039;t already, by clicking the top-right &quot;Screen options&quot; link and selecting a one-column layout. Also, the various blocks on that page are draggable, and you can rearrange the order so that the handful you use all the time are at the top: The editor, the excerpt, the control panel (&quot;Publish&quot; button).

Long term I intend to get rid of the dashboard, for everybody but me and podrock, and integrate the stuff you need right into the user interface. In the UI of my imagination, all editors are integrated into the page the way the new-comment editor is integrated. No more floating overlay windows. The latest version of WordPress added a modular WYSIWYG editor, and so finally I&#039;ll be able to give you rich text on comments as well as posts.

You have a netbook, eh? I just got a Samsung tablet, 1024x600 screen. My business reason for getting it is to start designing UIs to work on screens that small. What I&#039;m seeing is that the small devices use more of a &quot;kiosk&quot; design philosophy than the classic &quot;GUI&quot; we&#039;ve been using for three decades. You generally only see one thing on the screen at a time, and spend a lot of time moving from panel to panel. It won&#039;t be easy shoehorning a forum into that environment, but I&#039;ve been playing with it. This is just playing around, but how about some feedback?
&lt;img src=&quot;http://habitablezone.com/wp-content/uploads/2012/05/uix-cap-tab.jpg&quot; /&gt;
</description>
		<content:encoded><![CDATA[<p>For want of a comma&#8230;</p>
<p>I understand your complaint, though. This software is heavily adapted from WordPress, and the most awkward part of the adaptation is continuing to use admin pages from the WordPress dashboard for ordinary poster tasks like composing and editing. Sucks big time, on that we can agree.</p>
<p>You can make the cramped overlay window a little roomier, if you haven&#8217;t already, by clicking the top-right &#8220;Screen options&#8221; link and selecting a one-column layout. Also, the various blocks on that page are draggable, and you can rearrange the order so that the handful you use all the time are at the top: The editor, the excerpt, the control panel (&#8220;Publish&#8221; button).</p>
<p>Long term I intend to get rid of the dashboard, for everybody but me and podrock, and integrate the stuff you need right into the user interface. In the UI of my imagination, all editors are integrated into the page the way the new-comment editor is integrated. No more floating overlay windows. The latest version of WordPress added a modular WYSIWYG editor, and so finally I&#8217;ll be able to give you rich text on comments as well as posts.</p>
<p>You have a netbook, eh? I just got a Samsung tablet, 1024&#215;600 screen. My business reason for getting it is to start designing UIs to work on screens that small. What I&#8217;m seeing is that the small devices use more of a &#8220;kiosk&#8221; design philosophy than the classic &#8220;GUI&#8221; we&#8217;ve been using for three decades. You generally only see one thing on the screen at a time, and spend a lot of time moving from panel to panel. It won&#8217;t be easy shoehorning a forum into that environment, but I&#8217;ve been playing with it. This is just playing around, but how about some feedback?<br />
<img src="http://habitablezone.com/wp-content/uploads/2012/05/uix-cap-tab.jpg" /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TB</title>
		<link>https://habitablezone.com/2012/05/02/major-bitch-robert/#comment-14650</link>
		<dc:creator>TB</dc:creator>
		<pubDate>Wed, 02 May 2012 17:55:36 +0000</pubDate>
		<guid isPermaLink="false">http://habitablezone.net/?p=14568#comment-14650</guid>
		<description>&lt;p&gt;I don&#039;t use the title line.&lt;/p&gt;

I&#039;m still using the paragraph markers, but now when I put them in, the comment doesn&#039;t accept them at the first posting and I have to edit them in afterwards.

This is just my personal idiosyncracy, because I read comments a lot at the dashboard interface, and the title lines don&#039;t show up there.  I can work with it, and don&#039;t see any reason to change it from its current new format.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t use the title line.</p>
<p>I&#8217;m still using the paragraph markers, but now when I put them in, the comment doesn&#8217;t accept them at the first posting and I have to edit them in afterwards.</p>
<p>This is just my personal idiosyncracy, because I read comments a lot at the dashboard interface, and the title lines don&#8217;t show up there.  I can work with it, and don&#8217;t see any reason to change it from its current new format.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RobVG</title>
		<link>https://habitablezone.com/2012/05/02/major-bitch-robert/#comment-14651</link>
		<dc:creator>RobVG</dc:creator>
		<pubDate>Wed, 02 May 2012 17:55:36 +0000</pubDate>
		<guid isPermaLink="false">http://habitablezone.net/?p=14568#comment-14651</guid>
		<description>Maybe we&#039;re saying the same thing.  n/t</description>
		<content:encoded><![CDATA[<p>Maybe we&#8217;re saying the same thing.  n/t</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RobVG</title>
		<link>https://habitablezone.com/2012/05/02/major-bitch-robert/#comment-14649</link>
		<dc:creator>RobVG</dc:creator>
		<pubDate>Wed, 02 May 2012 17:51:35 +0000</pubDate>
		<guid isPermaLink="false">http://habitablezone.net/?p=14568#comment-14649</guid>
		<description>You get a space for a title line and a non-cluttered well placed textbox to type the body of the comment. 

But the comment &lt;strong&gt;edit&lt;/strong&gt; window is the same as &quot;Start new topic&quot;.</description>
		<content:encoded><![CDATA[<p>You get a space for a title line and a non-cluttered well placed textbox to type the body of the comment. </p>
<p>But the comment <strong>edit</strong> window is the same as &#8220;Start new topic&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TB</title>
		<link>https://habitablezone.com/2012/05/02/major-bitch-robert/#comment-14648</link>
		<dc:creator>TB</dc:creator>
		<pubDate>Wed, 02 May 2012 17:29:45 +0000</pubDate>
		<guid isPermaLink="false">http://habitablezone.net/?p=14568#comment-14648</guid>
		<description>&lt;p&gt;It always does that for comments.&lt;/p&gt;

I have gotten used to the fact that I have to post a comment, then fix the completed comment in the more robust edit mode for errors, format issues, and adding graphics.

I think Robert is working on that, but adding robust editing to the top level isn&#039;t going to be easy.</description>
		<content:encoded><![CDATA[<p>It always does that for comments.</p>
<p>I have gotten used to the fact that I have to post a comment, then fix the completed comment in the more robust edit mode for errors, format issues, and adding graphics.</p>
<p>I think Robert is working on that, but adding robust editing to the top level isn&#8217;t going to be easy.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
