libera/#clim - IRC Chatlog
Search
8:08:13
lukego
Yeah, I'm planning to write that code next. Just now I have constraints like (AND (= X2 (+ X1 20)) ...) defining the geometry of each part. I'll change that to (OR (AND ...) (AND ...) ...) so that the solver can consider several options.
8:09:47
lukego
Maybe I can also assign weights to the options e.g. so that the solver will prefer 90-degree orientations rather than 45-degree ones, or that all other things being equal it would prefer to use larger sizes of capacitors/resistors that are easier to assemble, etc.
10:50:42
jackdaniel
lukego: visibility-wise you may add # before lisp and clim (for sake of discoverability by other lispers)
10:52:47
jackdaniel
contrapunctus: you've mentioned restructuring the documentation to follow a principle of four different modules in it - I can see there 3 (and if we take off "introduction", then it is 2)
11:04:38
scymtym
jackdaniel: i think contrapunctus was referring to the four modes in the document they linked: https://diataxis.fr/
11:05:02
contrapunctus
jackdaniel: ah, right. The four are tutorials, how-to guides, explanation, and reference. I usually add an introduction alongside them, as is the case here. How-to guides are about "real world" tasks which can be achieved through the software...and I can't really think of any just yet (I'm not very experienced with GUI work). But I'd definitely like to separate some of the explanation from the tutorial
11:10:15
contrapunctus
(I saw that there's a reference, but I have not looked into that yet, so I kept it out of the "partial outline for the content I've read so far".)
11:12:55
jackdaniel
using views (if I understand that chapter correctly) definetely belongs to how to
11:13:35
jackdaniel
building mcclim along with bundled applications would a reference too, eventually how-to (how to build mcclim)
11:14:10
jackdaniel
output recording, display time, commands, incremental redisplay and views indeed belong to explanation, I'd add frames there too
11:14:46
jackdaniel
pjb: yes, I've fixed the issue you have mentioned in the mcclim repository; my point of leaving a comment that the pixmap representation is unspecified was strictly informative
11:21:12
contrapunctus
jackdaniel: cool ^^ I guess the installation process in the tutorial can be the quick and easy way (quicklisp), and building can go to how-to, as you say. (But McCLIM already has a README outlining installation, so maybe one can just link to that to avoid duplication and "drift".) It's okay to cover the same topic in different sections (each probably linking to the others); each section just has a diff
11:22:01
jackdaniel
I don't think that the documentation should rely on information provided in readme