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

List:       koffice-devel
Subject:    Re: A simple place for complex settings, KOffice-wide
From:       Dirk_Schönberger <dirk.schoenberger () sz-online ! de>
Date:       2007-01-10 21:08:34
Message-ID: 000501c734fb$82d23b80$14b2a8c0 () rincewind
[Download RAW message or body]

> Because I can type "file" (translated) and can quickly see all the options
> related to it (works very well assuming a rich enough dictionary is set
up).
> Options are related each other like in a graph stuctue not just a tree.
Users
> do search, not browse once the tree is larger than a big screen.

> It's not a replacement of handcrafted GUIs, it's a tool that enables the
same
> feature as in KControl. I mentioned Konqueror because it is most obvious
> candidate for such addition, even if the first user of the stuff would be
> Kexi, then KDevelop.

Possibly I am totally wrong on this, but why not do something along the
lines of
http://bugs.kde.org/show_bug.cgi?id=64191

Basically you have your list of possible configuration options / keys, say,
for configuring konqueror.
These keys are put into an action list. This action list could by created
automatically by say, kconfigxt resp. its compiler.
If you have a simple list, you could create multiple views from it. One view
would be a "normal" Qt dialog, which could be created from an external
XMLGUI resource.
Another view would be a a (GUI) list or tree.

The dependencies between different actions, say that a action sould be
disabled if another action is enabled, could be implemented as communition
between (K) Actions, instead of actual visual representations / widgets.

Regards
Dirk

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]