Am 30.03.2014 20:34, schrieb Vincent van Ravesteijn:
This stretches the phrase "documentation update" a bit too much to my liking.
OK.
Not only do you update documentation, you move around a lot of files, you're reverting other's commits, you mangle Makefiles and you update the release notes.
The makefile should be OK, no? I made a mistake with a commit but corrected it immediately.
If you'd have posted your proposed patch, others could have commented, and this might have prevented you to move the thesis, svmono and svmult as well. Now, it is very difficult to see what you changed, because you need to subtract the commit and the partial reversal.
I was again too rush then. However, this is what I changed in the files as we discussed it: www.lyx.org/trac/changeset/a860d18b5a722606c68fb1a4ec22ffe3e99792e6/lyxgit I only accidentally moved there all springer files too, while my intention was only to move back svjour.
I don't see this as a 'regression' because I really like having working examples more than non-working templates.
Hmm, these files were designed as templates and we know that people are using them as such. When one is used to have e.g. JASA in the templates and it is no longer there, it is kind of regression from the user's point of view. And we did this only because of a bib-file that users will have to change anyway. So now we fixed this issue and can keep the list as in LyX 2.0.x.
I am however still unsatisfied that we did not found a solution for child documents yet. I think it should not too complicated to implement: - when the user chooses via "New from templates" a master file, this file is copied to the user folder AND alls its childs will moved automatically to the same older too.
I think that will solve the issue, or do miss something. (Just an idea, I will bring this topic back to the list after the release and when I have time.) regards Uwe
