(Obviously this is not always the most productive way to work...).
I don't know. To a certain extent, if library gateway-to-whatever works just like "whatever", then we have a huge win: all the doc for whatever works for
I agree to an extent but you do need to know which parts of the underlying library are not implemented or at least how to get at them. Thankfully Peter helps us here in two ways as firstly he provides details of extending Ltk and secondly the code is nicely written so even a new CL user like me can have a go at adding a function (as I did with 81% success!).
Remember, this is opensource, with no reward to the provider for the massive eeffort first to conceive a gratuitous new API atop whatever, and then to document it. Speaking of which...
Yes, I totally agree and Ltk is great as it's so easy to use. I was mainly concerned that the list was so quiet. Maybe I could help. The only thing stopping me is that I've only been programming CL for a couple of months and while I had little trouble mapping one 'missing' Tk function, there is the danger of naive optimism derived from such a simple triumph!
elsewhere someone mavrelled at the apparent abandonment of LTk. I have no insight on that, but I do know that the risk/reward on Lisp open source is borderline. Possibly related?
I hope to contribute something at some point. I've already 'taken' a lot from the community: reading c.l.l, downloaded a free Lisp, a couple of OSS libraries and the free books. So I feel I would like to write something and put it out there. But it took me 8 years to really learn C++ and so it will probably be a little while before I'm really capable of producing anything decent in Lisp (excuses, excuses...).
Phil