freenode/#clim - IRC Chatlog
Search
5:53:26
loke
beach: I have gotten a few messages here and there of people who has had some comments. Not much yet though.
5:53:42
loke
However, I haven't advertised it anywhere outside the Maxima mailing list and some comments on Mastodon.
5:54:15
loke
It's perfectly usable, but as long as you can't even copy&paste, it's not really viable.
7:38:27
beach
I see, yes. The only non-discrete math I have done the past few decades is some trigonometry to derive the resonator formula.
9:07:31
jackdaniel
I disagree but it would be silly (and rude) of me to ask for comments and then reject them all (2v1). I'll treat text-margin as both of you suggest
9:10:37
scymtym
do you disagree with any of the stated observations or do you value the advantages and disadvantages differently?
9:10:56
jackdaniel
but it wasn't a vote, that were three educated opinions with same weight. I value the advantages and disadvantages differently
9:11:43
scymtym
your opinion shouldn't have the same weight (imho :) since you familiarized yourself with the subject matter more than at least me
9:14:19
jackdaniel
in that case (for consistency), we'll have duplicated initargs (:text-margin and :margin-x2) and on top of that :text-marginS which will add two margins (I'm talking about the mixin)
9:15:28
jackdaniel
generally speaking in this design each margin has two slots (mutually exclusive): margin-{x1,x2,y1,y2} an {left,right,top,bottom}-margin
9:16:10
jackdaniel
first gruop is defined in terms of stream coordinates and second in terms of relative distances
9:18:42
jackdaniel
me neither, I'm just concerned that someone may read :text-margin specification as I do. also that adds two very similar initargs: text-margin and text-margins
10:19:58
loke
jackdaniel: are you OK with me fixing a small bug in the freetype renderer by pushing directly on master?>
10:24:27
jackdaniel
I wonder if we could extract freetype renderer as a separate library as McCLIM extension. If you are certain it is local to freetype renderer then I'm OK with that if you are certain about the change
13:14:29
scymtym
i'm toying with the idea of automatically making screenshots of frames (or at least panes) for documentation and testing purposes. has anybody already tried this?
13:18:13
jackdaniel
I had an idea (of course I won't do it - too many other things) to record events, so a bug report could have a serialized event sequence which could be replayed (in order to reproduce bug *exactly*)
13:19:13
jackdaniel
that would count ostensibly as a session recorder when you think about it (so you can get back in time of a *tutorial* and do your own experimentation)
13:22:59
scymtym
interesting idea. i "just" meant rendering a pane or frame into a raster image file. for example, the README could say "After startup, the application will look like this" followed by the (automatically generated) image
13:23:07
jdz
I remember when I was learning CLIM and was making my game (clones), I was doing something wrong and on every redisplay the game window would replay all previous states.
13:24:05
jdz
http://www.ltn.lv/~jonis/clones.html should be resurrected and either put into QuickLisp or McCLIM examples.
13:27:31
scymtym
jackdaniel: this is what i have (code in the org file): https://techfak.de/~jmoringe/readme-screenshot/
13:27:50
scymtym
i would like have something generic and also show the whole frame instead of one pane
13:34:26
jackdaniel
oh, I've just noticed, my PR removing "muffle style-warning" has a cute number #666. if nobody raises other concerns I'm going to merge it myself
14:13:57
scymtym
in case anybody want to try the new inspector: https://github.com/scymtym/McCLIM/tree/wip-new-inspector
14:32:02
scymtym
no, the main object is an inspector pane, but wrapping an inspector gadget (which could be a value-gadget) around that could make sense
14:53:24
beach
I am not very good with this stuff. Perhaps I can use some help. How should I test it, given that I already have a link in quicklisp/local-projects to the normal McCLIM? Remove that link, make a different one to your repository, register-local-projects, remove cache entries, recompile?
14:55:30
beach
I did something that won't work. I put a link in quicklisp/local-projects to only the NewInspector directory and attempted to use the ordinary McCLIM with it.
14:55:36
scymtym
beach: should i push to mcclim/mcclim so you can just checkout the branch? or would that risk losing work in your mcclim repository?
14:56:25
beach
I won't lose anything, but I will likely end up in branch hell the way I did a few times in the past.