On Thu, 2006-12-14 at 22:37 +0100, Werner Hoch wrote:
> Hi Peter,
> 
> On Thursday 14 December 2006 22:15, Peter Clifton wrote:
> > I'm not running the very latest CVS, so don't have the new
> > auto-number
> 
> I inserted URLs to the screenshots of the three dialogs:

So you did... sorry. I clicked on the wiki link expecting to see
pictures (didn't), then opened gschem.

Comments:
(I'm being micro-critical for the sake of being a helpful reviewer, I
 realise many of these points are very cosmetic and minor.)

Component selector
------------------

** I know you didn't mention this one, but I wanted to add it **

Lovely new dialog, could perhaps do with a _little_ more padding around
its border and buttons. There are a few bigger usability changes which
could be made though:

Remember the size between uses. Possibly default to a larger default
size.

Text entry defaults to the tree-view, which invokes GTK's new annoying
search helper. The tree is collapsed, so nothing useful is found. I
think default text entry should be on / grabbed by the Filter entry.

The filter entry would benefit from being a libsexy entry too.. Having
the clear icon inside the entry is clean, keeps the entry the same width
as the tree-view it relates too - thus helping show the user they are
related (I think).

If I filter, then select a component, all is well. But now, if I clear
the filter.. the tree-view expands its self, it would be nice for the
list to scroll such that the item I have selected is still in view -
ideally in the same position relative to the dialog. I'm not sure if
this is easy / possible, but is sometimes handy.

I often search for a type of component, then like to scroll up and down
the similarly titled components near it. I filter, find one component,
then clear the filter. I then have to search for where I was in the list
manually.



Autonumber
----------

What does "Remove numbers" mean. I thought it meant re-number components
even if they are already numbered, but I just spotted "Overwrite
existing numbers" under "Scope".

I don't know what "Automatic slotting" does from the text. Perhaps I'm
being stupid... as already seen regarding URL links above, I'm tired!

Somehow the combo box with the text and picture seems too fat. Compared
to the "Starting number" entry above it (and too close to it). Something
doesn't feel quite right about it.

Also, the starting number entry feels very empty, lonely and wide
(necessitated by the width of the combo below). Is there text in some
other combo option which forces that width?

I'm liking the indenting, the bold headings. I'm not sure about a
horizontal rule before the buttons. I think I'd need to see them
side-by-side. My feeling is that good padding is most important.


Print
-----

Could potentially do with a little more padding, but generally feels
quite clean and usable.

The filename entry and "Save as" button are too close (and the field
isn't big enough). Peter B wanted to use a file-chooser button initially
IIRC, but these are only available in later GTK versions.

We could use a libsexy entry with a clickable folder icon on the RHS to
bring a chooser up. That gives space, looks nice and doesn't say "Save
as"

http://www.chipx86.com/wiki/Libsexy#SexyIconEntry

I'd use the folder icon, however I might put it on the RHS of the
entry.. would have to try and see.

(No flames about more lib deps. please.. we could copy-paste the
relevant - short, libsexy code). 


Line type
---------

Heading should be bold, sub-items should be indented - as you pointed
out.

Width is in what units? Can I have a spin button, or a preview of the
line?

Line type could have a drop-down list of example lines. Graphical is the
way forward when editing properties for a graphic object IMHO.

Dash length and space.. again, what units? Spin buttons would be nice,
and also a preview.


> I think that spacings and indentations are too large, even if I think 
> indentation and spacings and element alignments are good.

Sometimes, perhaps, but I expect we may disagree slightly on this point.
I guess it depends what you're used to, and how many pixels you have on
your screen.

It depends on what GTK theme engine you have how padding ends up
exactly, and how it looks w.r.t. the whole widget / dialog.

I personally can't stand raw GTK's look, and run Clearlooks. Others may
have different preferences, but I think raw GTK+ makes apps look like
they crawled out of the dark ages.


Peter C.




_______________________________________________
geda-dev mailing list
[email protected]
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev

Reply via email to