What to do with modules now ...

All, Once the module loading technology is in place and people are happier with it, I would like to start work on ripping out major parts of XEmacs and putting them in modules. I havem in my prototype tree, a mechanism in place where a given source file can either be compiled in as part of the dumped Emacs, or as a module. If module loading is availible, the makefile is constructed in such a way that it compiles things as modules rather than part of the dumped Emacs. This is a good thing. It is not only possible, but preferable (I believe) to make large parts of XEmacs modules. It will also make distribution a lot easier. I am working on making the TTY and X11 code loadable, so that you only ever load in those parts that you care about. At the same time, I will make the redisplay code loadable, so that if you ever load emacs in batch mode you dont get the redisplay engine pulled in. Many such things exist. The biggest win is how it will now be possible to distribute XEmacs. Many sites have only X11 or only TTYs, and it makes little sense to have an EMacs compile that contains code you know will never be used. This changes all of that. Things such as the font locking code, the MD5 stuff, Base64, alternate widget sets and dialog styles, sound support, and other parts of XEmacs can now all be made into modules, and auto-loaded as required. This gives users choices they didnt have before (eg, I think I'll try loading the Lucid widgets instead of the mOtif ones) and it reduces the size of the in-memory footprint of Emacs considerably. I find this all very exciting, and think we could be on our way to a new Emacs era (*drum roll*). Lets talk about this, and lots. -- J. Kean Johnston | "If equal affection cannot be, Engineer, SPG | let the more loving one be me" - W.H. Auden Santa Cruz, CA +---------------------------------------------------------- Tel: 831-427-7569 Fax: 831-429-1887 E-mail: jkj(a)sco.com