Jean-Marc Lasgouttes wrote: >The problem is that currently, classes that are not found are not >added to textclasses.lst. To make things work, one would have to have >all the classes in the file, but mark the ones which do not have a >corresponding latex class. This is probably not too difficult to code, >but I am not sure about the interface: how do we mark such classes in >the textclass dropdown box? do people really want to see a list of >classes with 100 classes they cannot use?
Well, a quick look at the layout directory tells me there are 58 layout files. As far as I can see the only major item in the GUI that needs to be changed is the "class" choice in the document dialog (as you already pointed out). On my machine, 26 document classes are displayed. Another 32 entries would make the choice list a little bit longer but IMHO this is acceptable, in particular, if the available document classes were listed on top. Why not just mark unavailable document classes by a preceeding star (*) or something similar? In order to avoid conflicts with existing code we might stored text classes not available in some file "textclass-na.txt"? (I certainly know whether this is really necessary) Apart from that, only some entries in the "View" menu and some "File>Export" entries would have to be greyed out in case a text class is not available. That's all. Doesn't sound too complicated, does it? >And being able to load the docs but not create them is bad UI, IMO. Yes, there is some asymmetry... Michael -- ======================================================================= Michael Schmitt Telefon: +49 651 97551-40 Institut für Telematik Telefax: +49 651 97551-12 Bahnhofstrasse 30-32 WWW: http://www.ti.fhg.de D-54292 Trier E-Mail: mailto:[EMAIL PROTECTED] =======================================================================
