Mercurial > hg > xemacs-beta

comparison man/lispref/dragndrop.texi @ 373:6240c7796c7a r21-2b2

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Import from CVS: tag r21-2b2
author cvs
date Mon, 13 Aug 2007 11:04:06 +0200
parents cc15677e0335
children
comparison
equal deleted inserted replaced
372:49e1ed2d7ed8 373:6240c7796c7a
10 10
11 @emph{WARNING}: the Drag'n'Drop API is still under development and the 11 @emph{WARNING}: the Drag'n'Drop API is still under development and the
12 interface may change! The current implementation is considered experimental. 12 interface may change! The current implementation is considered experimental.
13 13
14 Drag'n'drop is a way to transfer information between multiple applications. 14 Drag'n'drop is a way to transfer information between multiple applications.
15 To do this serveral GUIs define their own protocols. Examples are OffiX, CDE, 15 To do this several GUIs define their own protocols. Examples are OffiX, CDE,
16 Motif, KDE, MSWindows, GNOME, and many more. To catch all these protocols, 16 Motif, KDE, MSWindows, GNOME, and many more. To catch all these protocols,
17 XEmacs provides a generic API. 17 XEmacs provides a generic API.
18 18
19 One prime idea behind the API is to use a data interface that is 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 20 transparent for all systems. The author thinks that this is best
30 30
31 @node Supported Protocols 31 @node Supported Protocols
32 @section Supported Protocols 32 @section Supported Protocols
33 33
34 The current release of XEmacs only support a small set of Drag'n'drop 34 The current release of XEmacs only support a small set of Drag'n'drop
35 protocols. Some of these only support limited options avaiable in the API. 35 protocols. Some of these only support limited options available in the API.
36 36
37 @menu 37 @menu
38 * OffiX DND:: A generic X based protocol. 38 * OffiX DND:: A generic X based protocol.
39 * CDE dt:: Common Desktop Environment used on suns. 39 * CDE dt:: Common Desktop Environment used on suns.
40 * MSWindows OLE:: Mr. Gates way of live. 40 * MSWindows OLE:: Mr. Gates way of live.
61 is dragged from XEmacs (well, not yet...). 61 is dragged from XEmacs (well, not yet...).
62 62
63 XEmacs supports both MIME and URL drags and drops using this API. No application 63 XEmacs supports both MIME and URL drags and drops using this API. No application
64 interaction is possible while dragging is in progress. 64 interaction is possible while dragging is in progress.
65 65
66 For infomation about the OffiX project have a look at http://leb.net/~offix/ 66 For information about the OffiX project have a look at http://leb.net/~offix/
67 67
68 @node CDE dt 68 @node CDE dt
69 @subsection CDE dt 69 @subsection CDE dt
70 @cindex CDE dt 70 @cindex CDE dt
71 71
108 @code{dragdrop-drop-dispatch} and the object contains the data of the drop 108 @code{dragdrop-drop-dispatch} and the object contains the data of the drop
109 (converted to URL/MIME specific data). This function will search the variable 109 (converted to URL/MIME specific data). This function will search the variable
110 @code{experimental-dragdrop-drop-functions} for a function that can handle the 110 @code{experimental-dragdrop-drop-functions} for a function that can handle the
111 dropped data. 111 dropped data.
112 112
113 To modify the drop behaviour, the user can modify the variable 113 To modify the drop behavior, the user can modify the variable
114 @code{experimental-dragdrop-drop-functions}. Each element of this list 114 @code{experimental-dragdrop-drop-functions}. Each element of this list
115 specifies a possible handler for dropped data. The first one that can handle 115 specifies a possible handler for dropped data. The first one that can handle
116 the data will return @code{t} and exit. Another possibility is to set a 116 the data will return @code{t} and exit. Another possibility is to set a
117 extent-property with the same name. Extents are checked prior to the 117 extent-property with the same name. Extents are checked prior to the
118 variable. 118 variable.