18:55:04slyrus_hmm... I guess so, but it would seem to me that CLOS/MOP give us all the infrastructure to deliver a clean API (defclass/make-instance). Instead we end up with some hand-rolled set of macros. I agree that some of the cleverness is half-baked. Would be nice to see it removed or fully-baked.
19:01:13jackdanielalso I would be puzzled, if I've seen (defclass foo () () (:panes …) (:layouts …))
19:01:27jackdanielbecause these clearly are related to the application frame, not the class
19:02:01jackdanielmoreover :panes and :layouts section are both evaluated in a dynamic envifonment, where the instance is already present
19:02:13jackdanieland where clim:*application-frame* is bound
19:03:00jackdaniel(I don't like clever abstractions, they are hard to grasp and even harder to debug)
19:03:44jackdanielbut I acknowledge that from the api standpoint that would lead to some gains
19:15:41makomojackdaniel: thanks for the video! looking forwarding to watching it :-)
19:18:19jackdanielmakomo: sure, I hope you'll like it
6:42:00karloszthis shows the list of projects that gnu is doing, for example
6:43:14karloszi think your various projects like mcclim etc may qualify as organizations that you can apply to be part of gsocs, if that is something you're interested in
6:43:33jackdanielI like this two-column table design