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

List:       kde-bugs-dist
Subject:    [Bug 8333] setting 'home page' is unintuitive
From:       Casper Planken <cplanken () gmail ! com>
Date:       2008-06-03 17:22:44
Message-ID: 20080603172244.10469.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=8333         




------- Additional Comments From cplanken gmail com  2008-06-03 19:22 -------
A URL-based home isn't practical? I would not support the idea myself if I thought it \
was not practical. But I think you confuse the idea I support as being 1 solution \
over yours. By now I think some more extended ability to set home(s) in relation to \
url/protocol is a valuable addition in the konqueror working environment - separate \
from the problem around view profiles and how they affect home button behavior.

I agree about constantly changing behavior being a problem here - and it would have \
to be some none default ability I think.

If you have tabs then home can be based on the active tab url/protocol. If you have \
'one tab', that is the active tab as well, so the same applies there. If you split \
views, it still is the active view which counts. So...I think what I mean is active \
view, whatever the active view is, which automatically means which active tab.

You would not have to give up a 'fixed' home for a viewing profile. If a new tab/view \
is opened without url, use the current active profile default home. If a new konq. is \
opened, use the home location for that active profile. If a view has an active \
url/protocol, there could be a home in relation to that, optionally.

I think you would not have to give up your suggestion of 'mode of this konq. \
process'. Your kind of suggestion could solve one part of the problem. comment 122 \
would not need to be default behavior, but could make konq. more powerful. If I had \
the time, I would add a demo for this to konq., but I don't so I doubt it will get \
implemented.

But this is getting all too confusing for me to deal with in this bug report.


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