From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Marusich Subject: Re: Graphical Installer - Call for Testing. Date: Thu, 06 Jul 2017 21:48:47 -0700 Message-ID: <87wp7k97io.fsf@gmail.com> References: <20170104075928.GA23509@jocasta.intra> <87eg07cybi.fsf@gmail.com> <20170113063511.GA18383@jocasta.intra> <20170705192731.5fdd6933@scratchpost.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57762) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dTLCP-0001dH-HP for guix-devel@gnu.org; Fri, 07 Jul 2017 00:49:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dTLCO-0007PZ-DA for guix-devel@gnu.org; Fri, 07 Jul 2017 00:49:01 -0400 Received: from mail-pf0-x244.google.com ([2607:f8b0:400e:c00::244]:33252) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dTLCO-0007NZ-5m for guix-devel@gnu.org; Fri, 07 Jul 2017 00:49:00 -0400 Received: by mail-pf0-x244.google.com with SMTP id e199so2987968pfh.0 for ; Thu, 06 Jul 2017 21:48:58 -0700 (PDT) In-Reply-To: <20170705192731.5fdd6933@scratchpost.org> (Danny Milosavljevic's message of "Wed, 5 Jul 2017 19:27:31 +0200") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Danny Milosavljevic Cc: guix-devel@gnu.org, John Darrington --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi Danny, Wow! I just looked, and I see that a lot of changes have been made since January. Is the wip-installer-2 branch the one I should test with now? What's the difference between the wip-installer and wip-installer-2 branches? What steps should I take to create a disk image with the installer (or is a testable image available already)? I will see if I can test it again in the next couple of weeks. Danny Milosavljevic writes: >> * I think you made the first letter of some commands bold (like the "C" >> in "Continue"), but I didn't notice it until I tried the installation >> on a machine with a different monitor. More contrast, or an >> underlined character, might help call that out more. > > Yeah, the HIG standard is underline. Does underline work in curses on th= e Linux console? Apparently it's always auto-mapped to color. I don't know. >> * Partition the disks: when launching cfdisk, consider explaining that >> we're going to launch cfdisk to do the actual partitioning, and the >> user needs to quit cfdisk to come back and continue the installation. > > I'm writing guile-parted bindings now :) Cool! >> * The generated operating system configuration should use file system >> UUID or label, if possible, rather than device path. > > I didn't get that far yet. Is that still the case? I don't know. When I test it again, I'll check. >> * Choose mount point: since you can also set the label here, maybe >> change the title of the section to "Choose file system and mount >> point" or something? > > In the long run, I think this all should be "disk setup" and encompass pa= rtitioning, lvm, encryption, file system creation and mount point setup. I think it would be fantastic to accomplish all of the following: * It's easy to configure the disks for the common use cases. * It's possible to customize the configuration for any use case. * The installer doesn't overwhelm people with knowledge that they might not (yet!) possess, but it invites them to take control and to learn. I think each of those bullet points is in the spirit of Guix. >> * The installer takes a "window within a window" approach for >> installation phases. This conflicts with the "replace the whole >> window" behavior that occurs when running cfdisk.=20=20 > > Writing the parted bindings... :) Excellent! >> I think that using a "replace the whole window" approach for the >> whole installer would help unify the overall look and feel. So, >> instead of creating a window within the installer window for the >> "Partition the disks" phase, just replace the entire window with >> the relevant interface for the sub-menu. > > I actually like the window-within-window approach, especially since it > can show some kind of path or status of where the user is nicely. I > wonder whether the nesting works for more than two levels, though. That would work, too. As long as the choice is consistent, it'll be a better user interface. >> * Choose mount point: clarify what the actions Check, Write, and >> re(Create) mean. I wasn't sure until I tried them all! > > I think that's cfdisk ? Or where? It's been a few months, but I don't think that was in the cfdisk menu. Maybe that section of the installer has been changed since I last tested it. I think it was in a section called "choose mount point". I'm happy to see that this branch has remained active! I'm sure having a graphical installer will encourage more people to try GuixSD. =2D-=20 Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAllfEq8ACgkQ3UCaFdgi Rp0g7RAAtEHMqIa9SLPsZZMJwjrFZIlvN9SFrj2Oe93rpLrZZE7tDkWLOpf5nyMG tqPJAmeiudTQyq2p5I45J0d80CvxSuyZzz1NQxyMfjgQGm5JNuCqjpdCHw/NgKQp MjwZz+cPSHou+/3jQjUG+mdFyk/myU4AMarpvk8Llwft81iAqKfYPviSUKSrrq+I aUX2YLwHPAe7afC+Fvgi2WtsCvQABRdrRBEcV4u1oMkUgrdWkmaZYCI4OhJXsQKd wTCe7yebPaAk32WhUoSBQmrjaeC9Zlt44ysEMI4fiFynMS7ctQbT0S2BqVJIgwmH xzdjssFCNIZQl3UOcWamXSRqUvT62jxzjLe1zGhBY3W6m4iWr4XwVH5WM4CCrKqW NFC3HVv4MBZrMem/QR9XW89w3dGavLskLqocD6xXvwZqbD7zD1K5b57u+h1N0RrY EYr71FPsqEQdnaVvzB4y9EiLaZbbZSp0734keOrhltIH57TgQmjPZ9aINgf2oDBH bNTCDWbktx94GbB/4L2x44JBMwrmfcoK0nb1ubdDD301lwU7E7zrESis4ZnoLDjx 2HYU4LjJA32P8kWv87WQsUZHG2MIxRXgdhz5SYjPDw5rZLKvL7FSc5t1cwkax5AY hNzlqblLOtij5zMviCJqPumWkIhPo6vFcBq6z9tz7rCQMs2MZ90= =0Hwe -----END PGP SIGNATURE----- --=-=-=--