Helge Hafting wrote: > Not much of a problem, I think. 1.5svn is a development version, > so its file format can be a moving target. Or is the intention to > have perfect support at all times? I don't know how much work > it is to bump the number. But surely we can delay "official" > support: Keep adding good patches, and bump the version > when enough stuff has accumulated.
I agree fully with Jose here, especially since a format change + conversion is very easily implemented. >>I think we should in general avoid to add new packages to LaTeXFeatures >>unless the already existing conflicts are solved and we have a more >>flexible package loading mechanism. The more package syou load >>automatically, the more conflicts can arise. >> >> > What should such a system look like? I don't know. > A document settings page listing every package we support, > with radio buttons for "off" and "auto"? > > "Auto" should work for the common ERT-free document always. > "off" for the expert, who loads packages manually or provides > the commands in the preamble. > "on" could be provided too but isn't strictly necessary, someone > who want to load a certain package in order to use it in ERT only > will know how to put \usepackage in the preamble. He has to do > that anyway for packages without lyx support. This could be one possibility. Additionally it could be possible to adjust the order of the packages (before/after user preamble). This is sometimes needed with babel. > As for avoiding new features - I was rather hoping for the opposite. > As long as someone volunteer to implement properly, and the > feature itself is good -- lets make lyx a more feature-rich > document processor. This leads to a bigger userbase > and more developers. :-) And less need to keep other > wordprocessors around. This is a misunderstanding. LaTeXFeatures is the class that deals with automatic package loading. I am all for adding as many new fetaures to LyX as make sense. What I don't like until we have proper package management is to load more LaTeX packages automatically. Loading required packages manually is cumbersome, but IMO still better than automatic loading if the automatic loading can make certain package combinations impossible. Georg
