On Fri, Mar 25, 2011 at 10:30 PM, Anton Kreuzkamp <[email protected]> wrote: > On Monday 21 March 2011 00:51:27 Andrea Diamantini wrote: >> I'd like you to argue a bit more about how you "see" these sessions >> working, thanks. > Sorry that I answer only now, my spamfilter ate your mail. > > From a users pov it would simply be the possibility to > - save and close groups of tabs > - restore a closed group of tabs > (btw. I would propose to handle windows as groups of tabs) > > technically I would implement sessions as a new node in the sessions-file > (easy > to do with xml (https://git.reviewboard.kde.org/r/100604/) ) and change the > save/restoreSession() method in sessionmanager.cpp to > save/restoreSession(QString &session = QString()) //default: save/restore last > session(s) I propose this hierarchy for the xml root -windows --sessions [ one of them will be a special session consisting of pinned tabs that span accross sessions ] ---tabs ----history items
This way, a window consists of several tab groups, each group visible only one at a time. Some tabs are always displayed in a window, no matter which session. These are the app tabs. This hierarchy is used by both firefox 4 and opera to handle sessions. > _______________________________________________ > rekonq mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/rekonq > -- Tirtha Chatterjee National Institue of Technology, Durgapur _______________________________________________ rekonq mailing list [email protected] https://mail.kde.org/mailman/listinfo/rekonq
