freenode/#clim - IRC Chatlog
Search
10:52:17
jackdaniel
(there is a polish silly song: "była sobie żabka mała" - re re kum kum is the noise of the frog and kum phonetically-wise would be qm)
11:08:11
scymtym
now that i have a bit of time, the first thing i'm going to do is making another attempt to merge the new inspector into master
11:15:38
jackdaniel
another mini-project suggestion: see if user-command-table works and write a short guide how to use it to add (i.e) interactor commands to 3rd-party applications
11:18:30
jackdaniel
(I thought it is sort of global-command-table duplicate but for the end user to extend and disable/enable it on demand)
11:32:51
scymtym
so my plan is: 1) make a new branch based on the wip-new-inspector branch 2) remove all non-inspector commits and things that don't work with mcclim master 3) rename everything such that it replaces clouseau 4) collapse the ~ 150 commits to a couple of commits 5) make a pull request
11:40:56
jackdaniel
when you get to it I think that user documentation would be more useful as the first thing
11:41:35
scymtym
do we have established conventions for user documentation? if not, i would just write an org-mode file
11:43:09
jackdaniel
most documentation is in texinfo, beach converted part of it to latex, but I find the former better suited. as of the future, I believe we should use a CLIM tool to document things, but as many things work on it is stalled on my side
11:43:43
jackdaniel
if you write org documentation, then I think it would be better to put it in the same directory as the inspector itself
14:12:23
scymtym
is this enough as initial user documentation: https://github.com/scymtym/McCLIM/blob/merge-new-inspector/Apps/Clouseau/USER.org ?
14:21:44
ck_
maybe don't capitalize Boolean, I'm not sure. // replace the tree of inspected object -> of an inspected object (or of inspected objects) // with a new one root -> with a new root? with a new one, rooted at? // object that in which evaluating the given form resulted -> object that is the result of evaluating the form.
14:22:19
ck_
scymtym: in general, it feels a little like the explanation starts in the middle of things, if you know what I mean
14:23:55
ck_
So from the readme.md I know how to start the inspector and what it looks like. USER.org talks about embedding it into applications -- what does that mean? Is it any more involved than allowing the inspect function to be called from within an application?
14:24:48
ck_
Maybe but something a little like the readme.md screenshot, together with some context, at the beginning of USER.org is what I'm saying
14:28:39
scymtym
ck_: thanks for the feedback. i know what you mean. i was trying to get away with the bare minimum. i'm adding "The inspector window" as a new section with a screenshot near the beginning
14:44:51
ck_
scymtym: yeah that's a good contextualization, I'd be happy with that as the first inspector-related document I read
18:20:23
scymtym
ck_: i will probably go through the TODOs once more, maybe write a bit of developer documentation and think about backward compatibility before submitting the pull request
18:54:15
ck_
o_O does anybody know about an issue with the highlighting (I mean the box around presentations) in which a division by zero is signalled?
18:55:00
ck_
in DREI:: DRAW-LINE-STROKES -> STROKE-DRAWING-FN -> CALCULATE-STROKE-WIDTH -> ROUND-UP -> (TRUNCATE 144 0)