On Tuesday 17 December 2002 11:48 am, Jean-Marc Lasgouttes wrote: > >>>>> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: > > Angus> On Thursday 28 November 2002 12:45 pm, Jean-Marc Lasgouttes > > Angus> wrote: > >> >>>>> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: > > Angus> The idea is to store this generated .lyx file in a database > Angus> accessible through the BibTeX inset. Ie, it won't be visible to > Angus> the user, but he'll get things like pretty formatting of his > Angus> natbib labels, display of the contents in the citation dialog > Angus> and all for (almost) free. > > >> Why don't you just generate a text only version with a special > >> .bst format? It looked like a simpler and more useful scheme. > > Angus> Maybe simpler to create a text version of the database, but I > Angus> don't think it would be simpler to use within LyX. Correct me > Angus> if I'm wrong of course... > > Angus> This script generates a LyX BibKey environment. We already have > Angus> to handle such an environment. Many people actually use it > Angus> together with natbib, so we've done all the hardwork there > Angus> already. Using this script, we could through away /all/ the > Angus> current BibTeX code (and boy is there lots of it). It would be > Angus> replaced with something that merely generates/loads a hidden > Angus> LyX buffer, to be stored either by the BibTeX inset or by a > Angus> global store, à la graphics cache. > > But then you have to write all the code that uses this hidden buffer.
Are you clearing out your mail tray ;-) I don't get your point. However we handle the BibTeX file we should still load something into memory, rather than parse it each and every time some info is requested as we do now. -- Angus
