Eckhard Lehmann <
elehm...@gmail.com> writes:
> Hello,
>
> I am about to have a closer look at Common Lisp (decided to use Emacs
> + SLIME and CLISP to do some toy programming in my spare time).
>
> Now there are some question and I would find it useful to get input
> from experienced users:
>
> - What GUI Toolkits do you use and which one is the best for Platform
> independent development?
How needs a toolkit? Seriously. Check the sokoban example, written
directly in X11:
http://www.clisp.org/impnotes.html#incmod-toys
I always compile my emacs --with-x-toolkit=no
--without-toolkit-scroll-bars --with-x.
> I have done a lot in Tcl/Tk and I am somehow addicted to Tk. is there
> a usable binding which provides all the Tk functionality, as there is
> with Python Tkinter for example? Or are there better options
> available?
Ok, so you do need a toolkit. Indeed, there's Ltk.
> - How to install extensions
> Is there a standard way to install extension libraries somewhere, so
> that the lisp interpreter (CLISP in my case) finds them?
Yes, it's quicklisp.
> - How about deployment
> What is the best way to deploy a Lisp program, once it is finished?
Again, quicklisp. You just push the sources with an .asd file to some
git server, and tell Xach about them for inclusion in the quicklisp
distribution.
> Is it possible to wrap a Lisp interpreter with all the libraries and
> scripts together, which can be copied on the client machine? Once I
> heard about a machine code compiler... is that an option? Or is there
> another way to get your fine program to your customer (who doesn't
> care about the language in which it is developed)?
Yes, you can also compile and generate an executable.
http://www.clisp.org/impnotes.html#image
--
__Pascal Bourguignon__
http://www.informatimago.com/
A bad day in () is better than a good day in {}.
You can take the lisper out of the lisp job, but you can't take the lisp out
of the lisper (; -- antifuchs