I don't matter much, but your plan gets "+1" from me. People can find the hidden config by searching for bugs: they'll find their 'resolution' in #312684.
On 03/10/2013 12:15 PM, Mark wrote: > Hi, > > We've already had a long lengthy discussion about this [1] and i'm > really not about to start that over again. The conclusions thus far > seem clear to me, but they are for the future and still "leave a gap" > (in every sense) for the current 4.10 cycle. > > The conclusions: > - Remove the pager by default > - When one adds the pager it should be expected that the user really > wants to add the pager so show it regardless the number of VD's. > > Some more conclusions in case the pager would stay (copied from > Aaron's mail regarding this subject) > /// copy > * hide the pager applet in the chooser when there is only 1 VD. this isn't > great as it means if you have only 1 VD you don't get a pager ever. it also > means lots of instrumentation in the chooser (and probably more stuff in the > applet .desktop files) to make this happen. -1 > > * put a configuration option in the pager which controls the "hide when VD == > 1" behaviour. this could be a hidden config value defaulting to off, allowing > it > to be used by the default panel script .. or it could be in the UI, making it > easy to set whenever. > > personally, i lean towards hidden config. if you want a pager that's always > visible, just add one. > /// end copy > > I personally lean towards removing the pager completely and make it > always visible when it gets added. Right now we are in the situation > where the pager "empty gap" is being noticed and reported [2] > > I'd like to do the following: > 1. for the next 4.10.x patch release patch the main.qml file for this > pager and just show it always. That solves the open gap issue and > fixes the out of the box experience in this case. > 2. for the next release (4.11) remove the pager altogether from the > default setup. I do like to know where and how to do that since i > don't know :) > > I really like to jump to some final conclusions here for the 4.10.2 release. > Does this sound like a good plan? > > Kind regards, > Mark > > [1] http://mail.kde.org/pipermail/plasma-devel/2013-February/023991.html > [2] https://bugs.kde.org/show_bug.cgi?id=312684 > -- GPG fingerprint: 597E 4CE5 6D56 A7C2 DA3A 26FF F21F F828 0C86 165A _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
