On July 14, 2010, Thomas Fjellstrom wrote: > On July 14, 2010, Aaron J. Seigo wrote: > > On July 14, 2010, Thomas Fjellstrom wrote: > > > Normally I would agree. Do you volunteer to make sure the bug never > > > appears again? > > > > yes, we do. now that we're at the point of such questions, though, it's > > safe to say that this thread has reached the end of its ability to > > produce useful input. let's stop here. > > I happen to think its a perfectly valid point. If you can't guarantee the > bug won't reappear, an easily discoverable work around is going to have to > be made for it.
if the bug has a very low possibility of reappearing and if it does the consequences are nominal, then hobbling the default interface for everyone all the time is a really bad idea. so no, it isn't a valid point at all. > Just a little bit of brain storming, but some place, an interface showing a > list of the current running plasmoids (one item per plasmoid instance), > which when hovered over with the mouse cause them to be highlighted by > plasma itself. It would make the most sense if it were to hide all normal > windows, or bring plasma forward. last time we discussed this (on this list even, iirc), the possibility of having a listing of running plasmoids in the tasks (ctrl+escape) window from krunner sounded pretty nice. and it could be without all the other problems of adding removal to the "add widgets" interface. > Possibly tie it into the ZUI to show all > current containments. there is no ZUI anymore. > That said, a much simpler and easier to implement idea would be to add back > that minus button and just force people to add back instances they wanted > (if theres more than one running). which was exactly the problem: it doesn't say what is being removed, leading to loss of desired items. this made the minus sign less than useful. adding finer granularity to it just makes it harder to use. simpler does not always mean better. so, no, this feature will not be re-appearing. that is final. > Maybe as an option. that isn't how we work here. if there is a solution to a problem that isn't workable, we don't simply say "well, just throw it in there and make it an option, even if it does suck." that's just a way to make the software suck twice as hard: now it has a poor solution -and- a configuration option for people to deal with. lose. > > p.s. the javascript console lets you get to any plasmoid using scripting. > > And I'm sure its fully documented, it is. > easily discoverable, and understandable by mere users. it isn't. and i don't think it's a solution for "mere users" (a phrase that's a bit ... un-nice to the people who use kde software, imho). it's an option for those of us who run into such situations during development. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
