I chatted with David, and I've enabled &= #39;renameFromFile' and 'copyFromFile'. And I give an error if = one tries to rename a local url in the tags kioslave. This results in those= cut (from file) + paste (to tags) failing, and the file is not lost.

Ideally, this should have been seemly converted to a copy operation. We= still need to figure out a way to do that.

On Thu, Nov 29, 2012 at 5:17 PM, Vishesh Handa <me@vhanda.in> = wrote:

On Fri, Nov 23, 2012 at 12:57 = AM, Albert Astals Cid <aacid@kde.org> wrote:

El Dijous, 22 de novembre de 2012, a les 10:27:41, David Faure va escriure:=

> On Thursday 22 November 2012 00:24:12 Albert Astals Cid wrote: > > El Dimecres, 21 de novembre de 2012, a les 16:15:01, David Faure = va
>
> escriure:
> > > On Wednesday 07 November 2012 02:27:17 Albert Astals Cid wro= te:
> > > > Ahh, you mean copying from file: to tags:
> > > Moving from file: to tags:, rather.
> >
> > Right
> >
> > > > I see... I'd like to hear David's opinion on ho= w that is going to be
> > > > fixed
> > > > at =A0the kio/kioslave level.
> > >
> > > Not at that level. Apps should be able to call move and end = up with a
> > > move.
> >
> > Even if that means destroying the file into hyperspace?
>
> Well, kioslaves were meant to be V*FS*. A file system doesn't lose= files
> into hyperspace :)

Sure, but it's still Virtual ;-)

> However we already have a number of settings for "this or that fu= nctionality
> isn't supported by this kioslave". Hmm, I wonder, what does t= ags:/ do in
> put()? Where does it "write the file", if it's only a vi= rtual collection of
> stuff?

Not sure, but i understand it adds the tag of the url you are in to t= he file
you are dropping.

>
> If put() isn't supported, then moving (by get+put) won't be su= pported.
> Only copyFromFile would be possible, which is exactly what you need, i= sn't
> it?

Ah, interesting, maybe copyFromFile is what Vishesh needs? Vishesh do= es it
make sense dropping urls to tags:/ from something different than file:/ ?

No. It doesn't.

Theoreticall= y one can tag anything but for now I only want to support files.

Cheers,
=A0 Albert

>
> In other words, try not implementing put, if that makes sense, and let= me
> know what doesn't work.
>
> > > But the fix is to let drag-n-drop trigger a copy rather than= allowing
> > > the
> > > user to select "move". The quick fix for that is > > > http://www.davidfaure.fr/2012/konq_operations.cpp.= diff
> > > Which hardcodes the protocol name, but at least it gets the = job done.
> > >
> > > If we agree about this on principle, then the next step to m= ake it
> > > generic
> > > could be to add another field in .protocol files, say
> > > forceDropAction=3D(copy|move)
> > > The fact that kio_trash needs forceDropAction=3Dmove shows t= hat this might
> > > make sense, we already have two users for this setting.
> >
> > I guess that works for me, since apps won't probably ever cal= l "move" into
> > a tags: url
>
> OK. But let's keep this solution under the arm for now, until we f= ind out
> about put() above.
>

> >> Visit http://mail.kde.org/mailman/lis= tinfo/kde-devel#unsub to unsubscribe
> >> <<

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub= to unsubscribe <<

--
Vishesh Handa

--
Vishesh Handa