| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
When the NTP switch is turned ON/OFF we want to start/stop the chronyd.service
and make the date/time setting widgets (in)active.
|
|
|
|
|
|
|
|
|
| |
This removes the previous store and tree view code, adding instead the Accordion
and Page code. It also adds the Page that prompts you for how to create a new
partitioning layout and makes that the default for now.
So, no partitioning is yet displayed here and the creation button doesn't do
anything. But it's a start.
|
| |
|
| |
|
|
|
|
|
|
| |
I don't know why, but you can't set the background on a GtkBox using CSS like
I was elsewhere. So, I've introduced some intermediate Viewports that do
nothing but allow for background coloring.
|
| |
|
| |
|
|
|
|
|
|
|
| |
When a spoke is created, initialize should always be called before readiness is
checked. However for those spokes that spawn off a thread in the initialize
method, readiness could be checked before that thread is done. We need to make
sure to check that the watcher is still running as well.
|
|
|
|
|
| |
Since the code adding a language-related layout may return from the
apply method, move timezone preseting before it.
|
|
|
|
|
| |
When user adds/removes a layout, we want to add/remove it from the
X runtime configuration so that the change really happens.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Since the spoke's status is queried even before the refresh method is invoked we
need to populate the store in the initialize method.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
We need to set the timezone in the initialization method because
the Datetime spoke's status is queried before the refresh method
gets invoked. However the change of timezone results in a change
of the displayed date/time and we don't want to start timers for
updating the date/time when the spoke is not shown.
|
|
|
|
|
| |
Once we have a GeoIP available, we should use it for guessing
right timezone, but for now, try to use the chosen language.
|
| |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
| |
When we first try payloadInitialize from anaconda, it's possible there's no
network active. Thus, the thread fails. However if the network is brought
up on the network standalone spoke, we should try again. We also need to
limit trying again to only the cases where no base repo is set up (so, skip
doing anything on media installs).
Long story short, a netinst.iso boot with no configured repo and no network
should now work correctly.
|
|
|
|
|
|
|
| |
This is coming up for me when booting a netinst.iso with no network active.
Trying to load groups later will fail and throw a traceback. It'd be better
if we just made sure the software spoke was unavailable and let the user
fix the lack of network.
|
|
|
|
|
|
| |
The software spoke should only be ready when a valid source is
configured. Downloading of repo metadata happens in the background, as
does dependency checking.
|
|
|
|
| |
Filtering is separate from target disk selection.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Otherwise when the user changes language, they're going to see a string like
"WELCOME TO %s %s" which is of course not right. I do not yet know whether
more places are going to need this modification but if so that will be the
time to make this code more generic.
Also, it's still hard to test without real translations.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
XklWrapper provides read-only data and is initialized with
system-wide data, so it doesn't make sense to have multiple
instances.
|
|
|
|
|
|
| |
We need to store layouts as their names because that is the way how they are
identified in kickstarts, libxklavier and libgnomekbd. On the other hand, we
need to display layouts in a more user-friendly way.
|
|
|
|
|
| |
GtkBuilder doesn't know what to do with them besides spew warnings, which
are just bugs waiting to happen.
|
| |
|
|
|
|
|
|
| |
Starting off with the "Preparing to install" message makes the pause up front
seem a little less weird, and moving the package installation message around
means there's less pause after the last filesystem is made.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The basic idea is that we skip any standalone spokes that are already filled out
by the input kickstart file, and that we only display the summary hub so that
something's being displayed while background processes work.
Any important spokes not filled out by the input kickstart file will get the
caution icon and the user will have to complete them before continuing. The
message at the bottom of the summary hub explains that.
This behavior leaves open the possibility that the user will be able to visit a
spoke while background processes work. In that case, we want to wait until the
user leaves that spoke before automatically continuing. The alternative is to
move as soon as anaconda is ready, which is really quite jarring.
|
|
|
|
|
| |
This way if we're doing a kickstart install, we'll know to skip it and keep
going to the hub if we already have language information.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Remember that any images from the glade file that should be displayed need to
be listed in builderObjects.
|
| |
|
|
|
|
|
|
|
|
|
| |
* Provide status and apply methods.
* If you change the region combo, update the city combo to the first city
in that region. Otherwise you can end up in a situation where you go back
to the hub with no city selected, the status reflecting what was previously
selected, and the combos reflecting what you last did with them. It's very
confusing looking.
|
| |
|
| |
|
| |
|
| |
|