freenode/#clim - IRC Chatlog
Search
10:34:37
jackdaniel
that is not very convincing to me: queue-event indicates a will to put an event in a queue, how implementation handles it (i.e bypasses the queue for special events) is at its discretion.
10:35:33
jackdaniel
regarding handle-repaint, if it is not handle-repaint what implements primitive drawing on a sheet, then we need to come up with custom internal protocol for specifying how sheets are painted (i.e what calls replay)
10:36:48
beach
I am sorry, but this is too detailed for me. If you think I am wrong, go ahead with your suggestion.
10:37:50
jackdaniel
OK, thank you for writing that up and a discussion. I let some time pass and try to rethink it given all of the above
10:46:00
beach
Apparently, the demo by gilberth does something similar to what I suggested: "Drawing only happens in HANDLE-REPAINT and no where else. Altering the output history just updates a dirty region in the output history object, which is picked up by another thread which calls HANDLE-REPAINT as necessary. This even applies to sheet geometry, changing the size of a sheet does not make it to the window server immediately, but is picked up by
10:47:37
jackdaniel
right now event loop is implemented so it works even on implementations which do not have threading at all (that is worth keeping in mind that spec also suggests that applications should run in such environments)
10:48:41
loke
jackdaniel: but wasn't that part of the spec written at a time when such systems were actually used much more widely than today
10:49:30
jackdaniel
I've put recently a considerable amount of time to make it work again on single-threaded implementations (that shows I do care about that)
10:50:12
beach
jackdaniel: Right, I am not suggesting making it a requirement to be multi-threaded. All I am saying is that we should think twice before modifying the specification to rule it out.
10:50:52
loke
ACTION actually believes that having all the UI stuff in a single thread makes sense, and is in line with what pretty much every other UI toolkit does as well. That include Java and Android
11:36:32
jackdaniel
nb: fact that you have elaborated on your handle-repaint interpretation sheds more light on why you do disagree (it makes more sense than without that particular bit)
16:19:21
Inline
i found that tabify sneaks in tab characters into my files without checking for if use-tabs is set or not
16:33:00
jackdaniel
Inline: please write cleaner issue reports, it will be easier for us to process them (and that makes them more likely to be fixed in a timely fashion)
16:55:11
jackdaniel
everyone values their time above others, so asking people to review tickets which are not well formatted (or making pull requests which are code dumps) usually doesn't fly
16:59:07
jackdaniel
for instance making a honest peer review of a small non-trivial change may take a few hours (sometimes a day or more if there are doubts about some solutions) -- I'm saying that to share some experience (not to reproach you)
17:05:02
Inline
issue is this: i tabify a file and afterwards some words are almost like condensed together like (and (symbolpsym)) the thing is when i open it with emacs there's a real space, so nothing seems wrong but in climacs after selecting whole buffer and useing M-x Tabify Region on it my display is like i told at the beginning, some words seems like writ together, they are not ofc the space is there too but the cursor
17:12:41
jackdaniel
one potential cause of such thing could be that climacs may(!) measure things by words
21:54:44
jackdaniel
my last pr is not merged yet and I already have fixed for 3 another bugs waiting in a pipe