freenode/#clim - IRC Chatlog
Search
12:40:01
scymtym
jackdaniel: i didn't get to the visual appender for log4cl yet, but i have accumulated a bunch of cleanup changes on the way. would you be willing to review a pull request?
13:36:34
jackdaniel
scymtym: all looks good to me, I have some objections regarding bumping system definition requirement to ASDF >=3.1 (though BT already does that for us and we depend on it)
13:41:05
scymtym
jackdaniel: the final comment is funny because i specifically avoided UIOP:SYMBOL-CALL because i thought you wouldn't like it :)
13:42:30
scymtym
as you mention, because of bordeaux threads, the compatibility point is kind of moot
13:43:38
jackdaniel
I'd keep asd definitions compatible with ASDF 2.26, but I won't fight it if we jump into ASDF train (of constant change). I'd still add package accessors
13:44:21
jackdaniel
so if you have stronger than barely-against opinion, then go for it. in that case though I'd add error (like BT does) if older asdf is used
13:45:59
scymtym
i will keep/add ASDF: package to DEFSYSTEM forms and fix the typo in any case - those are easy
13:52:43
scymtym
ok, i will reduce the ASDF-related changes to a minimum (remove log4cl.system package, asdf:defsystem everywhere, string designators for systems) and leave the rest for later. that way, there should be no fallout from breaking clisp compatibility
16:32:23
scymtym
in case i don't any further today, this is what i have now: https://techfak.de/~jmoringe/visual-appender.ogv
16:32:47
jackdaniel
scymtym: regarding binary logging in log4cl, something what should be taken into consideration is flushing that data (so it may be gc-collected)
16:34:51
jackdaniel
regarding this "not repainting when no scroll is needed", how do you put new messages on the clim stream?
16:37:08
jackdaniel
also, are messages passed to the stream via events (and added in handle-event), or they are added asynchronously from other thread?
16:38:29
jackdaniel
while I have plans to make it working for asynchronous access, right now streams are not ready for that, so handle-event approach would be safer than that
16:39:14
scymtym
the appender basically submits a custom event to the pane. the pane makes an output record and adds it to the output history. it then recomputes space requirements and scrolls down
16:40:30
jackdaniel
I've encountered somewhat similar issue (where replay does not trigger handle-repaint so added record is not visible)
16:40:49
scymtym
i'm currently trying to figure out whether i can have presentations in the printed log message
16:54:31
scymtym
i can embed presentations in the formatted output of the log message but it's a terrible hack and i doubt it works in general