| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
This doesn't fix the redraw-related size problem. I think that might just
be an artifact of not using a compositing manager. This merely attempts to
fix it so we don't display a spoke entirely smashed up in the upper left
corner of the screen.
|
| |
|
|
|
|
|
|
|
|
| |
By hardcoding a color, it makes the status text almost invisible on the KDE
live disc where the theme is darker to begin with. Instead, use the theme
colors for everything.
This isn't a perfect fix: If you focus a SpokeSelector, the text will still
be black instead of white like everything else. However, I've been unable to
make that work.
|
| | |
|
| | |
|
| |
|
|
|
| |
This also changes the back-signal to button-signal. This is prep work for
allowing individual spokes to relabel the button if they so choose.
|
| | |
|
| | |
|
| |
|
|
| |
This can be handled higher up in the python portion of the UI if desired.
|
| |
|
|
|
| |
I discovered this searching for "iw" to make sure I deleted everything related
to the old interface.
|
| |
|
|
| |
I knew I'd forgotten something when I did this for MountpointSelectors.
|
| |
|
|
|
| |
This is largely just copy & paste from what msivak did elsewhere.
Thanks.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This means that when you press up and down with the keyboard to navigate the
accordion, whatever MS you hit will be the one displayed on the right, and
whatever one you were previously on will have its changes saved.
This is different from how DiskOverviews and SpokeSelectors work, but I think
it makes sense. When you keyboard to a DO, you are choosing to do include it
in the install. We don't want people doing that by accident. When you
keyboard to a SS, it would jump you into the spoke and that wouldn't work
at all. The MS, however, just changes what's displayed on part of the screen.
|
| | |
|
| |
|
|
| |
Also, don't translate it. That doesn't make any sense.
|
| | |
|
| |
|
|
|
|
| |
A side effect of this is that the whole left hand side is now wider, but I
think that can be fixed by adjusting the stuff that goes in the right hand
side.
|
| |
|
|
|
| |
When testing we, need to set the location of the bitmaps our TimezoneMap is
using, so let it try to get the location from the environment.
|
| |
|
|
|
| |
This is the thing on the left hand side of the custom partitioning interface,
allowing you to select a mount point and do some configuration on it.
|
| |
|
|
|
|
|
| |
Really, I'd like them to be grey only when the spoke is not ready and then
turn black afterwards. But I can't make that work, and it has to be done
in C since the labels aren't exposed outside of that. So this will have
to work for now.
|
| |
|
|
|
|
|
| |
Some keyboard layouts have pathologically long names, and we're already
trimming the status for network sources so just do it for all spokes. Note
that this does not change the text of the status, so it can still be used
for string comparisons.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Note the "selected" -> "chosen" change. "selected" means something specific
to GTK, and it doesn't mean what I thought. Thus, I am now using "chosen" to
mean you have hit enter/space on the DiskOverview and made it part of the
install.
This also gets rid of the rounded corner piece, since I was unable to make that
work with the keyboard focus (for now).
|
| |
|
|
|
|
|
|
|
| |
GTK doesn't really make this easy on us. The only thing we can do is tear
everything down and rebuild, which is not at all an optimal solution.
Alternatively, we can maintain lists of original strings and the widgets that
contain them, and do it on demand by hand.
Not everything is supported yet. I'll add support as needed.
|
| | |
|
| |
|
|
|
|
|
| |
This could go into an external CSS file instead, but then I have to worry
about loading it, and packaging it, and what the proper location should be,
and all that kind of stuff. I could just shove it into a variable and be
done with it.
|
| | |
|
| |
|
|
|
| |
200px makes it take up entirely too much of the screen. 125px is a better
compromise between the look we're going for and screen space usage.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
With the current setup, what happens is you have to pass the opposite value
from what you want into set_selected because a_d_o_clicked negates whatever
a_d_o_set_selected. Whoops.
|
| |
|
|
|
|
|
|
|
| |
(1) Increase font sizes in the nav area.
(2) Make the betanag warning bold so it stands out better.
(3) Increase the size of everything in the spoke selector to help us use
the screen real estate a little more wisely.
|
| | |
|
| |
|
|
|
|
| |
It's a little ugly (the default Gtk focus notification appears to be just
changing the background to blue), but that's the default and it makes it clear
what is currently selected.
|
| |
|
|
|
|
| |
First, remove the border width specified in each .ui file. This allows the
info bar to extend all the way to the edges of the screen. Then, add back
in some padding around the nav_area and various button areas.
|
| |
|
|
|
| |
If I use the same values, the selectors in the hubs look way too cramped.
Or, the spokes look like they're floating in space.
|
| |
|
|
|
| |
This means I can get rid of the current warning on hubs, since I can just
make the info bar pop up instead.
|
| |
|
|
|
|
|
| |
This requires exposing a lot more internal children because glade will not let
you get to internal children unless you also expose everything up the chain.
This patch should eliminate the need for any window to include its own alignment
and its own vbox. I hope it's also largely transparent.
|
| | |
|
| |
|
|
|
|
| |
This is not the fancy icon overlay as shown in the mockups, since that takes
a litle more work than I have time to do right now. Feel free to work on this
yourself.
|
| | |
|
| |
|
|
|
|
| |
Instead I'm using the slightly less deprecated GtkBox and GtkButtonBox, though
those will have to be converted to GtkGrid eventually. However that is a much
bigger change.
|
| |
|
|
| |
Also, make the betanag screen call it.
|
| |
|
