freenode/#clim - IRC Chatlog
Search
7:55:34
jackdaniel
do we have away to disable command "echo" in the interactor when defining a command?
8:56:03
scymtym
do you mean that after entering and confirming the command, the line would be cleared so that just the prompt remains?
8:56:57
scymtym
(and, relatedly, the :echo option has the issue that even with :echo nil, a fresh line and a new prompt is produced)
8:58:40
jackdaniel
right, I want some commands to be silent (i.e not inserted in the interactor) after calling execute-frame-command (i.e from another thread)
9:04:09
scymtym
not inserting the command in case of EXECUTE-FRAME-COMMAND could be ok regardless of any :ECHO option, i think
9:05:02
jackdaniel
perhaps, on the other hand I'd like to see some commands there (just not the "noise" commands without a name, like an asynchronous logger inserts)
9:05:08
scymtym
it would make sense (to me) to only insert commands that are typed by the user or translated by a translator with :echo t option (or rather absent :echo nil option)
9:06:43
scymtym
i use events rather than commands for asynchronous application logic, but i have to admit that those are also not a perfect fit
9:07:59
jackdaniel
I've been recently exploring non standard frame manager concepts and that led me to a conclusion, that if the application logic is contained in commands, it gives a certain advantage for writing non-orthodox backends
9:09:35
scymtym
my primary concern is usually reusability of components. if i make a pane that is a "view" and "observes" a "model", i want that pane to work in all contexts and not depend on the command processor
9:11:50
scymtym
i mean, do panes print to that *STANDARD-OUTPUT* stream or is there a separate mechanism?
9:12:25
jackdaniel
well, in this non-orthodox frame manager there are no panes - generate-panes yields nothing
9:32:46
scymtym
clouseau's INSPECTOR-PANE is one example. it can be embedded in any application and the display part will work since it does not rely on the application frame or the command loop. however, since the INSPECTOR-PANE also uses commands, it still depends on the application thought the command table
9:34:08
jackdaniel
n.b I have an idea for the problem of embedding panes with "private" command tables which seems to make sense in light of the CLIM spec
10:19:25
lukego
I'm doing (with-output-as-presentation (pane x 'x) (draw-circle* pane ...)) and I get the circle but can't seem to use it as a presentation e.g. can't select it as an argument to DESCRIBE. what could be wrong?
10:21:29
lukego
argument to display-function of a clim application frame, which has been wrapped in a with-scaling and with-translatoin
10:30:30
lukego
no luck. I've defined a presentation type like (define-presentation-type x ()) but no methods. is that wrong?
10:49:49
jackdaniel
so your presentation type must inherit from the expression (or you must present your object with the presentation type expression)
11:11:22
lukego
okay, really I just want to define a blurb for mouseover e.g. a tooltip, is that easy?
11:14:01
jackdaniel
my impression is that this should be implemented as a mixin for the presentation type (instead of defining methods); but I'm not certain
11:15:30
lukego
ok so zooming out the situation here is that I'm rendering objects as shapes but that necessarily leaves out a certain amount of information, and I'm looking for a convenient way to access that e.g. tooltip / popup / command / etc. is there a simple solution?
11:21:48
jackdaniel
but the default pointer documentation pane will try to tell what are available options
11:24:04
lukego
I'll read the manual about command translators, that seems to be a relevant concept that I'm still ignorant of
11:34:32
jackdaniel
the listener has a separate pane for showing arbitrary information (wholine pane afair)