Bo Peng wrote:
I still do not get it. configure/configure.py will scan through all
layout files. If some of them are 1.3, we can convert them to 1.4 in
place. It does not make sense to check the version of a layout file
whenever it is called.
I forgot that configure.py scans the layout
I forgot that configure.py scans the layout files. I thought that you wanted
to define a converter.
Regarding Angus' concern of 'in-place modification' and the version
signature problem, a quick solution may be a.layout - a.layout2
during configuration. Lyx then need to check a.layout2
Bo Peng wrote:
Then why do we need to 'convert' a layout file? Why can not we simply
handle two versions internally?
Because that would make the parsing code too complicated (not now, but if
the changes become bigger). Look at the tabular or graphics inset of older
versions of LyX to see an
Bo Peng wrote:
> I still do not get it. configure/configure.py will scan through all
> layout files. If some of them are 1.3, we can convert them to 1.4 in
> place. It does not make sense to check the version of a layout file
> whenever it is called.
I forgot that configure.py scans the layout
>
> I forgot that configure.py scans the layout files. I thought that you wanted
> to define a converter.
>
Regarding Angus' concern of 'in-place modification' and the version
signature problem, a quick solution may be a.layout -> a.layout2
during configuration. Lyx then need to check a.layout2
Bo Peng wrote:
> Then why do we need to 'convert' a layout file? Why can not we simply
> handle two versions internally?
Because that would make the parsing code too complicated (not now, but if
the changes become bigger). Look at the tabular or graphics inset of older
versions of LyX to see an
Am Samstag, 17. September 2005 17:09 schrieb Bo Peng:
Is there a way to tell whether a layout file is 1.3 or 1.4?
Only by looking at the contents. I guess we should add a version field.
If so,
your converter can be easily added to configure.py.
This is not the right place, since layout
This is not the right place, since layout files are not loaded via the
converter mechanism. If the converter is to be used we know that it is
available and it will be called directly from LyX (look how lyx2lyx is
called).
I still do not get it. configure/configure.py will scan through all
Bo Peng wrote:
This is not the right place, since layout files are not loaded via the
converter mechanism. If the converter is to be used we know that it is
available and it will be called directly from LyX (look how lyx2lyx is
called).
I still do not get it. configure/configure.py will
Just one reason why use of configure.py might not be a good idea.
Then why do we need to 'convert' a layout file? Why can not we simply
handle two versions internally? Anyway, a version signature would help
in all cases.
Bo
On Sunday 18 September 2005 19:09, Bo Peng wrote:
Just one reason why use of configure.py might not be a good idea.
Then why do we need to 'convert' a layout file? Why can not we simply
handle two versions internally? Anyway, a version signature would help
in all cases.
FWIW that is on my
Am Samstag, 17. September 2005 17:09 schrieb Bo Peng:
> Is there a way to tell whether a layout file is 1.3 or 1.4?
Only by looking at the contents. I guess we should add a version field.
> If so,
> your converter can be easily added to configure.py.
This is not the right place, since layout
> This is not the right place, since layout files are not loaded via the
> converter mechanism. If the converter is to be used we know that it is
> available and it will be called directly from LyX (look how lyx2lyx is
> called).
I still do not get it. configure/configure.py will scan through all
Bo Peng wrote:
>> This is not the right place, since layout files are not loaded via the
>> converter mechanism. If the converter is to be used we know that it is
>> available and it will be called directly from LyX (look how lyx2lyx is
>> called).
>
> I still do not get it.
> Just one reason why use of configure.py might not be a good idea.
>
Then why do we need to 'convert' a layout file? Why can not we simply
handle two versions internally? Anyway, a version signature would help
in all cases.
Bo
On Sunday 18 September 2005 19:09, Bo Peng wrote:
> > Just one reason why use of configure.py might not be a good idea.
>
> Then why do we need to 'convert' a layout file? Why can not we simply
> handle two versions internally? Anyway, a version signature would help
> in all cases.
FWIW that is
The fact that LyX 1.4 can't read all 1.3 layout files will annoy users
with customized layout files.
Since the differences are small I hacked together a little converter. It
will convert 1.3 layout files to 1.4 format. Usage:
python layout2layout.py old.layout new.layout
or as a filter:
I'd like to see this integrated in 1.4.0: Either call it at configure time
and convert all layout files permanently, or call it from
LyXTextClass::Read() if a layout file is too old. For the latter we
should probably add version information to the layout files.
Comments?
Is there a way to
The fact that LyX 1.4 can't read all 1.3 layout files will annoy users
with customized layout files.
Since the differences are small I hacked together a little converter. It
will convert 1.3 layout files to 1.4 format. Usage:
python layout2layout.py old.layout new.layout
or as a filter:
> I'd like to see this integrated in 1.4.0: Either call it at configure time
> and convert all layout files permanently, or call it from
> LyXTextClass::Read() if a layout file is too old. For the latter we
> should probably add version information to the layout files.
>
> Comments?
Is there a
20 matches
Mail list logo
