[mcclim-cvs] CVS update: mcclim/Backends/beagle/README.txt

[Andreas Fuchs]

Update of /project/mcclim/cvsroot/mcclim/Backends/beagle
In directory common-lisp.net:/tmp/cvs-serv29201/Backends/beagle

Modified Files:
	README.txt 
Log Message:
Install documentation update to reflect the ASDF changes & recommend mcclim.asd

Date: Sun Mar  6 19:57:22 2005
Author: afuchs

Index: mcclim/Backends/beagle/README.txt
diff -u mcclim/Backends/beagle/README.txt:1.6 mcclim/Backends/beagle/README.txt:1.7
--- mcclim/Backends/beagle/README.txt:1.6	Sun Aug 22 00:42:51 2004
+++ mcclim/Backends/beagle/README.txt	Sun Mar  6 19:57:20 2005
@@ -43,42 +43,29 @@
 changes in the OpenMCL Cocoa Bridge.
 
 Compiling and running the back end currently is a straight-forward (if
-rather limiting [see note #3]) task:
-
-Optional:
-
-1.  Create a symbolic link from .../McCLIM/Backends/beagle/load-clim.lisp
-    to your home directory.
-2.  Ditto for load-clx.lisp (if you intend to run the clx backend too... there
-    are other ways to do this, but this is how I'm doing it at the moment)
-3.  Ditto for load-beagle.lisp
-
-Then:
+rather limiting [see note #2]) task:
 
+1.  Install McCLIM according to INSTALL.ASDF in the McCLIM root
+    directory.
 2.  Start OpenMCL
 3.  Evaluate '(require "COCOA")'
 
 The following are evaluated from the 'OpenMCL Listener' that opens:
 
 4.  Evaluate '(require "ASDF")'
-5.  Evaluate '(load "home:load-clim")' [See note #1]
-6.  Evaluate '(load "home:load-beagle")' [See note #4]
+5.  Evaluate '(asdf:oos 'asdf:load-op :clim-beagle)'
+6.  Evaluate '(asdf:oos 'asdf:load-op :mcclim)' [See note #3]
 
 The McCLIM Listener should now be able to be started from the OpenMCL
 Listener by evaluating '(clim-listener:run-listener)'. See the McCLIM
-installation notes for other things you might want to do. [See note #2]
-
-Note #1: If you did not create the symbolic link in (1), load the
-         "load-clim.lisp" file from whereever it is; for example,
-
-         '(load "/Users/me/McCLIM/Backends/beagle/load-clim")'
+installation notes for other things you might want to do. [See note #1]
 
-Note #2: Some of the examples provided with McCLIM do not execute when using
+Note #1: Some of the examples provided with McCLIM do not execute when using
          the Beagle back end, either because of unimplemented features in
          the back end or because of lossage in the back end. Reports and
          patches would be appreciated!
 
-Note #3: Yes, this is a little silly. For a while the Beagle back end could
+Note #2: Yes, this is a little silly. For a while the Beagle back end could
          be built into its own bundle by making use of Mikel Evins'
          Bosco framework. This framework is currently undergoing some change
          in any case so I decided to make the initial CVS version available
@@ -89,10 +76,11 @@
          currently-executing (non-graphical) application can have an event
          loop.
 
-Note #4: If you'd rather run with the CLX back end, do a load-clx instead
-         here. Hopefully it will (soon?) be possible to run with multiple
-         ports simultaneously so that both a CLX and a Beagle Listener can
-         be run side by side for comparative purposes.
+Note #3: If you'd rather run with the CLX back end, load CLX
+         instead here. Hopefully it will (soon?) be possible to run
+         with multiple ports simultaneously so that both a CLX and a
+         Beagle Listener can be run side by side for comparative
+         purposes.
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%