Aaron J. Seigo aseigo at olympusproject.org
Mon Jun 30 18:08:23 BST 2003

Hash: SHA1

On Monday 30 June 2003 09:15, Ian Reinhart Geiser wrote:
> On Monday 30 June 2003 10:20 am, Waldo Bastian wrote:
> > Maybe the design should be reevaluated then. It's rather a huge burden if
> > we can no longer polish our UI without causing configuration breakage.
> This also implies that our config files where correct to start with?  While
> thats subjective, id be more inclined that UI polish takes precidence.

i think Waldo was referring to the fact that by storing a numerical value that 
relates to the ordering of the item in a combobox, the UI is now tied to that 
representation in the configuration file. 

if it was changed from a combobox to a listbox, or god forbid a tree, or radio 
buttons, or.... then a configuration file change would be necessary 
(kconfupdate, hooray for wasting developer's time)

if another option is added, causing the order of items in the listbox to 
changed, same story. unless we decide that we don't need/want to keep things 
in a sane alphabetical order.

honestly, i don't see the problem with enabling KAutoConfig to associate a map 
of values with the entries in a multi-entry widget. this would be a couple 
lines of code for the developer (basically codifying that mapping) and would 
ensure maximum flexibility in UI reorg later on. the fact that it's nicer to 
the config files would just be a bonus.

hope i've not oversummarized and bored everyone; i just woke up.. =)

- -- 
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE: The 'K' is for 'kick ass'
http://www.kde.org       http://promo.kde.org/3.1/feature_guide.php
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)


More information about the kde-core-devel mailing list