[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: Anaconda UX redesign / status update
- From: Will Woods <wwoods redhat com>
- To: Discussion of Development and Customization of the Red Hat Linux Installer <anaconda-devel-list redhat com>
- Subject: Re: Anaconda UX redesign / status update
- Date: Tue, 14 Jun 2011 11:35:06 -0400
On Fri, 2011-06-10 at 16:05 -0400, Máirín Duffy wrote:
> Well, there are certainly at least four ways to go here:
>
> 1 - Only ask stuff required for install pre-install. Fire & forgot, come
> back after you've gone to the kitchen and had a snack, and fill out
> firstboot. (Pretty much what happens today.)
>
> Only ask stuff required for install pre-install, while the install
> progresses, ask the stuff needed post-install (this is apparently what
> ubuntu does) Reboot and you're ready-to-go. If you're doing OEM
> pre-loaded installs you put some flag in the KS so that firstboot will
> start up and ask the questions that would have been asked during the
> actual install progress.
I'm a fan of the Middle Way (#4) as well - ask questions during install,
optionally (either by KS flag or "Ask me later" button) ask them at
firstboot instead.
(It'd be nice if we could ditch firstboot - less code means less bugs! -
but I really don't think we can get away with it. It has some legitimate
uses.)
Which brings me to two observations:
- Hey, shouldn't firstboot be a hub-and-spoke UI as well?
- User personalization is a post-install thing, so shouldn't that go
into the post-install-setup hub? (Or is there some info gathered there
[hostname?] that's needed pre-install?)
-w
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]