Mercurial > hg > xemacs-beta
annotate man/lispref/dragndrop.texi @ 5652:cc6f0266bc36
Avoid #'delq in core Lisp, for the sake of style, a very slightly smaller binary
lisp/ChangeLog addition:
2012-05-01 Aidan Kehoe <kehoea@parhasard.net>
Avoid #'delq in core code, for the sake of style and a (very
slightly) smaller binary.
* behavior.el (disable-behavior):
* behavior.el (compute-behavior-group-children):
* buff-menu.el (buffers-tab-items):
* byte-optimize.el (byte-optimize-delay-constants-math):
* byte-optimize.el (byte-optimize-logmumble):
* byte-optimize.el (byte-decompile-bytecode-1):
* byte-optimize.el (byte-optimize-lapcode):
* bytecomp.el:
* bytecomp.el (byte-compile-arglist-warn):
* bytecomp.el (byte-compile-warn-about-unresolved-functions):
* bytecomp.el (byte-compile-lambda):
* bytecomp.el (byte-compile-out-toplevel):
* bytecomp.el (byte-compile-insert):
* bytecomp.el (byte-compile-defalias-warn):
* cl-macs.el (cl-upcase-arg):
* cl-macs.el (cl-transform-lambda):
* cl-macs.el (cl-do-proclaim):
* cl-macs.el (defstruct):
* cl-macs.el (cl-make-type-test):
* cl-macs.el (define-compiler-macro):
* cl-macs.el (delete-duplicates):
* cus-edit.el (widget-face-value-delete):
* cus-edit.el (face-history):
* easymenu.el (easy-menu-remove):
* files.el (files-fetch-hook-value):
* files.el (file-expand-wildcards):
* font-lock.el (font-lock-update-removed-keyword-alist):
* font-lock.el (font-lock-remove-keywords):
* frame.el (frame-initialize):
* frame.el (frame-notice-user-settings):
* frame.el (set-frame-font):
* frame.el (delete-other-frames):
* frame.el (get-frame-for-buffer-noselect):
* gnuserv.el (gnuserv-kill-buffer-function):
* gnuserv.el (gnuserv-check-device):
* gnuserv.el (gnuserv-kill-client):
* gnuserv.el (gnuserv-buffer-done-1):
* gtk-font-menu.el (gtk-reset-device-font-menus):
* gutter-items.el (buffers-tab-items):
* gutter.el (set-gutter-element-visible-p):
* info.el (Info-find-file-node):
* info.el (Info-history-add):
* info.el (Info-build-annotation-completions):
* info.el (Info-index):
* info.el (Info-reannotate-node):
* itimer.el (delete-itimer):
* itimer.el (start-itimer):
* lib-complete.el (lib-complete:cache-completions):
* loadhist.el (unload-feature):
* menubar-items.el (build-buffers-menu-internal):
* menubar.el (delete-menu-item):
* menubar.el (relabel-menu-item):
* msw-font-menu.el (mswindows-reset-device-font-menus):
* mule/make-coding-system.el (fixed-width-generate-helper):
* next-error.el (next-error-find-buffer):
* obsolete.el:
* obsolete.el (find-non-ascii-charset-string):
* obsolete.el (find-non-ascii-charset-region):
* occur.el (multi-occur-by-filename-regexp):
* occur.el (occur-1):
* packages.el (packages-package-hierarchy-directory-names):
* packages.el (package-get-key-1):
* process.el (setenv):
* simple.el (undo):
* simple.el (handle-pre-motion-command-current-command-is-motion):
* sound.el (load-sound-file):
* wid-edit.el (widget-field-value-delete):
* wid-edit.el (widget-checklist-match-inline):
* wid-edit.el (widget-checklist-match-find):
* wid-edit.el (widget-editable-list-delete-at):
* wid-edit.el (widget-editable-list-entry-create):
* window.el (quit-window):
* x-font-menu.el (x-reset-device-font-menus-core):
1. Replace (delq nil (mapcar ....)) with analogous (mapcan ...)
forms; this is in non-dumped files, it was done previously in
dumped files.
2. Replace (delq FOO (copy-sequence BAR)) with (remove* FOO BAR),
where #'eq and #'eql are equivalent
3. Replace (delq FOO BAR) with (delete* FOO BAR), where FOO is not
a non-fixnum number. Saves a little space in the dumped file
(since the compiler macro adds :test #'eq to the delete* call if
it's not clear that FOO is not a non-fixnum number).
author | Aidan Kehoe <kehoea@parhasard.net> |
---|---|
date | Tue, 01 May 2012 16:17:42 +0100 |
parents | bc4f2511bbea |
children |
rev | line source |
---|---|
428 | 1 @c -*-texinfo-*- |
2 @c This is part of the XEmacs Lisp Reference Manual. | |
3 @c Copyright (C) 1998 Oliver Graf <ograf@fga.de> | |
444 | 4 @c Original reference is (c) 1990, 1991, 1992, 1993, 1994 Free Software Foundation, Inc. |
428 | 5 @c See the file lispref.texi for copying conditions. |
6 @setfilename ../../info/dragndrop.texi | |
7 @node Drag and Drop, Modes, Scrollbars, Top | |
8 @chapter Drag and Drop | |
9 @cindex drag and drop | |
10 | |
11 @emph{WARNING}: the Drag'n'Drop API is still under development and the | |
12 interface may change! The current implementation is considered experimental. | |
13 | |
14 Drag'n'drop is a way to transfer information between multiple applications. | |
4790
bc4f2511bbea
Remove support for the OffiX drag-and-drop protocol. See xemacs-patches
Jerry James <james@xemacs.org>
parents:
904
diff
changeset
|
15 To do this several GUIs define their own protocols. Examples are CDE, Motif, |
bc4f2511bbea
Remove support for the OffiX drag-and-drop protocol. See xemacs-patches
Jerry James <james@xemacs.org>
parents:
904
diff
changeset
|
16 KDE, MSWindows, GNOME, and many more. To catch all these protocols, XEmacs |
bc4f2511bbea
Remove support for the OffiX drag-and-drop protocol. See xemacs-patches
Jerry James <james@xemacs.org>
parents:
904
diff
changeset
|
17 provides a generic API. |
428 | 18 |
19 One prime idea behind the API is to use a data interface that is | |
20 transparent for all systems. The author thinks that this is best | |
21 archived by using URL and MIME data, cause any internet enabled system | |
22 must support these for email already. XEmacs also already provides | |
23 powerful interfaces to support these types of data (tm and w3). | |
24 | |
25 @menu | |
26 * Supported Protocols:: Which low-level protocols are supported. | |
27 * Drop Interface:: How XEmacs handles a drop from another application. | |
28 * Drag Interface:: Calls to initiate a drag from XEmacs. | |
29 @end menu | |
30 | |
31 @node Supported Protocols | |
32 @section Supported Protocols | |
33 | |
34 The current release of XEmacs only support a small set of Drag'n'drop | |
35 protocols. Some of these only support limited options available in the API. | |
36 | |
37 @menu | |
38 * CDE dt:: Common Desktop Environment used on suns. | |
39 * MSWindows OLE:: Mr. Gates way of live. | |
40 * Loose ends:: The other protocols. | |
41 @end menu | |
42 | |
43 @node CDE dt | |
44 @subsection CDE dt | |
45 @cindex CDE dt | |
46 | |
47 CDE stands for Common Desktop Environment. It is based on the Motif | |
48 widget library. It's drag'n'drop protocol is also an abstraction of the | |
49 Motif protocol (so it might be possible, that XEmacs will also support | |
50 the Motif protocol soon). | |
51 | |
52 CDE has three different types: file, buffer, and text. XEmacs only uses | |
53 file and buffer drags. The API will disallow full URL drags, only file | |
54 method URLs are passed through. | |
55 | |
56 Buffer drags are always converted to plain text. | |
57 | |
58 @node MSWindows OLE | |
59 @subsection MSWindows OLE | |
60 @cindex MSWindows OLE | |
61 | |
62 Only allows file drags and drops. | |
63 | |
64 @node Loose ends | |
65 @subsection Loose ends | |
66 | |
67 The following protocols will be supported soon: Xdnd, Motif, Xde (if I | |
4790
bc4f2511bbea
Remove support for the OffiX drag-and-drop protocol. See xemacs-patches
Jerry James <james@xemacs.org>
parents:
904
diff
changeset
|
68 get some specs). |
428 | 69 |
70 In particular Xdnd will be one of the protocols that can benefit from | |
71 the XEmacs API, cause it also uses MIME types to encode dragged data. | |
72 | |
73 @node Drop Interface | |
74 @section Drop Interface | |
75 @cindex drop | |
76 @cindex Drop API | |
77 | |
904 | 78 For each activated low-level protocol, an internal routine will catch |
428 | 79 incoming drops and convert them to a dragdrop-drop type |
80 misc-user-event. | |
81 | |
82 This misc-user-event has its function argument set to | |
83 @code{dragdrop-drop-dispatch} and the object contains the data of the drop | |
84 (converted to URL/MIME specific data). This function will search the variable | |
444 | 85 @code{experimental-dragdrop-drop-functions} for a function that can handle the |
428 | 86 dropped data. |
87 | |
88 To modify the drop behavior, the user can modify the variable | |
89 @code{experimental-dragdrop-drop-functions}. Each element of this list | |
90 specifies a possible handler for dropped data. The first one that can handle | |
91 the data will return @code{t} and exit. Another possibility is to set a | |
92 extent-property with the same name. Extents are checked prior to the | |
93 variable. | |
94 | |
95 The customization group @code{drag-n-drop} shows all variables of user | |
444 | 96 interest. |
428 | 97 |
98 @node Drag Interface | |
99 @section Drag Interface | |
100 @cindex drag | |
101 @cindex Drag API | |
102 | |
103 This describes the drag API (not implemented yet). |