In my previous mail I wrote

>In order to start the window-based development environment, type
>(wt::start-composer) into the Listener (or try the menu named "Composer").
>If this results in an error, ...

PS: I forgot to mention that the Composer menues (see the Emacs menubar)
are enabled after the Composer has been started successfully. Also try
typing
:winspect <expression> into the Listener buffer. Or type :wdebug as a
command into the Listener buffer after an error has occurred and see what
happens.
IMHO the Composer development environment urgently needs renovation! It's
not state of the art any more.

Franz developers, please listen: [sprVERY-URGENT]: For Unix, WE NEED A CLIM
DEVELOPMENT ENVIRONMENT (preferrably with source code).

Maybe, the files I collected from various sources are a good starting point:
http://kogs-www.informatik.uni-hamburg.de/clim-environment/

As an addition to an environment for Common Lisp, the CLIM implementation
of a specific vendor should provide a development environment for CLIM
itself. It would be nice to have graphical representations of e.g. command
tables, a tree-like visualization of the pane structure of an application
frame, a presentation inspector (see the Genera docs :-). Ever searched an
error about why a certain translator is not active? Inspecting the
internals of the implementation of CLIM with the Composer is far too
complicated and no fun anyway. My students always complain about the
"opaqueness" of CLIM. CLIM is great, the development environment for CLIM
is poor (or not existing). I could convince our department to invest in a
CLIM development environment $-)

Kind regards,

--Ralf




---------------

Http://kogs-www.informatik.uni-hamburg.de/~moeller/