https://bugs.kde.org/show_bug.cgi?id=442186
Harald Sitter <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Show accessed Samba shares |Show accessed remote shares |as on-demand items in the |as on-demand items in the |Networks section of the |Networks section of the |places panel |places panel --- Comment #6 from Harald Sitter <[email protected]> --- After some musing I'm not convinced the worker actually should do anything. The main trick here is that the worker doesn't know what the client application is doing. e.g. you could have a sync application that uses KIO to implement network syncing. The user doesn't necessarily know about it nor did they take any active actions to visit the host, so it'd be odd if a random host then appears in the places model. That leads me to conclude that realistically this needs to be entirely handled in a higher level system. There is also the fact that this should extend to all remote slaves. There's no reason bluetooth, sftp, gdrive shouldn't all work the same. So, also from a code reuse POV it probably makes more sense that a higher level system takes care of this for all workers with a suitable property set to opt into this. A number of questions also popped into my mind: What does temporary mean exactly? Do they go away when you log out? Or on reboot? What if you don't reboot for a year? Or maybe there's always only N entries at most? What exactly is the UX here? You go into a host in dolphin and it adds it into the model? Or do you have to actually open a file there? Does it also apply if you manually enter the URL? What if you manually open a program with an url (`gwenview smb://foo/meow.jpg`)? Do file open dialogs work the same as though used through dolphin? -- You are receiving this mail because: You are watching all bug changes.
