freenode/#clim - IRC Chatlog
Search
8:12:46
fiddlerwoaroof
I have a tendency to go overboard when making a proof of concept :) Anyways, here's a utility for CLOS that's somewhat like my objective-c browser: https://gist.github.com/fiddlerwoaroof/444e817f915ad40edcfa50eba5aebe82
8:14:46
fiddlerwoaroof
If you load it, and then use "Filter Classes" to limit the list of classes to only those that match the regex .*-frame, the panel on the top-left ends up having way too much vertical space
8:19:22
fiddlerwoaroof
ok, so we don't have something like the graph-viz algorithms available either?
8:22:58
jackdaniel
oh, I'm wrong, we can layout the edges: http://bauhh.dyndns.org:8000/clim-spec/18-2.html#_995
8:24:27
fiddlerwoaroof
It's great coming back to clim, I forgot how much fun it was to write little gui tools using this
9:30:43
scymtym
fiddlerwoaroof: regarding the discussion in #lisp. beach was talking about https://techfak.de/~jmoringe/eclector-context-completion.ogv (and related, but older and showing other things https://techfak.de/~jmoringe/eclector-cst-toy.ogv https://techfak.de/~jmoringe/eclector-cst-toy-2.ogv )
14:07:58
josrr
jackdaniel: when you said "draggable graph allows dragging nodes"; Are you referring to the example in clim-examples? I'm asking because I'm trying to eliminate the non-exported symbols that it uses; but I can not find what I can use to access the edges. Any ideas?
14:59:19
jackdaniel
I don't see any interface in CLIM (as the specification) to access edges (or in a matter of fact even determine what kind of object they are)
15:00:23
jackdaniel
only solution I can think of would be creating non-standard-graph-output-record and specializing layout on that
15:05:46
josrr
About that, I do not understand how to do it. Every time I try to export something in that package (clime) it results in a conflict with climi.
15:06:51
jackdaniel
first add symbol to clim-extensions package in package.lisp and after that load mcclim
15:07:33
jackdaniel
so you can't add symbol from clim-internals to clim-extensions after the former is already defined - that would cause symbol conflict
15:13:21
jackdaniel
and changing that in the future would be breaking a contract with the programmer
15:31:11
jackdaniel
scymtym: I've got an answer. allegro is in the download page due to a "sponsored link" program - clisp is not there due to omission. if you are not subscribed to clo-devel you may check out the email in the ml archive
15:55:01
slyrus
our drag-output-record appears to be non-standard with the feedback-event arg instead of just feedback.
18:17:28
jackdaniel
blank area may be a presentation too (it is more natural to specify position of a newly added line/point with a pointer)
18:18:12
jackdaniel
when I invoke command "add line" and select one of the points already on the screen (they are active) I'm dropped to debugger
18:19:10
jackdaniel
so if it is not meant to be typed in an inspector, maybe inspector should not show this command (or be hidden entirely)
19:37:59
slyrus1
thanks jackdaniel. you're getting ahead of me :) haven't gotten there yet but hope to. initial step was just getting presentations working and then the dragging stuff.