Den 14. mai 2015 14:20, skrev Uwe Stöhr:
Dear LyXers,
as you know LyX has a lack of development manpower. It is therefore
sensible to see where we can save some.
In my opinion our current reversion policy to older LyX versions
should be changed.
Reality check:
- If you start a project
Den 14. mai 2015 14:20, skrev Uwe Stöhr:
Dear LyXers,
as you know LyX has a lack of development manpower. It is therefore
sensible to see where we can save some.
In my opinion our current reversion policy to older LyX versions
should be changed.
Reality check:
- If you start a project
Uwe Stöhr wrote:
I don't understand how a software update of a particular program can break
the integrity of the OS. I mean at the university and now in the industry
everybody needs his special programs, some need CAS, some CAD programs,
some need special simulation software, tax software
Am 18.05.2015 um 02:49 schrieb Pavel Sanda:
- There is no reason why one collaborator could not update to the same
software version since LyX is free. (Your admin cannot deny if he hinders
you from doing your job you are paid for.)
My own experience is very contrary to this. Institutions
Am 17.05.2015 um 02:58 schrieb Richard Heck:
This is why I proposed to warn the user that his file will be saved in
a new format and why we should create a backup copy in the old format.
In case of problems the user can continue with the backup copy and the
old version. So no reversion is
Am 18.05.2015 um 02:49 schrieb Pavel Sanda:
- There is no reason why one collaborator could not update to the same
software version since LyX is free. (Your admin cannot deny if he hinders
you from doing your job you are paid for.)
My own experience is very contrary to this. Institutions
Am 17.05.2015 um 02:58 schrieb Richard Heck:
This is why I proposed to warn the user that his file will be saved in
a new format and why we should create a backup copy in the old format.
In case of problems the user can continue with the backup copy and the
old version. So no reversion is
Uwe Stöhr wrote:
> I don't understand how a software update of a particular program can break
> the integrity of the OS. I mean at the university and now in the industry
> everybody needs his special programs, some need CAS, some CAD programs,
> some need special simulation software, tax
Le 14/05/2015 14:20, Uwe Stöhr a écrit :
Current policy:
- Assume that you have LyX 2.2 and your collaborator has 2.1. You add a
box with a 10 pt thick frame and export the document to the format of
LyX 2.1. As result you will get some TeX code. To be able to collaborate
you will have to live
Le 14/05/2015 14:20, Uwe Stöhr a écrit :
Current policy:
- Assume that you have LyX 2.2 and your collaborator has 2.1. You add a
box with a 10 pt thick frame and export the document to the format of
LyX 2.1. As result you will get some TeX code. To be able to collaborate
you will have to live
Uwe Stöhr wrote:
Reality check:
- There is no reason why one collaborator could not update to the same
software version since LyX is free. (Your admin cannot deny if he hinders
you from doing your job you are paid for.)
My own experience is very contrary to this. Institutions I'm/was
Uwe Stöhr wrote:
> Reality check:
> - There is no reason why one collaborator could not update to the same
> software version since LyX is free. (Your admin cannot deny if he hinders
> you from doing your job you are paid for.)
My own experience is very contrary to this. Institutions I'm/was
Le 14/05/2015 14:20, Uwe Stöhr a écrit :
Reality check:
- If you start a project one of the basic and also most common rule is
to use the same software. This was the case for collaborations at the
University (for most cases) and is a strict rule for all collaborations
in the industry I am part
2015-05-16 2:59 GMT+02:00 Uwe Stöhr :
Am 14.05.2015 um 14:34 schrieb Jürgen Spitzmüller:
I disagree with this proposal and opt for going with our current policy.
But why? What are your arguments? What are your experiences with
collaborations?
Backwards compatibility of course.
Jürgen
On 05/16/2015 07:11 PM, Uwe Stöhr wrote:
Am 16.05.2015 um 13:48 schrieb Jean-Marc Lasgouttes:
I do not agree with your analysis, in particular since upgrading LyX on
an administrated linux machine is not always a given: the admin will
have to update LyX on all machines, and some users may not
Am 16.05.2015 um 13:48 schrieb Jean-Marc Lasgouttes:
I do not agree with your analysis, in particular since upgrading LyX on
an administrated linux machine is not always a given: the admin will
have to update LyX on all machines, and some users may not agree with that.
The question is then
2015-05-16 2:59 GMT+02:00 Uwe Stöhr :
> Am 14.05.2015 um 14:34 schrieb Jürgen Spitzmüller:
>
> I disagree with this proposal and opt for going with our current policy.
>>
>
> But why? What are your arguments? What are your experiences with
> collaborations?
>
Backwards compatibility of course.
Le 14/05/2015 14:20, Uwe Stöhr a écrit :
Reality check:
- If you start a project one of the basic and also most common rule is
to use the same software. This was the case for collaborations at the
University (for most cases) and is a strict rule for all collaborations
in the industry I am part
Am 16.05.2015 um 13:48 schrieb Jean-Marc Lasgouttes:
I do not agree with your analysis, in particular since upgrading LyX on
an administrated linux machine is not always a given: the admin will
have to update LyX on all machines, and some users may not agree with that.
The question is then
On 05/16/2015 07:11 PM, Uwe Stöhr wrote:
Am 16.05.2015 um 13:48 schrieb Jean-Marc Lasgouttes:
I do not agree with your analysis, in particular since upgrading LyX on
an administrated linux machine is not always a given: the admin will
have to update LyX on all machines, and some users may not
Am 14.05.2015 um 14:34 schrieb Jürgen Spitzmüller:
I disagree with this proposal and opt for going with our current policy.
But why? What are your arguments? What are your experiences with
collaborations?
regards Uwe
Am 14.05.2015 um 14:34 schrieb Jürgen Spitzmüller:
I disagree with this proposal and opt for going with our current policy.
But why? What are your arguments? What are your experiences with
collaborations?
regards Uwe
Dear LyXers,
as you know LyX has a lack of development manpower. It is therefore
sensible to see where we can save some.
In my opinion our current reversion policy to older LyX versions should
be changed.
Reality check:
- If you start a project one of the basic and also most common rule is
Dear LyXers,
as you know LyX has a lack of development manpower. It is therefore
sensible to see where we can save some.
In my opinion our current reversion policy to older LyX versions should
be changed.
Reality check:
- If you start a project one of the basic and also most common rule is
24 matches
Mail list logo
