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.
Thomas, I do not know what Oliver is actually doing.
But just 2c:
- suppose you have a ConTeXt distro (the minimal) inside a mac app. At the end a mac app is typically a folder containing different programs/libraries etc
- suppose you are provided inside the app of an editor (say, TeXShop) already configured to read in the app's folder.
In sum, you have a TeXShop ready to go for the ConTeXt in the app.
Then, you have a context distro working out of the box.
It can be installed easily. You have always worked with Word and you want to try to work with ConTeXt? Download, drag and drop, open.
There shouldn't been configuration problems (they have been solved while creating the installer).
If there are bugs depending on ConTeXt, as usual in case of an app, the user has to wait for a next release of the app including the new ConTeXt version.
(with a bit more expertise, maybe you can simply replace the right folder inside the mac app)
This is indeed a limit, but the previous points can be pros for another user.
colorful pointy-clicky interface.
Not so much colorful, not so much pointy-clicky.
Just local, self-contained, with an editor.
No?
Best
-a-