On 12/09/2012 08:09 PM, Uwe Stöhr wrote:
Am 07.12.2012 10:09, schrieb Jean-Marc Lasgouttes:
OK. Let's face it: everything does not work like you are used to. It
is not good or bad, it is a
fact. And you cannot force everybody to do what you think is good.
I don't want to force anybody to do something. All I want to have is a
working LyX!
- What can I always assume as a user? - That if I have the latest
versions it works. But that was for modernCV not the case so I got
active. Why is that forbidden?
It's not. The point is that you have to add a new layout, not just
change the existing one. We want both to support the new version AND to
continue supporting whatever version we previously supported.
- From my point as the author of a layout I cannot know what a version
of the document class a user might have installed. So what should I
do, if the layout works only with modernCV 1.0, but fails with 0.9 and
the recent version 1.2? - I have update the layout to work with the
latest version.
Long-term, as I said, we should make layouts version-aware somehow, at
least in so far as we try to detect version during configuration and
enable or disable layouts depending upon which versions we detect. I can
even imagine putting conditional code into layouts themselves.
- What do you expect as LyX developer, that people are not bothering
you with complaints about things you already fixed years ago investing
your spare time. So please be that fair and allow also the modernCV
developer to act like you. Of course he has the right to improve his
class adding new commands, rename some, changing the number of
arguments etc.
And he thereby breaks huge numbers of documents created with his class?
One ought to take some care around this sort of issue.
Richard