freenode/#clim - IRC Chatlog
Search
5:58:53
nsrahmad
Well, yes if I also define an :after method on writer which clears the background and repaint.
6:01:07
loke
In my opinion, it makes sense, as long as it's possible to set it and the behaviour is reasonable (i.e. it performs the repaint, etc)
6:36:53
loke
jackdaniel: That's actually a pretty good hypothesis. Funny how a word can affect your thinking like that.
6:50:21
jackdaniel
advertisment: if you want to learn some german just read trough the geometry code ,)
6:55:20
jackdaniel
regions.lisp. I.e "map-over-schnitt-gerade/polygon" -- map over intersections between segment and polygon
6:57:47
loke
Speaking of interesting code. This is code I've been working on lately. I'm trying to improve the equation solver in Maxima. The comment on top of this function says a lot:
7:00:13
loke
Yes. I have bitten that bullet. :-) In fact, I had bitten the bullet before even reading the commend, and as I was reading I was like... “riiight... So it isn't just me”
7:01:01
loke
GENVARS is a special variable that holds a list of the underlying variables/expressions that is represented by the gensyms in the EXP list.
7:01:37
loke
It's pretty insane. EXP is meaningless without the content in VARLIST to go along with it, so why do they even bother passing it along as an argument. it could all be speical variables :-)
7:01:58
loke
Anyway, I could rant about that stuff for a while. I'm pretty sure that code was originally written in the 60's.
8:56:40
beach
loke: Would you like to collaborate on developing Second Climacs, or did you have something entirely different in mind?
8:58:35
beach
I may have gone overboard in my attempt to make Second Climacs independent of the underlying GUI library. I am not pleased with that pat of it at all.
8:59:13
beach
My main work has been with parsing Common Lisp code in the buffer, because that's what I think will make Second Climacs unique.
9:23:07
beach
So I guess what I am suggesting is to abandon my overly complex GUI layer in favor of something better (written by you) and then plug in my parsing framework and my buffer representation into that better thing.
9:43:02
loke
beach: Well, my intent was to build a minimally-functional Emacs-like. That is, fundamental editing capabilities and then see where it leads me.
9:43:11
jackdaniel
I've added two more commits to the pull request with refactor-regions (they move utilities to a separate file), since this is still no semantic change I think it belongs to this batch
9:43:33
loke
I did not consider Second Climacs as a starting point because frankly, I didn't think about it. Also, you told me you wanted to finish the base first. :-)
9:43:39
jackdaniel
next batch of changes will provide faster (and more complete) implementation of region-intersects-region-p
9:43:54
loke
I'm more intersted in starting as small as possible. To make as minimally viable product as it were ;-)
9:47:00
jackdaniel
with geometry module? currently they improve nothing functionally, until know I was organizing a module to be more comprehensible
9:47:31
jackdaniel
there are some tweaks (i.e generic region-difference was not defined by ommission)
9:48:41
jackdaniel
the gist of the current pull request is that geometry module is split into multiple parts which implement parts of the protocol. so if you want to "see" something you may compare previous "region.lisp" with current "geometry/region*"
9:54:46
jackdaniel
ultimately I hope to have more complete implementation (some methods are missing) and a faster one at that
9:55:25
jackdaniel
i.e region-intersects-region-p is currently: (not (region-equal +nowhere+ (region-intersection a b))) what is a total waste - you don't need to compute full intersectio nto tell that