Mercurial > hg > xemacs-beta
annotate man/lispref/dragndrop.texi @ 5882:bbe4146603db
Reduce regexp usage, now CL-oriented non-regexp code available, core Lisp
lisp/ChangeLog addition:
2015-04-01 Aidan Kehoe <kehoea@parhasard.net>
When calling #'string-match with a REGEXP without regular
expression special characters, call #'search, #'mismatch, #'find,
etc. instead, making our code less likely to side-effect other
functions' match data and a little faster.
* apropos.el (apropos-command):
* apropos.el (apropos):
Call (position ?\n ...) rather than (string-match "\n" ...) here.
* buff-menu.el:
* buff-menu.el (buffers-menu-omit-invisible-buffers):
Don't fire up the regexp engine just to check if a string starts
with a space.
* buff-menu.el (select-buffers-tab-buffers-by-mode):
Don't fire up the regexp engine just to compare mode basenames.
* buff-menu.el (format-buffers-tab-line):
* buff-menu.el (build-buffers-tab-internal): Moved to being a
label within the following.
* buff-menu.el (buffers-tab-items): Use the label.
* bytecomp.el (byte-compile-log-1):
Don't fire up the regexp engine just to look for a newline.
* cus-edit.el (get):
Ditto.
* cus-edit.el (custom-variable-value-create):
Ditto, but for a colon.
* descr-text.el (describe-text-sexp):
Ditto.
* descr-text.el (describe-char-unicode-data):
Use #'split-string-by-char given that we're just looking for a
semicolon.
* descr-text.el (describe-char):
Don't fire up the regexp engine just to look for a newline.
* disass.el (disassemble-internal):
Ditto.
* files.el (file-name-sans-extension):
Implement this using #'position.
* files.el (file-name-extension):
Correct this function's docstring, implement it in terms of
#'position.
* files.el (insert-directory):
Don't fire up the regexp engine to split a string by space; don't
reverse the list of switches, this is actually a longstand bug as
far as I can see.
* gnuserv.el (gnuserv-process-filter):
Use #'position here, instead of consing inside #'split-string
needlessly.
* gtk-file-dialog.el (gtk-file-dialog-update-dropdown):
Use #'split-string-by-char here, don't fire up #'split-string for
directory-sep-char.
* gtk-font-menu.el (hack-font-truename):
Implement this more cheaply in terms of #'find,
#'split-string-by-char, #'equal, rather than #'string-match,
#'split-string, #'string-equal.
* hyper-apropos.el (hyper-apropos-grok-functions):
* hyper-apropos.el (hyper-apropos-grok-variables):
Look for a newline using #'position rather than #'string-match in
these functions.
* info.el (Info-insert-dir):
* info.el (Info-insert-file-contents):
* info.el (Info-follow-reference):
* info.el (Info-extract-menu-node-name):
* info.el (Info-menu):
Look for fixed strings using #'position or #'search as appropriate
in this file.
* ldap.el (ldap-decode-string):
* ldap.el (ldap-encode-string):
#'encode-coding-string, #'decode-coding-string are always
available, don't check if they're fboundp.
* ldap.el (ldap-decode-address):
* ldap.el (ldap-encode-address):
Use #'split-string-by-char in these functions.
* lisp-mnt.el (lm-creation-date):
* lisp-mnt.el (lm-last-modified-date):
Don't fire up the regexp engine just to look for spaces in this file.
* menubar-items.el (default-menubar):
Use (not (mismatch ...)) rather than #'string-match here, for
simple regexp.
Use (search "beta" ...) rather than (string-match "beta" ...)
* menubar-items.el (sort-buffers-menu-alphabetically):
* menubar-items.el (sort-buffers-menu-by-mode-then-alphabetically):
* menubar-items.el (group-buffers-menu-by-mode-then-alphabetically):
Don't fire up the regexp engine to check if a string starts with
a space or an asterisk.
Use the more fine-grained results of #'compare-strings; compare
case-insensitively for the buffer menu.
* menubar-items.el (list-all-buffers):
* menubar-items.el (tutorials-menu-filter):
Use #'equal rather than #'string-equal, which, in this context,
has the drawback of not having a bytecode, and no redeeming
features.
* minibuf.el:
* minibuf.el (un-substitute-in-file-name):
Use #'count, rather than counting the occurences of $ using the
regexp engine.
* minibuf.el (read-file-name-internal-1):
Don't fire up the regexp engine to search for ?=.
* mouse.el (mouse-eval-sexp):
Check for newline with #'find.
* msw-font-menu.el (mswindows-reset-device-font-menus):
Split a string by newline with #'split-string-by-char.
* mule/japanese.el:
* mule/japanese.el ("Japanese"):
Use #'search rather than #'string-match; canoncase before
comparing; fix a bug I had introduced where I had been making case
insensitive comparisons where the case mattered.
* mule/korea-util.el (default-korean-keyboard):
Look for ?3 using #'find, not #'string-march.
* mule/korea-util.el (quail-hangul-switch-hanja):
Search for a fixed string using #'search.
* mule/mule-cmds.el (set-locale-for-language-environment):
#'position, #'substitute rather than #'string-match,
#'replace-in-string.
* newcomment.el (comment-make-extra-lines):
Use #'search rather than #'string-match for a simple string.
* package-get.el (package-get-remote-filename):
Use #'position when looking for ?@
* process.el (setenv):
* process.el (read-envvar-name):
Use #'position when looking for ?=.
* replace.el (map-query-replace-regexp):
Use #'split-string-by-char instead of using an inline
implementation of it.
* select.el (select-convert-from-cf-text):
* select.el (select-convert-from-cf-unicodetext):
Use #'position rather than #'string-match in these functions.
* setup-paths.el (paths-emacs-data-root-p):
Use #'search when looking for simple string.
* sound.el (load-sound-file):
Use #'split-string-by-char rather than an inline reimplementation
of same.
* startup.el (splash-screen-window-body):
* startup.el (splash-screen-tty-body):
Search for simple strings using #'search.
* version.el (emacs-version):
Ditto.
* x-font-menu.el (hack-font-truename):
Implement this more cheaply in terms of #'find,
#'split-string-by-char, #'equal, rather than #'string-match,
#'split-string, #'string-equal.
* x-font-menu.el (x-reset-device-font-menus-core):
Use #'split-string-by-char here.
* x-init.el (x-initialize-keyboard):
Search for a simple string using #'search.
author | Aidan Kehoe <kehoea@parhasard.net> |
---|---|
date | Wed, 01 Apr 2015 14:28:20 +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). |