[Octave-patch-tracker] [patch #8614] New gui icons

[Dan Sebald]

Follow-up Comment #1, patch #8614 (project octave):

Looks nice.  I like the smaller icons (but I just notice the existing setup
allows adjusting icons already).

Could you include a snapshot of the icons when the default theme is missing? 
E.g. Windows.  Or is there a way to make that happen easily even though the
defaults are present?

Should the prev/next breakpoint positions be switched (i.e., prev on the
left)?  A lot of one-line text search functions have the previous button on
the left.  (E.g., a browser cntrl-f "Find:".)

The "step-in" and "step-out" icons aren't so immediately understandable.  The
direction of the arrows seems like it should go the other direction for my
intuition.  It's a hard thing to represent, even though in a programmers it is
sort of very clear what the "step in" and "step out" phrases imply.  I wonder
if slightly changing the graphic might help, in particular the position of the
arrow.  I'll try to illustrate what I mean, but there probably isn't enough
space for this on the icon.  Say = represents the lines/blocks in the icons
just as they currently are, and -> is the swooshing arrow.  Below are two
"icons", for which I will not mention which is which.  Tell me what your first
impression is about which is which:


=
   =
 <-
=



=
 ->
   =
=


[To me the first sudo-icon looks like stepping out and the second sudo-icon
looks like stepping in.]

Beyond the look and feel.  I wonder if there should be an option to confirm
clearing the breakpoints.  Also, in the "Run" menu it would be nice to have
some way of entering a string of text that would serve as the argument of the
function being run (if it is a function).  Or maybe it would be an edit-box
right next to the "run" icon.  For example, one might put non-editable "(" and
")" characters and between that the user enters something like


"(" pi               ")"
"(" 15,xval,yval     ")"
"(" sqrt(3)          ")"


where any variables entered (xval and yval) would have to be global in order
for the "run" to work correctly.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/patch/?8614>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/