7GUI
fructure
| 7GUI | fructure | |
|---|---|---|
| 6 | 8 | |
| 54 | 443 | |
| - | - | |
| 3.2 | 3.7 | |
| 3 months ago | 3 months ago | |
| Racket | Racket | |
| GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
7GUI
-
Racket: The Lisp for the Modern Day
Looks like you're already in Emacs. I strongly recommend racket-mode as mentioned in another thread.
With regard to prototyping GUI's I'd suggest taking a look at https://github.com/mfelleisen/7GUI. https://github.com/Bogdanp/racket-gui-easy could also be a good place to start.
With regard to Racket more generally, I'm probably not the best person to ask since I had a very high friction start where I just banged my head against the wall until things made sense.
- Where to keep state for racket/gui app?
-
What programming language is good to make GUI's
Some simple examples using the Racket gui toolkit can be found at https://github.com/mfelleisen/7GUI
-
7GUIs
link: "https://github.com/mfelleisen/7GUI/",
-
If you had to pick a Scheme to write a standalone application which would you choose?
Racket has a nice gui that works across windows, Linux and MacOS, See https://github.com/mfelleisen/7GUI
fructure
-
Racket: The Lisp for the Modern Day
Even the racket teachpack libraries designed for education are very capable; I was able to make this structured editor with only using teachpack content without external deps: https://github.com/disconcision/fructure
-
Common Lisp vs Racket
Right, it's fine, and is a pretty basic macro. Doubly linked lists are pretty basic data structures too, even the Rust versions once you figure it out. I like your sibling comment making it look like the CL version. I still want to know in more detail though why you think that doing things this way instead of the CL way is less likely to be "fragile and break down" for the complicated stuff, it would help to have a specific complicated example to showcase. Perhaps the linked https://github.com/disconcision/fructure in another comment would be a good study? The author there claimed they might not have been able to manage with defmacro, maybe someone familiar with both could articulate the challenges in detail. Is it just an issue of some things benefit a lot from pattern matching, and if so, does using CL's Trivia system mitigate that at all (in the same way that using gensym+packages+Lisp-2ness can mitigate hygiene issues)?
- Fructure: A structured interaction engine in Racket
-
graph-based UI for Lisp/Scheme
see also: fructure
- Why text only.
- An Intuition for Lisp Syntax
What are some alternatives?
appy - an application framework for Racket
LIBUCL - Universal configuration library parser
rui - Declarative Rust UI library
slimv - Official mirror of Slimv versions released on vim.org
fidgetty - Widget library built on Fidget written in pure Nim and OpenGL rendered
vlime - A Common Lisp dev environment for Vim (and Neovim)
cyclone - :cyclone: A brand-new compiler that allows practical application development using R7RS Scheme. We provide modern features and a stable system capable of generating fast native binaries.
cmu-infix - Updated infix.cl of the CMU AI repository, originally written by Mark Kantrowitz
hy - A dialect of Lisp that's embedded in Python
coherence - Oracle Coherence Community Edition
racket-gui-easy - Declarative GUIs in Racket.
slime - The Superior Lisp Interaction Mode for Emacs