freenode/#clim - IRC Chatlog
Search
9:39:21
jackdaniel
I'm going to merge the cleanup panes PR, it is not controversial and will reduce number of pr's by one
9:40:30
|3b|
yeah, cl-opengl works with cl-sdl, glop, glfw, direct OS calls etc (just not things like CLX that skip ffi completely)
9:52:39
scymtym
jackdaniel: shouldn't *DOUBLE-CLICK-DELAY* be in events or input? the description sounds like it is intended to be used when producing (the currently unimplemented) POINTER-DOUBLE-CLICK-EVENT
10:06:59
jackdaniel
I was contemplating removing the parameter whatsoever and inlining the value in the gadget implementation, but that would involve semantic changes (so to speak), while I've tried hard to make it only a cleanup of file organization
10:10:32
scymtym
i assumed as much, but it seems like the intention was using it for POINTER-DOUBLE-CLICK-EVENT which we should implement at some point (it is in the specification)
10:11:27
jackdaniel
I do not contest that, when it is implemented then the parameter may be moved and options-pane implementation properly adjusted
10:24:59
jackdaniel
n.b we have an internal generic function frame-schedule-timer-event without 1) any implementation, 2) nobody uses it; I've just noticed that
10:27:26
scymtym
i don't know what the right way forward with respect to CI is. i can generate a very good setup for Jenkins which catches this sort of thing, tracks warnings, runs and asses tests and even builds the documentation, but the barrier seems to be too high for people to at it at all. GitHub's stuff, on the other hand, is convenient and accessible but cannot (without insane hoop jumping) do nearly as much
10:30:01
scymtym
because things stop working properly if GitHub doesn't work OR the Jenkins stuff doesn't work
10:30:36
jackdaniel
sure, but being able to see warnings directly in the pull request (or being referred to do so) greatly improves experience of using CI
10:30:57
scymtym
maybe nisar wants to extent his recipe based on the one i made available. that would give us something in between
10:33:03
jackdaniel
given no reply in the issue thread regarding ci, I think that he would not oppose replacing it with something else either. if it were me doing that (I'm not planning to; it would take ages for me to setup that), I'd try to integrate github and your jenkins setup
10:33:24
scymtym
by the way, i revived the stopwatch demo in some branch. not sure which timer event scheduling method i used
10:35:43
scymtym
which seems more idiomatic than the timed-condition-waiting-in-a-thread stuff it does
10:36:33
jackdaniel
schedule-event did not work until august last year when I've refactored input module