I'm implementing 7GUIs in #McCLIM. Here's some work in progress for the timer challenge.
https://eugenkiss.github.io/7guis/tasks/
I'm implementing 7GUIs in #McCLIM. Here's some work in progress for the timer challenge.
https://eugenkiss.github.io/7guis/tasks/
Using SBCL and McCLIM I wrote an Interlisp tool in modern Common Lisp with a CLIM GUI. That's what happens when one is having too much fun with Lisp.
https://journal.paoloamoroso.com/an-interlisp-file-viewer-in-common-lisp
Using SBCL and McCLIM I wrote an Interlisp tool in modern Common Lisp with a CLIM GUI. That's what happens when one is having too much fun with Lisp.
https://journal.paoloamoroso.com/an-interlisp-file-viewer-in-common-lisp
@sigue @jackdaniel @amoroso -> GenEd system by Michael Wessel using CLIM. It can recognize for constellations of graphical objects based on descriptions of relationships. For example it could recognize bubbles, rectangles, text and arrows to be parts of a type of graph. Or think of other visual representations like state charts, various networks, ... One could "draw" things and the system would assemble them into higher-level concepts as the user interacts with them.
still not working as intended, but I've hacked accepting-values-pane into #McCLIM (not part of CLIM 2 spec) and added a few kludges to GenEd and it loads and starts from asdf, so hurrey :)
n.b it prompted me to actually start implementing accepting-values-pane before the release.
Isn't the recognizer just the piece that (for example) takes the pointer location and figures out what object it correlates to? In which case CLIM already contains a recognizer. Well, I haven't read the paper so I'm probably barking up the wrong tree.
Semi-related, I have wondered many times about the relationship between the modern web and CLIM and how hard it would be to implement a CLIM-like programming interface for making web apps. That is, to get the much fancier interfaces that the web offers together with the high-level programmer interface provided by CLIM. Has this been done already?
I've attached a screenshot from the paper. Recognizers work ~like this:
Say that you have a rectangle, and inside a few output records with text put one below another.
A recognizer could suggest that the top-level rectangle is a frame, then infer that text one below another are paragraphs of a single body of text. According to the paper this process would be interactive where the user can modify system inferences, so that would be like a dialog.
Regarding CLIM on the web, I'm experimenting with porting #McCLIM directly to a browser using #ecl (that works as an webassembly program) treating <div> elements of certain class as sheets etc.
Finally I have worked through my subtle OpenGL bugs and have working SDF font rendering via pre-loaded VBOs with precomputed UV and geometry data.
There is still a lag with pointer highlighting but the stream test stays snappy and doesn't get progressively slower with each event displayed.
Finally I have worked through my subtle OpenGL bugs and have working SDF font rendering via pre-loaded VBOs with precomputed UV and geometry data.
There is still a lag with pointer highlighting but the stream test stays snappy and doesn't get progressively slower with each event displayed.
#oop #programming #GUI #commonLisp #McCLIM #softwareEngineering
Article in which I show simple multiple inheritance and method qualifiers in ANSI common lisp's common lisp object system, then show how the McCLIM implementation of the common lisp interface manager 2 specification turns the objects I was working with into rich general user interfaces with a minimal declarative effort presupposing that I was presenting lisp objects.
Rich interfaces pervade lisp's history.
https://screwlisp.small-web.org/clim/basic-principle/
#oop #programming #GUI #commonLisp #McCLIM #softwareEngineering
Article in which I show simple multiple inheritance and method qualifiers in ANSI common lisp's common lisp object system, then show how the McCLIM implementation of the common lisp interface manager 2 specification turns the objects I was working with into rich general user interfaces with a minimal declarative effort presupposing that I was presenting lisp objects.
Rich interfaces pervade lisp's history.
https://screwlisp.small-web.org/clim/basic-principle/
#lispGameJam #commonLisp #programming #devlog #commonLisp #mcclim #nicclim #gamedev #itchio in which I play with the make-my-own-level player activity. (It's unix-surrealism-jam not just NicCLIM because it is built around the unique unix-surrealism-jam controls not my preexisting NicCLIM's)
Article: https://screwlisp.small-web.org/lispgames/my-common-lisp-game-jam-self-experience/
Jam submission https://itch.io/jam/autumn-lisp-game-jam-2025/rate/3822491 ,
my fellow jammers:
+
Pixel Outlaw's #interlisp https://itch.io/jam/autumn-lisp-game-jam-2025/rate/4015363
@mdhughes ' MUD https://itch.io/jam/autumn-lisp-game-jam-2025/rate/4002647
#tootcoding #NicCLIM ( #gamedev #devlog ) #programming #fedi #McCLIM #commonLisp
In this article I am further investigating collaborative fediversal learning and programming.
(ql:quickload :mcclim)
(compile-file #P"~/Downloads/nicclim.lisp" :load t)
(in-package :nic)
(require 'bordeaux-threads)
(require 'uiop)
(uiop:chdir "~/GAME/") ; you do you.
(rect-file 'garden 5 5 '(soil))
(bt:make-thread
(lambda ()
(in-package :nic)
(enclose-map 'garden)))
#lispyGopherClimate
https://communitymedia.video/w/1iDniLCpYPSPjxFww6TzJ9
#climateCrisis #haiku by @kentpitman
Thinking about scarcity.
Interesting #IT notes from @AmenZwa recently
@jackdaniel 's #McCLIM #commonLisp multi-input ! (And moving towards #WECL for a few weeks)
https://functional.cafe/@jackdaniel/115334363009353916
- My #NicCLIM #gamedev and Dungeon Crawler Carl #bookReview (AMA in #lambdaMOO #live)
https://screwlisp.small-web.org/lispgames/nicclim-alpha-part-iii-map-edit-macros
I'm sure there was another topic. I think now just ping me in the hour before the show if you would like to be a guest