W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2009

Re: DnD vs CnP (was Copy/Paste Events)

From: Sebastian Markbåge <sebastian@calyptus.eu>
Date: Thu, 27 Aug 2009 08:55:31 +0200
Message-ID: <491930550908262355w1ca6c067ua8879b35a0e49afb@mail.gmail.com>
To: Paul Libbrecht <paul@activemath.org>
Cc: Ian Hickson <ian@hixie.ch>, timeless@gmail.com, Jacob Rossi <t-jacobr@microsoft.com>, "public-webapps@w3.org Group WG" <public-webapps@w3.org>
>
> I seem to understand that "supply data immediately" is the alternative
> proposed currently by HTML5. Right?


It has been proposed that a "DownloadURL" alternative be added to the list
of types to create downloadable files.

http://www.mail-archive.com/whatwg@lists.whatwg.org/msg17210.html
The problem with this is that you can't specify mime type for the file
content. I also suggested that the file API be extensible but this is too
messy.

Instead you could add a method such as: dataTransfer.setRemoteData(mimeType,
url);
Or as a type decorator: dataTransfer.setData("remote: " + mimeType, url);

Then you could declare any data to be loaded lazily from a remote server
when a drop operation occurs. Dragging of file data to a file manager would
cause the file on the specified URL to be downloaded to the target folder.

On Thu, Aug 27, 2009 at 12:20 AM, Paul Libbrecht <paul@activemath.org>wrote:

> While re-reading the spec:
>
> http://dev.w3.org/html5/spec/Overview.html#drag-and-drop-processing-model
> I seem to understand that "supply data immediately" is the alternative
> proposed currently by HTML5. Right?
>
> If yes, then it's clear that most server-implementors will not be able to
> offer rich flavours as possible conversion targets since you don't want to
> wait on a network load for a drag-start to fire!
>
> Honestly, I find the whole DnD and CnP treatment in HTML5 quite much
> ad-hoc. It's welcome to have such an addition but it makes too many
> arrangements and still is hard to read.
>
> What I would wish, and I think many many many others is a readable
> specification for copy-and-paste that meets large implementations and maybe
> later something for drag-and-drop.
>
> paul
>
>
>  Thanks for the pointers. We now have more words: supply data on demand or
>> supply data immediately is the crucial difference.
>>
>> The on-demand situation means: the application still must live for its
>> on-demand flavours to be available.
>>
>> We're now porting it all to a web-browser: an application is a web-page, a
>> document that is. So on-demand copy-and-paste would stop being available as
>> soon the document is gone, i.e., as soon as the page is changed following a
>> link or a back, right?
>>
>> I would feel bothered as a user.
>>
>
>
Received on Thursday, 27 August 2009 06:56:07 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:33 GMT