Hello,
> Does anyone still use the Motif toolkit [ ie (require 'clm), package XT] ? > The CMU graphical debugger seems to use it, but no one seems to mention it > on the list so my guess is that it is largely unused and forgotten. last year, from march till august 2001, we use motif from cmu for project! the idea wa to build a KEE system - KEE is like a database with inference and much more... I was responsable for the interface of the project - me and the person that quit later explore several alternatives of GUI's for lisp - mainly cmu! allegro was not available here at the ist campus! we found clm good but only from the docs because the machine at the campus has solaris installed and in this specific project, AI project, no one had spare time to spend to compile the clm sources to solaris... at the end i think motif was a good choise - there was garnet but this was a similar project to KEE and the object system was very similar to KEE! at the end we get the debugger and inspector for free - and that pleases me alot - we have only to added a lisp-listener to complete every thing! it was necessary more work to define better interface and correct several glitchs! for example the scroll-bars didn't scroll automaticly when more stuff was inserted! :\ be aware that for cmu motif the documentaion is not that good and i had to spend several time to figure it out with motif in the original c books and with cmu sources... it was not easy for one that knowns nothing about C motif and needs motif in lisp! - obvious lisp was better :)) lisp rulez! ;) > What is the relation between the motif toolkit that comes with CMUCL > [1] and that which is described in the Encycmuclopedia under the heading > 'CLM -- A Language Binding for Common Lisp and OSF Motif' at [2]? i think some else anwser this in a previous reply... but cmu motif comes for "free" in the sense that we only must download it for the specific platform and just do it... > The reason why I am asking is that I can't get certain features to work > in the cmucl motif interface though they are described in the docs of CLM. > For example, I think I should be able to make a non-resizable toplevel > window by > (xt:create-application-shell :allow-shell-resize NIL) > following the examples in [2], but the window always turns out to be resizable, > which messes up my attempts at making a robust drawing widget. Also, > I can't seem to be able to figure out how to make a drawing area of > a fixed size: > (xt:create-drawing-area parent-window "name" :height 100 :width 100) > seems to expand the window beyond its requested size. this specific questions i can't anwser now! its been a while that i don't work with motif - but the debuger in cmu with motif can simplify debuging - most of the times ;) > Incidentally, the Motif interface seems quite spiffy, and adding a small CLOS > interface between XT and the lisp world might make a perfectly nice standard > graphic toolkit for CMUCL. clos its a good idea - we also use gray streams for the lisp-listener and several other graphical-streams for better code - lisp code ;) we had a lisp-listener, a viewport-listener and a graphical-stream the idea was to use (format ...) for a graphical stream :)) - only in lisp :)) > [1] eg > http://www.isr.ist.utl.pt/library/docs/encycmuclopedia/doc/x/motif-toolkit.ps) > > [2]eg > http://www.isr.ist.utl.pt/library/docs/encycmuclopedia/doc/x/clm.ps > > [3] eg > http://www.isr.ist.utl.pt/library/docs/encycmuclopedia/doc/x/motif-internals.ps just another note: it seems that isr at ist.utl.pt is a good investigation center but the docs and sources/binaries could be outdated! for this particular docs i don't think they are but the binaries could be - be aware of this... also see www.cons.org/cmucl - the original cmu common-lisp! hope this helps ps: you also have garnet...
