view tests/Dnd/README @ 4905:755ae5b97edb

Change "special form" to "special operator" in our sources. Add a compatible function alias, and the relevant manual index entries. src/ChangeLog addition: 2010-01-31 Aidan Kehoe <kehoea@parhasard.net> * symbols.c (Fspecial_operator_p, syms_of_symbols): * eval.c (print_subr, Finteractive_p, Ffuncall) (Ffunction_min_args, Ffunction_max_args, vars_of_eval): * editfns.c: * data.c (Fsubr_max_args): * doc.c (Fbuilt_in_symbol_file): Change "special form" to "special operator" in our sources. man/ChangeLog addition: 2010-01-31 Aidan Kehoe <kehoea@parhasard.net> * xemacs/programs.texi (Defuns): * lispref/variables.texi (Local Variables, Defining Variables) (Setting Variables, Default Value): * lispref/symbols.texi (Definitions): * lispref/searching.texi (Saving Match Data): * lispref/positions.texi (Excursions, Narrowing): * lispref/objects.texi (Primitive Function Type): * lispref/macros.texi (Defining Macros, Backquote): * lispref/lispref.texi (Top): * lispref/intro.texi (A Sample Function Description): * lispref/help.texi (Help Functions): * lispref/functions.texi (What Is a Function, Simple Lambda) (Defining Functions, Calling Functions, Anonymous Functions): * lispref/frames.texi (Input Focus): * lispref/eval.texi (Forms, Function Indirection) (Special Operators, Quoting): * lispref/edebug-inc.texi (Instrumenting) (Specification Examples): * lispref/debugging.texi (Internals of Debugger): * lispref/control.texi (Control Structures, Sequencing): (Conditionals, Combining Conditions, Iteration): (Catch and Throw, Handling Errors): * lispref/commands.texi (Defining Commands, Using Interactive): Terminology change; special operator -> special form. Don't attempt to change this in texinfo.texi or cl.texi, which use macros I don't understand. * lispref/macros.texi (Defining Macros): Give an anonymous macro example here. * lispref/positions.texi (Excursions): Correct some documentation that called a couple of macros special forms. * lispref/searching.texi (Saving Match Data): Drop some documentation of how to write code that works with Emacs 18. * lispref/specifiers.texi (Adding Specifications): Correct this; #'let-specifier is a macro, not a special operator. * lispref/windows.texi (Window Configurations) (Selecting Windows): Correct this, #'save-selected-window and #'save-window-excursion are macros, not special operators. lisp/ChangeLog addition: 2010-01-31 Aidan Kehoe <kehoea@parhasard.net> * obsolete.el: * loadhist.el (symbol-file): * help.el (describe-function-1): * bytecomp.el: (byte-compile-save-current-buffer): * byte-optimize.el (byte-optimize-form-code-walker): * subr.el (subr-arity): Change "special form" to "special operator" in these files, it's the more logical term. * subr.el (special-form-p): Provide this alias for #'special-operator-p.
author Aidan Kehoe <kehoea@parhasard.net>
date Sun, 31 Jan 2010 20:28:01 +0000
parents bc4f2511bbea
children
line wrap: on
line source

 * Sun May 3 1998 Oliver Graf <ograf@fga.de>

This path contains test code for the new XEmacs
Drag'n'Drop code.

To test the code do the following:
1) call 'bash droptest.sh' to create the test files in /tmp
2) load and eval droptest.el in XEmacs
3) Try to do some internal DnD by using the sources and targets
   in the new buffer
4) Do some external DnD:
   4a) CDE: use dtfile and dtpad
   4b) MSWindows: well, explorer should do. But only file data
                  should work, and I don't know if the test
                  already handles this.

The misc-user-event now also responds as a button-x-event
to the event-* query functions.

The function of a drag is called dragdrop-drop-dispatch
as you can see in droptest.el. From within the function
you can access the actual misc-user-event through the
current-mouse-event variable.

Short description of the object part of a drop misc-user-event:
( TYPE . DATA )
TYPE is either the symbol dragdrop_MIME
     or the symbol dragdrop_URL

DATA is a list of URL strings if TYPE is dragdrop_URL
     if TYPE is dragdrop_MIME DATA is either a string
     which contains the MIME data, or it is a list of
     ( CONTENT-TYPE CONTENT-ENCODING MIME-DATA )
     CONTENT-TYPE is encoded for tm-view (list, first element type,
	rest key.value conses)
     CONTENT-ENCODING is a string
     MIME-DATA is a string

     CONTENT-TYPE and -ENCODING can be directly supplied to mime/viewer-mode.