When the document is saved or closed, the editor should hand the token back to the ftp client in one of the notification events described below. Interarchy uses strings (typeChar), NetFinder uses numbers (typeLongInteger) and Trasmit uses yet another type, but the server application shouldn't care about the type: it should just make a copy of the token descriptor and associate it internally with the open document. The tokens in the 'FTok' list are arbitrary descriptors. The 'FTok' and 'Burl' parameters are lists because the direct parameterof the 'odoc' event is itself a list of aliases, one for each documentto open, although in most cases the direct parameter is a list of onlyone alias. Text encoding hint (fallback used only if the document doesn't provide any encoding information) Text encoding hint (overrides the document-specified encoding, if any) The creator code of the client application.Ī list of arbitrary tokens to be associated with the opened documents. The ftp client sends the editor an 'odoc' event with some additional parameters: The augmented 'odoc' event. When the user saves the document from the external editor, the file is automagically uploaded back to the remote machine by the ftp client. When you select a file in a remote directory and choose that command, the file is downloaded to a temporary location (the invisible "Cleanup At Startup" folder) and opened in the external editor. The clients of this protocol have an "Edit with " menu command. This protocol is currently implemented by BBEdit, Style, Tex-Edit Plus and PageSpinner on the server side, and by Interarchy, NetFinder, Transmit and Fetch on the client side. The server application is usually a text editor, and the client application is usually an ftp client, but nothing prevents the protocol from being used in other scenarios as well. The External Editor Protocol described in this page is a client/server protocol based on Apple events. November 8, 2000: added a proposal for editor-initiated editing sessions.In the meantime, Fetch, Jim Matthews's popular ftp client, added support for the client side, but seems to limit the choice of external editors to BBEdit. January 12, 2001: the latest beta of Tex-Edit Plus supports the server side of this protocol.January 29, 2001: With a message to the Interarchy Talk mailing list, Peter N Lewis announced support for both of our proposed protocol enhancements in a future (post-4.0) version of Interarchy.February 4, 2001: The just released Tex-Edit Plus 4.1 adds support for this protocol.This version can edit remote text files with the aid of external editors other than BBEdit. April 26, 2001: Interarchy 4.1 (formerly Anarchie) is now available.May 1, 2001: Version 4.0 of Jim Matthews's venerable Fetch ftp client for Mac OS and Mac OS X adds full support for the external editor protocol.July 26, 2005: Added a new, optional, 'RdEV' parameter to the modified 'odoc' event.The External Editor Protocol Last updated on January 11, 2010
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |