11:44:45scymtymi says "can include the usual DEFCLASS options", so disallowing some seems like a stretch. and why, anyway? if somebody needs a funcallable application frame, why shouldn't they do that
11:45:08jackdanielalso, I wouldn't mind adding some hocus pocus like you did for autogenerated metaclasses, provided that by default all application frames are basically the same
11:46:11jackdaniel"can include the usual defclass options" stipulates, that it behaves like defclass by various regards, but it does i.e something weird with superclasses (provides different defaults)
11:46:57scymtymbut ok, i see there will be no progress
11:48:05jackdanielI'll take your word for that. In that case I'll get back to the layout protocol changes review.
12:53:44jackdanieloh my, compose-space around method for clim-stream-pane does something horrible when one of the user space requirements is :compute - namely it invokes the display function just to take the result output record history and know its dimensions
16:33:05jackdanielif anyone is interested in a summary of my notes regarding the layout protocol here's the gist of it: https://gist.github.com/dkochmanski/d1dcacabcfa35886000301a8882f0b2c