Here are my ideas on how Sessions support could look like from the end user perspective - pano
"Invisible" Sessions support
rekonq will only restore the previous session, if there was a crash. The next time rekonq is started it will automatically restore the previous session and open all tabs from that session. (The Multitask Implementation would make this obsolete, as if a tab crashes, only that particular tab would have to be restored)
Restoring sessions on startup automatically
rekonq will automatically restore your session after starting up rekonq.
A question dialog on every startup
On every startup, rekonq will show a question dialog, whether you want to restore your last session, or not.
"User configurable" Sessions support (aka "The Opera Way")
An additional option is added to the rekonq settings dialog, where the user can decide how his sessions are handled by rekonq, after starting up. For example he can choose between:
- Starting with the Home page (No restoring of Sessions, only when a crash occurs. Practically this is the same as "Possibility 1")
- Automatically restore the previous session (Possibility 2)
- Show a question dialog on every startup (Possibility 3)
pano: For me Possibility 4 is clearly the best, as it would make all users happy. Adjam already told me that this might be a bit too heavy for rekonq though...
What do you think about the following plan:
In the beginning, Possibility 1 is implemented and kept, until the multitask rekonq is finished. Then, since Possibility 1 is obsolete, it will be dropped. After that, Possibility 4 would be implemented. This time it would be more lightweight than it would be right now.