[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lyx-devel
Subject:    Automatic recognization of .cls/.layout files.
From:       "Bo Peng" <ben.bob () gmail ! com>
Date:       2006-03-31 17:11:47
Message-ID: 6ea7b5430603310911j3a907704m6453645992f24591 () mail ! gmail ! com
[Download RAW message or body]

Dear list,

With my previous pre-patch (is or will be working), a lyx user can
open a .lyx file with its .cls and .layout files stored together. Now,
it comes to the question how to make use of existing .cls/.layout when
a new lyx file is created.

Currently, a user is supposed to put .cls under TEXINPUTS (localtexmf
etc) and .layout under $HOME/.lyx/layouts, start lyx, run reconfigure
and restart lyx.

What would be more convenient to users? What do you think about the
following possibilities? (Please *only* think from a user's
prospective. :-)

1. When lyx starts, compare the dates between $HOME/.lyx/textclass.lst
and $HOME/.lyx/layouts. If new layouts have been added to local layout
directory. Run a (partial) reconfigure before lyx starts. (This can be
done through a call to, for example, configure.py --check-new-layout )

2. When lyx starts, check the availability of any .cls/.layout files
in the current directory and add them to testclasslist (without
changing $HOME/.lyx/textclass.lst ). This allows user to create new
document with cls/layout in the current directory. This will not work
well under windows when we always start lyx from a certain directory
(double click lyx icon.)

3. A "load" button next to the "document class" list in the "document
settings" dialog so a user can specify a layout file without
reconfiguration.

Again, please *only* think from a user's prospective. If you have to
think about implementation, 1, and 2 are easy to do, and 3 should not
be too difficult.

Bo

[prev in list] [next in list] [prev in thread] [next in thread]