>I'd be interested in knowing which editors you _rejected_ according to
>your criteria. For example, Jedit and Emacs both meet your needs, so far
>as I can see?
Jedit was the candidate that come closest to my expectations. But based on
Java, I had trouble to get it installed on old university machines which
had not the performance needed to run Java apps smoothly.
Trying out TEI-Emacs was a real pain. It installed itself in the Autostart
folder (I guess only one out of 100 Humanities students knows how to get
rid of Emacs starting whenever the computer is switched on -- the rest will
think the machine had been the victim of a virus), it messed up the
registry and the directory system because it does not understand umlauts in
a user name (as a result of this the file open dialog does not work
properly), and it created autosave files in a .emacs.d folder directly
under "C:". Next, it took me hours trying to figure out only the help
system, which was full of dead links, contained sometimes inaccurate
information and was extremely hard to navigate. So I gave it up ...
Sorry, if this description is disappointing for the UNIX experts on this
list who are fascinated by the power of Emacs' Lisp extensions etc. But
beside the fact that I never come across a program which so completely
failed to install, consider that each problem, which might be very simple
to fix for you, takes a novice hours to figure out a solution (if she
succeeds at all). Even if Emacs had installed correctly and the bugs in
the help system had been corrected, it would not meet the "easy to use"
>The trouble is, as Thijs' survey work (see posts last week) makes clear,
>it is hard to find one tool
>which suits all groups.
I do not think that a tool which suits all groups is actually
possible. Neither do I think that my editor is the best possible tool for
teaching XML. However, using it the students mastered the basic tasks of
typing, wellformedness-testing and validating the document very
quickly. The most difficult part was to understand the sometimes cryptic
error messages and to find out what really went wrong when a tag nesting
error occurred. An ideal editor for teaching XML should provide students
with better assistance for correcting errors, of course.