Abdelrazak Younes wrote:
Richard Heck wrote:
Manoj Rajagopalan wrote:
Hi dev group,
Sometime ago, I'd filed a feature request for supporting named
sessions in LyX:
http://bugzilla.lyx.org/show_bug.cgi?id=5551
I'd like to enquire if someone is already working on that or if I
could give this a shot. There seems to be a Session class already for
recording the state of files opened in the last session. This seems
to saved in the 'session' file in .lyx/ (possibly some other place in
windows).
I'd like to propose:
1. the creation of a sessions/ sub dir of the lyx app data folder
where each file stores info about a named session like the current
'session' file.
2. The File menu shows items like "Open session..." and "Recent
sessions >".
3. A "&Session" menu that shows items like "Open session...", "Rename
session...", "Manage sessions..." etc.
4. The extensions ".lys" for a lyx session file
5. command line arg support either with or without a switch (no
prefs) where the .lys file is treated as a session and the relevant
group of files is opened.
I see the developers talk about session management - I don't have a
good idea of whether it addresses the same issue.
I would think this would be quite useful in general. There will be
discussion about where exactly to put the menu items, etc. The only
session-aware stuff I regularly use is under KDE, e.g., the kate
editor. It has a Session menu where all session-related material lives.
I concur, that'd be useful. But before this improvment can take place,
all the home made session management (i.e. the Session class) should be
transferred to the Qt session management framework. At this point, it'd
be easy to have named session.
Abdel.
I just examined the Qt session management framework and it appears to be
tuned to application startup and shutdown as opposed to child document
management.
* QSessionManager does not have constructors
* No classes seem to generate QSessionManager instances
* QApplication seems to be the only consumer of such instances
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.
-- Manoj
