freenode/#clim - IRC Chatlog
Search
9:52:17
jackdaniel
I've submitted a PR which improves command table test suite and fixes numerous problems with it
9:52:53
jackdaniel
(a few days back); now I'm going to improve the command processor based on that, so menu invocations and chained gestures work
11:02:28
jackdaniel
the lead is the function add-input-editor-command (http://bauhh.dyndns.org:8000/clim-spec/24-1.html#_1322)
11:02:45
scymtym
i haven't looked into it yes, but i am interested and would like to talk about it at some point
11:02:49
jackdaniel
on top of that, there is nothing preventing in the spec to add keystrokes to :menu items
11:03:34
jackdaniel
so the only (not directly specified, but found in clim-tos) addition is to say, that if a sub-menu has associated keystroke, then lookup-keystroke-item does not traverse into that sub-menu
11:03:49
jackdaniel
instead, when the menu keystroke is hit, then that command table keystrokes "activate"
11:03:49
scymtym
but we are currently at 3 of 7 done in my list of suspected regressions and i would like to resolve that first
11:04:38
jackdaniel
(also, it is possible to implement alternative command processor like esa does; my point is that "stock" clim abstraction allows such chains)
11:06:31
scymtym
btw, do you know whether ailisp was/is interested in claiming the windows backend bounty?
11:07:03
jackdaniel
I know because I've asked him explicitly: he doesn't have issue if someone else calims the bounty
11:07:55
jackdaniel
that said the bounty program is temporarily suspended until we are able to move from bountysource -- currently cl.net works on providing a platform for continuous donations
11:09:00
scymtym
i don't think somebody else claiming it is a fair option for work based ailisp's. maybe they would agree to donating for something
11:10:02
jackdaniel
bountysource also allows that, but after the last move they have tried to make I've lost trust in that platform, that's why I've asked at cl.net
11:13:16
jackdaniel
I've only expressed my requirements regarding needed functionality; I don't think that they will be reluctant to hear ideas -- basically it is tailored at McCLIM needs right now, but they thought about similar functionality for some time before I've asked
11:14:42
jackdaniel
from IRC users I've first talked with easye, but afaik someone else works on the implementation part (and there was a brief email exchange with gendl too)
11:16:28
scymtym
sure. thanks for the information. i guess when and if the situation arises, i can just contact them
11:17:52
jackdaniel
I've received last update a month ago, Donald Ferschweiler listed current progress -- it was quite advanced; that said no eta has been mentioned
11:19:02
jackdaniel
from the financial perspective, we've agreed initially for 10% cut for the foundation, so it is basically the same as for bounty source but without trust issues
11:22:06
scymtym
i have to say that i was a bit concerned after the issue about receiving money for not listing one of the commercial implementations (i forgot which one) on the website
11:23:46
jackdaniel
either way I don't have reasons to not trust cl.net with handling that; I hope I won't have any too
13:42:35
beach
If it works out with common-lisp.net, I may post bounties there for SICL as well, but I already don't trust the commercial bounty platforms.
13:46:17
jackdaniel
I can (I was kind of involved): I've noticed that LispWorks is not listed under "common lisp implementations" on the common-lisp.net and asked about that (on the mailing list I think) why is that (I mean this resource: https://common-lisp.net/implementations)
13:47:10
jackdaniel
the answer was that allegro was one of the foundation sponsors, so they have temporarily listed only it -- that's as far as I recall
13:50:46
scymtym
beach: i can't find the discussion now, but what i remember is that redesigned cl.net website was announced and i noticed that ... ok jackdaniel already explained it
13:51:17
jackdaniel
this thread basically: https://mailman.common-lisp.net/pipermail/clo-devel/2018-October/001240.html
13:51:30
scymtym
jackdaniel: heh, i remember it as me noticing and asking somewhere (here?) about it
18:55:20
kpoeck
Hello, regarding https://common-lisp.net/implementations lispworks is mentioned now (but not cmucl)
19:11:30
jackdaniel
kpoeck: yes, I think that they have resolved right after it was mentioned on the mailing list
19:12:39
jackdaniel
I can understand what the person who decided that thought at the moment (however I don't endorse such way of thinking)