freenode/#clim - IRC Chatlog
Search
6:44:10
loke
I'm coming to the conclusion that the “items” in the LINE should be grapheme clusters, not Unicode codepoints.
6:44:30
loke
This is because the items describe individual drawn elements, as well as represents the way the cursor moves.
7:27:51
beach
I didn't think much about Unicode at all. Mainly because my knowledge is very limited.
7:28:43
loke
Fair enough, but even without the added issues of Unicode, you must have worked on displa optimisation? I'm pretty sure you're not repaininting the entire window whenever a button is pressed.
7:34:38
loke
That part of the code is probably just a few tens of lines of code though so it can easily be replaced.
7:35:32
loke
Thing is, one of the reasons that repainting is slower for me is that I draw every grapheme cluster individually.
7:41:25
jackdaniel
technically speaking you may put gadgets there and specialize handle-event for pointer clicks, but you do not want that
7:41:58
loke
Note that even when I switch to output history, I will still have to track and manage directly which elements are vidible on the screen.
7:42:17
loke
I can't create output records for every grapheme in the file. Imagine a multi-MB files...
7:44:23
loke
beach: so you suggest tracking the output records for a given libne together with that line's content?
7:45:26
beach
loke: If there is nothing particular on a line other than text, you make a single output record for an entire line.
7:46:07
jackdaniel
so if you can do anything you want; and you want to do the right thing; then do the right thing ,)
7:46:39
jackdaniel
because by means of variable substitution with 'anything' we have "I know I can do the right thing (I want)" ^_^
7:47:10
loke
I'm still not sure what the irght thing is :-) But, I will keep playing around with this until I have something that works.
7:56:21
ralt
beach: sorry for the long delay in replying. I wasn't sure what CLIM was. My experience with it was the listener, which looked very cool, but didn't quite get the point across that CLIM was a GUI library. Additionally, I was also seeing everyone else use CommonQt and friends, and not many people using CLIM, if any. So I wasn't sure exactly of what I was looking at.
7:58:07
jackdaniel
(bulk of the issue solving likes on QT developer shoulders, of course getting bindings and their api correct and practrical is also a big task)
7:58:50
beach
ralt: Even if jackdaniel is right, I think it is worthwhile trying McCLIM if you have a project in mind that needs a GUI. The more people use it, the faster the remaining issues can be resolved.
8:35:45
scymtym
coincidentally, i just added the following nikodemus quote in my website-changes merge request: "Some people swear it is the best thing since sliced bread, and some people think sliced bread is better for building GUIs then it is."
8:36:01
scymtym
jackdaniel: the merge request is https://gitlab.common-lisp.net/mcclim/mcclim-website/merge_requests/1
8:42:21
scymtym
ACTION believes self-deprecating humor and an having-nothing-to-prove attitude works best with CL
8:43:24
jackdaniel
I agree (I like the quote "McCLIM, the stuff that really boring dreams are made of.")