On June 29, 2010, Aaron J. Seigo wrote: > On June 29, 2010, Thomas Fjellstrom wrote: > > It is not absolutely necessary. But I can see wanting to group by type. > > I'm > > which can be accomplished in the visualization by looking at the type. > which is, i suppose, why you asked for something like a > getSourcesByProperty method. i'd prefer not to offer that as it is not > generic enough: most visualizations have no need for it, and others > would want/need something more complex. it's easier, for now at least, > to just put such filtering in the visualization code. > > > > to me, it would seem more natural to just list the hosts and the > > > visualization can initially iterate over all sources() and then > > > connect to the sourceAdded and sourceRemoved signals to be notified > > > when hosts come and go. > > > > > > that would resolve your issue fairly neatly? > > > > It is the first design I thought of. I'm not entirely convinced that > > grouping is necessary, but if you have a lot of hosts, you may want to > > hide entire groups of them. With libvirt and Zeroconf/DNDSD sources > > you could easily have many tens, or hundreds of hosts just appear if > > you walk into an office building, a data center, or you're sharing a > > busy wifi network that happens to have wifi-separation turned off. And > > you may also be interested in /some/ of those hosts but not all, so > > you may not want to turn off the dynamic sources. > > ... which should be possible in the visualization.
Oh right, just remembered why I needed the extra sources. At least the Manual source has a service that allows you to add and delete hosts. I imagine the other sources may want services for setting various things. -- Thomas Fjellstrom [email protected] _______________________________________________ Plasma-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/plasma-devel
