libera/#commonlisp - IRC Chatlog
Search
6:50:58
jackdaniel
no, in this case it was another silly joke; when you train neural networks answers are nudged towards the "optimal" answer :)
6:52:47
beach
Shinmera: Yes, I can imagine that. But the needs of Kandria might be a bit special compared to a desktop GUI library.
6:53:35
Shinmera
Then I don't know how to answer your question because in my mind there's an infinity of widgets and things and tools to add to a GUI toolkit, and as such it's never complete.
6:55:00
Shinmera
It has all the basic stuff like text input, combo boxes, toolbars, switches, scroll views, etc.
7:03:42
Shinmera
though it does not yet support many unicode features like bidi, combined diectretics (esp emoji), vertical text layouting, etc.
7:04:03
Shinmera
I did write the uax-9 library to support bidi in the future, but have not integrated it yet as there's currently no need.
9:00:09
pve
Good morning! Is it reasonable to provide default initargs to make-instance that may be "overridden", like in this situation, where I want to inherit properties from a parent object:
9:01:56
pve
an alternative would be to set the properties using accessors, but I can't really tell which is preferable
9:14:03
prxq
ah so only the values provided as initargs in the spawn-foo function should overwrite. Then yeah I guess you can do it this way.
9:15:57
pranavats
Also, initforms are different from default-initargs. initforms are default values for slots, default-initargs are default values for initargs. The latter is assigned before initforms.
9:21:13
pranavats
This article explains the differences between the two: https://courses.cs.northwestern.edu/325/readings/clos.php
13:50:35
bitblit1
Hello everyone! Is there a cross platform way to get command line arguments (any libraries) or is it better I just manually do #+clisp ext:args or whatever
14:45:21
bitblit1
I have seen many programs in common lisp which don't update in real time. Whereas programs like McCLIM and CEPL update as you recompile your code. Is there any reason for this. I don't understand how you make code update on the fly in common lisp.
14:57:04
pjb
bitblit1: you need to structure your program to be able to update on the fly. This is automatic for notinline functions, but for the other functions, you need to ensure that the main loop is replaced by the new version, so that new code is taken into account.
14:57:45
pjb
bitblit1: that said, the main loop doesn't need to change often, so just having it refer notinline functions (eg. functions compiled in a different compilation-unit), would be enough in most cases.