kdelibs/kdeui

Matthias Kretz kretz at kde.org
Sat Jun 22 17:01:54 BST 2002


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 22 June 2002 17:06, Thomas Zander wrote:
> Simon has a good point, I don't think this is a good idea from a usability
> POV, since this makes lazy loading of config modules a lot easier, which
> then makes for an inconsistent GUI.

What do you mean with lazy loading? Loading by accident? The way I'm doing it 
for my KView plugins is:
(void)new KViewPluginnameConfModule( this );
And that works just great, because when the plugin is deleted the module 
disappears automatically (thanks to QObject).

> Plus that is makes the design of the dialogs a lot harder since the naming
> can 'conflict'. Two parts that configure 'general' seems a bit stupid...

With design you're only talking about overlapping naming of modules? Hmm, what 
about the way Kate does it? Using a KDialogBase::TreeList and creating 
entries for the application and every part. Modules are then inserted as 
subentries.

OK, if you think it's bad using the Singleton Pattern I'd like to hear an 
alternative. Currently I can't imagine anything better than what I wrote ;-)

- -- 
C'ya
        Matthias
________________________________________________________
Matthias Kretz (Germany)
http://Vir.homeip.net/
MatthiasKretz at gmx.net, kretz at kde.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9FJ97yg4WnCj6OIoRAp55AKDji4wf23Ng4nOkabldU883RmqcugCgwpB3
FpcsT7QXsdDe13MrOn78bqU=
=QkB6
-----END PGP SIGNATURE-----





More information about the kde-core-devel mailing list