libera/#clim - IRC Chatlog
Search
11:50:25
lukego
oh interesting! is that a CLIM backend that outputs javascript code calling the canvas api?
11:53:22
scymtym
jackdaniel: are you generating javascript code or sending instructions to javascript code?
11:53:32
lukego
it would be neat to be able to discover this kind of stuff in some simple way e.g. if such branches had draft PRs open :) but that sounds like creating work for other people again
11:54:32
splittist
FWIW, I'm sketching out something that's communicating with the browser via WebSockets.
11:57:12
jackdaniel
splittist: I also have some hack for such thing ,) as an addendum to this backend: https://twitter.com/dk_jackdaniel/status/1379447011162873864
11:57:48
lukego
So to be honest thing big thing I'm wrestling with is opening source files and seeing Copyright notices from many of the best Lisp hackers in the known universe going back decades and worrying about how everyone's cumulative efforts haven't gotten mcclim to a version 1.0 yet. I worry that those people have somehow gotten stuck in a tarpit e.g. working on a doomed backend that later needs to be removed, and how to avoid such a fate
11:59:48
contrapunctus
jackdaniel: on the subject of documentation, what if the manual was converted to Org? I don't imagine as many people know Texinfo as they do Org, and Org colorizes source code too 🤔 (and of course it can export to HTML, info, LaTeX -> PDF, etc)
12:01:53
jackdaniel
if someone writes a decent documentation tool for common lisp (i.e in mcclim ;) I'll be happy to jump there, but doing org instead of texinfo would be too 2020s
12:07:18
scymtym
in the long run, i want to make the highlighter i used for https://techfak.de/~jmoringe/eclector-manual/eclector.html#Introduction easy to use. it can post-processes any HTML documentation with some hints
12:08:55
jackdaniel
(maybe except for "paren highlighting", but I suppose that not liking it is a personal preference)
12:09:44
scymtym
thanks, the style probably needs tweaking. the point is that appropriate "class=…" attributes in listings and also other text can be added after the fact
12:13:23
jackdaniel
it would be cool if we had a "live" documentation system (exportable to a dead-tree), something similar to a jupyter notebook interactivity-wise
12:18:28
scymtym
ideally, the documentation would consist of objects (like beach pointed out many times) and references to functions, classes, etc. could then just be the actual object presented in a suitable way. but that's a rather big departure from anything we have at the moment
12:21:59
jackdaniel
https://github.com/McCLIM/McCLIM/pull/1196 ; here's a started branch with a new ink sourcing model
13:18:00
contrapunctus
jackdaniel: re: restructuring the manual, here's a partial outline for the content I've read so far (which is up to the section on views) http://ix.io/3pVR ("->" means "move to", "<-" means "move from")
13:18:51
contrapunctus
and "(?)" is stuff I'm not quite sure where to put, or whether to leave it where it is.
13:22:18
contrapunctus
Existing explanations in the tutorials, whenever they can stand alone and are not really necessary for getting through the tutorial, will be moved to the Explanation section.