* Add .tedit files for Lafite manual and release notes -- PDFs on Google Drive * use 'docs' for subfolder name; wliminate dup * Remove duplicate LAFITEMANUAL-GLOSSARY-CUSTOMER.TEDIT --------- Co-authored-by: Nick Briggs <nicholas.h.briggs@gmail.com>
14 lines
2.5 KiB
Plaintext
14 lines
2.5 KiB
Plaintext
There is a new version of Lafite. For Medley/LispCore users, it is on {Eris}<LispCore>Internal>Library>. There is also a version compiled for Lyric, but substantially less tested, on {Phylum}<LispLibrary>Lyric>New>.
|
||
|
||
For many users, the highlight of the new version is that GV and NS mode run simultaneously. Details of this and some of the other features and bug fixes may be found in the 15-page file Lafite-Jun-88.IP (same directories).
|
||
|
||
If you want to load the new version on top of the old, first Quit out of the old Lafite, then load all of the following LCOMs from the appropriate directory:
|
||
|
||
LAFITEBROWSE
|
||
LAFITEMAIL
|
||
LAFITESEND
|
||
MAILCLIENT
|
||
NSMAIL
|
||
LAFITEFIND
|
||
LAFITE
|
||
|
||
Of the three files MAILCLIENT, NSMAIL, LAFITEFIND, you need only load those that are already present in your sysout from the old Lafite; I believe all are present in the standard Parc sysout, so all must be reloaded. Note that LAFITE.LCOM must be loaded last. Lyric users: you must have NSRANDOM loaded (it is in the Parc sysout) for full NS Mail functionality.
|
||
|
||
Rooms users should additionally load {Pogo:AISNorth}<Rooms>Medley>Users>NEW-LAFITE-WINDOW-TYPES.DFASL and re-dump their suite. Henceforth NEW-LAFITE-WINDOW-TYPES will be autoloaded when their suite is loaded, provided {Pogo:AISNorth}<Rooms>Medley>Users> is on DIRECTORIES. There apparently isn't a version compiled for Lyric just yet.
|
||
|
||
This version of Lafite is incompatible with Lens; Ramana will send a message when there is news on that front. It is also unlikely to be compatible with any other program that thinks it knows about Lafite internals, as many have changed.
|
||
|
||
If the brave pioneers report no outrageous bugs in the next week or two, these will get moved to the standard release places.
|
||
|