Start new session...

Martijn Klingens klingens at
Sun Oct 13 01:59:31 BST 2002

On Saturday 12 October 2002 20:16, Oswald Buddenhagen wrote:
> as a compromise i modified genkdmconf for now, so it does not
> automatically add reserve display entries. users that did not notice
> the feature yet also won't notice now. there are no new users
> "endangered" and those the already used and liked the feature now have
> an improved usability.

With that default value changed the KDE 3.0 behaviour is much less dangerous, 

I think you can better revert, think things over and commit something 
_complete_ and _stable_ when it is _finished_, for whenever release this may 
be. I think we sorted out most of the usability stuff, but rushing this in so 
close before really really makes me shiver.

No matter how much I like your code I also consider the new GUI a _new_ 
feature and moreover I agree with Ingo and Thomas that the feature is now 
extremely close to people that don't realize the danger until it is too late.

I am not at all convinced you can iron out all issues before 3.1 is out of the 
door, even if there were no string freezes, and even if you can you are not 
fixing (or at least preventing) bugs, but instead adding potential new ones.

This stuff either needs a close-to-perfect GUI, or none at all. Not much 
compromises are acceptable here. I understand from your mails that you can't 
make 'close-to-perfect' for 3.1 anyway, which automatically puts this in the 
'not at all' category.

Really, this is too late. We're in a feature freeze and this doesn't belong 
here. If it would have worked out immediately I may have let it slip but 
since it doesn't work out you're much better off postponing it.

Cheer up, 3.1 is not the end of the world and I'm sure 3.2 will have a killer 
feature for KDM! :-)

More information about the kde-core-devel mailing list