freenode/#clim - IRC Chatlog
Search
11:19:29
jackdaniel
sigh, second day of groking someone else's pull request (this time the layout protocol changes by admich)
11:20:09
jackdaniel
luckily it partially coincides with my own /unfinished/ changes, so I will benefit from this (comprehension wise)
11:22:21
scymtym
i also have some changes for theses problems, but at least at first glance, admich's changes seem more comprehensive and well thought out
11:25:55
scymtym
maybe we should all fork McCLIM and then (try to) re-integrate periodically instead of for each change
11:31:59
jackdaniel
either way, I hope that after this review I'll have a consistent theory about how things should work (hopefully supported by some kind of internal document)
11:32:33
jackdaniel
n.b, I want to add a directory in documentation directory called Notes/, which has writeups (like the one I've made for presentation types), which may be future candidates for a documentation integration
11:33:47
scymtym
Notes/ seems good. in fact, we should probably add older writeups as well. like the boundary event stuff
11:37:02
jackdaniel
scymtym: n.b the suspense is killing me. you were about to provide some motivation behind introducing a metaclass
11:40:10
scymtym
jackdaniel: you said different metaclasses for application frame classes were unacceptable, i said different metaclasses seem unavoidable since users can specify the :METACLASS option. i thought you would want to respond to that. before resolving the fundamental question, discussing more detailed aspects seems like a waste of time and effort
11:41:24
jackdaniel
you said, that you want to verify, if it is allowed to prevent supplying the metaclass option, and you did (concluding that it seems to be allowed)
11:41:44
jackdaniel
so I've waited for what comes next and since you were putting a kid to bed, I assumed that this will have to wait
11:42:35
scymtym
thus application frame classes cannot be made to all use a single metaclass with or without the pull request
11:42:43
jackdaniel
defclass-like arglist, so it is also allowed to take it out of the picture. that said, we could default to /our/ metaclass, but allow specifying another - in which case user would need to know what they are doing
11:43:11
jackdaniel
I mean, "defclass-style" seems to be vague enough to allow prohibiting some options
11:44:45
scymtym
i 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:08
jackdaniel
also, 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:11
jackdaniel
"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:48:05
jackdaniel
I'll take your word for that. In that case I'll get back to the layout protocol changes review.
12:53:44
jackdaniel
oh 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