Search
Sunday, 17th of March 2019, 4:18:51 UTC
6:57:26
phoe
well, nope, the modern compilers are too dumb to do what I want
6:58:03
phoe
I'll need to either fork simple-rgb and include it in Quicklisp or copy the relevant code part somewhere else and include it in Quicklisp or use a version that isn't inline
9:42:25
phoe
Shinmera: qimageblitz? I haven't heard about it at all
9:44:54
phoe
How do I use it at all? I can't really see any manuals for it.
9:46:53
phoe
I see a "Blitz::HueShift" method, I just gotta figure out how to use it
9:51:27
phoe
(qtools:q+apropos "hue-shift") ;=> Q+::BLITZ.HUE-SHIFT
9:51:35
phoe
but Q+::BLITZ.HUE-SHIFT is not exported, does not name a function, does not name a variable
9:51:43
phoe
this is after (ql:quickload :qimageblitz)
9:56:06
phoe
...it would be God damn nice if there were *any* examples of this library actually being used
9:57:08
Shinmera
things are not exported or have a function in q+ until you use them
9:58:17
phoe
how do I use them other than by using them
9:59:04
Shinmera
use ensure-q+-method
9:59:13
phoe
...wait a second, how the hell do I actually use this
9:59:21
phoe
https://api.kde.org/kdesupport-api/kdesupport-apidocs/qimageblitz/html/classBlitz.html#a6fb3d8a66fd1673efb84e160ae20089d
9:59:21
Colleen
api.kde.org/kdesupport-api/... Website (HTML), Title: Blitz Class Reference
9:59:40
phoe
a hue shift shifts RGB channels at once and yet this requires me to provide a single channel...
9:59:45
phoe
...and two images instead of one, for whatever reason
10:00:22
Shinmera
it's so you can shift per pixel
10:00:42
phoe
I don't understand - all I need is a single image and a radius
10:01:28
Shinmera
use another image that's all white I guess
10:02:05
phoe
but why would I need to cons up another qimage to use that function
10:02:51
phoe
and which RGB channel do I pass
10:03:06
phoe
this interface is so generic that I could transmit a hamburger through it
10:04:00
Shinmera
I think you can make the modImg just 1x1
10:04:18
Shinmera
should be able to even make it just single-channel
10:05:27
Shinmera
it seems to use wraparound lookup in the function
10:18:35
phoe
okay, it's more or less working
10:18:51
phoe
now to figure out what the "modulation value" I pass and the color of the mod-image mean
10:25:03
phoe
rotation = (factor / 100) * (rgb_value / 255)
10:25:20
phoe
rotation = factor * rgb_value / 22500
10:26:22
phoe
That's going to hold true for a single-pixel mod-image.
10:40:30
phoe
you know you're likely overdoing things when you end up solving a hyperbolic equation over integers to find the best values for the modifier and color
10:42:49
phoe
it's a little limiting that this function only effectively accepts integers between 0 and 100 as modifiers
10:47:00
phoe
...siigh, what's worse, setting the modifier to 200 doesn't bring me back to where I started
10:49:20
phoe
it needs 207 to bring me back to the original, and ten times that already deviates from the original color
11:08:53
phoe
Shinmera: image-tools, qimage-tools, or qimagetools?
11:09:37
phoe
there's already svgtools so I guess the last one would make some sense.
11:14:52
Shinmera
qtools-ui-imagetools sounds fine to me.
11:29:06
phoe
https://i.imgtc.com/fDj9xz9.png
11:29:07
Colleen
i.imgtc.com/fDj9xz9.png Image (PNG)
11:29:16
phoe
looks like it more or less works then
11:29:27
phoe
lemme upload hue-shift to a branch
11:53:05
phoe
look ma, I'm contributin' to free software projects online
12:23:39
phoe
Why #:process-executions is exported from executable.lisp?
12:23:47
phoe
It's a slot name, you generally don't seem to export those.
12:30:19
Shinmera
you can't export slots and the slot method does not have that name.
12:30:51
phoe
"(define-slot (executable process-executions) () ...)"
12:30:56
phoe
that's what I read in executable.lisp
12:31:04
phoe
oh right, but the method is named differently
12:31:15
phoe
still, you don't consistently export signals from everywhere
12:31:25
phoe
like, repl.lisp has two unexported signals
12:31:26
Shinmera
some signals are meant to be used, others are not
12:31:33
phoe
welp, so it's even more tricky
12:31:51
Shinmera
an executable is obviously a very generic thing
12:31:55
phoe
how do we document these signals then? we'll need a documentation type
12:31:58
Shinmera
and its signal is meant to be used by a subclass
12:32:19
phoe
and a backend for that documentation type
12:32:39
Shinmera
Signals are not global
12:32:45
Shinmera
they cannot be documented in the same way
12:33:01
Shinmera
document them in the class documentation.
12:33:53
Shinmera
A shortcoming in CL's documentation facility
12:34:15
Shinmera
Can't document restarts and such either, for instance.
12:34:49
Shinmera
I hope to help that problem with Definitions, but I'll need time to work out a protocol for local definitions first
12:35:04
phoe
in executable's docstring, "Accepts a signal named PROCESS-EXECUTIONS." will do?
12:35:36
Shinmera
Write what it does, too.
12:41:20
phoe
"A qobject superclass that allows running functions within the GUI thread.
12:41:24
phoe
Accepts a signal named PROCESS-EXECUTIONS."
12:41:28
phoe
this, plus SEE definitions
12:42:29
Shinmera
"Accepts a signal named PROCESS-EXECUTIONS. When signalled runs all pending functions.
12:47:20
phoe
okay, I'm slowly building up a pile of new docstrings at #17
12:47:28
Shinmera
Yeah I know, I get emails
12:51:10
phoe
OK - I'll let you know when I'm done with them.
13:29:58
phoe
I've noticed that (qtools:with-main-window (window (make-instance 'qui:notification :message "a"))) doesn't auto-close for me. Is it supposed to close when invoked that way?
13:30:49
phoe
It disappears only after I click elsewhere.
13:36:25
phoe
so - only configurable, dialog, and options are left
13:36:28
phoe
dialog, because it's borked
13:36:35
phoe
the other two, because hell if I understand that mechanism right now
13:37:44
phoe
anyway, I guess the branch is now more or less ready for review
13:39:05
phoe
...oh, I missed PLOT - you don't export its symbols at all
13:39:46
Shinmera
there's plenty of unfinished stuff in the repo
13:54:26
phoe
holy cow, the option framework is pretty damn big
13:54:38
phoe
nope, I'm not documenting that one
15:11:14
Shinmera
phoe: your PR somehow has merge conflicts
15:11:27
Shinmera
did you ammend a merged commit or something?
15:39:22
phoe
I didn't base it off the freshest master with hue-shift merged
Sunday, 17th of March 2019, 16:18:51 UTC