On Fri, Nov 06, 2015 at 11:17:56AM +0100, Martin Kolman wrote: > On Fri, 2015-11-06 at 04:35 -0500, David Cantrell wrote: > > On Thu, Nov 05, 2015 at 11:33:57AM -0600, Michael Catanzaro wrote: > > > On top of that original proposal, we are now additionally > > > planning to run language selection and keyboard layout selection > > > as soon as the live media starts, so those will be done before > > > Anaconda is ever started. This is because it's much too > > > difficult for users to figure out how to change these currently, > > > unless they already know where to look in System > > > Settings. There's been some debate about whether time has to be > > > set prior to installation as well, but that would be handled by > > > g-i-s either way. This is currently targeted for F24, but nobody > > > is currently working on it, so it might slip. > > > > > > But your proposal would work too. Both proposals eliminate the > > > duplication between Anaconda and g-i-s, and that is the most > > > important goal here. Do keep in mind the move of > > > language/keyboard selection; with your proposal, we'd need to > > > separately hide those in Anaconda. > > > > > > (Our secondary goal is to reduce complexity in Anaconda, since > > > we fear having so many spokes is quite confusing to users who > > > don't understand computers.) > > > > The two proposals should be viewed separately. The Workstation WG > > installation experience can and should be customized for the > > Workstation product, but anaconda still should have a way to > > ensure that duplicate screens are avoided in instances where both > > codepaths are run. > > That's also the way I see it - as a complementary mechanism meant to > assure that screens shown to the user in Anaconda are not needlessly > shown in tools running *after* Anaconda. > > So if a given screen is skipped in Anaconda, it can't be visited and > therefore also can't be marked as visited. > > Also theoretically if any tools showing configuration screens before > Anaconda starts (as in the example above) could record these screens as > visited in the config file, Anaconda could then parse the file on > startup and hide screens marked as visited. I'll make it a point in our upcoming Workstation meeting to check that whoever's working on these pre-installer screens is talking with the Anaconda team to figure out how best to do that. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ The open source story continues to grow: http://opensource.com _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
