[prev in list] [next in list] [prev in thread] [next in thread] 

List:       konq-bugs
Subject:    [Bug 63505] Wish: Save and load of current browsing session (tab
From:       Peter Schuller <peter.schuller () infidyne ! com>
Date:       2003-11-24 1:12:47
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
     
http://bugs.kde.org/show_bug.cgi?id=63505     




------- Additional Comments From peter.schuller@infidyne.com  2003-11-24 02:12 \
------- I think the problem here is that Konqueror is typically used both as a \
one-window-with-many-tabs web browser aswell as the conventional multiple-window web \
browser. So, being used to browsers like Opera where one typically have a single \
Opera session running with all Windows in the MDI interface, one miss the way Opera \
manages itself without explicit interaction.

But on the other hand, the ability to pop up additional browser windows is obviously \
not something to give up. Nor is the ability to have multiple Windows, each \
containing multiple tabs.

The core problem is that it is not obvious (to a human nor to Konqueror) which set of \
tabs a user would want went starting a Konqueror window without a target URL, because \
Konqueor is not limited to the one-single-main-browser-window concept.

I have a suggestion for how this might be "handled", meaning how to satisfy those who \
want Opera style profile handling without giving up any of the advantages of \
Konqueror's Windows handling in general. In other words, having a "main browser \
window" with automatic profile management in addition to several other windows.

Konqueror could have one "special" automatically managed profile. When this profile \
is used, changes to it (i.e., additions and removals of tabs and/or changing the \
contents of tabs) would be automatically saved continously as the user is browsing. \
Thus, when closing Konqueror (or even in the event of some form av uncontrolled \
shutdown, barring file corruption) this profile will be up to date for the next \
invocation.

The question is how to tell Konqueror that one want to launch the "main window" (in \
which the automatically managed profile is used) without actually having to \
explicitly manage this. I have think of three possible solutions:

(1) Provide a command line argument that says to invoke whatever is being requested \
in the "main window". If the "main window" is not open yet, it will be opened, with \
the addition of any requested tabs given to it. This could be a separate icon in the \
GUI aswell. This fully retains all features and forms of usability of the current \
Konqueror, while adding to the abilities with respect to Opera style profile \
management.

(2) One could also have a startup sequence where:
   - If the main window is already open, always open a new window
   - If the main window is not open, open a new window if a specific URL
     is specified as a target; but if konqueror is launched without
     a specific target, assume the user wants to open his/her
     main window.

(3) Another option for a startup sequence:
   - If the main window is already open, always open in the form
     of a new tab in the main window.
   - If the main window is not already open, open the main window
     and add a tab for the specified target, if any.
   - Only open a separate window if explicitly asked for (such as
     by command line argument). The main window will always
     remain the main window, only tabs explicitly opened in 
     these independent windows would end up here.

Just a few thoughts.
_______________________________________________
Konq-bugs mailing list
Konq-bugs@mail.kde.org
https://mail.kde.org/mailman/listinfo/konq-bugs


[prev in list] [next in list] [prev in thread] [next in thread]