Pavel Sanda <[EMAIL PROTECTED]> writes: > it would be possible for me to lead lyx layout editor as a small > school project provided that it is work complicated enough.
If the goal is to build something useful (!) and maintained, I think it should be coded in C++ and part of LyX, or at least using parts of LyX, like tex2lyx does. In particular, the compilation should break as soon as an incompatible change is done to our Layout system changes. If this is not done, you are going to experience bitrot rather rapidly. > by 'complicated enough' i mean it should know more than just provide > database sheet for the attributes described in our customization > manual, since that is trivial to write and won't need more > people/months to code... so its a question whether we can produce such > a feature-list :) Having a wysiwlwd (what you see is what LyX will do) mechanism that shows an example layout would be nice (and require to hook into LyX itself). Also, it is important to support and encourage mechanisms to inherit styles (Input and CopyStyle). The styles should be cumulative and the code produced by the editor should be as minimal as possible. JMarc
