The Script Plugin’s purpose is to make it easy to extend DrRacket with small Racket scripts that can be used in the definition window.
Selected text can be transformed, text can be inserted, and there is direct access to some elements of DrRacket, like the frame and the current text editor. Each script is automatically added as an item to the Script menu, without needing to restart DrRacket. A keyboard shortcut can be assigned to a script (via the menu item).
It is similar to GEdit’s External Tools plugin (for those who use it), but has more potential for interacting with the text editor.
Click on the Scripts/New Script menu item, and enter Reverse for the script name. This creates and opens the files reverse.rkt and reverse.rktd in the script directory. Also, a new item automatically appears in the Scripts menu.
Then go to a new tab, type some text, select it, and click on Scripts/Reverse.
This DrRacket plugin adds a Script menu to the main window. This menu has several items, followed by the (initially empty) list of active scripts.
a .rkt file, the script itself (with a sample program)
a .rktd file, the metadata of the script with the default values
The script menu is rebuilt each time the user activates it, so that changes are taken into account as soon as possible.
The default location of the scripts is in a sub-folder of (find-system-path 'home-path). The directory of the user scripts can be change through DrRacket’s preferences (in Edit/Preferences/Scripts). Important: The scripts directory must have write-access for the user.
This is the script file. It must provide the modify-selection function, as in the sample code. It is meant to be executable by itself, to ease the testing process.
The path to the current file of the definition window, or #f if there is no such file (i.e., unsaved editor).For example:
(define (modify-selection str #:file f) (string-append "(in " (if f (path->string f) "no-file") ": " str))
#:editor : text%
The text% editor of the current definition window. For advanced scripting.
#:frame : drracket:unit:frame<%>
DrRacket’s frame. For advanced scripting.For example:
The name of the function can also be changed, but this requires to change it also in the functions entry of the .rktd file, and the function must be provided.
This is the metadata file. It contains an association list that defines the configuration of the script.
Most options (label, shortcut, shortcut-prefix, help-string) are the same as for the menu-item% constructor. In particular, a keyboard shortcut can be assigned to an item.
If a symbol, the name of the function to call (which must be provided), and must follow modify-selection’s signature.
If a list, each symbol is the name of a function, and each string is a label for that function. In this case, a sub-menu holding all these functions is created, and the label option is used as the parent menu name.
Note that a sub-menu can be shared among scripts.
If 'selection, the output of the transform function replaces the selection in the current tab (or insert at the cursor if there is no selection). If 'new-tab, a new tab is created and the output of the script is written to it. If 'message-box, the output is displayed in a message-box.
Note: The quote must not be included in the .rktd file.
If set to #f, no menu item is generated for this dictionary.
Finally, one .rktd file can contain several such dictionaries (one after the other), which allows for multiple sub-menus and menu items and in a single script. This would have roughly the same effect as splitting such a script into several script, each one with its own .rktd file and its dictionary.
ASCII frames and styling (upper-case, camel-case, etc.) for comment titles, sections, etc.
Code snippets scripts, with keyboard shortcuts, e.g., adding a require line for each planet package you usually use, or a license header.
Automatic comments, or even generic contracts from signatures and conventions.
Automatic reformatting and custom indentation.
Count the number of words/lines/characters/whatever and display it in a message-box.
Open a new tab with a template code.
Note that racket/gui can be used to ask the user for more information and more.
Remark: Code snippets should probably be of rare usage, as one should better take advantage of Racket’s wonderful macro system. In some cases however, snippets might be useful, e.g., to require your common module where all your usual macros and functions are defined, or for automatic comments.