>IIUC we should be careful to distinguish the application session from >the document session. The LyX application is a part of the windows/ >linux/mac desktop and is handed a session manager from the desktop >overlord for clean startup and shutdown. But for named document >sessions, LyX plays the role of the overlord that should issue a >session-handle to its minion documents. My feeling is that the document >sessions have a much simpler spec than the Qt session framework and we >might be better of writing our own (simpler) classes. > >Please correct me if I am wrong. >
Hi Manoj, Just another e-mail to support your enthusiasm. I was thinking about your proposal and I wondered the following. You want to make a LyX session file to manage master and child documents. However, as it is now, all child and master documents are loaded when loading a child or master document. This basically means that we already have the possibility to open a set of files at once. (To see this, open a master document and press Ctrl-Tab. Because of a bug this will open or show (as it is already loaded) the child documents). There also is a section in the Document->Outline which shows all child documents. This might be improved a little to show the structure of the master file and all child documents (and maybe childs of childs), but it shows the structure in some way. That's why I was wondering whether a Session file is really needed. Do you want the possibility to add other documents to the session and/or non-LyX files ? My idea would be to enhance the GUI to show/manage the files. Also, I'm sort of working on the embedding issue, which needs to collect all dependent files of a document. This might be close related to this issue. I'd like to encourage you to discuss your ideas on the list and do ask for help if you have any questions. > -- Manoj Vincent
