Bug 103312

Summary: Configure dialog KConfigXT problems and confusion
Product: [Applications] akregator Reporter: icefox
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: CONFIRMED ---    
Severity: wishlist    
Priority: NOR    
Version: 1.0   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description icefox 2005-04-05 21:35:13 UTC 
Version:           1.0 (using KDE 3.4.0, Debian Package 4:3.4.0-0pre2 (3.1))
Compiler:          gcc version 3.3.5 (Debian 1:3.3.5-8)
OS:                Linux (i686) release 2.6.8-1-686

I see there is a KConfigXT file in cvs which suggest that 1.0 uses KConfigXT, but the buttons never get disabled suggesting something is wrong.  Right now if I hit the Defaults button and the Defaults button is still enabled (it should automatically disable itself as it is at the default).

A few other nit picks in the dialog:

-The network GROUP box only has one item in it.
-What does "Use the browser cache" mean? There isn't a "Whats This" for this explaining what it does.  Does that refure to the polling of rss files of the web servers and to ignore 304 returns or does it mean to use Konquror's web cache or something else?  Is there even ever a time where a users (me)  would want to turn this off?
-Default Archive Settings group box isn't needed as it is a group box with nothing else in the page to separate them from.  It should be hidden.
-Hitting the Default button makes the appearance font size's go to 2, probably not the correct size.  There might be other incorrect default values.
-Left and middle click behavior should probably be grouped in a box "Mouse Behavior" with the strings "Left mouse click: [Open in...]" and "Middle mouse click: [Open in...]".  This removes two group boxes that each only have 1 item in them and makes it much easier to read/understand.
-The External browsing dialog should be removed and just call the kde browser() function which will open the default one as specified by the user.  This way if a users change from FireFox to Opera they only have to change one place and not in ten applications. 
-There is a checkbox to open new articles in background tabs, but that option is present in in left/middle click list.  When does this checkbox apply?  What if I select to open in external browser and then check this box?  what will happen?  It is really an unclear option.
Comment 1 Teemu Rytilahti 2005-04-06 14:40:25 UTC 
Use browser cache means that librss tells KIO to use cache. It causes no new articles appearing for some people, like me.
Comment 2 icefox 2005-04-06 15:32:38 UTC 
Wouldn't the browser cache be an option in KIO or konqeror config dialog?  It sounds almost like a bug in kio that should be fixed rather then having a workaround.
Comment 3 Frank Osterfeld 2005-04-26 20:31:21 UTC 
The problem with default values exists for options where we don't use kconfigxt due to its limitations. We have to fix that, same for disabling them when immutable flag is set. (via Kiosk)

> -The External browsing dialog should be removed and just call the kde
> browser() function

Hmm, would this also work for people having only kdelibs and kdepim installed?

> There is a checkbox to open new articles in background tabs, but that option is present in in left/middle click list. 

Yup, that option should be removed.
Comment 4 icefox 2005-04-29 05:22:43 UTC 
KConfigXT should automatically disable options that are immutable.  Does it not work for you?

For the browser issue I am not sure if the Gnome tools set the KDE's default when you set the Gnome default.  Many applications did in the past include there own browser configuration and they were all removed in an effort to make the desktop more consistant.  I know that in KDE4 the mimetype files/datbase for KDE and Gnome will be the same, but like I said I am not 100% sure what the gnome tool does right now.
Comment 5 Justin Zobel 2021-03-09 04:10:43 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.