<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: gpk-log crap UI</title>
	<link>http://blogs.gnome.org/hughsie/2008/04/17/223/</link>
	<description>My fiancee is like Windows Vista: Looks pretty, difficult to understand and sometimes unpredictable...</description>
	<pubDate>Sun, 06 Jul 2008 16:29:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Rob J. Caskey</title>
		<link>http://blogs.gnome.org/hughsie/2008/04/17/223/#comment-214</link>
		<dc:creator>Rob J. Caskey</dc:creator>
		<pubDate>Mon, 21 Apr 2008 15:14:17 +0000</pubDate>
		<guid>http://blogs.gnome.org/hughsie/2008/04/17/223/#comment-214</guid>
		<description>Thoughts:

* I'd really like to be able to see a per-package history by clicking on the package names and then be able to initiate a rollback of that package along with the required changes.
* Horizontal scrolling is ebil, use an expander widget, ellipses, grow rows vertically, anything.
* Can we include time as part of the heading for days that have multiple installation events?
* The vertical scroll-bar is already a time-line, no need to complicate.
* I'd like user-readable names instead of package names, even though they are longer (as we can see even the package names are already too long).
* We know deep down in our hearts that a search widget belongs here that will search by user visible description, actual package name, etc!</description>
		<content:encoded><![CDATA[<p>Thoughts:</p>
<p>* I&#8217;d really like to be able to see a per-package history by clicking on the package names and then be able to initiate a rollback of that package along with the required changes.<br />
* Horizontal scrolling is ebil, use an expander widget, ellipses, grow rows vertically, anything.<br />
* Can we include time as part of the heading for days that have multiple installation events?<br />
* The vertical scroll-bar is already a time-line, no need to complicate.<br />
* I&#8217;d like user-readable names instead of package names, even though they are longer (as we can see even the package names are already too long).<br />
* We know deep down in our hearts that a search widget belongs here that will search by user visible description, actual package name, etc!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Technical Blog of Richard Hughes &#187; Blog Archive &#187; gpk-log improvements</title>
		<link>http://blogs.gnome.org/hughsie/2008/04/17/223/#comment-204</link>
		<dc:creator>Technical Blog of Richard Hughes &#187; Blog Archive &#187; gpk-log improvements</dc:creator>
		<pubDate>Mon, 21 Apr 2008 12:44:01 +0000</pubDate>
		<guid>http://blogs.gnome.org/hughsie/2008/04/17/223/#comment-204</guid>
		<description>[...] to the old log viewer, I think this one is much [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] to the old log viewer, I think this one is much [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Remm</title>
		<link>http://blogs.gnome.org/hughsie/2008/04/17/223/#comment-191</link>
		<dc:creator>Remm</dc:creator>
		<pubDate>Fri, 18 Apr 2008 13:43:01 +0000</pubDate>
		<guid>http://blogs.gnome.org/hughsie/2008/04/17/223/#comment-191</guid>
		<description>Well, I wish the pup/pirut folks had the same dedication towards producing good UIs. I think this history UI addition is very useful, and nice enough as is.</description>
		<content:encoded><![CDATA[<p>Well, I wish the pup/pirut folks had the same dedication towards producing good UIs. I think this history UI addition is very useful, and nice enough as is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nils Philippsen</title>
		<link>http://blogs.gnome.org/hughsie/2008/04/17/223/#comment-186</link>
		<dc:creator>Nils Philippsen</dc:creator>
		<pubDate>Fri, 18 Apr 2008 07:50:40 +0000</pubDate>
		<guid>http://blogs.gnome.org/hughsie/2008/04/17/223/#comment-186</guid>
		<description>I've two suggestions:

1) Don't put individual package updates and system updates on the same level, e.g. use a (by default unexpanded) tree where the system updates are on the first level and the package updates they comprise on a second level.

2) Avoid "anonymous" package update entries, I'm surely not going to click on dozens of equally looking "Updated package" entries to find the one I'm interested in.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve two suggestions:</p>
<p>1) Don&#8217;t put individual package updates and system updates on the same level, e.g. use a (by default unexpanded) tree where the system updates are on the first level and the package updates they comprise on a second level.</p>
<p>2) Avoid &#8220;anonymous&#8221; package update entries, I&#8217;m surely not going to click on dozens of equally looking &#8220;Updated package&#8221; entries to find the one I&#8217;m interested in.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nils Philippsen</title>
		<link>http://blogs.gnome.org/hughsie/2008/04/17/223/#comment-185</link>
		<dc:creator>Nils Philippsen</dc:creator>
		<pubDate>Fri, 18 Apr 2008 07:43:45 +0000</pubDate>
		<guid>http://blogs.gnome.org/hughsie/2008/04/17/223/#comment-185</guid>
		<description>Well, an package updated is surely a part if a system having been updated, so maybe a light-weight tree is helpful, i.e. system updates at the root and package updates on the next level. I'd also find it helpful if  the list contained what package was updated -- dozens of entries all looking alike aren't really inviting. I won't click on all of them to find out what was being updated ;-).</description>
		<content:encoded><![CDATA[<p>Well, an package updated is surely a part if a system having been updated, so maybe a light-weight tree is helpful, i.e. system updates at the root and package updates on the next level. I&#8217;d also find it helpful if  the list contained what package was updated &#8212; dozens of entries all looking alike aren&#8217;t really inviting. I won&#8217;t click on all of them to find out what was being updated ;-).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jtin</title>
		<link>http://blogs.gnome.org/hughsie/2008/04/17/223/#comment-184</link>
		<dc:creator>jtin</dc:creator>
		<pubDate>Fri, 18 Apr 2008 03:11:42 +0000</pubDate>
		<guid>http://blogs.gnome.org/hughsie/2008/04/17/223/#comment-184</guid>
		<description>Use a single tree view instead of two lists?</description>
		<content:encoded><![CDATA[<p>Use a single tree view instead of two lists?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: reinouts</title>
		<link>http://blogs.gnome.org/hughsie/2008/04/17/223/#comment-183</link>
		<dc:creator>reinouts</dc:creator>
		<pubDate>Thu, 17 Apr 2008 22:45:32 +0000</pubDate>
		<guid>http://blogs.gnome.org/hughsie/2008/04/17/223/#comment-183</guid>
		<description>Thought about a timeline widget?</description>
		<content:encoded><![CDATA[<p>Thought about a timeline widget?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: triton</title>
		<link>http://blogs.gnome.org/hughsie/2008/04/17/223/#comment-182</link>
		<dc:creator>triton</dc:creator>
		<pubDate>Thu, 17 Apr 2008 20:09:31 +0000</pubDate>
		<guid>http://blogs.gnome.org/hughsie/2008/04/17/223/#comment-182</guid>
		<description>The icons are TOO big!</description>
		<content:encoded><![CDATA[<p>The icons are TOO big!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: adamc</title>
		<link>http://blogs.gnome.org/hughsie/2008/04/17/223/#comment-181</link>
		<dc:creator>adamc</dc:creator>
		<pubDate>Thu, 17 Apr 2008 18:00:39 +0000</pubDate>
		<guid>http://blogs.gnome.org/hughsie/2008/04/17/223/#comment-181</guid>
		<description>I would put the package name next to the updated text, like this:
"Updated package glib2-debuginfo"

Also, I would hide the details using a GtkExpander (I think thats what its called, the one that can be hidden with a little triangle widget to show/hide).

This would leave the important information always viewable, what was updated and when, with more information like the version hidden from view but easily accessible.

You could also consider putting the version number in the main update text as well like this:
"Updated package glib2-debuginfo to 2.16.3-3-fc9"</description>
		<content:encoded><![CDATA[<p>I would put the package name next to the updated text, like this:<br />
&#8220;Updated package glib2-debuginfo&#8221;</p>
<p>Also, I would hide the details using a GtkExpander (I think thats what its called, the one that can be hidden with a little triangle widget to show/hide).</p>
<p>This would leave the important information always viewable, what was updated and when, with more information like the version hidden from view but easily accessible.</p>
<p>You could also consider putting the version number in the main update text as well like this:<br />
&#8220;Updated package glib2-debuginfo to 2.16.3-3-fc9&#8243;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mpt</title>
		<link>http://blogs.gnome.org/hughsie/2008/04/17/223/#comment-180</link>
		<dc:creator>mpt</dc:creator>
		<pubDate>Thu, 17 Apr 2008 16:26:19 +0000</pubDate>
		<guid>http://blogs.gnome.org/hughsie/2008/04/17/223/#comment-180</guid>
		<description>Low level:
* Imitate Epiphany's History window. Get rid of the "Help" and "Close" buttons (perhaps have a menu bar instead), and get rid of the padding between the lists and the edges of the window.
* Figure out what's causing the bottom list to have a horizontal scrollbar, and fix it.

Medium level:
* What are you trying to show here? I can't tell. If this is a history of past updates, why isn't there a Date column?
* What do the new-page icons mean?
* Would it make more sense to arrange the lists horizontally?
* Would it make more sense to have one list with expandable sections?

Toolkit/Theme level:
* Persuade whoever's responsible to stop putting a silly gap between a scrollbar and the list being scrolled.</description>
		<content:encoded><![CDATA[<p>Low level:<br />
* Imitate Epiphany&#8217;s History window. Get rid of the &#8220;Help&#8221; and &#8220;Close&#8221; buttons (perhaps have a menu bar instead), and get rid of the padding between the lists and the edges of the window.<br />
* Figure out what&#8217;s causing the bottom list to have a horizontal scrollbar, and fix it.</p>
<p>Medium level:<br />
* What are you trying to show here? I can&#8217;t tell. If this is a history of past updates, why isn&#8217;t there a Date column?<br />
* What do the new-page icons mean?<br />
* Would it make more sense to arrange the lists horizontally?<br />
* Would it make more sense to have one list with expandable sections?</p>
<p>Toolkit/Theme level:<br />
* Persuade whoever&#8217;s responsible to stop putting a silly gap between a scrollbar and the list being scrolled.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
