unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Sean O'Rourke" <sorourke@cs.ucsd.edu>
Cc: "Jan D." <jan.h.d@swipnet.se>, emacs-devel@gnu.org
Subject: Re: [patch] enhanced mac drag-n-drop
Date: Thu, 07 Apr 2005 06:33:30 -0700	[thread overview]
Message-ID: <m24qeibtjp.fsf@Sean-ORourkes-Computer.local> (raw)
In-Reply-To: <usm23rs10.fsf@jasonrumney.net> (Jason Rumney's message of "Thu,  07 Apr 2005 07:59:39 +0100")

Jason Rumney <jasonr@gnu.org> writes:
>> We should break out what you can use in a general dnd.el file.

First, the XDND part (there are two other dnd protocols in there, but
I didn't look at them much) seems to contain code for enter, tracking,
leave, and drop handlers, which should probably be made into separate
hooks.  Carbon generates events for all of these, but currently we
only pass the drop up to the Lisp level, while the X version passes
all such events.  If this were cleaned up, it shouldn't be too hard to
extend the Mac version to pass the other events.

Second, the XDND version has message decoding mixed throughout the
Lisp code.  This is implementation-dependent, so IMHO it should be
done before Lisp gets ahold of the data, or at least before the
platform-independent part.  Examples include splitting URL-list
strings into separate URLs and matching on the XDND command names.

Third, there are the drop types, which have both different encodings
(platform-dependent) and different default actions (platform-
independent).  For the latter, it would be nice to agree on a set of
names (e.g. text, URL, file).

Finally, the "suggested action" in XDND will be very useful on Mac, so
I hope it stays around.

/s

  reply	other threads:[~2005-04-07 13:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-06  0:53 [patch] enhanced mac drag-n-drop Sean O'Rourke
2005-04-06 11:37 ` Stefan Monnier
2005-04-06 16:17 ` Jan D.
2005-04-06 18:12   ` Sean O'Rourke
2005-04-06 19:22     ` Jan D.
     [not found]     ` <uwtrfsjhv.fsf@jasonrumney.net>
2005-04-07  4:36       ` Jan D.
2005-04-07  6:59         ` Jason Rumney
2005-04-07 13:33           ` Sean O'Rourke [this message]
2005-04-07 15:18             ` Jan D.
2005-04-11 19:39           ` Jan D.
2005-04-09 11:00 ` YAMAMOTO Mitsuharu
2005-04-09 13:46   ` Jan D.
2005-04-10  2:03     ` YAMAMOTO Mitsuharu
2005-04-10  5:47       ` Jan D.
2005-04-10 14:42       ` Stefan Monnier
2005-04-11  1:56         ` Richard Stallman
2005-04-11  3:35           ` Stefan Monnier
2005-04-11  9:49             ` YAMAMOTO Mitsuharu
2005-04-11 16:39               ` Stefan Monnier
2005-04-12  8:24                 ` YAMAMOTO Mitsuharu
2005-04-12  2:58             ` Richard Stallman
2005-04-12  3:59               ` Stefan Monnier
2005-04-12 17:24                 ` Richard Stallman
2005-04-11  1:56       ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m24qeibtjp.fsf@Sean-ORourkes-Computer.local \
    --to=sorourke@cs.ucsd.edu \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).