Date: Fri, 11 May 90 14:27 PDT From: Express Windows List Administrator Sender: snicoud@atc Reply-To: Express Windows List Administrator Subject: Welcome Message To: express-windows@atc Welcome to the Express Windows mailing list. This is an informal, unmoderated mailing list dedicated to the discussion of topics and issues arising out of the use of Express Windows. Express Windows is a package developed by Liszt Programming that runs on top of either Lucid 3.0 or Allegro Common Lisp and CLX. PCL is optional. Express Windows allows programs using a large subset of Symbolics' Dynamic windows(TM) to run on general purpose hardware. Express Windows can be found in the lisp directory on uunet.uu.net and in the pub directory of trix.ai.mit.edu. The title of the compressed tar file is express-windows.tar.Z. A copy of the copyright restrictions can be found in the file COPYING included in the distribution. Administrative requests (e.g., adding/deleting/changing addresses, forwarding/resending of bounced mail, or anything else having to do with mailing list administration) should be sent to: express-windows-request@atc.boeing.com Submissions should be sent to: express-windows@atc.boeing.com Date: Fri, 11 May 90 14:30 PDT From: Felix Ingrand To: express-windows@atc In-Reply-To: <19900511212743.5.SLN@SKAGIT.atc.boeing.com> Subject: First Question Organization: SRI International, Menlo Park, CA Phone: (415) 859 5584 Is Express Window going to be to CLIM what PCL was to CLOS? I must confess I have not installed and used EW yet, but I recall it implement Dynamic Window stuff, which itself is the base for the Lisp Machine CLIM implementation. So it looks like EW and CLIM has some common points. Felix Date: Fri, 11 May 90 14:39 PDT From: Express Windows List Administration Sender: snicoud@atc Reply-To: Express Windows List Administration Subject: Expect Failed Mail To: express-windows@atc Just a warning. Expect a certain amount of failed mail when making submissions to express-windows. I was not able to resolve every single address given to me to add to the list. Please bear with me. It would be a nice favor if you would forward/resend any express windows bounced mail to express-windows-request@atc.boeing.com. Thanks for your help, Steve -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences Date: Fri, 11 May 90 15:07 PDT From: Stephen L. Nicoud Subject: Boeing ATC mods to EW. To: express-windows@atc Well, to get the ball rolling, I suppose I'll list out some of the changes we made to EW to get it to run in Lucid 3.0.2 on a Sun 3 (OS 4.0.X). There's a long list of stuff we did. I'll submit them as groups in separate messages. The first one will be in this message. First of all we had to deal with a font name error when doing the (clear-all). tk@research.att.com gave us the solution which is appended here. Basically, the solution is correct the misspelling of the 'dec-adobe-...' fonts to '-adobe-...'. ------- Forwarded Message ------- Date: Wed, 18 Apr 90 07:13 PDT To: snicoud@atc.boeing.com From: tk@research.att.com Sender: tk@allegra.tempo.nj.att.com In-Reply-To: Stephen L. Nicoud's message of Tue, 17 Apr 90 11:04 PDT <19900417180449.6.SLN@SKAGIT.atc.boeing.com> Subject: Re: Name Error? the name-error is because a font EW is asking for doesn't exist. the following changes to code/fonts.lisp eliminate the error. *** fonts.lisp Wed Apr 4 18:42:38 1990 --- fonts.lisp~ Mon Apr 2 17:03:17 1990 *************** *** 200,211 **** (:SYMBOL (:roman ! (:small -adobe-symbol-medium-r-normal--10-100-75-75-p-61-adobe-fontspecific) ! (:normal -adobe-symbol-medium-r-normal--12-120-75-75-p-74-adobe-fontspecific) ! (:large -adobe-symbol-medium-r-normal--14-140-75-75-p-85-adobe-fontspecific) ! (:very-large -adobe-symbol-medium-r-normal--18-180-75-75-p-107-adobe-fontspecific) ! (:huge -adobe-symbol-medium-r-normal--24-240-75-75-p-142-adobe-fontspecific) ! (:very-small -adobe-symbol-medium-r-normal--8-80-75-75-p-51-adobe-fontspecific))))) --- 200,211 ---- (:SYMBOL (:roman ! (:small dec-adobe-symbol-medium-r-normal--10-100-75-75-p-61-adobe-fontspecific) ! (:normal dec-adobe-symbol-medium-r-normal--12-120-75-75-p-74-adobe-fontspecific) ! (:large dec-adobe-symbol-medium-r-normal--14-140-75-75-p-85-adobe-fontspecific) ! (:very-large dec-adobe-symbol-medium-r-normal--18-180-75-75-p-107-adobe-fontspecific) ! (:huge dec-adobe-symbol-medium-r-normal--24-240-75-75-p-142-adobe-fontspecific) ! (:very-small dec-adobe-symbol-medium-r-normal--8-80-75-75-p-51-adobe-fontspecific))))) ------- End of Forwarded Message ------- Date: Fri, 11 May 90 15:16 PDT From: Eric Buckman Subject: First Question To: express-windows@ALAN.kahuna.decnet.lockheed.com.ARPANET In-Reply-To: <9005112130.AA11013@Sunset.AI.SRI.COM> Date: Fri, 11 May 90 14:30:22 PDT From: felix@Warbucks.AI.SRI.COM (Felix Ingrand) Is Express Window going to be to CLIM what PCL was to CLOS? I must confess I have not installed and used EW yet, but I recall it implement Dynamic Window stuff, which itself is the base for the Lisp Machine CLIM implementation. So it looks like EW and CLIM has some common points. Felix That's my view. Originally, EW was written to be a commercial product that brought DW type functionality to other platforms. At about the time they were releasing EW for sale, it became apparent the CLIM was for the same purpose, but had better industry backing. So, my guess is that is why they made EW public domain (i.e. free). We are interested in using EW only because it's free, and my guess is that when and if we get the funding to buy CLIM, we'd be much better off using CLIM, because of all the obvious reasons like support, and later generation software. eric Date: Fri, 11 May 90 15:41 PDT From: Monty Kosma To: BUCKMAN@ALAN.kahuna.decnet.lockheed.com.ARPANET cc: express-windows@ALAN.kahuna.decnet.lockheed.com.ARPANET In-Reply-To: Eric Buckman's message of Fri, 11 May 90 15:16 PDT <19900511221659.6.BUCKMAN@NILS.kahuna.decnet.lockheed.com> Subject: First Question Date: Fri, 11 May 90 15:16 PDT From: Eric Buckman Date: Fri, 11 May 90 14:30:22 PDT From: felix@Warbucks.AI.SRI.COM (Felix Ingrand) Is Express Window going to be to CLIM what PCL was to CLOS? I must confess I have not installed and used EW yet, but I recall it implement Dynamic Window stuff, which itself is the base for the Lisp Machine CLIM implementation. So it looks like EW and CLIM has some common points. Felix That's my view. Originally, EW was written to be a commercial product that brought DW type functionality to other platforms. At about the time they were releasing EW for sale, it became apparent the CLIM was for the same purpose, but had better industry backing. So, my guess is that is why they made EW public domain (i.e. free). We are interested in using EW only because it's free, and my guess is that when and if we get the funding to buy CLIM, we'd be much better off using CLIM, because of all the obvious reasons like support, and later generation software. eric right, and the other advantage is that we now have codes which run on the symbolics which use dynamic windows, and we'd like to be able to just rcp those to the sun and compile and run them there...I don't know if ew will really be that good, but we'll see... monty Date: Fri, 11 May 90 16:19 PDT From: Stephen L. Nicoud Subject: EW with May Day PCL To: express-windows@atc The version of PCL provided with EW is the AAAI Day version (August 1988). Since we have been using Victoria Day, Rainy Day, and now, May Day PCL, we knew we were gonna have to convert EW for those versions. Here's a (hopefully somewhat complete and accurate) list of changes we made that make EW compatible with May Day PCL (should be fine with Rainy Day, too; don't know about Victoria Day, though). 1. Gave ":initarg"s to all slots in all the defclass forms. The :initarg should be a symbol in the keyword package with the same as the name of the slot. 2. Removed use of :accessor-prefix in defclass forms, installing ":accessor" for every slot in every class. The :accessor should be a symbol with the name of the class prepended to the name of the slot (with an intervening hyphen). 3. In frames.lisp, define-program-framework should use :initarg and :accessor now. So, replace #+EW-CLOS (defclass ,name (,inherit-from) ,(mapcar #'(lambda (variable) (if (consp variable) `(,(first variable) :INITFORM ,(second variable)) variable)) state-variables) (:accessor-prefix ,(intern (lisp-format NIL "~A-" name)))) with #+EW-CLOS (defclass ,name (,inherit-from) ,(mapcar #'(lambda (variable) (if (consp variable) `(,(first variable) :accessor ,(intern (lisp:format NIL "~A-~A" name (first variable)) (symbol-package name)) :initarg ,(intern (string (first variable)) :keyword) :INITFORM ,(second variable)) variable)) state-variables)) 4. Removed the &rest arguments in print-object methods in frames.lisp and macros.lisp (and removed their corresponding (declare (ignore ignore)) statements). 5. Added this form at the end of system.lisp in order for macros.lisp to compile properly. (when (boundp 'pcl::*defclass-times*) (pushnew 'compile pcl::*defclass-times*) (pushnew 'compile pcl::*defmethod-times*)) 6. In type.lisp, lisp-window.lisp, presentation-types.lisp, flavors-to-pcl.lisp: change PCL::IWMC-CLASS-P to PCL::STANDARD-CLASS-P. 7. In lisp-window.lisp, calls to define-lisp-command with keyword args broke lucid3.0 (">>Trap: Bus error"). This is a PCL problem, I think. What I did was to add an "&rest ignore" to the arglist if it has &key in it. Basically, it just looks for &key and splices in "&rest ignore" if it finds it there. While it seems to be only a PCL problem, it shouldn't hurt any other CLOS's to do this (I hope). So, in frames.lisp replace: (defun get-argument-list (args) (let ((args (mapcar #'(lambda (arg) (if (symbolp arg) arg (list (first arg) (getf (cddr arg) :DEFAULT)))) args))) (when args (cons '&OPTIONAL args)))) with: (defun get-argument-list (args) (let ((args (mapcar #'(lambda (arg) (if (symbolp arg) arg (list (first arg) (getf (cddr arg) :DEFAULT)))) args))) (let ((key-position (position '&key args))) (when key-position (cond ((zerop key-position) (setq args (append '(&rest ignore) args))) (t (let* ((list (append '(&rest ignore) (nthcdr key-position args)))) (setq args (rplacd (nthcdr (%1- key-position) args) list)))))) (when args (cons '&OPTIONAL args))))) -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences Date: Fri, 11 May 90 16:42 PDT From: Stephen L. Nicoud Subject: EW & CLX R4.x To: express-windows@atc EW comes with CLX R3. Since we have been using the latest and greatest versions of CLX (R4, then R4.1, and now R4.2), we had to make at least one modification. CLX R3 defined a macro called DECLARE-VALUES. You either have to grab the definition from R3 in file depdefs.lisp #+lispm (defmacro declare-values (&rest vals) `(declare (sys:values ,@vals))) #-lispm (defmacro declare-values (&rest vals) `(declare (values ,@vals))) or just go through the EW code changing "(declare-values ...)" to "(declare (values ...))". For no particular reason, we chose the latter approach. Steve -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences Date: Fri, 11 May 90 17:08 PDT From: Stephen L. Nicoud Subject: Miscellaneous mods to EW To: express-windows@atc Here are some miscellaneous changes we made to EW. 1. Since only Lispms seem to treat a variable called IGNORE as a special case (i.e., ignorable, we added the form at the bottom of system.lisp to suppress the numberous and annoying warnings about "Variable: IGNORE bound but not referenced.": #-lispm (proclaim '(special ew::ignore)) The proper way to handle this is probably to go through and put (declare (ignore ignore)) all over the place. We decided to take the short cut. 2. We sprinkled (declare (ignore ...)) throughout the code for those other "bound but not referenced" warnings and commented out unused bindings. 3. symbols.lisp was shadowing CLEAR-INPUT, but it didn't seem to be defined anywhere, so we commented it out of the list EW::*Common-Lisp-Symbols-To-Shadow*. 4. x-interface.lisp changed "#+symbolics cl:pi #-symbolics user::pi" to just lisp:pi. 5. We got tired of looking at all those undefined function warnings, so, in system.lisp we changed: (defun compile-ew () (unless (fboundp 'compile-file-maybe) (load (make-pathname :NAME "defsystem" :TYPE "lisp" :DEFAULTS *Default-EW-Code-Pathname*))) (dolist (file *Ew-Files*) (compile-file-maybe file) (load-file-maybe file)) (dolist (file *Optional-Ew-Files*) (compile-file-maybe file) (load-file-maybe file))) To: (defun compile-ew () (unless (fboundp 'compile-file-maybe) (load (make-pathname :NAME "defsystem" :TYPE "lisp" :DEFAULTS *Default-EW-Code-Pathname*))) (#+lucid lucid::with-deferred-warnings #+symbolics compiler:compiler-warnings-context-bind #-(or lucid symbolics) progn (dolist (file *Ew-Files*) (compile-file-maybe file) (load-file-maybe file)) (dolist (file *Optional-Ew-Files*) (compile-file-maybe file) (load-file-maybe file)))) 6. We also cleaned up the load-ew.lisp and system.lisp pathname stuff. Nothing important, just local customizations to the pathname constructions that enhance portability between lispms and non lispms without all the #+symbolics crap. If you really, really want to see this, let me know. Steve -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences Date: Fri, 11 May 90 17:14 PDT From: Stephen L. Nicoud Subject: QUERY-FOR-QUERY-MENU To: express-windows@atc In query.lisp: function QUERY-FOR-QUERY-MENU refers to two variables, both of which are undefined: *Gray-gcontext* and pattern. Don't know why they are there, so don't know what to do with 'em. Steve -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences Date: Fri, 11 May 90 21:04 PDT From: Stephen L. Nicoud Subject: First Question To: Eric Buckman cc: express-windows@atc In-Reply-To: <19900511221659.6.BUCKMAN@NILS.kahuna.decnet.lockheed.com> Date: Fri, 11 May 90 15:16 PDT From: Eric Buckman Date: Fri, 11 May 90 14:30:22 PDT From: felix@Warbucks.AI.SRI.COM (Felix Ingrand) Is Express Window going to be to CLIM what PCL was to CLOS? I must confess I have not installed and used EW yet, but I recall it implement Dynamic Window stuff, which itself is the base for the Lisp Machine CLIM implementation. So it looks like EW and CLIM has some common points. Felix That's my view. Originally, EW was written to be a commercial product that brought DW type functionality to other platforms. At about the time they were releasing EW for sale, it became apparent the CLIM was for the same purpose, but had better industry backing. So, my guess is that is why they made EW public domain (i.e. free). We are interested in using EW only because it's free, and my guess is that when and if we get the funding to buy CLIM, we'd be much better off using CLIM, because of all the obvious reasons like support, and later generation software. eric I guess I've viewed EW as strictly an implementation of DW for other Common Lisps. We are looking into using EW for a couple of reasons (1) you can't beat the price (2) it offers way to get our DW-based applications running on other customer's hardware quickly. Personally, I see it as only a temporary solution until we get, then convert to CLIM. The rub is, though, I need portability for some of my work not today, but yesterday, so I can't wait until CLIM gets released for all the vendors. Besides, (and you can debate the logic of having done this in the first place) we've invested a great deal of time into developing our current DW applications. It's tough to go ask for money to RE-do old work. Management is always so interested in seeing new and more functionality. Steve -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences Date: Fri, 11 May 90 21:09 PDT From: Express Windows List Administration Sender: snicoud@atc Subject: Archives To: express-windows@atc FYI, we're not keeping formal archives of these mail messages. If someone wants to provide that service for the list, let us all know. Thanks, Steve -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences Date: Fri, 11 May 90 22:42 PDT From: Stephen L. Nicoud Subject: Express Windows on Symbolics To: express-windows@atc cc: Andrew L. Ressler It just doesn't seem to me that EW is set up to be run on the Symbolics very well. For one thing :UNIX and :X are pushed onto the *FEATURES* list in system.lisp. Removing the :UNIX push is fine, but if you remove the :X push, you're in trouble. The XFONTS stuff (fonts.lisp) won't get compiled. The code is sprinkled with #+(and symbolics (not x)) and a form, typically followed by a #+X and a form. This suggests to me that the Symbolics can be both a client and a server with and without X. Now, I was successful in compiling EW on Symbolics (7.2) with CLX R4 and May Day PCL. I set the EW::*DEFAULT-HOST* to my Sun's name (thus the Symbolics is merely the client), and did a (clear-all) [which after prompting me to redefine all sorts of fonts to which I replied (P)roceed]. The EW window came up just fine on my Sun. I placed it where I wanted it, and (clear-all) returned. Next, I did (run-program 'lisp-window). Sure enough the Lisp Window came up. It even took a command 'Show Environment'. Only as soon as I touched the mouse, BANG, ZOWIE, the windows disappeared and the (run-program 'lisp-window) form ends up in the debugger complaining about timing out on mouse stuff. I'm hosed from then on. I can't run any more lisp-windows or (clear-all) or anything, unless I reboot. My (totally naive) guess is that there's some difference between CLX R3 and R4 which might explain this. Can anyone verify this? Any ideas? So, all of this begs the question, "In what manner is EW to run on the Symbolics?" As client or server, with or without X? The code seems to indicate that EW can perform all, only I can barely get to fulfill an X client role and not at all in any other capacity. Right now, I need code to run standalone on Symbolics (client and server, with no X) and standalone in Lucid and Allegro (client and server, with X). Of course, since EW::define-program-framework creates classes, I have to rid myself once and for all of the message sending our applications do to the program frameworks. Ughh! Steve -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences Date: Mon, 14 May 90 08:55 PDT From: Stephen L. Nicoud Subject: Best Copy of EW To: express-windows@atc I am forwarding this message because it brings up a relevant question about how modifications to EW will be tracked and maintained. Suggestions are hereby solicited. ------- Forwarded Message ------- Summary-line: 12-May vax!esrig@wrath.cs.cornel #not posting code Date: Sat, 12 May 90 13:56 PDT From: Bruce Esrig To: express-windows-request@atc.boeing.com Subject: not posting code Will there be a "best copy" of EW edited by someone ? If I have to read and track all the changes myself, it probably won't be worth it. We could post descriptions of our changes, but posting the code would be completely impractical. Bruce esrig%oravax.uucp@cu-arpa.cs.cornell.edu ------- End of Forwarded Message ------- -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences Date: Mon, 14 May 90 09:14 PDT From: Patrick Logan To: express-windows Subject: Looking for documentation for EW or Symbolics' window system I am looking for more documentation for EW. It's been several years since I've used a lisp machine. What would be ideal (I think) would be to pick up some used Symbolics manuals. Any ideas? Thanks, Patrick -- Patrick Logan uunet!mntgfx!plogan | Mentor Graphics Corp. 8500 SW Creekside Pl | Beaverton, Oregon 97005-7191 | Date: Mon, 14 May 90 11:06 PDT From: Monty Kosma To: express-windows@atc In-Reply-To: Stephen L. Nicoud's message of Fri, 11 May 90 16:19 PDT <19900511231946.7.SLN@SKAGIT.atc.boeing.com> Subject: EW with May Day PCL Date: Fri, 11 May 90 16:19 PDT From: Stephen L. Nicoud The version of PCL provided with EW is the AAAI Day version (August 1988). Since we have been using Victoria Day, Rainy Day, and now, May Day PCL, we knew we were gonna have to convert EW for those versions. Here's a (hopefully somewhat complete and accurate) list of changes we made that make EW compatible with May Day PCL (should be fine with Rainy Day, too; don't know about Victoria Day, though). What do these PCL version designations correspond to? How do I know which one I have? When I got EW I couldn't get it to run under lcl 3.0, so I ftped myself the latest pcl from arisia.xerox.com... monty kosma lockheed research kosma@alan.decnet.lockheed.com To: express-windows@atc Reply-To: todd.kaufmann@NL.CS.CMU.EDU Subject: New to EW, but plenty of questions (sun4/acl3.1beta) Date: Mon, 14 May 90 11:07 PDT From: Todd.Kaufmann@NL.CS.CMU.EDU Okay, so I just got the big tar file and tried loading it. It just about all loaded, until the last file: ; Loading /afs/cs/project/cmt-1/sun4/express-w/ew/code/lisp-window.lisp. Error: Invalid initialization argument :NAME for class PROGRAM-FRAMEWORK This looks like some PCL problem, possibly version diffs between that and the in-core version on "Allegro CL 3.1.beta.22 [Sun4] (6/8/89)". Wait-- I just got a bunch of EW mail, and it looks like this is explained; at least somewhat. However, if there's anyone who's got this running on ACL3.1 already, I'd be glad to hear about any special tweaks. Thanks, -todd ps: cmu people, please contact me. ------------------------------------------------------------------ Here's that bug-- [1] :dn Evaluation stack: (ERROR "Invalid initialization argument ~S for class ~S" :NAME ...) ->(PCL::CHECK-INITARGS-1 # (:NAME LISP-WINDOW :COMMAND-TABLE ...) ...) (PCL::|(METHOD MAKE-INSTANCE (STANDARD-CLASS))| # :NAME ...) (APPLY # # ...) Summary-line: 14-May p2@Porter.ASL.dialnet.sym #Archives Date: Mon, 14 May 90 11:37 PDT From: Peter Paine Subject: Archives To: express-windows%atc.boeing.com%riverside.SCRC.symbolics.com@SKYWALKER.ENTERPRISE.DIALNET.SYMBOLICS cc: EW-Boeing@Porter.ASL.dialnet.symbolics In-Reply-To: <19900512040925.8.SLN@SKAGIT.atc.boeing.com> Date: Fri, 11 May 90 21:09 PDT From: Express Windows List Administration FYI, we're not keeping formal archives of these mail messages. If someone wants to provide that service for the list, let us all know. Thanks, Steve -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences I am keeping a record of everything that I receive (re. EW). However, the mail to here (the UK) is not very reliable at the moment. <= p2 Date: Mon, 14 May 90 11:56 PDT From: Stephen L. Nicoud Subject: EW with May Day PCL To: Monty Kosma cc: express-windows@atc In-Reply-To: <9005141806.AA02808@human-torch.lockheed.com> Date: Mon, 14 May 90 11:06:58 PDT From: kosma%human-torch@STC.LOCKHEED.COM (Monty Kosma) Date: Fri, 11 May 90 16:19 PDT From: Stephen L. Nicoud The version of PCL provided with EW is the AAAI Day version (August 1988). Since we have been using Victoria Day, Rainy Day, and now, May Day PCL, we knew we were gonna have to convert EW for those versions. Here's a (hopefully somewhat complete and accurate) list of changes we made that make EW compatible with May Day PCL (should be fine with Rainy Day, too; don't know about Victoria Day, though). What do these PCL version designations correspond to? AAAI Day PCL is the August 1988 version Victoria Day PCL is the May 1989 version Rainy Day PCL is the February 1990 version May Day PCL is the May 1990 version May Day PCL is the final release of PCL. How do I know which one I have? You can look at the variable PCL::*PCL-SYSTEM-DATE*, which is defined at the top of the defsys.lisp file of the pcl directory. When I got EW I couldn't get it to run under lcl 3.0, so I ftped myself the latest pcl from arisia.xerox.com... You will need to modify EW to run with Victoria, Rainy, or May Day PCL. (see the previous message for a list of those modifications). Also note that you should be able to compile EW without PCL at all, though I haven't tried that myself. Steve -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences Date: Mon, 14 May 90 12:17 PDT From: Stephen L. Nicoud Subject: New to EW, but plenty of questions (sun4/acl3.1beta) To: todd.kaufmann@NL.CS.CMU.EDU.ARPANET cc: express-windows@atc In-Reply-To: <2921.642708473@NL.CS.CMU.EDU> Date: Mon, 14 May 90 14:07:53 EDT From: Todd.Kaufmann@NL.CS.CMU.EDU Okay, so I just got the big tar file and tried loading it. It just about all loaded, until the last file: ; Loading /afs/cs/project/cmt-1/sun4/express-w/ew/code/lisp-window.lisp. Error: Invalid initialization argument :NAME for class PROGRAM-FRAMEWORK This looks like some PCL problem, possibly version diffs between that and the in-core version on "Allegro CL 3.1.beta.22 [Sun4] (6/8/89)". It's not a PCL problem per se, just that Allegro CL comes with Victoria Day PCL which requires you to specify the :initarg for each slot in a class. The EW code is set up to use AAAI PCL (an earlier version) which didn't have that requirement. We went through and added that option (:initarg) to every slot of every defclass in EW (probably overkill, but we didn't want to take the time to investigate which ones were initialized and which ones weren't). Steve -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences Summary-line: 14-May p2@Porter.ASL.dialnet.sym #First Question Date: Mon, 14 May 90 12:22 PDT From: Peter Paine Reply-To: EW-Boeing%porter.asl.dialnet.symbolics.com@RIVERSIDE.SCRC.SYMBOLICS Subject: First Question To: express-windows%atc.boeing.com%riverside.SCRC.symbolics.com@SKYWALKER.ENTERPRISE.DIALNET.SYMBOLICS cc: p2@Porter.ASL.dialnet.symbolics In-Reply-To: <19900512040455.7.SLN@SKAGIT.atc.boeing.com> Date: Fri, 11 May 90 21:04 PDT From: Stephen L. Nicoud Date: Fri, 11 May 90 15:16 PDT From: Eric Buckman Date: Fri, 11 May 90 14:30:22 PDT From: felix@Warbucks.AI.SRI.COM (Felix Ingrand) Is Express Window going to be to CLIM what PCL was to CLOS? I must confess I have not installed and used EW yet, but I recall it implement Dynamic Window stuff, which itself is the base for the Lisp Machine CLIM implementation. So it looks like EW and CLIM has some common points. Felix That's my view. Originally, EW was written to be a commercial product that brought DW type functionality to other platforms. At about the time they were releasing EW for sale, it became apparent the CLIM was for the same purpose, but had better industry backing. So, my guess is that is why they made EW public domain (i.e. free). We are interested in using EW only because it's free, and my guess is that when and if we get the funding to buy CLIM, we'd be much better off using CLIM, because of all the obvious reasons like support, and later generation software. eric I guess I've viewed EW as strictly an implementation of DW for other Common Lisps. We are looking into using EW for a couple of reasons (1) you can't beat the price (2) it offers way to get our DW-based applications running on other customer's hardware quickly. Personally, I see it as only a temporary solution until we get, then convert to CLIM. The rub is, though, I need portability for some of my work not today, but yesterday, so I can't wait until CLIM gets released for all the vendors. Besides, (and you can debate the logic of having done this in the first place) we've invested a great deal of time into developing our current DW applications. It's tough to go ask for money to RE-do old work. Management is always so interested in seeing new and more functionality. Steve -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences We held off using DW stuff, staying with Rel.6 message passing TV windows, for as long as possible as it was not clear that there was any general market for DW material outside Symbolics targets. This left us in touch with the installed base of Smbx and TI (& LMI) machines along with the limited GoldHill graphics we had to run on the PC. Meanwhile, hacking DW on every possible non-persistant application as it was so much more powerful and productive - if slow to run. CLOE was embraced politically and found to be hard work, skinny and very late. So when CLIM/EW came along it seemed that the cheap and generalised grownup lisps would at last be available widely. In Europe, there are almost no Lispms available in academia. So the bright new graduates (and hence new C s/w engineers in industry) know only of Lisp as that headache with all the brackets and recursion. CLIM today is very tied up with Symbolics, it will be some time coming and at a price. We want a platform on which to float small utilities and gadgets in powerful Lisp and one which we can share with the widest audience possible. The market for Lispm developed systems seems to be confined to enormous things like Concordia. The fact that EW is free is very important as it will entice the participation of a lot of people who wait and watch the doings of Lisp fraternity from the side lines - fearful that any involment will necessitate the purchase of a Lisp Machine (the cost of which, in Europe, is generally double that in the US, and which brings technical and cultural isolation). EW seems to offer a space before CLIM is dirt cheap or a standard, where we can hope to give away Lisp applications whose value is based upon what they can DO - rather than on the operating system licences and hardware that are required to run the applications. <= p2 Subject: Introduction and Info To: express-windows Date: Mon, 14 May 90 12:38 PDT From: Andrew Ressler X-Mailer: Elm [version 2.1 PL1] Hi, I'm Andrew L. Ressler. The designer of Express Windows (EW). For those of you using EW I should probably fill you in on a few details. 1. The general philosphy behind the design of EW was to make it easy to port Genera 7.2 window applications from a Symbolics machine to other lisp platforms. In general, the emphasis was on speed, and not on full 100% functionality. I know of a couple things one can still do to improve the speed of EW. If any of you come up with better ways, please post them to the world. 2. The license for EW is NOT as restrictive as GNU Emacs. When distributing software using Express Windows you need only to distribute the source to EW. You can do whatever you want with the code you build on top of it. (i.e. charge for it, not give sources, etc.) 3. EW was designed under X11R3 and an older version of PCL. It does work under newer versions of either with only minor changes. Most of which people have already figured out. 4. EW does not have to have CLOS or PCL to work. If your application does not need to build its own classes of windows so that you add slots or methods to the basic windows, then EW can be compiled to use defstructs for the windows. In the original version as shipped this could provide speedups of 20-30%. 5. EW seems to run faster in Franz Allegro than Lucid Lisp. I think this is mainly due to the low levels of CLX being faster. 6. EW was originally written on a Symbolics using Rel 6 style windows. That's why you may see some obsolete references to symbolics style windows in the code. It WILL STILL work as a CLIENT on a symbolics, but it must drive an X server. I have not tried the Symbolics X server. But it works very nicely driving a SUN. 7. You can easily make your code so that it will port between a Symbolics and non-Symbolics and back by carefully declaring and using packages. EW can use the same symbols in the same packages as symbolics if you want. That way your code can use dw:define-presentation-action and when it is on a Symbolics it will use Genera and when it is not on Symbolics it will use EW. 8. EW is not completely compatible with Symbolics Genera. In some cases, this is because some people depend on behavior of Genera that was not fully documented. In other cases, I had to make tradeoffs so that EW would perform OK. a. For instance, Incremental Redisplay does not try to be clever about redisplaying graphics that have been obscured by something that has since been erased. This would not be to hard to add, but would certainly slow things down. b. Several obscure, seldomly used keywords to the supplied functions are not implemented. This was done to minimize the overall size of EW. 9. EW is coded using Common Lisp - CLX - and CLOS (PCL). It should not depend on anything else. Therefore, If you have a lisp that CLX and CLOS run in, then you should be able to port EW with almost no changes. I personally only know of people using EW with Franz and Lucid running on Sun 3s and 4s. If anybody has ported to other platforms please let us know. For instance, Anybody using it on Apollo machines? 10. Feel free to call me to discuss EW (whether for good or bad) at 301-643-4526. However, I'm out of town a lot consulting so you may need to be persistent to get me. I also read mail on the net 2 weeks out of 4 at aressler@oiscola.columbia.ncr.com Thanks for using EW and I hope you like it. Andrew L. Ressler Date: Mon, 14 May 90 15:25 PDT From: Christopher Owens To: express-windows@atc Subject: EW-CLOS feature Although I am led to believe that EW can be compiled with or without PCL, there appears to be a problem when I try to compile without PCL. If I answer *no* to the questions about loading and compling CLOS, then the following problem occurs. The file /code/system.lisp does a (pushnew :EW-CLOS *Features*) Then the file /code/symbols.lisp contains the form #+ew-clos (import '(pcl::with-slots pcl::defclass pcl::defmethod pcl::make-instance pcl::print-object) 'express-windows) which looks for the (non-existant because I didn't load it) pcl package What should I be doing here? Subject: Re: EW-CLOS feature To: express-windows Date: Tue, 15 May 90 07:02 PDT From: Andrew Ressler cc: aressler@uw-beaver.UUCP In-Reply-To: <9005142225.AA00215@avarice.uchicago.edu>; from "Christopher Owens" at May 14, 90 5:25 pm X-Mailer: Elm [version 2.1 PL1] EW will work without PCL. Unfortunately, I forgot that that mode hadn't been tested lately, so a few things crept in to make it easier for people using PCL. The particular bug you refer is not really a bug and is fixed by just commenting out the pushnew of :EW-CLOS. This should fix most things. However, there is still one small sticky point that I was never sure which way to do. That has to do with the class object created by a DEFINE-PROGRAM-FRAMEWORK. You may need to make a minor mode there to get it to do the "right" thing. Whatever you think it should be. It may be that you want the window objects to be defstruct, but would still like the program object to be a class. The appropriate code to look at is in the same file that DEFINE-PROGRAM-FRAMEWORK is in. Andrew L. Ressler aressler@oiscola.columbia.ncr.com 301-643-4526 > > Although I am led to believe that EW can be compiled with or without > PCL, there appears to be a problem when I try to compile without PCL. > If I answer *no* to the questions about loading and compling CLOS, > then the following problem occurs. > > > The file /code/system.lisp does a (pushnew :EW-CLOS *Features*) > > Then the file /code/symbols.lisp contains the form > > #+ew-clos > (import '(pcl::with-slots pcl::defclass pcl::defmethod pcl::make-instance pcl::print-object) > 'express-windows) > > which looks for the (non-existant because I didn't load it) pcl package > > > What should I be doing here? > Subject: Re: Looking for documentation for EW or Symbolics' window system To: express-windows Date: Tue, 15 May 90 07:05 PDT From: Andrew Ressler cc: aressler@uw-beaver.UUCP In-Reply-To: <9005141614.AA17269@pdx.MENTOR.COM>; from "Patrick Logan" at May 14, 90 9:14 am X-Mailer: Elm [version 2.1 PL1] The best documentation would be to use Symbolics. I think you can buy their documentation, but I'm not sure. The most useful manual is 7A of their documentation that was released with Genera 7.2. Andrew L. Ressler aressler@oiscola.columbia.ncr.com 301-643-4526 Subject: Re: Best Copy of EW To: express-windows Date: Tue, 15 May 90 07:09 PDT From: Andrew Ressler cc: aressler@uw-beaver.UUCP In-Reply-To: <19900514155510.2.SLN@SKAGIT.atc.boeing.com>; from "Stephen L. Nicoud" at May 14, 90 8:55 am X-Mailer: Elm [version 2.1 PL1] I'm looking for a volunteer to maintain the "right" version of EW. Unfortunately, my net access is not convenient for this since I log in through a site where I do consulting. Whoever wants to can be sure that I would be available to help. Andrew L. Ressler aressler@oiscola.columbia.ncr.com 301-643-4526 Subject: Re: QUERY-FOR-QUERY-MENU To: express-windows Date: Tue, 15 May 90 07:13 PDT From: Andrew Ressler cc: aressler@uw-beaver.UUCP In-Reply-To: <19900512001438.2.SLN@SKAGIT.atc.boeing.com>; from "Stephen L. Nicoud" at May 11, 90 5:14 pm X-Mailer: Elm [version 2.1 PL1] > > In query.lisp: function QUERY-FOR-QUERY-MENU refers to two variables, > both of which are undefined: *Gray-gcontext* and pattern. Don't know > why they are there, so don't know what to do with 'em. > These variables can be ignored, in fact they could be eliminated. They are part of an idea that I never finished. The idea was that multiple- choice type accepts could be disabled, but still in the menu. When disabled they would be displayed with gray text (not solid black). It's a nice hack that I've seen done in InterViews. Andrew L. Ressler aressler@oiscola.columbia.ncr.com 301-643-4526 Date: Tue, 15 May 90 08:33 PDT From: Brad Miller Subject: Re: EW with May Day PCL To: Stephen L. Nicoud cc: express-windows@ATC In-Reply-To: <19900514185632.5.SLN@SKAGIT.atc.boeing.com> Sender: miller@SOL.CS.ROCHESTER.EDU Reply-To: miller@SOL.CS.ROCHESTER.EDU Organization: University of Rochester, Department of Computer Science Postal-Address: 610 CS Building, Comp Sci Dept., U. Rochester, Rochester NY 14627 Phone: 716-275-1118 Date: Mon, 14 May 90 11:56 PDT From: Stephen L. Nicoud Date: Mon, 14 May 90 11:06:58 PDT What do these PCL version designations correspond to? AAAI Day PCL is the August 1988 version Victoria Day PCL is the May 1989 version Rainy Day PCL is the February 1990 version May Day PCL is the May 1990 version May Day PCL is the final release of PCL. How do I know which one I have? You can look at the variable PCL::*PCL-SYSTEM-DATE*, which is defined at the top of the defsys.lisp file of the pcl directory. Near as I can tell (having just loaded it) the version now on arisia is Victoria day. Where are the later versions?? ---- Brad Miller U. Rochester Comp Sci Dept. miller@sol {...allegra!rochester!miller} Date: Tue, 15 May 90 08:34 PDT From: Stephen L. Nicoud Subject: Introduction and Info To: Andrew Ressler cc: express-windows@atc In-Reply-To: <9005142035.AA08380@ames.arc.nasa.gov> Date: Mon, 14 May 90 15:38:16 EDT From: Andrew Ressler [...] Hi, I'm Andrew L. Ressler. The designer of Express Windows (EW). First of all, I'd like to thank Andrew for making Express Windows freely and easily available. We are excited at the prospect of getting our DW-based applications running on our Suns. 10. Feel free to call me to discuss EW (whether for good or bad) at 301-643-4526. However, I'm out of town a lot consulting so you may need to be persistent to get me. I also read mail on the net 2 weeks out of 4 at aressler@oiscola.columbia.ncr.com For everyone's information, Andrew is on the mailing list for Express Windows, so postings there will make it to him. I urge everyone to cc: express-windows@atc.boeing.com on any messages about Express Windows to Andrew. Chances are, that if you have a question, someone else (most likely me) also has the same question and we can all benefit by the exchange. Thanks for using EW and I hope you like it. Andrew L. Ressler In case any of you were wondering, the Express Windows list currently contains 77 addresses, many of which are distribution mailboxes at other organizations. I'm still getting half a dozen or so requests to be added each day. Obviously, interest in Express Windows is substantial. Steve -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences Date: Tue, 15 May 90 08:47 PDT From: Stephen L. Nicoud Subject: Re: EW with May Day PCL To: miller@SOL.CS.ROCHESTER.EDU.ARPANET cc: Stephen L. Nicoud , express-windows@ATC In-Reply-To: <19900515153329.4.MILLER@DOUGHNUT.CS.ROCHESTER.EDU> Date: Tue, 15 May 90 11:33 EDT From: Brad Miller Near as I can tell (having just loaded it) the version now on arisia is Victoria day. Where are the later versions?? Hmmm, that's odd. I just checked arisia.xerox.com. Here's what I found: > ftp arisia.xerox.com Connected to arisia.xerox.com. 220 arisia FTP server (Version 4.165 Tue Dec 6 18:32:49 PST 1988) ready. 331 Guest login ok, send ident as password. 230 Guest login ok, access restrictions apply. ftp> cd /pcl 250 CWD command successful. ftp> dir 200 PORT command successful. 150 Opening ASCII mode data connection for /bin/ls (0 bytes). total 1012 drwxrwxrwx 2 393 100 512 May 9 19:42 archive drwxrwxr-x 2 375 100 512 Apr 2 13:38 doc drwxr-xr-x 2 375 100 512 May 8 12:44 mop -rw-r--r-- 1 375 100 1024000 May 2 13:38 tarfile drwxr-xr-x 2 481 100 512 Oct 26 1988 web 226 Transfer complete. 315 bytes received in 0.06 seconds (5.1 Kbytes/s) ftp> Note, the PCL source is the 'tarfile' (dated May 2 of this year). That's the May Day version I pulled down a couple of weeks ago. The defsys.lisp file in that version has this toward the beginning of the file: (defvar *pcl-system-date* "5/1/90 May Day PCL (REV 2)") REV 1 of May Day PCL was released on 5/1/90 hence the name May Day. Because of some minor problems, though, Gregor posted a new and corrected version (REV 2). Here's Gregor's announcement of the release of May Day PCL. ------- Forwarded Message ------- From: Gregor J. Kiczales Newsgroups: bcsaic.mail-list.cloops Subject: new version of PCL Date: Tue, 1 May 90 19:22 PDT Lines: 11 There is a new version of PCL on arisia.xerox.com. This version, May Day PCL, is essentially Rainy Day PCL plus most of the various patches people have mailed out. The patches that didn't get included were the ones that had more to do with the programming environment. Barring unforseen circumstances, this is the last release of PCL I will produce. Gregor ------- End of Forwarded Message ------- Steve -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences Date: Tue, 15 May 90 09:22 PDT From: Brad Miller Subject: Re: EW with May Day PCL To: Stephen L. Nicoud cc: express-windows@ATC In-Reply-To: <19900515154712.6.SLN@SKAGIT.atc.boeing.com>, The message of 1 May 90 22:22 EDT from gregor@parc.xerox.com, The message of 1 May 90 22:22 EDT from Gregor J. Kiczales Sender: miller@SOL.CS.ROCHESTER.EDU Reply-To: miller@SOL.CS.ROCHESTER.EDU Organization: University of Rochester, Department of Computer Science Postal-Address: 610 CS Building, Comp Sci Dept., U. Rochester, Rochester NY 14627 Phone: 716-275-1118 Date: Tue, 15 May 90 08:47 PDT From: Stephen L. Nicoud Near as I can tell (having just loaded it) the version now on arisia is Victoria day. Where are the later versions?? Hmmm, that's odd. I just checked arisia.xerox.com. Here's what I found: Hmm. Right you are. My file sez the same thing, though evaling the var gives, and I know I booted since compiling the new system and loaded the new one (becaue of all the stuff that broke :-). pcl::*pcl-system-date* "5/22/89 Victoria Day PCL" Must have been something I did :-)... Thanks for the confirm. ---- Brad Miller U. Rochester Comp Sci Dept. miller@sol {...allegra!rochester!miller} To: express-windows@atc Reply-To: todd.kaufmann@NL.CS.CMU.EDU Subject: Color support? Date: Tue, 15 May 90 13:09 PDT From: Todd.Kaufmann@NL.CS.CMU.EDU Anyone have ideas for adding color to EW? I'm working on an interface to demo in <4 weeks. I just got EW up and running, and looked at the demos. I know CLX moderately well, though haven't played with it in color much. Boss would like color to wow crowds. I'll try to get my hands on some genera 7.2 docs and see how it's handled there. Something clean & compatible would be best, but if I have to resort to quick and dirty, I will. How about samples that run under the symbolics, to compare with? I'm off to hijack a LM now, so thanks, Todd Kaufmann Center for Machine Translation Summary-line: 15-May felix@Warbucks.AI.SRI.COM #EW under Sun Lisp 4.0 Beta Date: Tue, 15 May 90 17:44 PDT From: Felix Ingrand To: express-windows@atc Subject: EW under Sun Lisp 4.0 Beta Organization: SRI International, Menlo Park, CA Phone: (415) 859 5584 Anybody successfully loaded EW under Sun Lisp 4.0 Beta (with CLOS not PCL) and CLX X11R4? Felix Subject: Re: Color support? To: express-windows Date: Wed, 16 May 90 07:11 PDT From: Andrew Ressler cc: nl.cs.cmu.edu!todd.kaufman In-Reply-To: <11782.642802192@NL.CS.CMU.EDU>; from "nl.cs.cmu.edu!Todd.Kaufmann" at May 15, 90 4:09 pm X-Mailer: Elm [version 2.1 PL1] > > > Anyone have ideas for adding color to EW? Color should be straight forward to add. I never had a color monitor so I could test anything though. Each drawing primitive can take a COLOR keyword argument that could be a simple object with slots for RGB. Then inside the with-gcontext you would pass the appropriate information from the\ color object to the gcontext. You would also need to add a slot to the base level presentation if you want the color to be remembered. I don't think symbolic's color objects are much more complicated than that. Of course, you can always add fancy primitives for building appropriate colors. You would also want to minimize consing color objects on the fly. Call me at 803-739-7812 in the next few days if you want to discuss it furthur. Andrew L. Ressler aressler@oiscola.columbia.ncr.com 301-643-4526 Date: Wed, 16 May 90 07:57 PDT From: Richard Weyhrauch To: express-windows Subject: Where to get EW Could someone post where to get some "current" version of EW. Thanks Richard Weyhrauch IBUKI Summary-line: 16-May ARTHUR@GUINEVERE.tamu.edu #EW on MACII? Date: Wed, 16 May 90 10:02 PDT From: Arthur Keen Subject: EW on MACII? To: express-windows@atc Just out of curiosity, what would it take to run EW on a MAC II (Allegro.) I have been told that the missing ingredient is X-windows. Arthur A. Keen Knowledge Based Systems Lab Texas A&M University Date: Wed, 16 May 90 12:31 PDT From: Stephen L. Nicoud Subject: Where to get EW To: Richard Weyhrauch cc: express-windows@atc In-Reply-To: <9005161457.AA09057@ibuki.com> Date: Wed, 16 May 90 07:57:38 PDT From: ames!ibuki.com!rww@uw-beaver.UUCP (Richard Weyhrauch) Could someone post where to get some "current" version of EW. Thanks Richard Weyhrauch IBUKI To my knowledge the ONLY publicly available (anonymous ftp) version of EW can be had from either: trix.ai.mit.edu [IP Address: 128.52.32.6] (in the /pub directory) or uunet.uu.net [IP Address: 192.48.96.2] (in the /lisp directory) The file on both hosts is called express-windows.tar.Z (dated April 3rd on trix and April 2nd on uunet). Steve -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences Date: Thu, 17 May 90 03:43 PDT From: Peter Paine Subject: Re: Best Copy of EW To: express-windows%atc.boeing.com%riverside.SCRC.symbolics.com@SKYWALKER.ENTERPRISE.DIALNET.SYMBOLICS.COM.ARPANET, Peter@SKYWALKER.ENTERPRISE.DIALNET.SYMBOLICS.COM.ARPANET cc: p2@Porter.ASL.dialnet.symbolics.com.ARPANET In-Reply-To: <9005151450.AA09345@ames.arc.nasa.gov> One volenteer to maintain "right"version of EW in UK/Europe. <= p2 Subject: Express Windows and CLIM To: express-windows Date: Thu, 17 May 90 15:02 PDT From: Andrew Ressler X-Mailer: Elm [version 2.1 PL1] I'm curious what people think about the following: Do People want Express Windows to evolve into a Public Domain version of CLIM or at least to be more compatible or do they prefer it for now to be more like the original Dynamic Windows? If the answer is that you would like it to evolve to be more like CLIM are you willing to help add functionality to make it that way? Or would you be interested in funding furthur development of EW similar to the GNU software? What major features of DW do you wish it supported that is doesn't now. 1. format-graph ?? for example 2. ???? What major features do you not care about? How important is a small compact window system? (i.e. takes up less than 2 megabytes in your image) Thanks, Andrew Ressler 301-643-4526 Subject: Re: Best Copy of EW To: express-windows Date: Fri, 18 May 90 11:20 PDT From: Andrew Ressler In-Reply-To: <19900517104334.6.P2@Porter.ASL.dialnet.symbolics.com>; from "Peter Paine" at May 17, 90 10:43 am X-Mailer: Elm [version 2.1 PL1] > > One volenteer to maintain "right"version of EW in UK/Europe. > > <= p2 > Thanks Peter. We need to coordinate this a little. Does this mean you will be able to maintain a copy of EW that sites in UK/Europe will be able to FTP from? There have already been some fixes sent around so you would need to update the version from what you got from MIT. Also it would be good to make sure you advertise any new things you put in the version you are keeping. Now we also need to find a site in the USA. Any more volunteers? Andrew L. Ressler From: davel@whutt.att Date: Mon, 21 May 90 11:28 PDT Original-From: whutt!davel (David Loewenstern +1 201 386 6516) To: express-windows@atc cc: whutt!davel Subject: EW under Apollo Domain Lisp We are attempting to compile EW under Apollo's Domain/Common Lisp (a product of Lucid) with CLOS and CLX. We have been hung up on the file io-functions.lisp because: 1. It appears to redefine standard lisp functions, and *then* call the function (setup-lisp-functions) which is designed to take care of saving away the old version of the functions. 2. It uses pcl internals to handle type checking instead of CLOS functions. Simply adding (IN-PACKAGE 'CLOS :NICKNAMES '(PCL)) to the system file doesn't solve the problem. Does anyone have a version of EW which compiles correctly on a CLOS, CLX, and CLtL2 version of Common Lisp? David Loewenstern AT&T Bell Laboratories 14B-253 Whippany, NJ 07981 email: davel@whutt.att.com || whutt!davel at&t: 201-386-6516 To: express-windows@atc cc: aressler@oiscola.columbia.ncr.com.ARPANET Subject: installing expressing windows (problem) Date: Mon, 21 May 90 14:35 PDT From: poesio@cs.rochester.edu Hi! I am trying to install express windows for lucid 3.0, on a Sun SPARC, and the window system is X11 (I can grab the exact version if relevant). The problem I have is the following: I have compiled the files OK, loaded them, and executed (clear-all). At this point, the following error message appears: > (clear-all) >>Error: X-Error: NAME-ERROR in request 121 (last request was 158) Code 45.0 [O penFont] XLIB::X-ERROR: Required arg 0 (CONDITION): XLIB:NAME-ERROR Rest arg 1 (KEYARGS): (:DISPLAY # :ERROR-KEY XLIB:NAME-ERROR :MAJ OR 45 :MINOR 0 :SEQUENCE 121 ...) :A 0: Abort to Lisp Top Level this is the status of the stack: -> :n XLIB::REPORT-ERROR: Required arg 0 (DISPLAY): # Required arg 1 (EVENT): #S(XLIB::REPLY-BUFFER SIZE 4096 IBUF8 #) -> :n XLIB::WAIT-FOR-REPLY: Required arg 0 (DISPLAY): # Required arg 1 (EXPECTED-SIZE): NIL -> :n XLIB::QUERY-FONT: Required arg 0 (FONT): # -> :n FONT-HEIGHT: Required arg 0 (FONT): # -> :n PCL::|(METHOD EXPRESS-WINDOWS:SET-WINDOW-STYLE (EXPRESS-WINDOWS:WINDOW T))|: Required arg 0 (WINDOW): # Required arg 1 (NEW-STYLE): (:FIX :ROMAN :NORMAL) Optional arg 2 (SET-LINE-HEIGHT): T It seems, of course, that the problem occurs when EXPRESS-WINDOWS:SET-WINDOW-STYLE tries to get the height of the font -adobe-courier-medium-r-normal--12-120-75-75-m-70-iso8859-1 (which is what XLIB:GET-FONT-FROM-STYLE returns for the style (:FIX :ROMAN :NORMAL)) using the macro RECOMPUTE-LINE-HEIGHT. It may help to know that in order to get this far I had to make the following changes to the files I ftp-ed from uunet.uu.net: 1) change the suffix `lbin' to `sbin' (for the SPARC compiler) in LOAD-EW and the value of *Binary-File-Type* as follows: ;;(defvar *Binary-File-Type* #+Excl "fasl" #+lucid "lbin" #+symbolics "BIN") ;; OLD (defvar *Binary-File-Type* #+Excl "fasl" #+lucid "sbin" #+symbolics "BIN") ;; NEW 2) change the value of *Default-Host* in x-interface.lisp from "Electro" to "". Thanks Massimo Poesio University of Rochester Computer Science Department Rochester, NY 14627 email: poesio@cs.rochester.edu phone: (716) 275-5605 Date: Mon, 21 May 90 15:03 PDT From: Stephen L. Nicoud Subject: installing expressing windows (problem) To: poesio@cs.rochester.edu.ARPANET cc: express-windows@atc, aressler@oiscola.columbia.ncr.com.ARPANET In-Reply-To: <9005212135.AA09153@granite.cs.rochester.edu> Date: Mon, 21 May 90 17:35:51 -0400 From: poesio@cs.rochester.edu [...] At this point, the following error message appears: > (clear-all) >>Error: X-Error: NAME-ERROR in request 121 (last request was 158) Code 45.0 [O penFont] [...] This is a known bug. The solution is to correct the misspelling of the 'dec-adobe-...' fonts to '-adobe-...' in the file fonts.lisp. Steve -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences Date: Tue, 22 May 90 05:00 PDT From: Peter Magee Subject: EW under Apollo Domain Lisp To: davel%whutt.att.com@RIVERSIDE.SCRC.SYMBOLICS, express-windows%atc.boeing.com@RIVERSIDE.SCRC.SYMBOLICS Fcc: SKYWALKER:>PETER>outgoing.mail.newest In-Reply-To: <9005220150.AA22260@atc.boeing.com> Date: Mon, 21 May 90 14:28 EDT From: davel@whutt.att.com We are attempting to compile EW under Apollo's Domain/Common Lisp (a product of Lucid) with CLOS and CLX. We have been hung up on the file io-functions.lisp because: 1. It appears to redefine standard lisp functions, and *then* call the function (setup-lisp-functions) which is designed to take care of saving away the old version of the functions. 2. It uses pcl internals to handle type checking instead of CLOS functions. Simply adding (IN-PACKAGE 'CLOS :NICKNAMES '(PCL)) to the system file doesn't solve the problem. The problem is in the definition of type-of. PCL appears to not allow the use of type-of to find the type of a class so EW does one of it's little substitution tricks to redirect this call to the right PCL call. (typep pcl::standard-class-p ) Unfortunatley this function does not exist in CLOS. Fortunatley CLOS can use type-of to return the type of a class. Use #-clos to switch out the defintion of type-of in type.lisp, the references to type-of in *functions-shadowed* in io-functions.lisp and *common-lisp-functins-shadowed* [or something] in symbols.lisp. This will then prevent shadowing type-of in the package EW when CLOS is loaded. This assumes that no one has :clos in their *features* unless they really have CLOS and not just PCL. Does anyone have a version of EW which compiles correctly on a CLOS, CLX, and CLtL2 version of Common Lisp? David Loewenstern AT&T Bell Laboratories 14B-253 Whippany, NJ 07981 email: davel@whutt.att.com || whutt!davel at&t: 201-386-6516 Peter T. Magee 44 71 356 3524 Subject: Re: EW under Apollo Domain Lisp To: express-windows Date: Tue, 22 May 90 10:36 PDT From: Andrew Ressler In-Reply-To: <9005220150.AA22260@atc.boeing.com>; from "whutt.att.com!davel" at May 21, 90 2:28 pm X-Mailer: Elm [version 2.1 PL1] > > We are attempting to compile EW under Apollo's Domain/Common Lisp > (a product of Lucid) with CLOS and CLX. We have been hung up on the > file io-functions.lisp because: > 1. It appears to redefine standard lisp functions, and *then* call > the function (setup-lisp-functions) which is designed to take care of > saving away the old version of the functions. io-functions is used to allow standard CL io functions to interface with the presentation substrate. That way functions like PRINT will work inside of functions like WITH-OUTPUT-AS-PRESENTATION. Since I didn't have access to the internals of such functions as PRINT I needed to redefine them so that they would handle the presentations as well as perform their appropriate behavior. Unfortunately, if there is an interaction with the system's primitives they tend to crash horribly. The best thing to debug is to change the file so that only one function is defined at a time until you see which causes the problem. > 2. It uses pcl internals to handle type checking instead of CLOS > functions. Simply adding (IN-PACKAGE 'CLOS :NICKNAMES '(PCL)) > to the system file doesn't solve the problem. It shouldn't be to hard to find out which is the proper CLOS function. Unfortunately, I'm not in front of the code this week and can't tell you. However, fixing this may solve all your problems. Hope this helps. Andrew L. Ressler 301-643-4526 Subject: Re: EW on MACII? To: express-windows Date: Tue, 22 May 90 10:39 PDT From: Andrew Ressler In-Reply-To: <19900516170216.2.ARTHUR@TOKOLOSHE.tamu.edu>; from "Arthur Keen" at May 16, 90 12:02 (noon) X-Mailer: Elm [version 2.1 PL1] > > Just out of curiosity, what would it take to run EW on a MAC II (Allegro.) > I have been told that the missing ingredient is X-windows. > In Theory you would need only a working X and CLX with your Lisp. Andrew L. Ressler 301-643-4526 Subject: Re: EW under Apollo Domain Lisp To: express-windows Date: Tue, 22 May 90 13:52 PDT From: Andrew Ressler In-Reply-To: <19900522120046.1.PETER@skywalker.ENTERPRISE.dialnet.symbolics.com>; from "Peter Magee" at May 22, 90 12:00 (noon) X-Mailer: Elm [version 2.1 PL1] > The problem is in the definition of type-of. PCL appears to not allow > the use of type-of to find the type of a class so EW does one of > it's little substitution tricks to redirect this call to the right PCL > call. (typep pcl::standard-class-p ) Unfortunatley this function > does not exist in CLOS. Fortunatley CLOS can use type-of to return the > type of a class. Use #-clos to switch out the defintion of type-of in > type.lisp, the references to type-of in *functions-shadowed* in > io-functions.lisp and *common-lisp-functins-shadowed* [or something] in > symbols.lisp. This will then prevent shadowing type-of in the package > EW when CLOS is loaded. > When you start fixing up your calls with respect to type-of, pay careful attention to the code that does type matching for presentations. For instance, subtypep may do different things as well. One problem I had was that the behavior of subtypep was not consistent between Lucid, Franz, and Symbolics. If your lisp handles types correctly you may be able to eliminate several hacks like the above mentioned hack. Andrew L. Ressler 301-643-4526 From: Ashok Kumar Kamshatti Subject: Help needed in compiling express-window files! To: express-windows@atc Date: Tue, 22 May 90 18:58 PDT cc: express-windows-request@atc X-Mailer: ELM [version 2.3 PL0] I copied Express Windows software from the public directory of trix.ai.mit.edu and tried compiling the files using Allegro CL 3.1.4. I started getting different error messages and it was not able to compile some of the files [lisp-window.lisp, file- manager.lisp, system.lisp, processes.lisp, demos.lisp, menu- definer.lisp, sym-comp.lisp, clx-hacks.lisp]. Could you help me in compiling the express-window files? Here is the dribble-bug output. rootkak# cl -qq Allegro CL 3.1.4 [Sun3] (12/1/89) Copyright (C) 1985-1989, Franz Inc., Berkeley, CA, USA (dribble "franz.bugs") dribbling to file "/users/ew/code/franz.bugs" LISP-IMPLEMENTATION-TYPE: Allegro CL LISP-IMPLEMENTATION-VERSION: 3.1.4 [Sun3] (12/1/89) MACHINE-TYPE: Sun3 MACHINE-VERSION: SOFTWARE-TYPE: SunOS SOFTWARE-VERSION: SHORT-SITE-NAME: surya *features*: (:BIG-ENDIAN :GSGC :M68881 :M68020 :ALLEGRO-V3.1 :FRANZ-INC :EXCL :ALLEGRO :COMMON-LISP :CONFORMING-IEEE :IEEE :FLAVORS :SUN :M68K :SUN3 :UNIX :MULTIPROCESSING :XLIB :GC-CURSOR :CW-X) *modules*: ("XVARS" "XCW" "CLX" "CLXEXCLDEP" "ADVISE" "TRACE" "MDPROC" "PROCESS" "FOREIGN" "FOREIGN-FUNCTIONS" "SA68881") PATCH::*XCW-PATCHES*: (16 . "scrolling set clipping region correctly") (15 . "programmatic iconization with old wm's") (14 . "stop-default-handler race condition") (13 . "install font error on bad server name") (12 . "restart icons and textures") (11 . "get-box-region allows full size") (10 . "documentation-print in menus can pop-up *p-w*") (9 . "rubout-handler ok when stream closed") (8 . "default deselect method") (7 . "sequential restores ok") (6 . "menus handle exposure events") (5 . "scrollbar popup and border sanity") (4 . "wm-shrink-method") (3 . "clip lines correctly") (2 . "make k-c-w finish correctly") (1 . "window creation stacking order") trace: $Header: trace.cl,v 1.35 89/07/22 18:56:24 layer Rel $ mdproc: $Header: mdproc.cl,v 1.20 89/07/22 18:56:29 layer Rel $ process: $Header: process.cl,v 1.44 89/08/17 18:45:20 layer Rel $ foreign: $Header: foreign.cl,v 1.49 89/08/28 14:45:00 layer Rel $ NIL (use-package :cw) T (require :pcl) ; Fast loading /usr/local/lib/cl/code/pcl.fasl. T (load "../load-ew.lisp") ; Loading /users/ew/load-ew.lisp. Load CLX?n Compile CLX?n Load CLOS?n Compile CLOS?n ; Loading /users/ew/code/system.lisp. ; Loading /users/ew/code/symbols.lisp. Load Express Windows?n Compile Express Windows?y ; Loading /users/ew/code/defsystem.lisp. ; Fast loading /users/ew/code/clx-hacks.fasl. ; Fast loading /users/ew/code/meter.fasl. ; Fast loading /users/ew/code/cl-clos-macros.fasl. ; Fast loading /users/ew/code/fixnum-macros.fasl. ; Fast loading /users/ew/code/x-macros-interface.fasl. ; Fast loading /users/ew/code/fonts.fasl. ; Fast loading /users/ew/code/macros.fasl. ; Fast loading /users/ew/code/x-interface.fasl. ; Fast loading /users/ew/code/read-internal.fasl. ; Fast loading /users/ew/code/quad-trees.fasl. ; Fast loading /users/ew/code/base-presentations.fasl. ; Fast loading /users/ew/code/type.fasl. ; Fast loading /users/ew/code/scrolling.fasl. ; Fast loading /users/ew/code/graphic-primitives.fasl. ; Fast loading /users/ew/code/io-functions.fasl. ; Fast loading /users/ew/code/command-processor.fasl. ; Fast loading /users/ew/code/misc.fasl. ; Fast loading /users/ew/code/memo.fasl. ; Fast loading /users/ew/code/table.fasl. ; Fast loading /users/ew/code/query.fasl. ; Fast loading /users/ew/code/completion.fasl. ; Fast loading /users/ew/code/frames.fasl. ; Fast loading /users/ew/code/input-editor.fasl. ; Fast loading /users/ew/code/proprietary-presentation-types.fasl. ; Fast loading /users/ew/code/presentation-types.fasl. ; --- Compiling file /users/ew/code/lisp-window.lisp --- Error: Invalid initialization argument :NAME for class PROGRAM-FRAMEWORK [changing package from "USER" to "EXPRESS-WINDOWS"] [1] :cl file-manager.lisp ; --- Compiling file /users/ew/code/file-manager.lisp --- ; Compiling MAKE-NODE ; Compiling NODE-P ; Compiling MAKE-DIRECTORY-NODE ; Compiling DIRECTORY-NODE-P ; Compiling PRINT-DIRECTORY-NODE ; Compiling MAKE-FILE-NODE ; Compiling FILE-NODE-P ; Compiling PRINT-FILE-NODE ; Compiling |printer-DIRECTORY-NODE| ; Compiling |printer-FILE-NODE| Error: Invalid initialization argument :NAME for class EXPRESS-WINDOWS::PROGRAM-FRAMEWORK [changing package from "EXPRESS-WINDOWS" to "FILE-MANAGER"] [2] :cl system.lisp ; Fast loading /users/ew/code/system.fasl. ; Loading /users/ew/code/symbols.lisp. [2] :cl process.lisp Error: couldn't find source file: process.lisp [3] :cl processes.lisp ; --- Compiling file /users/ew/code/processes.lisp --- Error: Invalid initialization argument :NAME for class EXPRESS-WINDOWS::PROGRAM-FRAMEWORK [changing package from "FILE-MANAGER" to "PROCESS-MANAGER"] [4] :cl demos.lisp ; --- Compiling file /users/ew/code/demos.lisp --- ; Compiling DEFINE-DEMO ; Compiling WAIT-NEXT-STEP ; Compiling DEMO-LINES ; Compiling DEMO-LIST-OF-NUMBERS ; Compiling DEMO-LIST-OF-NUMBERS-2 ; Compiling DEMO-MAKE-TABLE-MULTIPLY ; Compiling DEMO-MAKE-TABLE-SIMPLE-MULTIPLY ; Compiling DEMO-MEMOIZED-MAKE-TABLE-ROW-CHANGES ; Compiling DEMO-MENU-CHOOSE ; Compiling DEMO-MENU-CHOOSE-WITH-GRAPHICS ; Compiling DEMO-MEMOIZED-MAKE-TABLE-FONT-CHANGES ; Compiling DEMO-SIMPLE-TABLE-WITH-BORDERS ; Compiling DEMO-MAKE-TABLE-AFTER-TABLE ; Compiling DEMO-DOUBLE-TABLE ; Compiling DEMO-DISPLAYS-AND-QUERIES ; Compiling |translator-STRING-TO-INTEGER| Warning: variable IGNORE is never used ; Compiling |translator-STRING-TO-INTEGER-test| Warning: variable IGNORE is never used ; Compiling DEMO-QUERYING-VALUES ; Compiling DEMO-TRACKING-MOUSE ; Compiling RUN-DEMOS Error: Invalid initialization argument :NAME for class PROGRAM-FRAMEWORK [changing package from "PROCESS-MANAGER" to "EXPRESS-WINDOWS"] [5] :cl sym-comp.lisp ; Fast loading /users/ew/code/sym-comp.fasl. [5] :cl clx.hacks.lisp Error: couldn't find source file: clx.hacks.lisp [6] :cl clx-hacks.lisp ; Fast loading /users/ew/code/clx-hacks.fasl. [6] (dribble) Thanx -- Ashok Kumar Kamshatti University of Hawaii at Manoa, EE Dept. (808) 948 7249 Email :: ashok@wiliki.eng.hawaii.edu Date: Tue, 22 May 90 19:26 PDT From: Stephen L. Nicoud Subject: Help needed in compiling express-window files! To: Ashok Kumar Kamshatti cc: express-windows@atc In-Reply-To: <9005230158.AA25731@atc.boeing.com> [Removed express-windows-request@atc.boeing.com] Date: Tue, 22 May 90 15:58:28 HST From: Ashok Kumar Kamshatti I copied Express Windows software from the public directory of trix.ai.mit.edu and tried compiling the files using Allegro CL 3.1.4. I started getting different error messages and it was not able to compile some of the files [lisp-window.lisp, file- manager.lisp, system.lisp, processes.lisp, demos.lisp, menu- definer.lisp, sym-comp.lisp, clx-hacks.lisp]. [...] Error: Invalid initialization argument :NAME for class PROGRAM-FRAMEWORK [...] All of these "Invalid initialization argument" errors are the result of using a version of PCL newer than AAAI PCL (AAAI PCL (August 1988) being the one packaged in the Express Windows files). You will need to perform several modifications to the Express Windows code in order to get it to run in this newer version of PCL (Victoria Day (May 1989), in your case, being the version of PCL supplied with Franz's Allegro CL). See the attached message which recently appeared on express-windows. Steve -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences ------- Forwarded Message ------- Date: Fri, 11 May 90 16:19 PDT From: Stephen L. Nicoud Subject: EW with May Day PCL To: express-windows@atc.boeing.com The version of PCL provided with EW is the AAAI Day version (August 1988). Since we have been using Victoria Day, Rainy Day, and now, May Day PCL, we knew we were gonna have to convert EW for those versions. Here's a (hopefully somewhat complete and accurate) list of changes we made that make EW compatible with May Day PCL (should be fine with Rainy Day, too; don't know about Victoria Day, though). 1. Gave ":initarg"s to all slots in all the defclass forms. The :initarg should be a symbol in the keyword package with the same as the name of the slot. 2. Removed use of :accessor-prefix in defclass forms, installing ":accessor" for every slot in every class. The :accessor should be a symbol with the name of the class prepended to the name of the slot (with an intervening hyphen). 3. In frames.lisp, define-program-framework should use :initarg and :accessor now. So, replace #+EW-CLOS (defclass ,name (,inherit-from) ,(mapcar #'(lambda (variable) (if (consp variable) `(,(first variable) :INITFORM ,(second variable)) variable)) state-variables) (:accessor-prefix ,(intern (lisp-format NIL "~A-" name)))) with #+EW-CLOS (defclass ,name (,inherit-from) ,(mapcar #'(lambda (variable) (if (consp variable) `(,(first variable) :accessor ,(intern (lisp:format NIL "~A-~A" name (first variable)) (symbol-package name)) :initarg ,(intern (string (first variable)) :keyword) :INITFORM ,(second variable)) variable)) state-variables)) 4. Removed the &rest arguments in print-object methods in frames.lisp and macros.lisp (and removed their corresponding (declare (ignore ignore)) statements). 5. Added this form at the end of system.lisp in order for macros.lisp to compile properly. (when (boundp 'pcl::*defclass-times*) (pushnew 'compile pcl::*defclass-times*) (pushnew 'compile pcl::*defmethod-times*)) 6. In type.lisp, lisp-window.lisp, presentation-types.lisp, flavors-to-pcl.lisp: change PCL::IWMC-CLASS-P to PCL::STANDARD-CLASS-P. 7. In lisp-window.lisp, calls to define-lisp-command with keyword args broke lucid3.0 (">>Trap: Bus error"). This is a PCL problem, I think. What I did was to add an "&rest ignore" to the arglist if it has &key in it. Basically, it just looks for &key and splices in "&rest ignore" if it finds it there. While it seems to be only a PCL problem, it shouldn't hurt any other CLOS's to do this (I hope). So, in frames.lisp replace: (defun get-argument-list (args) (let ((args (mapcar #'(lambda (arg) (if (symbolp arg) arg (list (first arg) (getf (cddr arg) :DEFAULT)))) args))) (when args (cons '&OPTIONAL args)))) with: (defun get-argument-list (args) (let ((args (mapcar #'(lambda (arg) (if (symbolp arg) arg (list (first arg) (getf (cddr arg) :DEFAULT)))) args))) (let ((key-position (position '&key args))) (when key-position (cond ((zerop key-position) (setq args (append '(&rest ignore) args))) (t (let* ((list (append '(&rest ignore) (nthcdr key-position args)))) (setq args (rplacd (nthcdr (%1- key-position) args) list)))))) (when args (cons '&OPTIONAL args))))) -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences ------- End of Forwarded Message ------- From: Ashok Kumar Kamshatti Subject: Problem in running express-windows !! To: express-windows@atc Date: Fri, 25 May 90 14:13 PDT cc: express-windows-request@atc X-Mailer: ELM [version 2.3 PL0] I am having problem in running express-windows. It is saying undefined variable "MAKE-WINDOW". Could you Please help me ?? I am sending the dribble-bug output. dribbling to file "/usr1/users/ashok/ew.fail" LISP-IMPLEMENTATION-TYPE: Allegro CL LISP-IMPLEMENTATION-VERSION: 3.1.4 [Sun3] (12/1/89) MACHINE-TYPE: Sun3 MACHINE-VERSION: SOFTWARE-TYPE: SunOS SOFTWARE-VERSION: SHORT-SITE-NAME: surya *features*: (:BIG-ENDIAN :GSGC :M68881 :M68020 :ALLEGRO-V3.1 :FRANZ-INC :EXCL :ALLEGRO :COMMON-LISP :CONFORMING-IEEE :IEEE :FLAVORS :SUN :M68K :SUN3 :UNIX :MULTIPROCESSING :XLIB :GC-CURSOR :CW-X) *modules*: ("XVARS" "XCW" "CLX" "CLXEXCLDEP" "ADVISE" "TRACE" "MDPROC" "PROCESS" "FOREIGN" "FOREIGN-FUNCTIONS" "SA68881") PATCH::*XCW-PATCHES*: (16 . "scrolling set clipping region correctly") (15 . "programmatic iconization with old wm's") (14 . "stop-default-handler race condition") (13 . "install font error on bad server name") (12 . "restart icons and textures") (11 . "get-box-region allows full size") (10 . "documentation-print in menus can pop-up *p-w*") (9 . "rubout-handler ok when stream closed") (8 . "default deselect method") (7 . "sequential restores ok") (6 . "menus handle exposure events") (5 . "scrollbar popup and border sanity") (4 . "wm-shrink-method") (3 . "clip lines correctly") (2 . "make k-c-w finish correctly") (1 . "window creation stacking order") trace: $Header: trace.cl,v 1.35 89/07/22 18:56:24 layer Rel $ mdproc: $Header: mdproc.cl,v 1.20 89/07/22 18:56:29 layer Rel $ process: $Header: process.cl,v 1.44 89/08/17 18:45:20 layer Rel $ foreign: $Header: foreign.cl,v 1.49 89/08/28 14:45:00 layer Rel $ NIL (use-package :cw) T (initialize-common-windows :gc-cursor 't) ; Fast loading /usr/local/lib/cl/code/sigio.fasl. ; Fast loading /usr/local/lib/cl/code/cstructs.fasl. T (load "/users/ew/clos/pcl.fasl") ; Fast loading /users/ew/clos/pcl.fasl. T (load "/usr/local/lib/cl/code/clx.fasl") ; Fast loading /usr/local/lib/cl/code/clx.fasl. ; Fast loading /usr/local/lib/cl/code/defsys.fasl. Error: opening "/users/ew/clx/socket.o" resulted in error: Permission denied [changing package from "USER" to "XLIB"] [1] :pop [changing package from "XLIB" to "USER"] (load "/usr/local/lib/cl/code/clx.fasl") ; Fast loading /usr/local/lib/cl/code/clx.fasl. ; Foreign loading /users/ew/clx/socket.o. ; Foreign loading /users/ew/clx/excldep.o. Warning: No address found for foreign function C-READ-BYTES-INTERRUPTIBLE T (load "/users/ew/load-ew.lisp") ; Loading /users/ew/load-ew.lisp. Load CLX?n Compile CLX?n Load CLOS?n Compile CLOS?n ; Loading /users/ew/code/system.lisp. ; Loading /users/ew/code/symbols.lisp. Load Express Windows?n Compile Express Windows?y ; Loading /users/ew/code/defsystem.lisp. ; Fast loading /users/ew/code/clx-hacks.fasl. ; Fast loading /users/ew/code/meter.fasl. ; Fast loading /users/ew/code/cl-clos-macros.fasl. ; Fast loading /users/ew/code/fixnum-macros.fasl. ; Fast loading /users/ew/code/x-macros-interface.fasl. ; Fast loading /users/ew/code/fonts.fasl. ; Fast loading /users/ew/code/macros.fasl. ; Fast loading /users/ew/code/x-interface.fasl. ; Fast loading /users/ew/code/read-internal.fasl. ; Fast loading /users/ew/code/quad-trees.fasl. ; Fast loading /users/ew/code/base-presentations.fasl. ; Fast loading /users/ew/code/type.fasl. ; Fast loading /users/ew/code/scrolling.fasl. ; Fast loading /users/ew/code/graphic-primitives.fasl. ; Fast loading /users/ew/code/io-functions.fasl. ; Fast loading /users/ew/code/command-processor.fasl. ; Fast loading /users/ew/code/misc.fasl. ; Fast loading /users/ew/code/memo.fasl. ; Fast loading /users/ew/code/table.fasl. ; Fast loading /users/ew/code/query.fasl. ; Fast loading /users/ew/code/completion.fasl. ; Fast loading /users/ew/code/frames.fasl. ; Fast loading /users/ew/code/input-editor.fasl. ; Fast loading /users/ew/code/proprietary-presentation-types.fasl. ; Fast loading /users/ew/code/presentation-types.fasl. ; Fast loading /users/ew/code/lisp-window.fasl. ; Fast loading /users/ew/code/demos.fasl. ; Fast loading /users/ew/code/sym-comp.fasl. ; Fast loading /users/ew/code/time.fasl. ; Fast loading /users/ew/code/lisp-machine-lisp-compatible.fasl. ; Fast loading /users/ew/code/file-manager.fasl. ; Fast loading /users/ew/code/menu-definer.fasl. ; Fast loading /users/ew/code/processes.fasl. T (defvar *My-Window* NIL) *MY-WINDOW* (defun make-my-window () (let ((window-height 250) (window-width 250) (left-edge 250) (top-edge 250)) (setq *My-Window* (make-window 'WINDOW :BORDERS 1 :LEFT left-edge :TOP top-edge :HEIGHT window-height :WIDTH window-width :SUPERIOR *Ultimate-Root-Window*)) (xlib:set-standard-properties (window-real-window *My-Window*) ;;;type XLIB:WINDOW :normal-hints (xlib:make-wm-size-hints :WIDTH window-width :min-WIDTH window-width :height window-height :min-height window-height :X left-edge :Y top-edge)) (expose-window *My-Window*))) MAKE-MY-WINDOW (make-my-window) Error: attempt to call `MAKE-WINDOW' which is an undefined function. Restart actions (select using :continue): 0: prompt for a new function, instead of `MAKE-WINDOW'. [1c] (in-package 'simulator :use 'lisp) # [1c] (import '(fpcl:defmethod fpcl:defflavor pcl:make-instance) 'simulator) Error: Package "FPCL" not found. Restart actions (select using :continue): 0: prompt for a new function, instead of `MAKE-WINDOW'. [2] :pop Previous error: attempt to call `MAKE-WINDOW' which is an undefined function. If continued, prompt for a new function, instead of `MAKE-WINDOW'. [1c] (import '(pcl:make-instance) 'simulator) T [1c] (import '(ew::formatting-table ew::formatting-row ew::formatting-cell ew:define-presentation-to-command-translator ew:accept ew:present ew:boolean ew:define-presentation-type ew:define-presentation-translator ew:self ew:send ) 'simulator) T [1c] (defun make-my-window () (let ((window-height 250) (window-width 250) (left-edge 250) (top-edge 250)) (setq *My-Window* (make-window 'WINDOW :BORDERS 1 :LEFT left-edge :TOP top-edge :HEIGHT window-height :WIDTH window-width :SUPERIOR *Ultimate-Root-Window*)) (xlib:set-standard-properties (window-real-window *My-Window*) ;;;type XLIB:WINDOW :normal-hints (xlib:make-wm-size-hints :WIDTH window-width :min-WIDTH window-width :height window-height :min-height window-height :X left-edge :Y top-edge)) (expose-window *My-Window*))) MAKE-MY-WINDOW [1c] (make-my-window) Error: attempt to call `MAKE-WINDOW' which is an undefined function. Restart actions (select using :continue): 0: prompt for a new function, instead of `MAKE-WINDOW'. 1: prompt for a new function, instead of `MAKE-WINDOW'. [2c] (dribble) To: Ashok Kumar Kamshatti cc: express-windows@atc Reply-To: todd.kaufmann@NL.CS.CMU.EDU Subject: Re: Problem in running express-windows !! In-Reply-To: Your message of Fri, 25 May 90 11:13:01 -1000. <9005252113.AA16046@atc.boeing.com> Date: Fri, 25 May 90 15:07 PDT From: Todd.Kaufmann@NL.CS.CMU.EDU You missed the package for MAKE-WINDOW. (find-all-symbols "MAKE-WINDOW") will help you find it. I use find-all-symbols all the time when I'm stumbling through packages.. try this alias for your allegro: (tpl:alias ("fas" :string) (sym-name) (let ((finds (find-all-symbols (string-upcase sym-name)))) (format t "~s~%" finds) ;; and return value, so accessible by * at top-level. finds )) and then you'll see :fas make-window (XLIB::MAKE-WINDOW EXPRESS-WINDOWS:MAKE-WINDOW) T good luck, -todd From: Ashok Kumar Kamshatti Subject: Problem in running express-windows !! To: express-windows@atc Date: Fri, 25 May 90 17:43 PDT cc: express-windows-request@atc X-Mailer: ELM [version 2.3 PL0] Question 1: ----------- Still having problems in making the window. Here is the dribble output file. dribbling to file "/usr1/users/ashok/ew.fail" LISP-IMPLEMENTATION-TYPE: Allegro CL LISP-IMPLEMENTATION-VERSION: 3.1.4 [Sun3] (12/1/89) MACHINE-TYPE: Sun3 MACHINE-VERSION: SOFTWARE-TYPE: SunOS SOFTWARE-VERSION: SHORT-SITE-NAME: surya *features*: (:BIG-ENDIAN :GSGC :M68881 :M68020 :ALLEGRO-V3.1 :FRANZ-INC :EXCL :ALLEGRO :COMMON-LISP :CONFORMING-IEEE :IEEE :FLAVORS :SUN :M68K :SUN3 :UNIX :MULTIPROCESSING :XLIB :GC-CURSOR :CW-X) *modules*: ("XVARS" "XCW" "CLX" "CLXEXCLDEP" "ADVISE" "TRACE" "MDPROC" "PROCESS" "FOREIGN" "FOREIGN-FUNCTIONS" "SA68881") PATCH::*XCW-PATCHES*: (16 . "scrolling set clipping region correctly") (15 . "programmatic iconization with old wm's") (14 . "stop-default-handler race condition") (13 . "install font error on bad server name") (12 . "restart icons and textures") (11 . "get-box-region allows full size") (10 . "documentation-print in menus can pop-up *p-w*") (9 . "rubout-handler ok when stream closed") (8 . "default deselect method") (7 . "sequential restores ok") (6 . "menus handle exposure events") (5 . "scrollbar popup and border sanity") (4 . "wm-shrink-method") (3 . "clip lines correctly") (2 . "make k-c-w finish correctly") (1 . "window creation stacking order") trace: $Header: trace.cl,v 1.35 89/07/22 18:56:24 layer Rel $ mdproc: $Header: mdproc.cl,v 1.20 89/07/22 18:56:29 layer Rel $ process: $Header: process.cl,v 1.44 89/08/17 18:45:20 layer Rel $ foreign: $Header: foreign.cl,v 1.49 89/08/28 14:45:00 layer Rel $ NIL (use-package :cw) T (initialize-common-windows :gc-cursor 't) ; Fast loading /usr/local/lib/cl/code/sigio.fasl. ; Fast loading /usr/local/lib/cl/code/cstructs.fasl. T (load "/users/ew/clos/pcl.fasl") ; Fast loading /users/ew/clos/pcl.fasl. T (load "/usr/local/lib/cl/code/clx.fasl") ; Fast loading /usr/local/lib/cl/code/clx.fasl. ; Fast loading /usr/local/lib/cl/code/defsys.fasl. ; Foreign loading /users/ew/clx/socket.o. ; Foreign loading /users/ew/clx/excldep.o. Warning: No address found for foreign function C-READ-BYTES-INTERRUPTIBLE T (load "/users/ew/load-ew.lisp") ; Loading /users/ew/load-ew.lisp. Load CLX? Type "y" for yes or "n" for no. Load CLX?n Compile CLX?n Load CLOS?n Compile CLOS?n ; Loading /users/ew/code/system.lisp. ; Loading /users/ew/code/symbols.lisp. Load Express Windows?n Compile Express Windows?y ; Loading /users/ew/code/defsystem.lisp. ; Fast loading /users/ew/code/clx-hacks.fasl. ; Fast loading /users/ew/code/meter.fasl. ; Fast loading /users/ew/code/cl-clos-macros.fasl. ; Fast loading /users/ew/code/fixnum-macros.fasl. ; Fast loading /users/ew/code/x-macros-interface.fasl. ; Fast loading /users/ew/code/fonts.fasl. ; Fast loading /users/ew/code/macros.fasl. ; Fast loading /users/ew/code/x-interface.fasl. ; Fast loading /users/ew/code/read-internal.fasl. ; Fast loading /users/ew/code/quad-trees.fasl. ; Fast loading /users/ew/code/base-presentations.fasl. ; Fast loading /users/ew/code/type.fasl. ; Fast loading /users/ew/code/scrolling.fasl. ; Fast loading /users/ew/code/graphic-primitives.fasl. ; Fast loading /users/ew/code/io-functions.fasl. ; Fast loading /users/ew/code/command-processor.fasl. ; Fast loading /users/ew/code/misc.fasl. ; Fast loading /users/ew/code/memo.fasl. ; Fast loading /users/ew/code/table.fasl. ; Fast loading /users/ew/code/query.fasl. ; Fast loading /users/ew/code/completion.fasl. ; Fast loading /users/ew/code/frames.fasl. ; Fast loading /users/ew/code/input-editor.fasl. ; Fast loading /users/ew/code/proprietary-presentation-types.fasl. ; Fast loading /users/ew/code/presentation-types.fasl. ; Fast loading /users/ew/code/lisp-window.fasl. ; Fast loading /users/ew/code/demos.fasl. ; Fast loading /users/ew/code/sym-comp.fasl. ; Fast loading /users/ew/code/time.fasl. ; Fast loading /users/ew/code/lisp-machine-lisp-compatible.fasl. ; Fast loading /users/ew/code/file-manager.fasl. ; Fast loading /users/ew/code/menu-definer.fasl. ; Fast loading /users/ew/code/processes.fasl. T (in-package 'simulator :use 'lisp) # (import '(pcl:make-instance) 'simulator) T (import '(ew::formatting-table ew::formatting-row ew::formatting-cell ew:define-presentation-to-command-translator ew:accept ew:present ew:boolean ew:define-presentation-type ew:define-presentation-translator ew:self ew:send ) 'simulator) T (in-package 'ew) # (find-all-symbols "MAKE-WINDOW") (XLIB::MAKE-WINDOW MAKE-WINDOW) (tpl:alias ("fas" :string) (sym-name) (let ((finds (find-all-symbols (string-upcase sym-name)))) (format t "~s~%" finds) ;; and return value, so accessible by * at top-level. finds )) :fas make-window (XLIB::MAKE-WINDOW MAKE-WINDOW) :fas *root-window* (*ROOT-WINDOW* COMMON-WINDOWS:*ROOT-WINDOW*) :fas initialize-window-system (INITIALIZE-WINDOW-SYSTEM) (setq *My-Window* (make-window 'WINDOW :BORDERS 1 :LEFT 250 :TOP 250 :HEIGHT 250 :WIDTH 250 )) Error: Attempt to take the value of the unbound symbol *ROOT-WINDOW* [1] (defvar *my-window* nil) *MY-WINDOW* [1] (defvar *root-window* nil) *ROOT-WINDOW* [1] (setq *My-Window* (make-window 'WINDOW :BORDERS 1 :LEFT 250 :TOP 250 :HEIGHT 250 :WIDTH 250 )) Error: No matching method for the generic-function #, when called with arguments (NIL). [2] :fas window-left (WINDOW-LEFT) [2] (dribble) QUESTION 2 :: ------------ Is it possible to make a dumplisp file after loading the files of express-windows ? If so, could you tell me how ? It was getting stuck when I tried dumping into a file. The steps I followed after starting the LISP were, 1. (use-package :cw) 2. (initialize-common-windows :gc-cursor 't) 3. (load "pcl.fasl") 4. (load "clx.fasl") 5. (load "load-ew.lisp") 6. (require :xcw) 7. (excl:dumplisp :name "ewcl" :checkpoint t :read-init-file t) Thanx for the Help. Ashok Kumar Kamshatti 2540 Dole street, #493 University of Hawaii at Manoa, EE Dept Honolulu, HI 96822 (808) 948-7249 Email :: ashok@wiliki.eng.hawaii.edu To: Ashok Kumar Kamshatti cc: express-windows@atc Reply-To: todd.kaufmann@NL.CS.CMU.EDU Subject: Making a simple window, and dumplisp in allegro (was Re: Problem in running express-windows !! ) In-Reply-To: Your message of Fri, 25 May 90 14:43:41 -1000. <9005260043.AA20032@atc.boeing.com> Date: Sun, 27 May 90 13:25 PDT From: Todd.Kaufmann@NL.CS.CMU.EDU You can't make a window until you call (initialize-window-system). Have you tried running the demos, by doing :pa ew (run-program 'lisp-listener) ; see frames.lisp The mouse window should show you what the buttons do. Click right to get a menu, or type SM, which is an abbreviation for System Menu. You don't need to load the common windows at all, just CLX. I don't think this should cause any problems; at its most harmless will probably only make method dispatch just a little bit slower. --------------------------------- Here's what I just tried: (initialize-window-system) NIL *root-window* # ;this is default superior if I don't specify (setq w2 (make-window 'WINDOW :BORDERS 1 :LEFT 10 :TOP 10 :HEIGHT 250 :WIDTH 400)) # (expose-window w2) ;;; now we see it NIL (let ((*query-io* w2)) (querying-values (*query-io* :label "Just a test.") (query '((alist-member :alist (one two three))) :prompt "Choose one" :default 'two))) THREE (print "Hello." w2) "Hello." (force-output w2) ; forces out any waiting output. NIL Normally, your application will be using Express-Windows for input, and the output will automatically be flushed, so (force-output ..) is rarely necessary. You can also use (sync) for this, which will take care of any waiting output (for the X display). Again, you should look at the demos for example i/o coding and use of define-program-framework. --------------------------------- BUILDING A CORE: Here's how I did it. If the following is make-ew-core.lisp, then (in allegro) cl -qq < make-ew-core.lisp > make-ew-core.output You'll have to load pcl & clx yourself (my core already had these). Note that I call (load-ew) directly, otherwise I would be prompted for (compile, load) x (pcl, clx, ew). Also, I put the optional files onto the ew-files, and set optional files to (), so I don't get prompted for those either. You might want to replace the call to (load-ew) with similar loading code, depending on your needs. ------------ ;;; Dump a core with express windows loaded. (in-package :user) #+excl (unless (excl::scheduler-running-p) (mp:start-scheduler)) (load (make-pathname :name "system" :type "lisp" :defaults *Default-EW-Code-Pathname*)) ;; Don't ask about optional files, just do 'em (setf *Ew-Files-Copy* (append *Ew-Files-Copy* *Optional-Ew-Files-Copy*) *Optional-Ew-Files-Copy* ()) (user::load-ew) (setq ew::*Default-Host* "unix") ; will this give better results? ;;; Okay, now save the world... (excl:chdir "/usr/toad/") ;; are these necesary? right order? (excl:gc t) (excl:gc :tenure) (excl:dumplisp :name "express" :read-init-file t :restart-function nil ; :restart-actions nil :checkpoint nil) (print "Core dumped.") (excl:exit 0 :no-unwind t) --------------------------------- It was my first dumplisp for allegro, and though it works, I'm not satisfied with the way (room) looks; there seems to be several empty oldspaces taking up a couple meg, and the core file is 12M (on a sparc (RISC)); space in core (by (room)) shows 6.5M used. I tried a couple gc tweaks, but it didn't seem to change. Anyone have hints? -todd To: Ashok Kumar Kamshatti cc: express-windows@atc Reply-To: todd.kaufmann@NL.CS.CMU.EDU Subject: Re: Making a simple window, and dumplisp in allegro (was Re: Problem in running express-windows !! ) In-Reply-To: My message of Sun, 27 May 90 16:25:59 -0400. <21779.643839959@NL.CS.CMU.EDU> Date: Mon, 28 May 90 12:10 PDT From: Todd.Kaufmann@NL.CS.CMU.EDU > (run-program 'lisp-listener) ; see frames.lisp Oops, lest anyone get confused, I meant (run-program 'lisp-window) as in the file doc/introduction.text. -todd Date: Tue, 29 May 90 08:37 PDT From: Stephen L. Nicoud Subject: Express Windows and CLIM To: Andrew Ressler cc: express-windows@bcsaic In-Reply-To: <9005180050.AA03547@ames.arc.nasa.gov> Date: Thu, 17 May 90 18:02:35 EDT From: Andrew Ressler I'm curious what people think about the following: Do People want Express Windows to evolve into a Public Domain version of CLIM or at least to be more compatible or do they prefer it for now to be more like the original Dynamic Windows? My main requirement is user-interface compatibility/portability. CLIM would appear to give me a very clean way to do this. My use of Express Windows has been, so far, strictly temporary in nature. A stopgap until CLIM. I am concerned, however, about the cost of CLIM. Not so much for me as for my (potential) users. The more they have to buy, the less attractive my systems become. To that end, a public domain CLIM would really help. The fact that EW uses CLX/PCL makes it desirable on this very point. If the answer is that you would like it to evolve to be more like CLIM are you willing to help add functionality to make it that way? Aye, there's the rub. While I can certainly offer lots of encouragement, commitment of personal assistance isn't something I can promise. Or would you be interested in funding furthur development of EW similar to the GNU software? I don't think I can sell my management on providing the entire funding for a public domain CLIM. Perhaps if you made a proposal for funding that involved other corporations/institutions,... perhaps. Can you estimate time/cost for such a venture? What major features of DW do you wish it supported that is doesn't now. 1. format-graph ?? for example 2. ???? Our Symbolics-based systems make extensive use of the FORMAT-GRAPH-FROM-ROOT function. Our non-Symbolics based system use their own graphing code or do without a graphing capability. It would be nice to have FORMAT-GRAPH-FROM-ROOT available for all systems, since this is such a universally needed feature. What major features do you not care about? How important is a small compact window system? (i.e. takes up less than 2 megabytes in your image) Currently, size of the image is not a major concern for me. Thanks, Andrew Ressler 301-643-4526 Steve -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences Date: Tue, 29 May 90 09:20 PDT From: PT_MAGEE%VAX.ACS.OPEN.AC.UK@CORNELLC.cit.cornell.edu To: express-windows@ATC Subject: Package creation style Sender: "JANET \"PT_MAGEE@UK.AC.OPEN.ACS.VAX\"" In system.lisp all the Symbolics packages are faked by creating new ones which :use user if you aren't running on a Symbolics. Is it not nicer to create EW package with all these packages as :nicknames after building the appropriate list of packages which need to be created by appropriate use of (find-package ... etc. We have found that otherwise our millions of calls to tv:make-window fail. Pete Magee. Date: Wed, 30 May 90 16:39 PDT From: Stephen L. Nicoud Subject: Program Framework Title Panes and REDISPLAY-FUNCTION To: express-windows@atc I'm having problems getting output to the title pane of a program framework using :redisplay-function. Perhaps someone can identify a way to modify my code to get the desired effect. Assuming I have a program framework defined with a title pane like this: (DW:DEFINE-PROGRAM-FRAMEWORK . . . :PANES ((TITLE :TITLE :HEIGHT-IN-LINES 3 :REDISPLAY-AFTER-COMMANDS NIL :REDISPLAY-FUNCTION #'ERASMUS-FRAME-TITLE) (LISTENER :LISTENER :HEIGHT-IN-LINES 30 :TYPEOUT-WINDOW T :more-p nil :deexposed-typeout-action :permit :BLINKER-P T :MARGIN-COMPONENTS '((DW:MARGIN-BORDERS :THICKNESS 1) (DW:MARGIN-LABEL :STRING "Erasmus Listener" :STYLE (:FIX :ITALIC :NORMAL)) (DW:MARGIN-SCROLL-BAR :MARGIN :BOTTOM) (DW:MARGIN-SCROLL-BAR :MARGIN :LEFT))) ...) . . . ) For the Symbolics version of the title pane's redisplay function (ERASMUS-FRAME-TITLE) here's what we have: (defun erasmus-frame-title (program stream) (declare (ignore program)) (send stream :set-default-character-style '(:dutch :bold :large)) (multiple-value-bind (ignore y) (send stream :draw-horizontally-centered-string "Erasmus" 0) (send stream :set-default-character-style '(:fix :roman :very-small)) (send stream :draw-horizontally-centered-string "COPYRIGHT (C) 1990 THE BOEING COMPANY" (+ y 2)))) The intent is to write "Erasmus" and "COPYRIGHT (C) 1990 THE BOEING COMPANY" in the title pane. The method :DRAW-HORIZONTALLY-CENTERED-STRING is a locally defined method which centers the strings in the window. We tried this as an EW alternative: (defun erasmus-frame-title (program stream) (declare (ignore program)) (ew::set-window-style stream '(:dutch :bold :large)) (multiple-value-bind (ignore y) (draw-horizontally-centered-string stream "Erasmus" 0) (ew::set-window-style stream '(:fix :roman :very-small)) (draw-horizontally-centered-string stream (format nil "COPYRIGHT (C) ~s THE BOEING COMPANY" (multiple-value-bind (sec min hr day mo yr) (cl:get-decoded-time) (declare (ignore sec min hr day mo)) yr)) (+ y 2)))) The problem is that "Erasmus" is not drawn on the screen at all (or that I can see). The "COPYRIGHT ..." string appears in the Listener Pane (it is centered, though :-) and it doesn't appear to be in the proper font/character-style. Here's the definition for :DRAW-HORIZONTALLY-CENTERED-STRING for the Symbolics: tv: (defmethod (:draw-horizontally-centered-string graphics-mixin) (string from-y &optional (font current-font) (alu char-aluf) (inside-width (send self :inside-width)) (xoffset 0)) "Draw string centered on the line whose y-coordinate is from-y; i.e. the top of characters drawn will be at from-y. string will be centered with respect to the horizontal region from xoffset to (xoffset + inside-width). Use font and alu as specified. The default behavior is to ceneter the string with respect to the entire line" (let* ((string-width (erasmus::string-pixel-width string font)) (from-x (+ xoffset (max 0 (floor (- inside-width string-width) 2)))) (char-alu char-aluf)) (setq current-font font char-aluf alu) (send self :set-default-character-style (si:backtranslate-font font)) (send self :set-cursorpos from-x from-y) (send self :string-out string) (setq char-aluf char-alu) (values from-x (+ from-y (send self :vsp) (zl:font-char-height current-font))))) and our try at a version for EW: (pcl:defmethod draw-horizontally-centered-string ((self ew::program-title-pane) string from-y &optional (font (ew::window-font self)) alu (inside-width (ew::window-inside-width self)) (xoffset 0)) (declare (ignore alu)) (let* ((string-width (string-pixel-width string font)) (from-x (+ xoffset (max 0 (floor (- inside-width string-width) 2))))) (setf (ew::window-font self) font) (ew::set-window-style self (xfonts::backtranslate-font font)) (ew:draw-string string from-x from-y) (values from-x (+ from-y (ew::window-line-spacing self) (ew::font-height font))))) BTW, we defined a function called BACKTRANSLATE-FONT in fonts.lisp: (defun backtranslate-font (font &rest ignore) (if (equal font *Cached-Font*) *Cached-Font-Style* (loop named find-the-font for family in *font-table* do (loop for faces in (rest family) do (loop for (size xfont) in (rest faces) when (equal xfont font) do (return-from find-the-font (list (first family) (first faces) size))))))) Any ideas, thoughts? I guess the stream passed to ERASMUS-FRAME-TITLE should be a stream for the TITLE pane. I s'pose I should go digging through the code to find it ... Naw, it's the end of the day. Tomorrow, ... maybe. :-) Steve -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences Summary-line: 31-May p2@Porter.ASL.dialnet.sym #Program Framework Title Panes and REDISPLAY-FUNCTION Date: Thu, 31 May 90 01:12 PDT From: Peter Paine Subject: Program Framework Title Panes and REDISPLAY-FUNCTION To: Express-Windows%atc.BOEING.com%Riverside.SCRC.symbolics.com@SKYWALKER.ENTERPRISE.DIALNET.SYMBOLICS cc: p2@Porter.ASL.dialnet.symbolics In-Reply-To: <19900530233923.0.SLN@SKAGIT.atc.boeing.com> My 5 second thought is that you made the title pane, then set it's character style in #'ERASMUS-FRAME-TITLE. If '(:dutch :bold :large) has a larger line height than the default ((:fix :roman :normal)?) then there is no room to write out anything. Fix: give the title pane a :default-character-style in the :panes title field and remove it from the drawing function. (PS. If it works in Genera buy not EW, I would guess that Genera does some clever stuff in :size-from-contents that sees that the output is in large font. <= p2 Date: Thu, 31 May 90 11:22 PDT From: Stephen L. Nicoud Subject: Program Framework Title Panes and REDISPLAY-FUNCTION To: Stephen L. Nicoud cc: express-windows@atc In-Reply-To: <19900530233923.0.SLN@SKAGIT.atc.boeing.com> Date: Wed, 30 May 90 16:39 PDT From: Stephen L. Nicoud I'm having problems getting output to the title pane of a program framework using :redisplay-function. Perhaps someone can identify a way to modify my code to get the desired effect. [...] Any ideas, thoughts? I guess the stream passed to ERASMUS-FRAME-TITLE should be a stream for the TITLE pane. Okay, I dug around just a little on this. The problem was my code for the DRAW-HORIZONTALLY-CENTERED-STRING method. It was calling EW::DRAW-STRING without passing the :STREAM argument. Okay, that seems to solve the stream problem. Now, however, when I specify 0 as the Y position of the stream for the string to be printed, it is off the window. I wonder if the Y position is the bottom of the string for EW, and the top for DW, because specifying 0 in DW yields the intended result. Steve -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences To: Stephen L. Nicoud Reply-To: todd.kaufmann@NL.CS.CMU.EDU Subject: Re: Program Framework Title Panes and REDISPLAY-FUNCTION In-Reply-To: Your message of Thu, 31 May 90 11:22:00 -0700. <19900531182220.4.SLN@SKAGIT.atc.boeing.com> Date: Thu, 31 May 90 12:09 PDT From: Todd.Kaufmann@NL.CS.CMU.EDU Resent-To: express-windows@atc Resent-From: Stephen L. Nicoud Resent-Date: Fri, 1 Jun 90 13:37 PDT Resent-Comments: This may be of general interest to everyone. > Now, however, when I specify 0 as the Y position of the stream for the > string to be printed, it is off the window. I wonder if the Y position > is the bottom of the string for EW, and the top for DW, because > specifying 0 in DW yields the intended result. That's the way draw-string works in CLIM too.. Perhaps the default value for the &key param #+genera :attachment-y #+clim :align-y are different (one of :center :top :bottom) ?? Just a guess, --todd Date: Sat, 2 Jun 90 13:14 PDT From: James Lawton To: express-windows@atc Subject: Color in EW Hello Fellow EW users, Some time ago there was a brief mention of using color in EW. The jist of the responses seemed to say that just by using the ":color" keyword to the various "draw-" type functions, this would work. Well, either I misinterpreted these claims, or I am doing something wrong [imagine that! ;-) ], because I cannot get anything to draw in color on my Sun 3/280 with an RGB monitor (Running Allegro CL 3.something, with the versions of PCL and CLX that come with Allegro). What I would really like to be able to do is mix my own color ALU's like I can do on my Symbolics. Is this too ambitious? Has anyone else got anything to draw in color under EW? Thanks. James Lawton Rome Air Development Center Griffiss AFB, NY Disclaimer: The opinions expressed here are MINE, ALL MINE! I doubt the RADC or the Air Force would want any claim to them, so they won't accept any blame. To: James Lawton cc: express-windows@atc Reply-To: todd.kaufmann@NL.CS.CMU.EDU Subject: Re: Color in EW In-Reply-To: Your message of Sat, 02 Jun 90 16:14:32 -0400. <9006022014.AA06688@ra.radc.af.mil> Date: Sat, 2 Jun 90 15:20 PDT From: Todd.Kaufmann@NL.CS.CMU.EDU Well, I looked a bit, made a small change, and was able to draw a color polygon, but didn't go any farther than that. That was a couple weeks ago.. let's see if I remember the changes-- in graphics-primitives.lisp, most of the graphics functions contain a (xlib:with-gcontext (gcontext :FUNCTION (draw-alu alu) :LINE-WIDTH thickness ... )) wrapper around the xlib: graphics functions; I did the most simple thing and just added a :COLOR color line, and passed in a pixel value. I witnessed an actual color polygon on my screen. The color slot should also be added to the base presentation types, if you want to see them redisplayed. > What I would really like to be able to do is mix my > own color ALU's like I can do on my Symbolics. Is this too > ambitious? Has anyone else got anything to draw in color under > EW? Yes. The correct thing to do would probably be to define a (make-color r g b) function, and pass this as an argument in for color. These would have to be allocated entries in the color map, and then decoded to pixel values for use in the gcontext. This would give you access to the full range of colors available. I'm not sure what the Symbolics gives you for color. Volume 7B shows keywords for the eight rgb, cym & b/w colors. It should be simple to map keywords into the appropriate pixel value, like :black -> 1, etc, like the function DRAW-ALU does in x-interface.lisp. The mapping should also allow straight pixel values to be passed in unchanged, for people who like to hack color maps themselves. I was the person who originally asked about color. I have a color monitor now, but only temporarily in order to make a whizzy demo, then it goes away. If I had had more time I think I might have tried implementing the color, but instead I'm using CLIM now, only for the color. It's still not as "mature" as EW (yet) in many ways, but sufficient for this one-shot job. If and when time allows, I'd like to work on it. Okay, there's even more explicit directions for adding color.. who's going to implement? Todd Kaufmann Center for Machine Translation CMU 412/ 268-7130 Date: Mon, 2 Jul 90 17:01 PDT From: Stephen L. Nicoud Subject: EXCL::FAST-WRITE-STRING To: express-windows@atc Here's something I found which is helpful in EW on Allegro CL ;; From io-functions.lisp #+excl (eval-when (lisp:load lisp:eval) (defun fast-write-string (string &OPTIONAL output-stream start end) (setup-output-stream output-stream) (if (window-p output-stream) (presentation-print-string string output-stream start end) (excl-fast-write-string string output-stream start (or end (length string))))) (setf (symbol-function 'excl-fast-write-string) (symbol-function 'excl::fast-write-string)) (setf (symbol-function 'excl::fast-write-string) (symbol-function 'fast-write-string))) Steve Date: Tue, 10 Jul 90 14:49 PDT From: Stephen L. Nicoud Subject: Framework classes, flavors, objects, etc.. To: express-windows@atc Am I the only one confused by the lack of symmetry between DW and EW objects and the naming of 'em? For instance, A DW:PROGRAM appears to be analagous to an EW:BASIC-FRAME-PROGRAM (at least this is the type of object to which EW:*PROGRAM* is bound). Although an EW:PROGRAM-FRAME object appears to hold some of the corresponding that is present in DW:PROGRAM. More later on how to get the corresponding EW:PROGRAM-FRAME object. A DW:PROGRAM-FRAME appears to be roughly analagous to an EW:PROGRAM-FRAMEWORK-INSTANCE (this is the type of object to which EW::*PROGRAM-FRAME* is bound). I'm not sure what the analagous object in DW is to EW:PROGRAM-FRAMEWORK. In the ROOT-WINDOW slot of an EW:PROGRAM-FRAMEWORK-INSTANCE instance (e.g., EW:*PROGRAM-FRAME*) is an instance of EW:PROGRAM-FRAME (remember EW:PROGRAM-FRAME from above). In the PROGRAM-FRAMEWORK-INSTANCE slot of an EW:PROGRAM-FRAME is an instance of not EW:PROGRAM-FRAMEWORK-INSTANCE, but EW:BASIC-FRAME-PROGRAM, of course. Can you believe that!? Yech!! This must be one of those "it is intuitively obvious to the casual reader ..." things. Confused yet? Do these names drive you batty? They do me! We have also found while a call to DW:FIND-PROGRAM-WINDOW returns an object of type DW:PROGRAM-FRAME, the analagous call to EW:FIND-PROGRAM-WINDOW returns an EW:BASIC-FRAME-PROGRAM instance, when it should return, if it wanted to be analagous to DW, an instance of EW:PROGRAM-FRAMEWORK-INSTANCE. So, here's a proposed INCOMPATIBLE change to FIND-PROGRAM-WINDOW (found in ew/code/frames.lisp) which has it return the appropriate EW:PROGRAM-FRAMEWORK-INSTANCE instance (got that!). No other part of EW references FIND-PROGRAM-WINDOW, so user calls (the important ones!) should be the only affected ones. (defun find-program-window (program-name &REST make-window-options &KEY (create-p T) (activate-p t) (selected-ok T) reuse-test console superior program-state-variables &ALLOW-OTHER-KEYS) (declare (ignore program-state-variables superior console reuse-test selected-ok activate-p make-window-options)) ;4/30/90 (SLN) (let ((framework-definition (find-program-framework program-name))) (unless framework-definition (error "Framework ~A Does not Exist." program-name)) (let ((instances (program-framework-program-instances framework-definition))) (cond (instances ; 7/10/90 [SLN] - return the EW:PROGRAM-FRAMEWORK-INSTANCE (program-frame (first instances))) (create-p ; 7/10/90 [SLN] - return the EW:PROGRAM-FRAMEWORK-INSTANCE (program-frame (create-program-framework-instance framework-definition))) (T NIL))))) Okay, so my comments are a little sarcastic and all. It's just that sometimes it gets a little frustrating working with EW. Comments? Other observations? Steve -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences Date: Wed, 11 Jul 90 13:48 PDT From: Christopher.Maeda@A.GP.CS.CMU.EDU To: express-windows@ATC Subject: port to vaxlisp Has anyone ported express-windows to vaxlisp under VMS? If not, I'm about to. Date: Mon, 23 Jul 90 02:16 PDT From: David Gadbois To: express-windows@ATC Subject: Express Windows with AKCL Reply-To: gadbois%adler.philosophie.uni-stuttgart.de@RELAY.CS.NET I have gotten the required parts of EW to compile under AKCL 1-478 with May Day PCL and CLX R4.3. I have reached the point where I can get the main screen to come up, though that is about it. When I run the lisp-window program, I don't get any response from the keywoard. Before I go diving into the code, has anyone out there had any success with the configuration? Here are some of the changes I had to make in order to get EW to compile with AKCL and the version of CLX I have: o Install the patches for May Day PCL that have appeared on this list. (Thanks Stephen! The patches saved me a lot of work.) o In macros.lsp, there are a number of redundant structure type predicate macros that cause AKCL to barf. Comment them out. Also, AKCL can't handle structure field type declarations of the form (FIXNUM 0 15); I had to change these to just FIXNUM. o In clx-hacks.lsp, there are references to undefined functions XLIB::DECLARE-VALUES and XLIB::DECLARE-FUNARG. I suppose that these are from an earlier version of CLX. I removed the references without any apparent harm. o There is a mysterious bug in the AKCL reader that sometimes causes it to get an undefined dispatching macro error when it sees things like #P"foo" in comments. You may have to remove these. o The names of characters in AKCL are completely different than in other Lisps. Here is a list: EW AKCL ===================== Rubout ‡ Meta-Rubout \377 Control-A  Control-Shift-a  Control-B  Meta-B \342 Meta-Control-B \202 Meta-C \343 Control-D  Meta-D \344 Control-E  Control-F  Meta-F \346 Meta-Control-F \206 Control-K Control-L Meta-L \354 Control-N  Control-O  Control-P  Control-T  Meta-T \364 Meta-Control-T \224 Meta-U \365 Control-V  Meta-V \366 Control-Meta-W \227 Control-Y  Meta-Y \371 Meta-Control-Y \231 Meta-Control-Z \232 control-? ? Meta-K \353 Meta-Control-> \276 Meta-Control-< \274 Meta-> \276 Meta-< \274 Meta-Control-? \277 Note that some characters are not distinct, so you'll have to reassign the key mappings in command-processor.lsp to suit your tastes. o There were a number of references to a #\CR character. I replaced them with #\Newline characters. o In AKCL, byte specs are not self-evaluating (in fact, they are just dotted conses) so you have to quote the read time reference to one in read-internal.lsp. o PCL under AKCL is excruciatingly slow. Some of the EW files with big DEFCLASSes in them took over an hour to compile and another hour to load on a Sun 3. Does anyone know how to speed this up? I ended up splitting the files macros.lsp and x-macros-interface.lsp into a number of pieces to make things bearable. Hope this helps, --David Gadbois Date: Mon, 6 Aug 90 09:37 PDT From: Stephen L. Nicoud Subject: New Version of Express Windows To: express-windows@atc I'm a little hesitant to do this, lest I become known as the "maintainer" of Express Windows (which I'm not), but here goes anyway ... Announcing the availability of a new version of Express Windows. There are two reasons for wanting to release this new version. The first is to unify bug fixes and other suggestions which have appeared on this list. The second is to encourage further enhancements through other user submissions. This release should help in establishing a baseline from which other modifications can evolve. This version, which is dubbed the "Goodwill" version of Express Windows, represents the version currently in use at The Boeing Company. However, neither Boeing nor I accept responsibility to anyone for the consequences of using it or for whether it serves any particular purpose or works at all. There is no express or implied warranty. Neither does the release of this version consitute endorsement of Express Windows by The Boeing Company. Some of the features of Goodwill EW are: - Should work with Victoria, Rainy and May Day PCL and Symbolics CLOS. - Should work with CLX R3 & R4.3. - Compiled and cursorily tested in - Sun/Lucid Common Lisp 3.0.2 (Sun 3, SunOS 4.1) - Franz Allegro Common Lisp 3.1.13 (Sun 3, SunOS 4.1) - Symbolics Common Lisp (Symbolics 3650, Genera 8.0) - Numerous (too numerous to list) bugs and compilation warning messages from the original version have been handled. [Note: not all of 'em have been handled, though. If you know how to handle the remaining ones, let us know.] - CLX and PCL are not distributed with Goodwill EW. Goodwill Express Windows can be FTPed (user: anonymous, password: ) from atc.boeing.com (IP address [130.42.28.80]). In the /pub/ew/ directory is the file express-windows.goodwill.tar.Z. This is a compressed tar file containing Goodwill Express Windows. Also in that directory is express-windows.original.tar.Z, which is the original version of Express Windows. Consult the COPYING file in that directory for license agreement information. Consult the READ_ME.GOODWILL file in that directory for more information. Our Lisp environments are probably not quite the same as other users. We are working primarily with Symbolics Genera 8.0, Lucid Common Lisp 3.0.2, and Franz' Allegro Common Lisp 3.1.13. Additionally, we are using May Day PCL in Lucid and Allegro, Symbolics' native CLOS, and CLX R4.3. While no deliberate attempt has been made by us to drop support in EW for any CL, CLOS, or CLX implementation, we haven't tried, either, to insure compatibility with any version other than those listed above. Goodwill EW should work in non-May Day versions of PCL and in CLX R3. We have, no doubt, inadvertantly missed some things. I urge you to let everyone know of any incompatibilities you discover by sending a note to express-windows@atc.boeing.com. Likewise, any other enhancements, suggestions, questions, comments, et al, should be directed to express-windows@atc.boeing.com. This is the first time I've ever been involved in the Internet-wide distribution of a system. I expect that this initial release will reveal configuration / installation problems that I have overlooked. As a result, this release should probably be dubbed "BETA". Once any initial difficulties are handled, a "RELEASED" Goodwill version will be posted (if necessary; I'm crossing my fingers :-). One final note. I make no promises that there will ever be another release of EW by me or anyone at Boeing beyond this Goodwill version. My primary duties at Boeing do not involve supporting EW. Enough said. I hope everyone finds this release useful and will decide to contribute their enhancements for all to use. Good Luck, Steve -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences From: Francois-Xavier TESTARD-VAILLANT Organization: Universite Pierre et Marie Curie Paris VI - LITP Aile 45-55 - Piece 205 - Equipe CLIP 4 Place Jussieu, F-75252 PARIS CEDEX 05 voice : +33 (1) 43-54-13-65 fax : +33 (1) 46-34-19-27 To: express-windows@atc Subject: memo In-Reply-To: Your message of Fri, 25 May 90 18:07:35 EDT. <12215.643673255@NL.CS.CMU.EDU> Date: Wed, 8 Aug 90 11:32 PDT Could anybody give me a simple example of 'memo' and 'run-memo'? For example, is it possible to write something (a number) at the same place every time without having to remember the coordinates? Thanks in advance, Francois-Xavier Date: Wed, 8 Aug 90 19:09 PDT From: Felix Ingrand To: snicoud@atc cc: express-windows@atc, lisp-4-0@sun, bhart@sun In-Reply-To: <19900806163743.2.SLN@SKAGIT.atc.boeing.com> Subject: bug in lisp 4.0 beta Organization: SRI International, Menlo Park, CA Phone: (415) 859 5584 I managed to narrow the problem to the following function: streamp (in-package :user) (defpackage ew (:shadow lisp:streamp)) (in-package :ew) (defun streamp (object) (or (lisp:typep object 'window) (lisp-streamp object))) (defun setup-lisp-functions (&OPTIONAL (functions '(lisp:streamp))) (dolist (function functions) (let ((local-name (intern (concatenate 'STRING "LISP-" (symbol-name function)) (find-package "EW"))) (new-function (intern (symbol-name function) (find-package "EW"))) (cl-function function)) (unless (fboundp local-name) (setf (symbol-function local-name) (symbol-function cl-function))) (when (fboundp new-function) (setf (symbol-function cl-function) (symbol-function new-function)))))) If you then do: (ew::setup-lisp-functions) You get: Nasty recursive error in debugger. Expanding main stack due to overflow... Expanded. Please be patient--it will take a few minutes to build debugger data structures. Expanding main stack due to overflow... Felix From: Francois-Xavier TESTARD-VAILLANT Organization: Universite Pierre et Marie Curie Paris VI - LITP Aile 45-55 - Piece 205 - Equipe CLIP 4 Place Jussieu, F-75252 PARIS CEDEX 05 voice : +33 (1) 43-54-13-65 fax : +33 (1) 46-34-19-27 To: express-windows@atc Subject: Redisplay Date: Thu, 9 Aug 90 07:12 PDT Is there any other documentation apart the source code? Francois-Xavier From: Francois-Xavier TESTARD-VAILLANT Organization: Universite Pierre et Marie Curie Paris VI - LITP Aile 45-55 - Piece 205 - Equipe CLIP 4 Place Jussieu, F-75252 PARIS CEDEX 05 voice : +33 (1) 43-54-13-65 fax : +33 (1) 46-34-19-27 To: express-windows@atc Subject: redisplay Date: Thu, 9 Aug 90 07:14 PDT What is the simplest way to get redisplayable windows such as the ones got when running (run-program 'demo)? Francois-Xavier Date: Thu, 9 Aug 90 19:30 PDT From: Jean-Francois Rit To: allegro-cl@ucbvax.berkeley.edu.ARPANET, express-windows@atc Subject: Font problem with Express-windows, ACL, DS3100 Reply-To: Jean-Francois Rit I have a problem with launching Express-windows on a DECstation 3100 Running Franz ACL 3.1, and UWS 2.2. In short, a (xlib:font-ascent some-font-object) causes a name-error, while other slots like xlib:font-name are accessed without problem. When I open another display in the same environment and open new fonts, the bug disappears. I am afraid this is a situation where the Allegro and Express-windows will throw the ball at each other. Anyway, any kind of indication on what to investigate next would be useful. JF Here is a transcript of the session, the interesting stuff is at the end. dribbling to file "/user/rit/drib" LISP-IMPLEMENTATION-TYPE: Allegro CL LISP-IMPLEMENTATION-VERSION: 3.1.12 [DEC 3100] (3/30/90) MACHINE-TYPE: DEC 3100 MACHINE-VERSION: SOFTWARE-TYPE: Ultrix SOFTWARE-VERSION: SHORT-SITE-NAME: ostrich.Stanford.EDU *features*: (:HAS-RCSNOTE :LOOP LOOP :COMPOSER :FAKE-ACTIVE-REGIONS :PCL :CLOS :LITTLE-ENDIAN :GSGC :ALLEGRO-V3.1 :FRANZ-INC :EXCL :ALLEGRO :COMMON-LISP :CONFORMING-IEEE :IEEE :FLAVORS :MIPS :R2000 :UNIX :DEC3100 :MULTIPROCESSING :CLX-LITTLE-ENDIAN :CLX :XLIB :CLX-MIT-R4 :CLX-CL-ERROR :CW-X) *modules*: ("EMACS" "IPC" "DFSYS" "LOOP" "COMPOSER" "GPROF" "GR" "PROF" "TTYPROF" "MENU" "CLOS" "PCL" "XVARS" "XCW" "XLIB" "CLX" "CLXEXCLDEP" "CSTRUCTS" "SIGIO" "ADVISE" "TRACE" "MDPROC" "PROCESS" "FOREIGN" "FOREIGN-FUNCTIONS" "QSTRUCTS") emacs: $Header: emacs.cl,v 1.2 89/08/07 16:54:38 layer Rel $ ipc: $Header: ipc.cl,v 1.26 89/08/16 13:52:26 layer Rel $ loop: $Header: loop.cl,v 1.2 89/07/22 18:56:13 layer Rel $ Allegro Composer: Composer Final 1.0.17 (3/16/90 12:30) disassmip: $Header: disassmip.cl,v 1.1 89/08/10 12:26:22 layer Rel $ X Common Windows: X-CW 1.3.final.11 (3/19/90 16:15) cstructs: $Header: cstructs.cl,v 1.18 89/08/22 11:42:07 layer Rel $ sigio: $Header: sigio.cl,v 1.3 89/08/24 14:03:01 layer Rel $ trace: $Header: trace.cl,v 1.35 89/07/22 18:56:24 layer Rel $ mdproc: $Header: mdproc.cl,v 1.20 89/07/22 18:56:29 layer Rel $ process: $Header: process.cl,v 1.44 89/08/17 18:45:20 layer Rel $ foreign: $Header: foreign.cl,v 1.49 89/08/28 14:45:00 layer Rel $ NIL :ld def-ew.lisp ; Loading /usr/local2/cl/lib/code/def-ew.lisp. (load-ew) ; Fast loading /usr/local/ew/binary/excl/rel3/require.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/define-defpackage.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/defpackage.fasl. Error: "EXPRESS-WINDOWS" is a package name, so it cannot be a nickname for "EW". Restart actions (select using :continue): 0: Ignore this nickname. [1c] :continue ; Fast loading /usr/local/ew/binary/excl/rel3/clx-hacks.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/meter.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/cl-clos-macros.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/fixnum-macros.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/x-macros-interface.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/fonts.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/macros.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/x-interface.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/read-internal.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/quad-trees.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/base-presentations.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/type.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/scrolling.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/graphic-primitives.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/io-functions.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/command-processor.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/misc.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/memo.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/table.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/query.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/completion.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/frames.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/input-editor.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/proprietary-presentation-types.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/presentation-types.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/lisp-window.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/demos.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/sym-comp.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/time.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/lisp-machine-lisp-compatible.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/file-manager.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/menu-definer.fasl. ; Fast loading /usr/local/ew/binary/excl/rel3/processes.fasl. (:EW :EW-GOODWILL :X :DEFPACKAGE :EW-CLOS :PCL-VICTORIA :HAS-RCSNOTE :LOOP LOOP :COMPOSER ...) (in-package 'ew) # (setq *default-host* "killdeer") "killdeer" (initialize-window-system) Debug: Asynchronous NAME-ERROR in request 97 (last request was 158) Code 45.0 [OpenFont] Restart actions (select using :continue): 0: Ignore [1c] :zoom Evaluation stack: ->(CERROR "Ignore" XLIB:NAME-ERROR ...) (APPLY # "Ignore" ...) (APPLY # "Ignore" ...) (XLIB::X-CERROR "Ignore" XLIB:NAME-ERROR . :DISPLAY) (APPLY # "Ignore" ...) (APPLY # "Ignore" ...) (XLIB:DEFAULT-ERROR-HANDLER # XLIB:NAME-ERROR ...) (APPLY XLIB:DEFAULT-ERROR-HANDLER # ...) ... more older frames ... [1c] :dn 9 Evaluation stack: ... 7 more (possibly invisible) newer frames ... (APPLY # "Ignore" ...) (XLIB:DEFAULT-ERROR-HANDLER # XLIB:NAME-ERROR ...) (APPLY XLIB:DEFAULT-ERROR-HANDLER # ...) (APPLY XLIB:DEFAULT-ERROR-HANDLER # ...) ->(XLIB::REPORT-ERROR # 15 ...) (APPLY # # ...) (APPLY # # ...) (XLIB::READ-ERROR-INPUT # 97 ...) ... more older frames ... [1c] :dn 9 Evaluation stack: ... 16 more (possibly invisible) newer frames ... (XLIB::READ-REPLY # #s(XLIB::PENDING-COMMAND :SEQUENCE # :REPLY-BUFFER # ...)) (XLIB::QUERY-FONT #) (XLIB::FONT-FONT-INFO # ) (XLIB:FONT-ASCENT #) ->(FONT-HEIGHT #) (EW-CLOS::|(METHOD EW:SET-WINDOW-STYLE (EW:WINDOW T))| # (:FIX :ROMAN :NORMAL) ...) (APPLY # # ...) (APPLY # # ...) ... more older frames ... [1c] (setq font2 (xlib:open-font *x-display* "courier12")) # [1c] (xlib:font-name font2) "courier12" [1c] (xlib:font-ascent font2) Debug: Asynchronous NAME-ERROR in request 98 (last request was 160) Code 45.0 [OpenFont] Restart actions (select using :continue): 0: Ignore 1: Ignore [2c] :pop Previous error: Asynchronous NAME-ERROR in request 97 (last request was 158) Code 45.0 [OpenFont] If continued, Ignore [1c] (xlib:font-direction font2) Debug: Asynchronous NAME-ERROR in request 99 (last request was 161) Code 45.0 [OpenFont] Restart actions (select using :continue): 0: Ignore 1: Ignore [2c] :pop Previous error: Asynchronous NAME-ERROR in request 97 (last request was 158) Code 45.0 [OpenFont] If continued, Ignore [1c] [1c] (dribble) ;;; Then I tried to open my own display: dribbling to file "/user/rit/drib2" NIL [1c] (setq *dd* (xlib:open-display "killdeer")) # [1c] (xlib:open-font *dd* "courier12") # [1c] (xlib:font-ascent *) 10 [1c] (describe *x-display*) # is a XLIB:DISPLAY There are 69 elements [1c] (describe *dd*) # is a XLIB:DISPLAY There are 69 elements [1c] (dribble) Date: Sun, 12 Aug 90 04:56 PDT From: F-X TESTARD-VAILLANT To: express-windows@atc Subject: Questions cc: snicoud@atc 1 - Is there any other documentation apart the source code? 2 - What is the simplest way to get redisplayable windows such as the ones got when running (run-program 'demo)? Thanks in advance, Francois X. Testard-Vaillant Universite Pierre et Marie Curie Institut Blaise Pascal - LITP From: Francois-Xavier TESTARD-VAILLANT Organization: Universite Pierre et Marie Curie Paris VI - LITP Aile 45-55 - Piece 205 - Equipe CLIP 4 Place Jussieu, F-75252 PARIS CEDEX 05 voice : +33 (1) 43-54-13-65 fax : +33 (1) 46-34-19-27 To: express-windows@atc cc: snicoud@atc Subject: Questions Date: Sun, 12 Aug 90 05:07 PDT 1 - Is there any other documentation apart the source code? 2 - What is the simplest way to get redisplayable windows such as the ones got when running (run-program 'demo)? Thanks in advance, Francois X. Testard-Vaillant Universite Pierre et Marie Curie Institut Blaise Pascal - LITP PARIS FRANCE Date: Mon, 13 Aug 90 08:17 PDT From: Stephen L. Nicoud Subject: Redisplay To: Francois-Xavier TESTARD-VAILLANT cc: express-windows@atc In-Reply-To: <9008091312.AA04813@zeta.ibp.fr> Date: Thu, 09 Aug 90 15:12:43 +0100 From: fxtv@zeta.ibp.fr (Francois-Xavier TESTARD-VAILLANT) Is there any other documentation apart the source code? Francois-Xavier Symbolics' manuals on Dynamics Windows and User Interfaces is probably the best documentation of what EW is supposed to be like. Apart from that, there should be a "doc" subdirectory distributed with EW with some documentation. Steve -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences Date: Wed, 15 Aug 90 11:20 PDT From: Jean-Francois Rit To: express-windows@atc Subject: Alu problem Reply-To: Jean-Francois Rit I have some problem with alu values. I am running Allegro 3.1 on a DECstation3100, UWS 2.2. First my query: can somebody who has xlib:screen-black-pixel to 0 and displaying working properly give me the values of its xlib boolean constants?(You just have to eval the following forms and give me the result: (XLIB:SCREEN-BLACK-PIXEL (xlib:display-default-screen ew::*X-DISPLAY*)) (dolist (x '(boole-1 boole-2 boole-andc1 boole-andc2 boole-and boole-c2 boole-clr boole-eqv boole-ior boole-nand boole-nor boole-orc1 boole-orc2 boole-set boole-xor)) (format t "~% ~a ~s" x (eval x))) Now the bug description: Alu values are set in this function (in x-interface.lisp): (defun init-alu-values (black-color) (ecase black-color #+excl ((255 1) (setq *Draw-Alu-Value* 7 *Erase-Alu-Value* 0 *Flip-Alu-Value* 8 *Magic-Alu-Value* 2)) #-excl ((255 1) (setq *Draw-Alu-Value* 7 *Erase-Alu-Value* 2 *Flip-Alu-Value* 6 *Magic-Alu-Value* 5)) (0 (setq *Draw-Alu-Value* 1 *Erase-Alu-Value* 15 *Flip-Alu-Value* 9 *Magic-Alu-Value* 10)))) I fall in the last case because my xlib:screen-black-pixel is 0. The behavior I get in the Lisp Interactor is: When I try to type sys (space) me (space) I get: The first s is not echoed (it should echo a S) then ys is echoed then tem is echoed, The S appears in inverse video, and ys is overwritten by a black blob. then men is echoed normally, then, no more echo but the system menu appears. In the system menu, menu items appear as a black bar when the mouse is over them. In the Lisp Window, previous commands are higlighted correctly when the mouse is over. I've tried the other (255 1) cases, they are much worse (nothing appears in the mouse panel and the system menu). I hope that by getting the boolean xlib values from a working implementation, I can translate them to correct integer values, hence my query. Is there a reason why this is not done directly in the code? Right now, these values are for me: *Draw-Alu-Value* 1 SET *Erase-Alu-Value* 15 ORC2 *Flip-Alu-Value* 9 EQV *Magic-Alu-Value* 10 NAND Jean-Francois Rit Tel: (415) 725 8813 CS Dept Robotics Laboratory e-mail: rit@cs.stanford.edu Cedar Hall Stanford, CA 94305-4110 Date: Wed, 15 Aug 90 11:36 PDT From: Jean-Francois Rit To: express-windows@atc cc: franz.com!xcw-bugs@uunet.uu.net.ARPANET, gadbois@cs.utexas.edu.ARPANET Subject: [spr1822] Font problem with Express-windows, ACL, DS3100 Reply-To: Jean-Francois Rit This problem has been solved. The cause is that there is no -bitstream-charter font family in UWS 2.2. The fix is a neutralization of the (:charter ... form in (setq *Font-Table* ... in fonts.lisp. I used #-:dec3100 (which is not completely satisfactory, apparently, there is no feature for discriminating the MIT X server from the DEC one), I couldn't find this (trivial) error because of my illiteracy in X, thanks to Franz Inc. support for suggesting it and giving the advice function to pinpoint it which I reproduce here: (setq fns (xlib:list-font-names *x-display* "*")) (advise xlib:open-font :before :check-name nil (let ((name (second arglist))) (unless (member name fns :test #'string-equal) (error "Bad font name ~a." name)))) J-F Rit Date: Thu, 9 Aug 90 16:18 PDT From: Felix Ingrand To: lisp-4-0@sun.com.ARPANET, bhart@sun.com.ARPANET cc: snicoud@atc In-Reply-To: <9008091654.AA13323@Sunset.AI.SRI.COM> Subject: bug in lisp 4.0 beta (6 July 1990) Organization: SRI International, Menlo Park, CA Phone: (415) 859 5584 Resent-To: express-windows@atc Resent-From: Stephen L. Nicoud Resent-Date: Fri, 17 Aug 90 08:26 PDT Resent-Comments: EW Lucid 4.0 bug workaround. I have found a fix for the problem reported bellow: Just swap the call to typep and lisp-streamp in streamp like this: (defun streamp (object) (or (lisp-streamp object) (lisp:typep object 'window))) Felix Felix Ingrand writes: > >In case you have not received this bug report. > >(this happens in express windows) > >I managed to narrow the problem to the following function: streamp > >(in-package :user) > >(defpackage ew (:shadow lisp:streamp)) > >(in-package :ew) > >(defun streamp (object) > (or (lisp:typep object 'window) > (lisp-streamp object))) > >(defun setup-lisp-functions (&OPTIONAL (functions '(lisp:streamp))) > (dolist (function functions) > (let ((local-name (intern (concatenate 'STRING "LISP-" (symbol-name function)) (find-package "EW"))) > (new-function (intern (symbol-name function) (find-package "EW"))) > (cl-function function)) > (unless (fboundp local-name) > (setf (symbol-function local-name) (symbol-function cl-function))) > (when (fboundp new-function) > (setf (symbol-function cl-function) (symbol-function new-function)))))) > >If you then do: >(ew::setup-lisp-functions) >You get: > >Nasty recursive error in debugger. >Expanding main stack due to overflow... >Expanded. Please be patient--it will take a >few minutes to build debugger data structures. >Expanding main stack due to overflow... > >Felix > Date: Sat, 18 Aug 90 21:25 PDT From: Ramu Iyer To: sri-unix!atc.boeing.com!express-windows@unix.sri.com.ARPANET Subject: Lisp break with goodwill EW Goodwill EW compiled on my Symbolics running Genera 8.0 without a hitch. However, I encountered the following break while I started running it. In order to see at least one EW window show up on either my SUN3 (running X), I did the following: a) Added the Symbolics to the X-server's access control list via the xhost command. b) On the Lisp machine, I did the following: > (in-package 'ew) > (setf ew::*Default-Host* "spike") ;; that's the name of my Sun (the X server) > (clear-all) > (initialize-window-system) ;; No root window appeared. Any ideas why? ;; In order to run the demos in demos.lisp, should one use (run-program 'demo)? > (run-program 'lisp-window) whereupon I got the following break Thanks for any input. --Ramu ramu%tcipro.uucp@unix.sri.com ---------------------------------cut here-------------------------------------------------------- Trap: The variable EW::*UNREAD-CHAR* is unbound. 0While in the function EW::LISTEN-ANY  EW::READ-CHAR-FOR-QUERY-INTERNAL  EW::EDITOR The condition signalled was DBG:UNBOUND-SYMBOL-TRAP Trap microcode PC = #o2 in 3675-MIC 430 Error-table entry = (BAD-DATA-TYPE) 1EW::LISTEN-ANY0 (P.C. = 2) (2 0 (NIL 0) (NIL :ITALIC NIL) "CPTFONTI")(from ALBA:>iyer>ew>code>x-interface) 0 Arg 0 (STREAM): # Arg 1 (EW::TIMEOUT): 0 1EW::READ-CHAR-FOR-QUERY-INTERNAL0 (P.C. = 154) 2(from ALBA:>iyer>ew>code>query) 0 Arg 0 (STREAM): # 1EW::EDITOR0 (P.C. = 247) 2(from ALBA:>iyer>ew>code>input-editor) 0 Arg 0 (STREAM): # 1EW:READ-CHAR-FOR-QUERY0 (P.C. = 7) 2(from ALBA:>iyer>ew>code>query) 0 Arg 0 (STREAM): # 1EW:PEEK-CHAR-FOR-QUERY0 (P.C. = 20) 2(from ALBA:>iyer>ew>code>query) 0 Arg 0 (STREAM): # Arg 1 (EW::HANG): T 1EW::|parser-COMMAND-OR-FORM|0 (P.C. = 34) 2(from ALBA:>iyer>ew>code>proprietary-presentation-types) 0 Arg 0 (STREAM): # Arg 1 (TYPE): (EW::COMMAND-OR-FORM # :DISPATCH-MODE :FORM-PREFERRED) Arg 2 (EW::ORIGINAL-TYPE): (EW::COMMAND-OR-FORM # :DISPATCH-MODE :FORM-PREFERRED) Arg 3 (EW::INITIALLY-DISPLAY-POSSIBILITIES): NIL Arg 4 (EW::DEFAULT): NIL Arg 5 (EW::DEFAULT-SUPPLIED): NIL Arg 6 (EW::DEFAULT-TYPE): (EW::COMMAND-OR-FORM # :DISPATCH-MODE :FORM-PREFERRED) 1(:INTERNAL EW:QUERY 0 EW::QUERY-2)0 (P.C. = 34) 2(from ALBA:>iyer>ew>code>query) 0 Arg 0 (COMPILER:.LEXICAL-ENVIRONMENT-POINTER.): ((EW::COMMAND-OR-FORM # :DISPATCH-MODE :FORM-PREFERRED) (:STREAM # :PROMPT-MODE :RAW :PROMPT "> ") # (EW::COMMAND-OR-FORM # :DISPATCH-MODE :FORM-PREFERRED) NIL (EW::COMMAND-OR-FORM # :DISPATCH-MODE :FORM-PREFERRED) NIL 0 (EW::COMMAND-OR-FORM # :DISPATCH-MODE :FORM-PREFERRED) EW::|parser-COMMAND-OR-FORM|) 1EW::INPUT-EDITOR-INTERNAL0 (P.C. = 6) 2(from ALBA:>iyer>ew>code>input-editor) 0 Arg 0 (STREAM): # Arg 1 (EW::STATE): # Arg 2 (EW::CONTINUATION): # 1(CLOS:METHOD EW::INPUT-EDITOR (EW:WINDOW T))0 (P.C. = 123) 2(from ALBA:>iyer>ew>code>input-editor) 0 Arg 0 (STREAM): # Arg 1 (CLOS-INTERNALS::.EXTRA-ARGUMENT.): NIL Arg 2 (CLOS-INTERNALS::.GENERIC.): # Arg 3 (EW::CONTINUATION): # 1EW:QUERY0 (P.C. = 437) 2(from ALBA:>iyer>ew>code>query) 0 Arg 0: (EW::COMMAND-OR-FORM # :DISPATCH-MODE :FORM-PREFERRED) Rest arg: (:STREAM # :PROMPT-MODE :RAW :PROMPT "> ") 1EW:READ-PROGRAM-COMMAND0 (P.C. = 127) 2(from ALBA:>iyer>ew>code>frames) 0 Arg 0 (EW::PROGRAM): # Rest arg (EW::OPTIONS): (:PROMPT "> " :COMMAND-QUERY (EW::COMMAND-OR-FORM # :DISPATCH-MODE :FORM-PREFERRED) :UNKNOWN-ACCELERATOR-IS-COMMAND NIL) 1EW:DEFAULT-COMMAND-TOP-LEVEL0 (P.C. = 173) 2(from ALBA:>iyer>ew>code>frames) 0 Arg 0 (EW::PROGRAM): # Rest arg (EW::OPTIONS): NIL 1EW:RUN-PROGRAM0 (P.C. = 113) 2(from ALBA:>iyer>ew>code>frames) 0 Arg 0 (EW::FRAMEWORK-NAME): EW:LISP-WINDOW 1CP::COMMAND-LOOP-EVAL-FUNCTION0 (P.C. = 27) Arg 0 (CP::FORM): (EW:RUN-PROGRAM (QUOTE EW:LISP-WINDOW)) 2 --Defaulted args:-- 0 Arg 1 (CP::ENVIRONMENT): NIL 1(:INTERNAL SI:WITH-PROCESS-NON-INTERACTIVE-PRIORITY-INTERNAL 0)0 (P.C. = 5) Arg 0 (COMPILER:.LEXICAL-ENVIRONMENT-POINTER.): # Arg 1 (PROCESS:START-DELAYED-PRIORITIES): # 1PROCESS::WITH-DELAYED-PROCESS-PRIORITIES-INTERNAL0 (P.C. = 124) Arg 0 (PROCESS::CONTINUATION): # Arg 1 (PROCESS::PRIORITY): T Rest arg (PROCESS::NEW-PRIORITIES): (2.0 -822083583) 1SI:WITH-PROCESS-NON-INTERACTIVE-PRIORITY-INTERNAL0 (P.C. = 31) Arg 0 (PROCESS:PROCESS): # Arg 1 (PROCESS::CONTINUATION): # Rest arg: NIL 1TV:WITH-NOTIFICATION-MODE-INTERNAL0 (P.C. = 15) Arg 0 (TV:NEW-MODE): :BLAST Arg 1 (TV:STREAM): #:TERMINAL-IO-SYN-STREAM Arg 2 (TV:CONTINUATION): # 1(:INTERNAL SI:WITH-PROCESS-INTERACTIVE-PRIORITY-INTERNAL 0)0 (P.C. = 3) Arg 0 (COMPILER:.LEXICAL-ENVIRONMENT-POINTER.): # 1PROCESS::WITH-PROCESS-PRIORITY-INTERNAL0 (P.C. = 61) Arg 0 (PROCESS::CONTINUATION): # Arg 1 (PROCESS::NEW-PRIORITY): -824180735 1SI:WITH-PROCESS-INTERACTIVE-PRIORITY-INTERNAL0 (P.C. = 57) Arg 0 (PROCESS:PROCESS): # Arg 1 (PROCESS::CONTINUATION): # Rest arg: NIL 1SI:LISP-COMMAND-LOOP-INTERNAL0 (P.C. = 24) Arg 0 (PROCESS::NAME): "Lisp Top Level" Arg 1 (SI:ABORT-FUNCTION): NIL Arg 2 (SI:READ-FUNCTION): NIL Arg 3 (SI:EVAL-FUNCTION): NIL Arg 4 (SI:PRINT-FUNCTION): NIL Arg 5 (PROCESS::INITIAL-FORM): NIL Arg 6 (SI:STANDARD-VALUE-BINDINGS): (NIL) 1SI:LISP-COMMAND-LOOP0 (P.C. = 100) Arg 0: # Rest arg: (:NAME "Lisp Top Level") 1SI:LISP-TOP-LEVEL10 (P.C. = 6) Arg 0 (SI:STREAM): # 1(FLAVOR:METHOD PROCESS::PROCESS-TOP-LEVEL-1 PROCESS:PROCESS)0 (P.C. = 114) Arg 0 (SELF): # Arg 1 (SYS:SELF-MAPPING-TABLE): # Arg 2 (FLAVOR::.GENERIC.): # 1PROCESS::PROCESS-TOP-LEVEL0 (P.C. = 311) 2 --Defaulted args:-- 0 Arg 0 (IGNORE): NIL Special EW::*UNREAD-CHAR*: "unbound" ------------------------------------------cut here--------------------------------------------- To: express-windows@atc Subject: Goodwill EW under Franz trouble Date: Fri, 24 Aug 90 08:56 PDT From: mac@trantor.harris-atd I grabbed a copy of the Goodwill version of EW yesterday and I'm having a problem compiling it. When (compile-ew) gets done compiling code/io-functions and loads it, my lisp hangs waiting for input. This is caused by the (setup-lisp-functions) call. Has anyone else run across this? Any fixes? I'm running Allegro Common Lisp 3.1.13 on a Sun3. Thanks, Mike McDonald mac@trantor.harris-atd.com (407) 727-5060 Advanced Technology Dept. Harris Corp. M.S. 3A-1912 P.O. Box 37 Melbourne, Florida 32902 Date: Fri, 24 Aug 90 10:52 PDT From: Stephen L. Nicoud Subject: Goodwill EW under Franz trouble To: mac@trantor.harris-atd.com.ARPANET cc: express-windows@atc In-Reply-To: <9008241557.AA02063@trantor.harris-atd.com> Date: Fri, 24 Aug 90 11:56:52 -0400 From: mac@trantor.harris-atd.com I grabbed a copy of the Goodwill version of EW yesterday and I'm having a problem compiling it. When (compile-ew) gets done compiling code/io-functions and loads it, my lisp hangs waiting for input. This is caused by the (setup-lisp-functions) call. Has anyone else run across this? Any fixes? I'm running Allegro Common Lisp 3.1.13 on a Sun3. I've think I've run into this before. I had similar symptons with EW not being configured correctly for the version of PCL being used. Which version of PCL are you using? The Victoria Day one provided with Allegro? or maybe Rainy or May Day PCL? Also, what's the value of *features*? Steve -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences Date: Fri, 24 Aug 90 14:06 PDT From: Stephen L. Nicoud Subject: Re: Goodwill EW under Franz trouble To: mac@trantor.harris-atd.com.ARPANET cc: express-windows@atc In-Reply-To: <9008241914.AA03466@trantor.harris-atd.com> [Added CC: express-windows] Date: Fri, 24 Aug 90 15:14:00 -0400 From: mac@trantor.harris-atd.com Date: Fri, 24 Aug 90 10:52 PDT From: Stephen L. Nicoud Date: Fri, 24 Aug 90 11:56:52 -0400 From: mac@trantor.harris-atd.com I grabbed a copy of the Goodwill version of EW yesterday and I'm having a problem compiling it. When (compile-ew) gets done compiling code/io-functions and loads it, my lisp hangs waiting for input. This is caused by the (setup-lisp-functions) call. Has anyone else run across this? Any fixes? I'm running Allegro Common Lisp 3.1.13 on a Sun3. I've think I've run into this before. I had similar symptons with EW not being configured correctly for the version of PCL being used. Which version of PCL are you using? The Victoria Day one provided with Allegro? or maybe Rainy or May Day PCL? Also, what's the value of *features*? I'm using the Victoria Day pcl that comes with Allegro. My *features* list looks like this after loading code/require: (:X :DEFPACKAGE :EW-CLOS :PCL-VICTORIA :PCL :CLOS :CLX-MIT-R4 :XLIB :CLX :MULTIPROCESSING :LOOP LOOP :UNIX :SUN3 :M68K :SUN :SUNOS4.0 :FLAVORS :IEEE :CONFORMING-IEEE :COMMON-LISP :ALLEGRO :EXCL :FRANZ-INC :ALLEGRO-V3.1 :M68020 :M68881 :GSGC :BIG-ENDIAN) In the file require.lisp, it states that if you're using Franz, you can use (require :pcl) instead of the larger form. I believe that this is in error. You must put the (require :pcl) before that form. If you don't include that form, the pcl package will not be given a nickname of ew-clos nor will one of the :pcl- keywords be added to *features*. You're correct about this error. Thanks for pointing it out. Your suggestion of putting "(require :pcl)" prior to the larger form should handle the error well. Probably adding "#+excl (require :pcl)" would be best. Assuming that you already made this fix and are still having the problem, I'm afraid I don't know what the problem is. I just recompiled EW from a lisp image which already had pcl and clx in it, and the recompilation went well. -- Steve From snicoud@atc.boeing.com Fri Aug 24 14:58:24 1990 Received: by atc.boeing.com on Fri, 24 Aug 90 14:58:24 PDT Date: Fri, 24 Aug 90 15:04 PDT From: Express Windows List Administrator Sender: snicoud@atc.boeing.com Subject: Mail Archives To: express-windows@atc.boeing.com Message-Id: <19900824220444.6.SLN@SKAGIT.atc.boeing.com> An archive of postings to express-windows@atc.boeing.com can be found in atc.boeing.com:/pub/ew/mail-archive.text. Steve -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences From snicoud@atc.boeing.com Wed Aug 29 13:43:13 1990 Received: by atc.boeing.com on Wed, 29 Aug 90 13:43:13 PDT Date: Wed, 29 Aug 90 13:49 PDT From: Stephen L Nicoud Subject: Re: Goodwill EW under Franz trouble To: mac@trantor.harris-atd.com Cc: snicoud@atc.boeing.com, express-windows@atc.boeing.com In-Reply-To: <9008291958.AA10020@trantor.harris-atd.com> Message-Id: <19900829204908.2.SNICOUD@SKAGIT.atc.boeing.com> [Added cc: express-windows@atc.boeing.com] Date: Wed, 29 Aug 90 15:58:05 -0400 From: mac@trantor.harris-atd.com Date: Wed, 29 Aug 90 11:52 PDT From: Stephen L. Nicoud Subject: Re: Goodwill EW under Franz trouble To: mac@trantor.harris-atd.com In-Reply-To: <9008241914.AA03466@trantor.harris-atd.com> Message-Id: <19900829185224.0.SNICOUD@SKAGIT.atc.boeing.com> Were you ever able to overcome this bug? If so, what was the solution? Steve Yes, I was finally able to get it to work. This time I too used a lisp with PCL and a clossified version of CLX already loaded. I also removed all of the binaries that I had already compiled. By the way, is there any easy way to make the initial lisp window smaller? The default is wider than my screen and almost as high. Right now, I'm just doing (run-program 'lisp-window) to start things up. I'd sure like to do this as well. I'm not even able to resize the window under the window manager I'm using (twm). If you or someone else can figure it out, let us all know. Mike McDonald mac@trantor.harris-atd.com postmaster@trantor.harris-atd.com (407) 727-5060 Advanced Technology Dept. Harris Corp. M.S. 3A-1912 P.O. Box 37 Melbourne, Florida 32902 -- steve From @research.att.com.ARPANET:tk@allegra.tempo.nj.att.com Wed Aug 29 14:36:11 1990 Received: by atc.boeing.com on Wed, 29 Aug 90 14:36:11 PDT Message-Id: <9008292136.AA26149@atc.boeing.com> Received: by research; Wed Aug 29 17:41:03 EDT 1990 Date: Wed, 29 Aug 90 17:40:56 EDT To: snicoud@atc.boeing.com From: tk@research.att.com Sender: tk@allegra.tempo.nj.att.com Cc: mac@trantor.harris-atd.com, snicoud@atc.boeing.com, express-windows@atc.boeing.com In-Reply-To: Stephen L Nicoud's message of Wed, 29 Aug 90 13:49 PDT <19900829204908.2.SNICOUD@SKAGIT.atc.boeing.com> Subject: Re: Goodwill EW under Franz trouble > By the way, is there any easy way to make the initial lisp window > smaller? The default is wider than my screen and almost as high. Right > now, I'm just doing (run-program 'lisp-window) to start things up. > >I'd sure like to do this as well. I'm not even able to resize the window >under the window manager I'm using (twm). If you or someone else can >figure it out, let us all know. the simple (if not proper) way to do this is to hack initialize-window-system. the following code allows the dimensions to be specified as keyword args. the mouse doc window will be sized proportionately. ;;; from x-interface.lisp ;;; (defun initialize-window-system (&OPTIONAL (host *Default-Host*) &KEY protocol (display 0) (width (xlib:screen-width *screen*)) (height (xlib:screen-height *screen*))) (setq *Menu-Choose-Resource* NIL *mouse-window* NIL) (when *X-Display* ;; remove pixmaps from stipples so they can be GC'd. (dolist (stipple *stipple-arrays*) (setf (stipple-pattern-pixmaps stipple) (delete (xlib:screen-root *screen*) (stipple-pattern-pixmaps stipple) :KEY #'FIRST))) (xlib:close-display *X-display*)) (setq *X-Display* (xlib:open-display host :DISPLAY display :PROTOCOL protocol) *Screen* (xlib:display-default-screen *X-Display*)) (init-alu-values (xlib:screen-black-pixel *Screen*)) (xfonts::init-fonts) (let ((screen-width width) (screen-height height) (mouse-documentation-window-height 36)) (setq *Ultimate-Root-Window* . . . From snicoud@atc.boeing.com Wed Aug 29 14:55:46 1990 Received: by atc.boeing.com on Wed, 29 Aug 90 14:55:46 PDT Date: Wed, 29 Aug 90 15:01 PDT From: Stephen L Nicoud Subject: patch to with-compilation-unit in defsystem.lisp To: express-windows@atc.boeing.com Message-Id: <19900829220141.7.SNICOUD@SKAGIT.atc.boeing.com> There were a few bugs in the definition of with-compilation-unit in ew/code/defsystem.lisp. I think the appended replacement code should work okay. Steve -- Stephen L. Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences (defmacro with-compilation-unit ((&rest options &key override (verbose :default) &allow-other-keys) &body body) #-excl (declare (ignore options)) (setq override (case override #+lispm (:warn :just-warn) #-lucid (:query nil) (t override))) `(#+lucid lucid::with-deferred-warnings #+symbolics compiler:compiler-warnings-context-bind #-(or lucid symbolics) progn (let (#+lispm (SYS:INHIBIT-FDEFINE-WARNINGS ,override) #+lucid (lcl::*redefinition-action* ,override) #+excl (excl::*redefinition-warnings* ,override) #+excl (compiler::*compile-verbose* (if (eq ':default ,verbose) compiler::*compile-verbose* ,verbose)) #+lucid (lucid::*compiler-options* (apply #'lucid::process-compiler-options (unless (eq ':default ,verbose) (list ':messages ,verbose)))) #+symbolics (compiler::compiler-verbose (if (eq ':default ,verbose) compiler::compiler-verbose ,verbose))) #+(or symbolics excl lucid) (declare (special #+symbolics compiler::compiler-verbose #+excl compiler::*compile-verbose* #+lucid lucid::*compiler-options*)) .,body))) From snicoud@atc.boeing.com Wed Oct 31 12:51:50 1990 Received: by atc.boeing.com on Wed, 31 Oct 90 12:51:50 PST Message-Id: <9010312051.AA27227@atc.boeing.com> Return-Path: Received: from atc.boeing.com by SKAGIT.atc.boeing.com via INTERNET with SMTP; 31 Oct 90 14:15:33 PST Received: by atc.boeing.com on Wed, 31 Oct 90 12:44:26 PST Received: by sanpoil.boeing.com (4.1/SMI-3.0DEV3) id AA05691; Wed, 31 Oct 90 14:12:08 PST From: Johanna Moore To: info-ti-explorer@sumex-aim.stanford.edu Subject: Wanted: Copy of Express Windows to run on MicroExplorer Date: 31 Oct 90 14:59:52 GMT Resent-To: express-windows@atc.boeing.com Resent-From: Stephen L Nicoud Resent-Date: Wed, 31 Oct 90 14:22 PST Resent-Message-Id: <19901031222254.1.SNICOUD@SKAGIT.atc.boeing.com> Resent-Comments: From info-ti-explorer@sumex-aim.stanford.edu Does anyone have source for Express Windows running on a microExplorer? If so, please send mail to jmoore@cs.pitt.edu indicating how I can get a copy of the software. I'd also like to know if anyone has ported this code to a DEC 2100, DEC 3100, or Sun 386i -- all running LUCID 3.0. Thank you, Johanna Moore From snicoud@atc.boeing.com Fri Nov 30 13:06:22 1990 Received: by atc.boeing.com on Fri, 30 Nov 90 13:06:22 PST Return-Path: Received: from atc.boeing.com by SKAGIT.atc.boeing.com via INTERNET with SMTP; 30 Nov 90 08:39:08 PST Received: by atc.boeing.com on Fri, 30 Nov 90 08:40:11 PST Received: Fri, 30 Nov 90 11:39:34 EST from CERBERUS.STSCI.EDU by stsci.edu (4.1) Received: Fri, 30 Nov 90 11:39:32 EST by cerberus.stsci.edu (4.1) Date: Fri, 30 Nov 90 11:39:32 EST From: Jeffrey Sponsler Message-Id: <9011301639.AA11406@CERBERUS.STSCI.EDU> To: express-windows-request@atc.boeing.com Subject: Details about EW Resent-To: express-windows@atc.boeing.com, sponsler@stsci.edu Resent-From: Stephen L Nicoud Resent-Date: Fri, 30 Nov 90 13:05 PST Resent-Message-Id: <19901130210523.8.SNICOUD@SKAGIT.atc.boeing.com> Resent-Comments: Passing on a request. - snicoud I am working on an automatic scheduling system for the Hubble Space Telescope. We have Suns and Explorerers here and I am interested in Express Windows as a portable window system for those platforms. Has EW been ported to Explorers - if not how difficult might it be to do the port. The Explorer supports a robust CLX. Thanks Jeff Sponsler Space Telescope Science Institute Baltimore MD 301 338 4565 From demers@src.honeywell.com Thu Jan 3 09:40:37 1991 Received: by atc.boeing.com on Thu, 3 Jan 91 09:40:37 PST Return-Path: Received: from horta.src.honeywell.com by src.honeywell.com (4.0/smail2.6.3/SRCv0.25); Thu, 3 Jan 91 11:42:27 CST id AA11385 for express-windows@atc.boeing.com at atc.boeing.com Posted-Date: Thu, 3 Jan 91 11:42:25 CST Received: by horta.src.honeywell.com (4.0/SMI-3.2) id AA02045; Thu, 3 Jan 91 11:42:25 CST Date: Thu, 3 Jan 91 11:42:25 CST From: demers@src.honeywell.com (Robert DeMers) Message-Id: <9101031742.AA02045@horta.src.honeywell.com> To: express-windows@atc.boeing.com Subject: Express Windows Dear Representative, I am interested in your Express Windows product. Would you please send me some information on it? In particular, I would appreciate an evaluation copy and/or a users manual. thanks, Bob DeMers Honeywell Systems and Research Center 3660 Technology Drive, MN65-2500 Minneapolis, MN 55418 tel: 612-782-7269 fax: 612-782-7269 internet: demers@src.honeywell.com From snicoud@atc.boeing.com Thu Jan 3 10:43:56 1991 Received: by atc.boeing.com on Thu, 3 Jan 91 10:43:56 PST Date: Thu, 3 Jan 91 10:44 PST From: Stephen L Nicoud Subject: Express Windows To: Robert DeMers Cc: express-windows@atc.boeing.com In-Reply-To: <9101031742.AA02045@horta.src.honeywell.com> Message-Id: <19910103184454.3.SNICOUD@SKAGIT.atc.boeing.com> Date: Thu, 3 Jan 91 11:42:25 CST From: demers@src.honeywell.com (Robert DeMers) I am interested in your Express Windows product. Would you please send me some information on it? In particular, I would appreciate an evaluation copy and/or a users manual. Express Windows does not have its own user manual per se. Refer to a Symbolics Dynamic Windows manual since Express Windows is designed to support Dynamic Windows functionality in Lucid and Franz Allegro Lisp (using CLX). What little other documentation exists for Express Windows can be found (using anonymous ftp) on atc.boeing.com in files in the /pub/ew/ directory. Stephen -- Stephen L Nicoud uw-beaver!bcsaic!snicoud Boeing Advanced Technology Center for Computer Sciences Bellevue, Washington USA From jamey@cache.crc.ricoh.com Mon Jan 14 17:55:41 1991 Received: by atc.boeing.com on Mon, 14 Jan 91 17:55:41 PST Received: by uunet.UU.NET (5.61/1.14) with UUCP id AA28884; Mon, 14 Jan 91 20:56:42 -0500 Received: by mercury.ricoh.com (4.0/6.3Junet-1.0) id AA26625; Mon, 14 Jan 91 17:33:51 PST Received: by cache.crc.ricoh.com (5.57/6.3Junet-1.0) id AA17774; Mon, 14 Jan 91 16:51:43 -0800 Date: Mon, 14 Jan 91 16:51:43 -0800 From: jamey@cache.crc.ricoh.com (Jamey Graham) Return-Path: Message-Id: <9101150051.AA17774@cache.crc.ricoh.com> To: express-windows@atc.boeing.com Subject: ew on DECstation 5000, Lucid 4.0 Has anyone gotten ew to work on a DECstation 5000, Lucid 4.0, Ultrix 4.0? My first couple of attempts have failed during the compilation of ew. The following were part of the lisp image when I tried this: WTK & CLOS (which also means CLX). When I attempt the load of load-ew.lisp it asks if I want to load CLX and CLOS and I say no because they are already loaded. I am not sure what version of CLOS or CLX is part of Lucid 4.0 the old pcl::*pcl-system-date* is not there anymore. Anyway, I guess I should describe in more detail what happened but, first, I would like to know if someone has successfully ported ew to the 5000 using Lucid 4.0. Thanx. Jamey Graham Ricoh California Research Center jamey@crc.ricoh.com 2882 Sand Hill Road, Suite 115 Menlo Park, CA 94025-7022 From kanderso@DINO.BBN.COM Wed Jan 16 12:40:32 1991 Received: by atc.boeing.com on Wed, 16 Jan 91 12:40:32 PST Message-Id: <9101162040.AA26020@atc.boeing.com> To: express-windows@atc.boeing.com Cc: kanderson@DINO.BBN.COM Subject: request Date: Wed, 16 Jan 91 15:59:06 -0500 From: kanderso@DINO.BBN.COM Please add me to your express windows mailing list. Any idea how many people are using it? k Ken Anderson BBN STC 10 Moulton St. Mail Stop 6/3C Cambridge MA 02138 USA Internet: kanderson@bbn.com Work Phone: 617-873-3160 Home Phone: 617-643-0157 FAX: 617-873-3776 From snicoud Wed May 1 10:42:31 1991 Received: by atc.boeing.com on Wed, 1 May 91 10:42:31 PDT Received: by moclips.boeing.com (4.1/SMI-3.0DEV3) id AA09734; Wed, 1 May 91 10:44:59 PDT Resent-From: snicoud Resent-Message-Id: <9105011744.AA09734@moclips.boeing.com> Summary-Line: 29-Apr mdb@zero.arc.ab.ca #Lucid Debugger Article: 4773 of comp.lang.lisp Path: bcsaic!ssc-vax!uw-beaver!ubc-cs!alberta!arcsun.arc.ab.ca!zero!mdb From: mdb@zero.arc.ab.ca (Mark Brinsmead) Newsgroups: comp.lang.lisp Subject: Lucid Debugger Message-Id: <1991Apr29.212806.5829@arc.ab.ca> Date: 29 Apr 91 21:28:06 GMT Sender: nobody@arc.ab.ca (Absolutely Nobody) Reply-To: mdb@zero.arc.ab.ca (Mark Brinsmead) Organization: Alberta Research Council Lines: 21 Resent-Date: Wed, 1 May 91 10:44:59 PDT Resent-To: express-windows@atc.boeing.com Apparently-To: express-windows@atc.boeing.com I am currently in the throws of implementing a window-based debugger interface for Lucid (Sun) Common Lisp on top of express windows. (For those who don't already know, express windows does not mix well with debuggers...) I have managed to achieve most of what I want to do, but there is one last nagging problem; how do I make the ":A" (abort) command stop throwing all the way to the lisp top level? (My applictation also has its own top level function, to which I would like to return after errors.) I have tried catching throws to system:top-level, but this does not work. Could anyone (especially anyone at lucid...) throw me a useful hint? -- Mark Brinsmead Alberta Research Council email: mdb@arcsun.arc.ab.ca --or-- mdb@[128.144.1.3] telephone: (403) 297-2662 From snicoud Wed May 1 10:50:50 1991 Received: by atc.boeing.com on Wed, 1 May 91 10:50:50 PDT Received: by moclips.boeing.com (4.1/SMI-3.0DEV3) id AA09833; Wed, 1 May 91 10:53:18 PDT Resent-Message-Id: <9105011753.AA09833@moclips.boeing.com> Summary-Line: 30-Apr mdb@zero.arc.ab.ca #Re: Lucid Debugger Article: 4786 of comp.lang.lisp Path: bcsaic!ssc-vax!uw-beaver!cornell!batcomputer!rpi!zaphod.mps.ohio-state.edu!van-bc!ubc-cs!alberta!arcsun.arc.ab.ca!zero!mdb From: mdb@zero.arc.ab.ca (Mark Brinsmead) Newsgroups: comp.lang.lisp Subject: Re: Lucid Debugger Keywords: Oh, never mind... Message-Id: <1991Apr30.004321.7673@arc.ab.ca> Date: 30 Apr 91 00:43:21 GMT References: <1991Apr29.212806.5829@arc.ab.ca> Sender: nobody@arc.ab.ca (Absolutely Nobody) Reply-To: mdb@zero.arc.ab.ca (Mark Brinsmead) Organization: Alberta Research Council Lines: 19 Resent-From: Stephen L Nicoud Resent-Date: Wed, 1 May 91 10:53:17 PDT Resent-To: express-windows@atc.boeing.com Apparently-To: express-windows@atc.boeing.com In article <1991Apr29.212806.5829@arc.ab.ca>, mdb@zero.arc.ab.ca (Mark Brinsmead) writes: |> |> Could anyone (especially anyone at lucid...) throw me a useful |> hint? |> Never mind! I figured it out. For some reason, it never occurred to me that a commercial CL debugger might actually make use of conditions and restarts. My appologies for the waste of net bandwidth! -- Mark Brinsmead Alberta Research Council email: mdb@arcsun.arc.ab.ca --or-- mdb@[128.144.1.3] telephone: (403) 297-2662 From klehr@sun.soe.clarkson.edu Thu Aug 8 23:38:01 1991 Received: by atc.boeing.com on Thu, 8 Aug 91 14:14:48 PDT Received: from sun.soe.clarkson.edu by omnigate.clarkson.edu id aa01301; 8 Aug 91 14:41 EDT Received: by sun.soe.clarkson.edu (4.1/SMI-4.1) id AA26837; Thu, 8 Aug 91 14:41:44 EDT Date: Thu, 8 Aug 91 14:41:44 EDT From: "Thomas J. Klehr" Message-Id: <9108081841.AA26837@sun.soe.clarkson.edu> To: common-lisp-object-system-request@mcc.com, common-lisp-request@mcc.com, cl-windows-request@mcc.com, x3j13-request@mcc.com, info-ti-explorer-request@sumex-aim.stanford.edu, slug-request@ai.sri.com, allegro-cl-request@berkely.edu, clim-request@bbn.com, clue-review-request@csc.ti.com, bug-clx-request@zermatt.lcs.mit.edu, commonloops-request@cis.ohio-state.edu, express-windows@boeing.com Reply-To: "Thomas J. Klehr" signup klehr@sun.soe.clarkson.edu From snicoud Tue Aug 13 11:36:36 1991 Received: by atc.boeing.com on Tue, 13 Aug 91 11:36:36 PDT Received: by moclips.boeing.com (4.1/SMI-3.0DEV3) id AA08164; Tue, 13 Aug 91 11:38:05 PDT Date: Tue, 13 Aug 91 11:38:05 PDT Message-Id: <9108131838.AA08164@moclips.boeing.com> From: Stephen L Nicoud Sender: snicoud To: express-windows@boeing.com Subject: EW List status To: EW List recipients It's been almost a year since any substantive messages have appeared on the Express Windows mailing list (express-windows@boeing.com). Because of that and other commitments on my part, I intend to close down the list on boeing.com on September 1st. Additionally, on the same date the original and Goodwill versions of Express Windows will be removed from the /pub/ew directory on atc.boeing.com [130.42.28.80]. If you are interested in picking up the task of administering the list, and/or if you know of a site that would be willing to pick a copy of EW code, please contact me at stephen@boeing.com. Stephen -- Stephen L Nicoud uw-beaver!bcsaic!stephen Boeing Computer Services Research and Technology, Computer Science Bellevue, Washington USA "I ask unananimous consent to revise and extend my remarks." Received: from glinda.oz.cs.cmu.edu by A.GP.CS.CMU.EDU id aa08044; 26 Aug 91 18:35:28 EDT Date: Mon, 26 Aug 91 18:34:47 EDT From: Mark.Kantrowitz@GLINDA.OZ.CS.CMU.EDU To: express-windows-archive@A.GP.CS.CMU.EDU Subject: test This is a test of the archive. --mark Received: from glinda.oz.cs.cmu.edu by A.GP.CS.CMU.EDU id aa23724; 30 Aug 91 18:20:33 EDT Date: Fri, 30 Aug 91 18:10:09 EDT From: Mark.Kantrowitz@GLINDA.OZ.CS.CMU.EDU To: express-windows@CS.CMU.EDU Subject: Express Windows Administration Change Cc: mkant@A.GP.CS.CMU.EDU The Express Windows mailing list and anonymous ftp site have changed from The Boeing Company to Carnegie Mellon University. Both the original and Goodwill versions of Express Windows may now be found as part of the Common Lisp Utilities Collection, in the ew/ subdirectory of the directory /afs/cs.cmu.edu/user/mkant/Public/Lisp-Utilities/ For access by anonymous ftp, ftp to any CMU CS machine (e.g., A.GP.CS.CMU.EDU [128.2.242.7]) and cd to the directory. Note that the CMU ftp daemon restricts access to intermediate directories, so one must cd to the Lisp-Utilities directory in one fell swoop. Of course, if your site is running the Andrew File System, you should be able to cd to this directory directly without using ftp. The mailing list has also changed, and is now express-windows@cs.cmu.edu An archive of mail sent to the list may be found in ew/mail-archive.text. Administrative requests (e.g., to be added to or removed from the mailing list) should be directed to express-windows-request@cs.cmu.edu Please note that although I am administrating the list and ftp site, I am not maintaining the software. Bug reports and fixes should be sent to the mailing list, not to me. If you have any questions, please feel free to send mail to express-windows-request@cs.cmu.edu. --mark Received: from glinda.oz.cs.cmu.edu by A.GP.CS.CMU.EDU id aa08873; 11 Dec 91 22:21:12 EST Received: from glinda.oz.cs.cmu.edu by GLINDA.OZ.CS.CMU.EDU id aa04709; 11 Dec 91 22:20:43 EST To: express-windows@CS.CMU.EDU Subject: [fwd: ew on lucid 4.0.2?] Date: Wed, 11 Dec 91 22:20:40 EST Message-ID: <4707.692508040@GLINDA.OZ.CS.CMU.EDU> From: Mark Kantrowitz Sorry for the delay in forwarding this message. It got buried in about 300 other messages while I was away. --mark ------- Forwarded Message Return-Path: <@cs.cmu.edu:bachrach@aragorn.stanford.edu> Received: from cs.cmu.edu by A.GP.CS.CMU.EDU id aa02435; 15 Nov 91 18:43:19 EST Received: from aragorn.stanford.edu by CS.CMU.EDU id aa17964; 15 Nov 91 18:43:04 EST Received: by aragorn.stanford.edu (4.1/inc-1.0) id AA09278; Fri, 15 Nov 91 15:40:03 PST Date: Fri, 15 Nov 91 15:40:03 PST From: bachrach@aragorn.stanford.edu (Jonathan Bachrach) Message-Id: <9111152340.AA09278@aragorn.stanford.edu> To: express-windows-request@cs.cmu.edu Subject: lucid 4.0.2 on Sparc SunOS 4.1 Has anyone been able to get express windows to work on lucid 4.0.2 on Sparc SunOS 4.1. If so, what changes (if any) need to be made to the latest release? Has anyone started to modify EW to be more like CLIM? - -- jonathan PS please reply to bachrach@psych.stanford.edu ------- End of Forwarded Message Received: from EDRC.CMU.EDU by A.GP.CS.CMU.EDU id aa04204; 2 Jun 93 14:34:05 EDT Received: from MAYA.CS.NYU.EDU by EDRC.CMU.EDU id aa21950; 2 Jun 93 14:33:30 EDT Received: by maya.cs.nyu.edu (5.61/1.34) id AA25606; Wed, 2 Jun 93 14:33:34 -0400 Date: Wed, 2 Jun 93 14:33:34 -0400 From: marcoxa@maya.cs.nyu.edu (Marco Antoniotti) Message-Id: <9306021833.AA25606@maya.cs.nyu.edu> To: express-windows@cs.cmu.edu Subject: This is a test! Hello, is there anybody there? -- Marco Antoniotti ------------------------------------------------------------------------------- Robotics Lab | room: 1219 - tel. #: (212) 998 3370 Courant Institute NYU | e-mail: marcoxa@cs.nyu.edu Received: from CS.CMU.EDU by A.GP.CS.CMU.EDU id ab06040; 2 Jun 93 15:54:47 EDT Received: from eureka.arc.ab.ca by CS.CMU.EDU id aa16292; 2 Jun 93 15:54:23 EDT Received: from skyler.arc.ab.ca by eureka.arc.ab.ca (4.0/SMI-4.0) id AA01355; Wed, 2 Jun 93 13:58:21 MDT Received: from [128.144.6.34] by skyler.arc.ab.ca (4.1/SMI-4.0) id AA16616; Wed, 2 Jun 93 13:54:08 MDT Date: Wed, 2 Jun 93 13:54:06 MDT Message-Id: <9306021954.AA16616@skyler.arc.ab.ca> To: Marco Antoniotti , express-windows@cs.cmu.edu From: gamble@skyler.arc.ab.ca (Ken Gamble) X-Sender: gamble@skyler Subject: Re: This is a test! At 12:56 PM 6/02/93 -0600, Marco Antoniotti wrote: >Hello, is there anybody there? > >-- >Marco Antoniotti >------------------------------------------------------------------------------- >Robotics Lab | room: 1219 - tel. #: (212) 998 3370 >Courant Institute NYU | e-mail: marcoxa@cs.nyu.edu Yup. I'm here. Ken Gamble Alberta Research Council Calgary Alberta Canada (403) 297-7580 email: gamble@arc.ab.ca Received: from EDRC.CMU.EDU by A.GP.CS.CMU.EDU id aa08604; 2 Jun 93 19:54:06 EDT Received: from MAYA.CS.NYU.EDU by EDRC.CMU.EDU id aa23149; 2 Jun 93 19:53:52 EDT Received: by maya.cs.nyu.edu (5.61/1.34) id AA26758; Wed, 2 Jun 93 19:53:55 -0400 Date: Wed, 2 Jun 93 19:53:55 -0400 From: marcoxa@maya.cs.nyu.edu (Marco Antoniotti) Message-Id: <9306022353.AA26758@maya.cs.nyu.edu> To: express-windows@cs.cmu.edu Subject: Express Windows (Poor Man's CLIM?) and CMUCL 16f Hello, I downloaded EW from the lisp repository and I am trying to make it run under CMUCL v16f. I have a couple of questions about the package (I hope who wrote the original package is still around to answer). 1) Has anybody tried to to the same (i.e. loading EW under CMUCL) before? 2) Why one must redefine the i/o functions (e.g. lisp:format ==> ew:lisp-format): the original functions are shadowed in the packages defined by EW, so I do not see the need for such redefinition (which seems to be the cause of CMUCL barfing on the file 'io-functions'). 3) Under CMUCL it should be possible to use the function 'system::serve-event' for X related code. Has anybody any suggestion on its use? Thanks in advance -- Marco Antoniotti ------------------------------------------------------------------------------- Robotics Lab | room: 1219 - tel. #: (212) 998 3370 Courant Institute NYU | e-mail: marcoxa@cs.nyu.edu Received: from EDRC.CMU.EDU by A.GP.CS.CMU.EDU id aa01392; 4 Jun 93 18:29:09 EDT Received: from linus.mitre.org by EDRC.CMU.EDU id aa29703; 4 Jun 93 18:28:25 EDT Return-Path: Received: from dylan2.mitre.org by linus.mitre.org (5.61/RCF-4S) id AA22049; Fri, 4 Jun 93 18:28:21 -0400 Full-Name: Myra Jean Prelle Posted-Date: Fri, 04 Jun 93 18:28:19 -0400 Received: by dylan2.mitre.org (5.61/RCF-4C) id AA19329; Fri, 4 Jun 93 18:28:19 -0400 Message-Id: <9306042228.AA19329@dylan2.mitre.org> To: Marco Antoniotti Cc: express-windows@cs.cmu.edu, mjp@linus.mitre.org Subject: Re: This is a test! In-Reply-To: Your message of "Wed, 02 Jun 93 14:33:34 EDT." <9306021833.AA25606@maya.cs.nyu.edu> Date: Fri, 04 Jun 93 18:28:19 -0400 From: mjp@linus.mitre.org perhaps. Received: from EDRC.CMU.EDU by A.GP.CS.CMU.EDU id aa01412; 4 Jun 93 18:30:01 EDT Received: from linus.mitre.org by EDRC.CMU.EDU id aa29706; 4 Jun 93 18:29:16 EDT Return-Path: Received: from dylan2.mitre.org by linus.mitre.org (5.61/RCF-4S) id AA22065; Fri, 4 Jun 93 18:29:12 -0400 Full-Name: Myra Jean Prelle Posted-Date: Fri, 04 Jun 93 18:29:09 -0400 Received: by dylan2.mitre.org (5.61/RCF-4C) id AA19337; Fri, 4 Jun 93 18:29:10 -0400 Message-Id: <9306042229.AA19337@dylan2.mitre.org> To: Marco Antoniotti Cc: express-windows@cs.cmu.edu, mjp@linus.mitre.org Subject: Re: Express Windows (Poor Man's CLIM?) and CMUCL 16f In-Reply-To: Your message of "Wed, 02 Jun 93 19:53:55 EDT." <9306022353.AA26758@maya.cs.nyu.edu> Date: Fri, 04 Jun 93 18:29:09 -0400 From: mjp@linus.mitre.org sorry I can't help.