Version: (using Devel) Installed from: Compiled sources It would be really nice if Dolphin had Dropbox support integrated into it. Currently there's a nautilus plug-in (GPL'ed) that's maintained by the Dropbox people themselves, to be found at http://getdropbox.com/ . What the plugin does is download the dropbox daemon (which is proprietary) and puts "emblems" on files and folders that indicate their state in relation to the dropbox server (in sync, out of sync, syncing).
I would also love this :) I would also be happy with just some sort of plasmoid instead. A variance of the Folder View perhaps??
That would be really awesome! If it's made as a KIO-slave it could be used anywhere in KDE: Dolphin, Konqueror, plasmoids (like Folderview)... 20 votes :D
Well, I've never voted before, but this one has 20 votes from me too! Dropbox has quickly become essential for my work, and Nautilus is causing some very funky behaviour in KDE - sometimes even causing one of my virtual desktops to change over to Gnome (I guess that would be pretty cool if I liked Gnome). I'd write a bug report on that, but it would be so much nicer not to have to use Nautilus at all ;-)
I've created a new account here to vote for Dropbox functionality in KDE :) 20 votes more ! :)
As we have the functionality for these overlays already for Subversion folders, wouldn't it be possible to expand it for the dropbox-folder ?
*** Bug 204396 has been marked as a duplicate of this bug. ***
(In reply to comment #3) Did you find a way around that? More annoying is the gnome userspace mounting stuff seems to take over and my KDE tools can't mount (or see those items.) I am not sure why they even tied it to nautilus at all. It works just fine when I add stuff to the drop box folder using dolphin
(In reply to comment #7) > (In reply to comment #3) > Did you find a way around that? More annoying is the gnome userspace mounting > stuff seems to take over and my KDE tools can't mount (or see those items.) > > I am not sure why they even tied it to nautilus at all. It works just fine > when I add stuff to the drop box folder using dolphin There's no need to have Nautilus installed. Dropbox does not depend on it to work. Nautilus provides a UI for sync status feedback and some context-menu options to make the user's life easier, but it is the dropbox daemon that takes care of the syncing. What you have to do to install dropbox without Nautilus is to install the dropbox package and then manually tell it to download the daemon with this command: $ dropbox start -i after the process is complete, you just have to make sure that ~/.dropbox-dist/dropboxd is started upon logging in. That said, I still want the UI functionality (sync status, context menu items) integrated into KDE! :D
(In reply to comment #8) > (In reply to comment #7) > > (In reply to comment #3) > > Did you find a way around that? More annoying is the gnome userspace mounting > > stuff seems to take over and my KDE tools can't mount (or see those items.) > > > > I am not sure why they even tied it to nautilus at all. It works just fine > > when I add stuff to the drop box folder using dolphin > > There's no need to have Nautilus installed. Dropbox does not depend on it to > work. Nautilus provides a UI for sync status feedback and some context-menu > options to make the user's life easier, but it is the dropbox daemon that takes > care of the syncing. > > What you have to do to install dropbox without Nautilus is to install the > dropbox package and then manually tell it to download the daemon with this > command: > > $ dropbox start -i > > after the process is complete, you just have to make sure that > ~/.dropbox-dist/dropboxd is started upon logging in. > > That said, I still want the UI functionality (sync status, context menu items) > integrated into KDE! :D I've tried the following steps: I've installed the nautilus ubuntu package then I execute the "dropbox start -i" command then a program installed the deamon then I execute "dropbox start" and then I got a tray icon. when I execute "dropbox status" i get the hint that the deamon issn't linked to an account... how can I fix that problem ?
It seems to me you get reduced functionality either way. Either you have the problems with nautilus impinging on the rest of your system, or you're never quite sure of the status of your syncing. I must confess, I've been neglecting to even turn it on lately, then wondering why things haven't synced when I look for them on other computers in our "network". I must try the daemon only alternative suggested below. Re: being linked to an account (last message below), I would think you somehow need to invoke the wizard that either opens a new account or links you to an existing one. That seems to happen automatically with either the Nautilus or Windows versions, whenever you're not logged into an account. Not sure how it would work using just the daemon. I just had a quick look at the forums, and you may not be alone. Look here: http://forums.getdropbox.com/topic.php?id=10933&replies=12 and here: http://forums.getdropbox.com/topic.php?id=4687&replies=8#post-32048 Hope this helps. Cheers Ian 2009/9/13 <muell@k-p-v.de> > https://bugs.kde.org/show_bug.cgi?id=179302 > > > > > > --- Comment #9 from <muell k-p-v de> 2009-09-13 16:16:48 --- > (In reply to comment #8) > > (In reply to comment #7) > > > (In reply to comment #3) > > > Did you find a way around that? More annoying is the gnome userspace > mounting > > > stuff seems to take over and my KDE tools can't mount (or see those > items.) > > > > > > I am not sure why they even tied it to nautilus at all. It works just > fine > > > when I add stuff to the drop box folder using dolphin > > > > There's no need to have Nautilus installed. Dropbox does not depend on it > to > > work. Nautilus provides a UI for sync status feedback and some > context-menu > > options to make the user's life easier, but it is the dropbox daemon that > takes > > care of the syncing. > > > > What you have to do to install dropbox without Nautilus is to install the > > dropbox package and then manually tell it to download the daemon with > this > > command: > > > > $ dropbox start -i > > > > after the process is complete, you just have to make sure that > > ~/.dropbox-dist/dropboxd is started upon logging in. > > > > That said, I still want the UI functionality (sync status, context menu > items) > > integrated into KDE! :D > > I've tried the following steps: > I've installed the nautilus ubuntu package > then I execute the "dropbox start -i" command > then a program installed the deamon > then I execute "dropbox start" > and then I got a tray icon. > when I execute "dropbox status" i get the hint > that the deamon issn't linked to an account... > > how can I fix that problem ? > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are a voter for the bug. > You are on the CC list for the bug. >
Found this neat post: http://dreadknight666.com/2009/07/dropbox-in-kde-linux/
And even better if this support is generic, so it can be reused for Ubuntu One, ownCloud...
Please take a look at: http://trichard-kde.blogspot.com/2010/12/introducing-dropbox-integration-for.html And let me know how it works. Thanks
(In reply to comment #13) > Please take a look at: > http://trichard-kde.blogspot.com/2010/12/introducing-dropbox-integration-for.html > > And let me know how it works. > Thanks After git clone and compiling/installing plugin sync status is shown not for all folders and files in dropbox. I can't notice pattern for what files and folders it is shown or not. Context menu entry to browse on website works fine for those directories that have sync status shown, for others it doesn't appear. I'd suggest to use different set of icons for sync status if possible, preferably based on the icons used by Dropbox itself - that way it will be more intuitive.
@Alexy: That's strange. It works perfect here. What version of KDE are you using and where is your dropbox folder located on your computer? The plugin looks for a .dropbox folder in the top of the directory structure. I might have to change that behavior. Changing the icons is not currently possible. I'm using the icons that are used by the git and svn plugins. I'm planning on enhancing this inside Dolphin though. Unfortunately those changes can't make it in the KDE4.6 release.
(In reply to comment #15) > @Alexy: > That's strange. It works perfect here. What version of KDE are you using and > where is your dropbox folder located on your computer? The plugin looks for a > .dropbox folder in the top of the directory structure. I might have to change > that behavior. It's Alexey, with e between x and y. I'm using KDE 4.4.5 on Debian Sid. My dropbox folder located in ~/Dropbox. Folder ~/.dropbox is being used by dropbox itself for it's own files. There is no /.dropbox folder. Hope that helps.
@Alexey: In Dolphin for KDE SC 4.4.x there are still some minor issues regarding this kind of plugins, I think updating to KDE SC 4.5.x is necessary in this case.
@Thomas I think I speak for all here in saying THANK YOU SO MUCH for working on this! > where is your dropbox folder located on your computer? The plugin looks for a > .dropbox folder in the top of the directory structure. I might have to change > that behavior. My dropbox is located inside my work directory, which is unfortunately located on a different partition, so I'll need to move my files before trying out your plugin. I don't know if this helps, but I notice that in the kdropbox preferences section, there is an option to set the dropbox location. Hopefully it wouldn't be too difficult to replace your constant with that variable. Anyway, I'm already using KDE SC4.5, so I'll try compiling your current version on the weekend (my repo is OpenSuse, so can't use the .deb I'm afraid). Thanks once again for your efforts.
Resetting assignee to default as per bug #305719
Now that Thomas' plugin exists (many thanks for that!), is there any reason to keep this report open?
(In reply to comment #20) > Now that Thomas' plugin exists (many thanks for that!), is there any reason > to keep this report open? It seems that this is not the case -> closing.
Actually it is, the plugin is broken because Dropbox has changed the API. So it should be kept open.
(In reply to comment #22) > Actually it is, the plugin is broken because Dropbox has changed the API. All right, but why didn't anyone tell us that before? If the report isn't assigned to the plugin, then the plugin developers don't see it. It would be good if anyone could file a bug report for the plugin then and add a link here (to prevent duplication of effort). I know that it would be easier for you if we would just reopen the present report, but I don't like recycling old reports for new issues and changing the topic after 20 comments because this makes bug reports unreadable.
Probably because that plugin seems to be in a scratch repo (thus not a kde component, and no bugtracker as known) and hasn't seen activity for two years. I definitely wouldn't consider it a replacement for this bug (though having a third party provide it makes sense compared to say dolphin core).
(In reply to comment #24) > no bugtracker as known The product 'dolphin' at bugs.kde.org has a 'plugins/dropbox' component. If reports posted there are not read (is that the case?), then this component should be removed and the corresponding bugs be closed as UNMAINTAINED. > I definitely wouldn't consider it a replacement for this bug (though > having a third party provide it makes sense compared to say dolphin core). The point of the plugin system is to make it easy for people to add this kind of functionality without changing Dolphin itself. Even if I had the time to do it, I would not add anyting to Dolphin that can be implemented as a plugin/service menu/etc. Just imagine we added anything Dropbox-related to the Dolphin core. As soon as that happened, we would get requests to also add support for every other cloud-based storage service out there, which is obviously impossible.
> The product 'dolphin' at bugs.kde.org has a 'plugins/dropbox' component. If > reports posted there are not read (is that the case?), then this component > should be removed and the corresponding bugs be closed as UNMAINTAINED. ok, I did not know that. As far as I know there never was an offical release, no packages. That is why assumed this never had a bug tracker. Since it does not appear to be released, I would assume to be unmaintained.