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

List:       kwrite-devel
Subject:    [Bug 102868] dump configuration variables to stdout
From:       Anders Lund <anders () alweb ! dk>
Date:       2005-03-31 13:58:53
Message-ID: 20050331135853.2486.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=102868         




------- Additional Comments From anders alweb dk  2005-03-31 15:58 -------
Wednesday 30 March 2005 17:50 skrev Leo Savernik:
[bugs.kde.org quoted mail]

Just to let you know:

I have had the wish of a display of document configuration for a long time, as 
well as thoughts about better maintainability as for the commands and 
modelines variations of configuration data. So I'm all for.

I dislike hidden obfuscated shortcuts. Any action in a GUI application should 
have a representation in the GUI.

My thoughts are
* move the handling of configuration related modelins to the *KateConfig 
derived classes
* move the commands related to configuration data to the KateConfig* classes 
(which will then derive Kate::Command, and be added to the command line). I 
also want to provide a 'global' option to all the configuration data setters.
* have a virtual QString KateConfig::dump() const method, and implement it. 
the GUI representation could be a sidget to display the data, with a 'copy' 
button on it, available by an action or a command.

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