ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: distro info
Date: Sat, 14 Jun 2008 13:35:09 +0200	[thread overview]
Message-ID: <C2E0A72D-A7A2-4A8C-9567-EF51344B4B90@uni-bonn.de> (raw)
In-Reply-To: <A1D677F8-F069-4DCB-AF2E-65170BE59F96@mpq.mpg.de>


On Jun 14, 2008, at 1:07 PM, Oliver Buerschaper wrote:

> Actually, I strongly disagree with the opinion that the only way to
> properly interact with TeX is via the command line.
>
> Counter example: in Mac application development your IDE of choice
> will almost certainly be Xcode. Although it delegates the entire
> compilation process to gcc you *never* ever see the command line. And
> there's no need to. All errors and warnings output by gcc are
> intercepted and passed on to you via the graphical IDE and you won't
> lose a tiny bit of information. In fact you gain a lot when trying to
> track down a problem ...
>
> Furthermore, in my humble opinion interaction with TeX should
> concentrate on programming the actual typesetting language and not on
> fumbling around with dozens of configuration files ... for instance,
> if you develop applications you wouldn't want to reconfigure your
> compiler twice a week either but rather focus on the source code *you*
> write.
>
> Oliver

Who said that "the only way to properly interact with TeX is via the  
command line"? What I said is: you can provide all the GUI tools you  
want, at some point (and this will be rather sooner than later)  
problems will crop up, and these problems will be impossible to  
resolve if you don't want to use the command line, don't want to learn  
about PATH settings, don't want to learn about where configuration  
files go and what they do. This may be different in, say 10 years, but  
it would be misleading to pretend that it is different today. TeXLive  
2008 is just being tested, and in this regard, it's no better than its  
predecessors. Unless and until we have systems which will be easier to  
maintain, users who expect to be able to stay away from the CLI are  
bound to be disappointed.

Your example about Apple's Xcode actually proves my point: I said that  
if you can afford to throw a couple of million $ and a dozen  
programmers at this, it is actually feasible (but will still take  
time). Apple has done just that; the Xcode IDE hasn't been built by  
volunteers in their spare time, now has it? So far, nobody has done  
anything similar for TeX, and I had the impression that the volunteer  
programmers who are actively contributing to it seem more interested  
in adding new features and improving the code than in adding a  
colorful pointy-clicky interface. But of course my impression could be  
wrong and someone is already building such a GUI as we speak...

As for "fumbling around with dozens of configuration files": such  
exaggerations are not very helpful in this discussion.

Thomas
___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2008-06-14 11:35 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 14:36 Andrea Valle
2008-06-10 14:43 ` Andrea Valle
2008-06-10 15:29   ` Wolfgang Schuster
2008-06-10 15:30   ` Otared Kavian
2008-06-10 15:34   ` Hans Hagen
2008-06-10 17:21     ` David
2008-06-10 17:37       ` Hans Hagen
2008-06-10 20:31         ` Andrea Valle
2008-06-12  1:22         ` David
2008-06-12  7:51           ` Olivier Guéry
2008-06-12  8:58             ` Mojca Miklavec
2008-06-10 15:58 ` Mojca Miklavec
2008-06-10 20:27   ` Andrea Valle
2008-06-10 21:08     ` Mojca Miklavec
2008-06-11 12:09   ` Oliver Buerschaper
2008-06-11 14:55     ` Andrea Valle
2008-06-11 16:05       ` Mojca Miklavec
2008-06-11 16:55         ` Andrea Valle
2008-06-11 20:43           ` Jesse Alama
2008-06-12  9:00             ` Andrea Valle
2008-06-13 16:40               ` Henning Hraban Ramm
2008-06-13 17:08                 ` Andrea Valle
2008-06-13 18:01                   ` Mojca Miklavec
2008-06-13 18:20                   ` Henning Hraban Ramm
2008-06-13 18:26                     ` Matthias Weber
2008-06-13 19:23                       ` Henning Hraban Ramm
2008-06-13 17:57                 ` Thomas A. Schmitz
2008-06-14 11:07                   ` Oliver Buerschaper
2008-06-14 11:35                     ` Thomas A. Schmitz [this message]
2008-06-14 13:57                       ` Andrea Valle
2008-06-14 17:36                         ` Thomas A. Schmitz
2008-06-14 21:38                           ` Henning Hraban Ramm
2008-06-14 23:32                             ` Charles P. Schaum
2008-06-14 14:19                       ` Oliver Buerschaper
2008-06-14 16:35                       ` Jesse Alama
2008-06-14 18:59                         ` Mojca Miklavec
2008-06-14 23:05                           ` Diego Depaoli
2008-06-15  0:41                             ` Charles P. Schaum
2008-06-15  1:36                               ` Matthias Weber
2008-06-15  9:40                             ` Andrea Valle
2008-06-30  5:27                           ` Jesse Alama
2008-06-30  7:03                             ` Alan Stone
2008-06-30  8:20                             ` Mojca Miklavec
2008-06-30 16:21                               ` George N. White III
2008-06-14 11:48                     ` Andrea Valle
2008-06-14 13:55                     ` John Culleton
2008-06-17 16:02 ` searchable pdf in mkii, usepdffontresource stub Oleg Kolosov
2008-06-17 16:34   ` Hans Hagen
2008-06-17 18:55     ` Oleg Kolosov
2008-06-17 19:13       ` Hans Hagen

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=C2E0A72D-A7A2-4A8C-9567-EF51344B4B90@uni-bonn.de \
    --to=thomas.schmitz@uni-bonn.de \
    --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).