> Assuming that this is 1.5 material, we could also try to reconsider > the way we detect textclasses. If we get rid of the current > \DeclareLaTeX class stuff and replace it with normal layout tags, will > we be able to read and detect classes on-the-fly using kpsewhich (or > linking to kpathsea library)? It should not be difficult to do a > 'quick' read of textclasses that ends as soon as we have enough > information on the class.
I do not quite get what you have in mind. Do you still want configure.py to build textclass.lst and read the list when lyx starts? What would be convenient, may be something like: 1. users can choose all available latex classes, which means *all* of the latex classes in TEXINPUTS. (I do not know how difficult it is.) 2. .layout file will be searched dynamically in system and local .layouts directory, current directory and pathes in TEXINPUTS. 3. If all fails, use a default .layout file or fail. As a matter of fact, since we are using configure.py, it is quite easy to check a online lyx layouts repository such as http://www.lyx/org/layouts for a usable layout file. Along this line, I would suggest that we put useful classes like dvipost.cls online ... Then, we do not have to configure lyx for tex classes. Cheers, Bo
