From: Marco <netuse@lavabit.com>
To: ntg-context@ntg.nl
Subject: Re: [t-rst] inclusion into Minimals, i. e. installation using `./first-setup.sh --extras='t-rst'`
Date: Mon, 9 May 2011 00:17:49 +0200 [thread overview]
Message-ID: <20110509001749.68535c84@glyph> (raw)
In-Reply-To: <9ED44F4D-67ED-4914-8DB1-4FAE1E7C0082@uni-bonn.de>
On 2011-05-08 "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de> wrote:
>
> On May 8, 2011, at 11:00 PM, Marco wrote:
>
> >> Having a GUI installer for the minimals (to make it more
> >> user-friendly and enable the user to choose what modules
> >> and fonts to install).
> >
> > Just a (maybe stupid) idea:
> >
> > What about making the existing windows GUI install and/or
> > update all available modules/fonts, since most windows
> > users don't care about a few hundred MiB disk space.
> >
> > Second, creating a repository for Debian/Ubuntu that
> > enables Linux users to install the minimals using the
> > system package manager. It's easy to create a package for
> > the modules.
> >
> > I have no idea how package management works for MacOS, if
> > something like repositories exist or how software is
> > installed/updated.
> >
> > And leave the existing interface for the other platforms,
> > since the vast majority uses either Linux, Windows or
> > MacOS.
>
> Just a few thoughts:
>
> 1. linux ≠ ubuntu/debian. Maintaining a repository for
> all different linux distros in their different package
> formats would be a nightmare.
ACK.
> 2. Maintaining a cross-platform GUI is incredibly
> difficult. gtk is an absolute non-starter on OS X.
If you say so. But anyway, we should not discuss about
which GUI toolkit we use, since it is not at all decided
that anything will change at this point.
> 3. Resources are limited. I would rather they go into
> development of luatex and mkiv then into eye-candy for
> mouse-pushers.
>
> 4. We now get reports from people (not necessarily, but
> sometomes newbies) going "I ran command X, and the
> output was Y." With a GUI we get: "I pushed the
> button, you know the one with the letters on it, and
> nothing happened." GUIs have a tendency to hide useful
> information, making debugging all but impossible. (I
> sometimes look at comp.text.tex on usenet - the number
> of people who confuse their editor and its shiny
> interface with the underlying TeX engine is staggering;
> the same would happen here).
I agree. My thought was the following: The
installation/update of ConTeXt is not integrated into the
systems default methods. How often do we get installation
help requests on the mailing list (on every platform)!
Supporting the default installation/update method of the
operating system would not necessarily need a GUI and be
easy for the users.
> 5. Even if it's "easy" to create a debian package for
> the modules, who's going to create and maintain it?
The creation of the package is scriptable. When the module
developer uploads/updates a module a (not yet existing)
script is called that creates the Debian package, which is
saved in the repository. Of course a scriptable solution
breaks when e.g. dependencies are not met.
> 6. Offering a GUI sends out a wrong message to new
> users: it pretends that this is just something that will
> work the same way as their word processor or office
> program works. But once people actually want to do
> useful things, they need to learn a minimum of coding
> techniques. Users will then feel deceived because the
> shiny GUI made them believe they could just write away
> and click buttons.
>
> In sum: I see no compelling reason in favor of, but many
> important reasons against such an installer.
As said before: Supporting the native package installation
mechanisms of the major OSs/distributions would be a big
help. For the rest the present mechanisms work fine.
Marco
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2011-05-08 22:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-01 10:18 Paul Menzel
2011-05-01 11:18 ` Mojca Miklavec
2011-05-01 12:33 ` Peter Münster
2011-05-01 12:37 ` Mojca Miklavec
2011-05-01 14:14 ` Aditya Mahajan
2011-05-02 5:58 ` Mojca Miklavec
2011-05-04 17:00 ` Philipp Gesang
2011-05-04 22:02 ` Aditya Mahajan
2011-05-05 9:47 ` Philipp Gesang
2011-05-06 18:55 ` Mojca Miklavec
2011-05-06 19:04 ` Aditya Mahajan
2011-05-06 19:08 ` Marco
2011-05-07 15:36 ` Mojca Miklavec
2011-05-08 11:18 ` Taco Hoekwater
2011-05-08 14:17 ` Marco
2011-05-08 19:43 ` Pontus Lurcock
2011-05-08 20:07 ` GUI for minimals WAS: " Marco
2011-05-09 8:03 ` Taco Hoekwater
2011-05-08 14:56 ` Arthur Reutenauer
2011-05-08 17:36 ` Hans Hagen
2011-05-08 18:17 ` Mojca Miklavec
2011-05-08 21:00 ` Marco
2011-05-08 21:28 ` Thomas A. Schmitz
2011-05-08 22:17 ` Marco [this message]
2011-05-08 14:01 ` Marco
2011-05-07 10:19 ` Philipp Gesang
2011-05-07 11:23 ` Wolfgang Schuster
2011-05-07 12:08 ` Philipp Gesang
2011-05-07 15:45 ` Mojca Miklavec
2011-05-08 18:32 ` Philipp Gesang
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=20110509001749.68535c84@glyph \
--to=netuse@lavabit.com \
--cc=ntg-context@ntg.nl \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).