all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Thomas Ingram <taingram@mtu.edu>
Cc: guix-devel@gnu.org
Subject: Re: [GSoC] Draft proposal for an Install Wizard for Guix
Date: Fri, 01 Apr 2016 14:09:40 +0200	[thread overview]
Message-ID: <871t6ph6nv.fsf@gnu.org> (raw)
In-Reply-To: <56F78298.7060806@mtu.edu> (Thomas Ingram's message of "Sun, 27 Mar 2016 02:50:00 -0400")

Thomas Ingram <taingram@mtu.edu> skribis:

> On 03/26/2016 07:39 AM, Ludovic Courtès wrote:
>> Personally, I would like to view the “wizard” as a helper, and not as
>> something that hides everything and turns people into “end users.”
>>
>> I don’t know how this could translate in the design of the tool.
>> Perhaps showing the ‘operating-system’ declaration as you suggest is one
>> thing, and making it easy to view the section of the manual that
>> corresponds to a particular item, or to jump to the code that defines a
>> specific service (say), would be helpful too.
> Yes as much as it is an installer it should also be an
> introduction. Something that not only lets a user easily input their
> options but also shows them how their settings will be put into
> config.scm, I'm trying to come up with some clever ideas of how to do
> this in a graceful way.

Awesome.

> Basically I was thinking of doing that with an ncurses UI that shows
> the user their config.scm with some documentation and then walks users
> through changing each option. But maybe an emacs installer makes more
> sense as this is the type of interface emacs does very well.
>
> The reason I had avoided proposing an emacs installer previously is I
> worry about confusion from users who are unfamiliar with emacs and how
> to use it. Should we be concerned with that when so many of Guix's
> great features that can be accessed through emacs. Perhaps there could
> be a simple introduction to emacs in the installer as well? On the
> other hand if a user has no experience with emacs throwing that at
> them along with config.scm could be overwhelming.

I understand your concern.

I think that in this case, Emacs should be viewed as a UI toolkit: just
like someone using an ncurses program doesn’t have to learn the ncurses
API, someone using an Emacs-based UI doesn’t have to learn Emacs.

It just happens that Emacs is a full-featured UI toolkit, especially
when it comes to Guix things.  For instance, it already has all we need
to display and navigate source code (from an ‘operating-system’
configuration, one can contextual documentation, jump to
procedure/variable definitions, etc.), to navigate packages, and so on.

Having said that, I think that if you’re more comfortable writing Guile
and ncurses code than Emacs code for this project, then that’s perfectly
fine, of course.

Thanks,
Ludo’.

  parent reply	other threads:[~2016-04-01 12:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-22 20:45 [GSoC] Draft proposal for an Install Wizard for Guix Thomas Ingram
2016-03-23  8:51 ` Chris Marusich
2016-03-23 11:29   ` Ricardo Wurmus
2016-03-23 14:11     ` Ludovic Courtès
2016-03-23 14:33     ` Chris Marusich
2016-03-23 11:53   ` Danny Milosavljevic
2016-03-23 14:13     ` Ludovic Courtès
2016-03-23 22:20 ` Mark H Weaver
2016-03-25 13:09 ` Ludovic Courtès
2016-03-25 15:48   ` Thomas Ingram
2016-03-26 11:39     ` Ludovic Courtès
2016-03-27  6:50       ` Thomas Ingram
2016-03-27 18:30         ` myglc2
2016-03-27 20:48           ` Jookia
2016-03-27 22:53             ` myglc2
2016-03-28 16:28               ` Christopher Allan Webber
2016-04-01 12:29                 ` Ludovic Courtès
2016-03-27 23:25           ` Leo Famulari
2016-03-28  6:20             ` Chris Marusich
2016-04-01 12:27           ` Ludovic Courtès
2016-04-19 17:49             ` myglc2
2016-04-01 12:09         ` Ludovic Courtès [this message]
2016-03-25 20:19 ` myglc2

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871t6ph6nv.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=taingram@mtu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.