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

List:       kde-bugs-dist
Subject:    [Bug 58580] Konqueror sidebar settings not stored in profile
From:       Alex Radu <WinterWolf () myway ! com>
Date:       2004-03-21 19:38:58
Message-ID: 20040321193858.7595.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=58580      




------- Additional Comments From WinterWolf myway com  2004-03-21 20:38 -------
Checkout the duplicated #62679 and #58620 for further clarification.

"It doesn't remember sidebar tabs. For example, if I add a new sidebar tab, such as a \
link to my pictures folder or a media player it will not remember it in the view \
profile, it will remember it globally for all profiles. Same thing happens if I want \
to remove a sidebar tab such as a the media player from one of my profiles, such as \
the web browsing profile. It removes it globally.   
 All sidebar options should be saved in the View Profile. This feature must really be \
fixed especially since KDE 3.2 will let me have RSS feeds and I definitely don't want \
to have 10 website RSS feeds and a sidebar media player + all the normal stuff \
cluttering all my views. I would want the RSS feeds + history, network, and bookmarks \
but not the rest in my web browsing mode."

This is a serious limitation to Konqueror's view profile and a big usability problem. \
KDE needs to further make the web browser and file managers feel like they are meant \
for that task when you are using it. Having 12 tabs because you can not individualize \
tabs for each view really limits this. The profile feature is the key to making \
Konqueror a more comfortable beast for file browsing and web browsing over virtually \
any protocol.

IMPORTANT: From Waldo Bastian:
"Konqueror now passes profile saving/loading info to the views. This makes it \
possible for the sidebar to implement the desired behavior. This is not yet \
implemented though. "

He made this comment on #58260, would this fix what I'm talking about?


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