python-meh for the newui

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I've started porting python-meh to Gtk3 and the new design. There is a
mockup of the exception dialog [1]. The obvious thing is that we don't
want the users clicking the Debug button, that would switch them to tty1
running pdb, from where they cannot get back and report bug. That's why
the Debug button is only a small link button at the bottom of the
window.
We have discussed the look on the IRC and we agreed on adding a
Traceback button [2], that would switch the user to tty3 with dumped
traceback. Then Martin Sivak came with an idea of creating a new window
with a traceback instead of using tty3, because it is better usable and
can display a lot more text on the screen. [3]

However, there are some issues with the main exception dialog:
1) Since there are two rows of the buttons, standard GtkDialog cannot be
used for it, which means having GtkWindow, running a new GtkMainLoop for
the window and using buttons' callbacks to quit it and save response ID.

2) Users can still easily get confused and lost after clicking the Debug
button which looks more like a link to the debugging guidelines
somewhere on the web than like a button that will switch you to the tty1
and run pdb.

3) Since python-meh is expected to be still used also in Firstboot, its
labels shouldn't refer to the installation.

To address 1) and 2) I've added a debug option to the configuration
class (that is instantiated and passed to python-meh when registering
the handler) and the code diplaying the Debug and Traceback buttons only
when the debug option is set to True. [4][5] This way, we can use
standard buttons placed in a more natural layout (of the GtkDialog).
Since we already have such an option in Anaconda, we can easily pass it
to python-meh and do not show buttons users are not expected to click.
Note that the "Show traceback" button is intentionally placed out of the
action area row because it doesn't close the dialog.

Is that acceptable? I believe it's easy for us to add a debug=1 option
when testing changes.

As always, comments are welcome.

[1] http://beefybeliever.wordpress.com/#jp-carousel-143
[2] http://vpodzime.fedorapeople.org/python-meh_mockup.png
[3] http://vpodzime.fedorapeople.org/python-meh_show-traceback.png
[4] http://vpodzime.fedorapeople.org/python-meh_non-debug.png
[5] http://vpodzime.fedorapeople.org/python-meh_debug.png

-- 
Vratislav Podzimek

Anaconda Rider | Red Hat, Inc. | Brno - Czech Republic

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list


[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux