dropping content onto Plasma

[Sebastian Kügler]

On Tuesday 24 March 2009 14:30:41 Aaron J. Seigo wrote:
> On Tuesday 24 March 2009, Marco Martin wrote:
> > > The above procedure works nicely for local content, such as files.
> > > URL's are a special kind of draggable content though. As far as I
> > > understand, a URL doesn't have a mimetype attached, it's either data +
> > > mimetype (+ other metainformation) or simply a URL.
> >
> > hmm i don't see any ways beside on dropevent on the containment trying to
> > download the url and see what it does contain (for http the header of the
> > response would suffice, for other urls like akonadi: i have no idea)
>
> for urls like akonadi and other similar special protocols we could offer a
> "protocol interpreter" that would decide what the content is by looking at
> the url. obviously, this is pretty hard with something like http, but i
> hope and imagine that akonadi urls are well formed and can be deduced as to
> their content by just looking at the url. we don't want to build these into
> plasma, obviously, so something in kdelibs (KMimeType?) or piggybacking on
> the applet plugin system might be workable ...

Ow, btw ... where's that code in plasma? I couldn't find it yet...
-- 
sebas

 http://www.kde.org | http://vizZzion.org |  GPG Key ID: 9119 0EF9 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 489 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/plasma-devel/attachments/20090324/a5cb88e8/attachment.sig