Newbie FAQ #2: Where's the GUI?

I know this is a FAQ, but I still don't have any answers, at least
answers that I like.

But let me ask it in the most vulgar way possible, with blunt
observations:

Where's the GUI?

* McCLIM is a wart. If someone honestly thinks I should pursue this,
I'm all ears. Otherwise, it is slow, incompatible with today's GUI
standards, and too big for its own good. I mean, it takes five minutes
to start up the demodemo.

* A lisp-qt thingy would be ideal for me, since I love Qt. If someone
has some ideas, then I am open. I looked at the CFFI-Qt attempt over
at Sourceforge (lcq I think it is called) and it seg faults on me. I
don't know how to approach seg faults in lisp. If someone has this
working, a tutorial would be very nice.

* I have a bias against Gtk. I think it stinks. But I am open if
someone says that this is the best way to go, I'll give Gtk another
chance.

* I took a passing look at Cello, but it seems to be almost 2 years
since anyone has done anything on it. I'll give it another chance if
someone says it's worth the time. Cello seems to be the right way to
go based on its mission statement. After all, you aren't confined to C
(Gtk) or C++ (Qt) when you code in lisp, so you don't have to limit
yourself to their conventions. A "Getting Started" guide for a newbie
like me that is still experiencing the thrill of discovering things
like multiple return values would be nice.

I am totally opposed to closed source or restrictive licenses. I have
just had too many good experiences dealing with the licensing issues
of GPL/BSD/MIT/Perl/etc... licensed code, at both work and play, to
give any other type of license a fair shake. If I can't legally look
inside, modify, and share it with people openly, I don't want to touch
it.

Finally, I think there are far too few evangelists in the lisp world.
(There are plenty of lisp evangelists outside of the lisp world,
though.) If you do something a certain way, don't be ashamed of
standing up and telling people that your way is the right way. When I
am learning the ropes, it is so much easier to simply rely on someone
else's experience, even if ultimately I will discover it is flawed. If
you really like your way of doing GUIs in lisp, by all means, be proud
and let me know.
.

Relevant Pages

  • Re: Making Lisp popular - can it be done?
    ... But let’s remember that the Lisp vendors grew into their markets. ... their lisp without any limits for noncommercial USE for free. ... it is also misleading because Scieneer ... commercial or academic use, and many such licenses have been issued, ...
    (comp.lang.lisp)
  • Re: A (non-negative) what is LISP good for?
    ... Cello was supposed to answer the Lisp ... Or does py-gtk somehow use libglade where Gtk normally does not? ... - one of the cells-gtk users felt Gtk look-feel was superior to the other portable GUI option, ... - as for Cells and GUIs, a little software shop called Adobe is reporting huge productivity gains from their parallel Adam/Eve hacks. ...
    (comp.lang.lisp)
  • Re: Making Lisp popular - can it be done?
    ... But let’s remember that the Lisp vendors grew into their markets. ... it is also misleading because Scieneer ... commercial or academic use, and many such licenses have been issued, ... make the Scieneer CL available for free while funding development then ...
    (comp.lang.lisp)
  • Re: Identifying CL Implementations?
    ... The GNU/FSF looks into it and sure enough Peter is using GPL/LGPL lisp software and just by using the GLP/LGPL code in his closed source products, Peter is in a legal gray zone because the way lisp variants actually work is not properly covered by the licenses. ... I think the LLGPL is much more appropriate for Lisp code, but there's nothing mysterious or gray about the LGPL that prevents using it in commercial work. ...
    (comp.lang.lisp)
  • Re: (Prolog + LISP + Erlang) with integration issues versus C++
    ... > more than a few licenses. ... > I think lisp isn't very popular because it lacks serious 3rd party library ... Isn't this part irrelevant since the development team already was ...
    (comp.lang.lisp)