On Wednesday, January 5, 2011, Kevin Ottens wrote: > But my point is that we also have this automounter service nowaday, so the > autorun logic could be moved there.
yes, that could make sense ... esp for services that need the volume to be mounted first. > Of course would mean that automount > would be a prerequisite to "autorun on insert", but I think that could be > a nice trade-off. yes, i agree :) so .. on to other design issues: * it's easy enough to have more than one service set as "run this automatically when <type> appears". we could do a "first come, first serve" approach, or use a weighting in the .desktop value, sort of how we do mimetypes? * how to distinguish between services that need the volume to be mounted first (e.g. gwenview for a disk with photos) and those which specifically should not have the volume mounted (e.g. digikam for a camera). sounds like something to add to the .desktop file as well do you have any suggestions for the above? -- 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
