Am Montag, 17. September 2012, 12:09:15 schrieb Daniel Nicoletti: > Congrats!
Thanks ;). > as soon as I got some spare time I'll take a look, > some time ago I found your code on some list and > was willing to continue it since I very upset with > mtp and linux (of course because of my new Android phone), > mtpfs is what get's closer to a good solution but it simply > stops working. go-mtpfs is the best Fuse-Implementation right now. It was in part created due to the limits of mtpfs. > Tho mtpfs also uses libmtp I'm not sure the kio will > be able to provide a better implementation, but it > will surely be more well integrated in KDE. And easier. Just plug the device in and click on the Icon in Dolphin (That is planned, but not yet implemented). One other thing that right now is not exactly possible with go-mtpfs (don't know about gvfs.mtp) is accessing multiple devices at the same time. go-mtpfs just mounts the first device it finds. > So now I wonder that it seems gfs, gphoto & friends > all try to talk to the device without locks leading to > some devices have to be rebooted or unplugged, > do you think it's possible to have a lock between these > implementations? I changed paths to writing a DBus Daemon that would do just that a while ago (also due to some limitations that I didn't know how to solve back then). A while ago that changed and the current implementation became feasible. I do however, because of the locks problem and due to the fact that devices can be plugged in and out at any time, keep the device open only for the duration that I am accessing it. So if you don't do anything with the slave, the device is not open. But you are right, all those programs need some form of synchronization. But that is something that needs to be discussed on the libmtp-Mailinglist. When tackling the next big thing, a rewrite of the Amarok MTP Collection I will keep that in mind though. Philipp >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
