freenode/#clim - IRC Chatlog
Search
3:01:22
beach
Exceptionally, my favorite coauthor comes for lunch today (a Thursday) rather than on Wednesdays as usual, so I'll be off a lot, but I'll check in regularly.
4:08:41
loke
I addressed all but one of his comments. The last one is a matter of style, and I'll change that too if he insists.https://github.com/McCLIM/McCLIM/pull/498
4:10:09
loke
beach: I'm so frustrated by the way... The new scrolling is super fast and super smooth... But... There is a problem that I believe happens if the “scrolled-in” area isn't repainted fully before the next scroll event. THat causes display problems.
4:11:34
loke
Or... an alterntive... Is there a way to determine if there are more scroll events waiting?
4:18:02
loke
beach: I think what happens is that after I move the visible area using xrender, I call repaint-sheet which adds a reqpaint request to the queue? But by then, there is already another scroll request in the queue, which will be processed before the repaint actually happens.
4:18:40
loke
but what I have noticed is that if I use the arrow buttons to scroll instead, there are no display artifacts
4:20:10
beach
If I remember right, the only thing I can see is if X11 has a buffer that needs flushing.
4:24:02
loke
I seem to be getting display artifacts even when scrolling a single pixel by very carefully moving the mouse. It's like it copes the wrong pixel line
4:24:53
loke
I really want this to work. You have no idea how enjoyable it is to scroll without flickering and without slowness
4:28:51
loke
I find it entertaining. And for so many other projects, I keep doing stuff someone else already ends up doing at the same time, or has already been done.
6:13:18
loke
I'm going for lunch now. Please let me know of any issues (and even better, if you can fix any such issues :-) )
6:27:44
slyrus_
but there are definitely still some issues (off by one maybe?) -- e.g. see the pane hierarchy viewer
6:40:51
loke
I think I know what it is. THe request to repaint the exposed area is someotimes one pixel too small due to rounding
6:48:24
loke
Wow. Scriolling in climaxima is so beautiftul now, and it seems to be remarkably stable.
6:49:42
loke
beach, slyrus, jackdaniel: would you be willing to test this stuff and tell me if you're able to create problems?
6:49:56
loke
I believe this was the proper solution to scrolling uglyness. Double-buffering is not needed.
7:49:34
scymtym
loke: there may be an issue with presentation highlighting. in the "Border Styles Test" demo, i placed the (mouse) cursor over one of the presentations at the bottom (the ones with yellow highlight color) and then scrolled using the mouse wheel. this resulted in half-highlighted presentations. i can make a video if you cannot reproduce the issue based on this description
7:52:38
jackdaniel
because 'source' hints, that demo is bad, while 'indicator' hints, that it is good - if it reveals issues it is rather good
8:00:53
loke
Hmm.. noo... I can't really figure out the order of mouse-movement scrolling and repaitning that would cause this
8:01:10
loke
clearly it's an issue of the contrnt scrolling away before the repaint happens, somewhow
8:18:30
beach
I tried it with the listener, and I think I see a difference. Scrolling is pretty smooth.
8:30:23
beach
Couldn't execute "cc": No such file or directory [Condition of type CFFI-GROVEL:GROVEL-ERROR]
8:33:46
loke
You need the development libraries because of CFFI-Grovel. It would be psosible to avoid that, but it'd take some work that I dont' want to undertake right now.
8:35:39
beach
I don't see a difference is scrolling behavior. It flashes a lot. Am I using the wrong branch or something?
8:49:31
loke
if it worked, you should get a list of files that have been changed, including Backends/CLX/medium.lisp
8:50:52
beach
git checkout origin render-scroll gives me error: pathspec 'origin' did not match any file(s) known to git.
8:53:27
loke
do the following: “git clone https://github.com/lokedhs/McCLIM mcclim-loke”. Then “cd mcclim-loke” and finally “git checkout render-scroll”
8:54:56
beach
and then I suppose I need a link in local-projects and register-local-projects, and then it won't know which one I want?
8:55:22
loke
beach: well, either that... or, better, would be to temporarily rename the old McCLIM directory
8:55:51
loke
beach: as for the original git repository, just doing “git checkout master” should get you back
8:56:24
loke
beach: You're still going to have a branch sitting there with the name ‘render-scroll’, but it'll be harmless.
8:58:40
loke
Please do. I need to hear it. There are far too many brainwashed people who actually believe it's well designed.
8:59:35
beach
I am not a sophisticated-enough GIT user to give you any information you don't already have.
9:00:15
loke
beach: That's the point. I clearly ahve more Git experience than you, and I _still_ think it's an utter dung-pile.
9:00:17
beach
GIT solves the fundamental problem with SVN etc., but it does that without my using branches, rebasing, whatever.
9:00:54
beach
Whenever I try doing something more sophisticated, I ruin everything, so I no longer try.
9:03:45
scymtym
magit for emacs makes git almost bearable in my experience but it has a slight learning curve of its own
9:04:49
beach
The thing is, my ambition is to create Common Lisp software and not to become a GIT wizard. I would do both (and more) if I had the luxury of infinite time on my hands. Sadly, that's not the case.
9:05:32
beach
I am also preparing lunch for my favorite coauthor. Lunch with her is WAY more interesting that wrestling with GIT.
9:05:33
loke
scymtym: Even with magit, you still have to obey to a lot of gitisms. At least it makes resetting of changes easy... I mean, in git, seriously, using “checkout” to revert your changes... Unless you want to revert _all_ changes, in which case you use “reset”, because reasons.
9:07:32
loke
scymtym: The one thing that I still haven't figured out about magit though, is how to do “git checkout somebranch”
9:09:18
scymtym
or b c REMOTE-BRANCH-NAME RET LOCAL-BRANCH-NAME RET to checkout and track a remote branch
10:07:22
jackdaniel
database also stores tickets and wikipedia; interface is bundled with the client
10:08:23
jackdaniel
also tickets are associated with the history (so if you fix the issue with a commit, if you travel back in the history, this issue is listed as opened)
10:19:47
jdz
I've read about fossil a while ago, one of the strong points is that all commits are stored in a relational DB (sqlite?), so one can make all kinds of queries using SQL.
10:22:33
jackdaniel
jdz: fossil merge basically. fossil tries to warn you, that forking is a bad idea and tries to update before commit though. I don't know the implementation details
10:25:38
jackdaniel
git has a strong point that it is very popular and solves most of the problems; that said I think that fossil solves the same problems in a better thought manner, but I'm still experimenting with it