view etc/MORE.STUFF @ 939:025200a2163c

[xemacs-hg @ 2002-07-31 07:23:39 by michaels] 2002-07-17 Marcus Crestani <crestani@informatik.uni-tuebingen.de> Markus Kaltenbach <makalten@informatik.uni-tuebingen.de> Mike Sperber <mike@xemacs.org> configure flag to turn these changes on: --use-kkcc First we added a dumpable flag to lrecord_implementation. It shows, if the object is dumpable and should be processed by the dumper. * lrecord.h (struct lrecord_implementation): added dumpable flag (MAKE_LRECORD_IMPLEMENTATION): fitted the different makro definitions to the new lrecord_implementation and their calls. Then we changed mark_object, that it no longer needs a mark method for those types that have pdump descritions. * alloc.c: (mark_object): If the object has a description, the new mark algorithm is called, and the object is marked according to its description. Otherwise it uses the mark method like before. These procedures mark objects according to their descriptions. They are modeled on the corresponding pdumper procedures. (mark_with_description): (get_indirect_count): (structure_size): (mark_struct_contents): These procedures still call mark_object, this is needed while there are Lisp_Objects without descriptions left. We added pdump descriptions for many Lisp_Objects: * extents.c: extent_auxiliary_description * database.c: database_description * gui.c: gui_item_description * scrollbar.c: scrollbar_instance_description * toolbar.c: toolbar_button_description * event-stream.c: command_builder_description * mule-charset.c: charset_description * device-msw.c: devmode_description * dialog-msw.c: mswindows_dialog_id_description * eldap.c: ldap_description * postgresql.c: pgconn_description pgresult_description * tooltalk.c: tooltalk_message_description tooltalk_pattern_description * ui-gtk.c: emacs_ffi_description emacs_gtk_object_description * events.c: * events.h: * event-stream.c: * event-Xt.c: * event-gtk.c: * event-tty.c: To write a pdump description for Lisp_Event, we converted every struct in the union event to a Lisp_Object. So we created nine new Lisp_Objects: Lisp_Key_Data, Lisp_Button_Data, Lisp_Motion_Data, Lisp_Process_Data, Lisp_Timeout_Data, Lisp_Eval_Data, Lisp_Misc_User_Data, Lisp_Magic_Data, Lisp_Magic_Eval_Data. We also wrote makro selectors and mutators for the fields of the new designed Lisp_Event and added everywhere these new abstractions. We implemented XD_UNION support in (mark_with_description), so we can describe exspecially console/device specific data with XD_UNION. To describe with XD_UNION, we added a field to these objects, which holds the variant type of the object. This field is initialized in the appendant constructor. The variant is an integer, it has also to be described in an description, if XD_UNION is used. XD_UNION is used in following descriptions: * console.c: console_description (get_console_variant): returns the variant (create_console): added variant initialization * console.h (console_variant): the different console types * console-impl.h (struct console): added enum console_variant contype * device.c: device_description (Fmake_device): added variant initialization * device-impl.h (struct device): added enum console_variant devtype * objects.c: image_instance_description font_instance_description (Fmake_color_instance): added variant initialization (Fmake_font_instance): added variant initialization * objects-impl.h (struct Lisp_Color_Instance): added color_instance_type * objects-impl.h (struct Lisp_Font_Instance): added font_instance_type * process.c: process_description (make_process_internal): added variant initialization * process.h (process_variant): the different process types
author michaels
date Wed, 31 Jul 2002 07:23:39 +0000
parents 376386a54a3c
children
line wrap: on
line source

More Neat Stuff for your Emacs			-*-Outline-*-

This file describes GNU Emacs programs and resources that are maintained
by other people.  Some of these may become part of the Emacs distribution
in the future.

* The LCD archive

There is a large collection of Emacs Lisp code available for FTP at
archive.cis.ohio-state.edu; it is actively maintained by Dave Brennan
<brennan@hal.com> and Dave Sill <de5@ornl.gov>.

To get started using this archive, do:

	ftp archive.cis.ohio-state.edu

Once you're in FTP, do

	cd pub/gnu/emacs/elisp-archive
	bin
	get lispdir.el.Z
	get LCD-datafile.Z

and exit.  Then do:

	compress -d *.Z

The lispdir.el package will help you search for useful packages in the
LCD-datafile, which is a list of the archive constants.  It will even
fetch them for you on command.

* Eric Ludlam's etalk system

Eric Ludlam has written a C program and Emacs Lisp code to do Internet talk
through an Emacs window.  The package also includes Emacs Lisp code which
assists you in using talk to play a number of different interactive games.

This system seems to be quite nicely put together and is well documented
with a texinfo file that you can integrate into Emacs's own on-line help.
It's too large and specialized to include in the Emacs distribution, though.

Sources of this system are available for FTP at

	nic.umass.edu		128.119.166.14

Look under pub/contrib.  As of March 23 1993, there are two relevant files:

	pub/contrib/etalk0.6B.tar.Z	--- sources of the talk system
	pub/contrib/egames0.6B.tar.Z	--- more game-support files

We don't know whether this can use the additional features in GNU talk.