libera/#clim - IRC Chatlog
Search
7:42:54
jackdaniel
lisp123w: mind that there are some disrapencies with clim 2.0 (and while some are adopted in mcclim, the specification we follow is clim 2.0 with our own corrections)
8:17:47
lisp123w
jackdaniel: Thanks, yeah I noted that too. Just trying to read from different angles for now to understand things better, but not using it as a 'reference'
8:41:32
jackdaniel
mind that lispworks clim guide is also a good read with better separation between "programmer" abstractions and "if you really want to tinker with clim" chapters
8:42:18
jackdaniel
loke: I'm working on incremental redisplay and your issue reports (from 2018!) provide valuable test cases, thanks
10:18:03
moon-child
approximately. Some of them may have made their way there by mistake, and some of them I think I have already read
10:22:18
lisp123w
beach: It's not too bad, I'm 55 pages in on the Franz manual, so will probably finish in about 2-3 days (don't need to memorize all the generic functions listed, just understand the main topics). Then probably skim through the LW equivalent. Apart from that, I have one book on my list that will take some time and PAIP is sort of there, but I'm not really motivated to do that right now
10:24:48
lisp123w
One issue with Lisp is that its intellectually stimulating, so its easy to get into the trap of reading all the wonderful material out there
10:31:30
lisp123w
It's a bitt off-topic (but on-topic at the same time), but a McCLIM based Emacs, sans IDE, could be a big hit
10:32:21
lisp123w
Since McClim supports graphics and other advanced functionality, but has a lot of the core concepts from Emacs. I know that the IDE part is quite hard to do, but "McClim Org Mode" might prove valuable
10:34:01
lisp123w
I was thinking outside of the IDE, just basic text editing, markdown preview (as shown a few days ago), IRC, Web Browser
10:34:48
moon-child
not that something useful would be less effort than an IDE. Quite the opposite, in fact
10:36:04
beach
lisp123w: I don't think it is reasonable to have applications such as a web browser or an IRC client as part of the editor. It is done that way in Emacs because Emacs is also a Lisp system. But we have a better Lisp system, so the editor could be but one component.
10:37:03
lisp123w
I see, so better to do LispOS then McClim-Emacs (although LispOS will presumably use McClim)
10:37:36
beach
lisp123w: No need for a LispOS. Just a Common Lisp image running McCLIM and various applications.
10:38:35
lisp123w
Okay. I guess as long as there is a window manager (like moon-child noted), that's sort of the glue IMO that makes all the parts of Emacs work well together
10:38:49
jackdaniel
well, mcclim (and common lisp in fact) is a great device for big balls of mud, defining a separate irc client and a separate text editor doesn't make it unfeasible to adopt both in a single frame
10:41:53
jackdaniel
(ftr some people call these big balls of muds a "melleable software", but the former has a nice ring to it:)