freenode/#clim - IRC Chatlog
Search
2:30:52
Colleen
loke: nsrahmad said 8 hours, 46 minutes ago: In menu-test.lisp at line 154--Instead of making a clim:application-pane, Try clim:clim-stream-pane.
2:31:34
loke
And I agree that the EU parliament is much more icitizen-focused than the regular swedish parliament.
3:46:57
loke
The way you seem to have to do it is to find the top-level-sheet-pane that is inside the frame, and then use CLIM:MOVE-SHEET on it.
3:47:46
beach
That might be correct, but X11 does not have to obey if it is a window managed by the window manager.
3:48:41
beach
Don't you think it would be better to define a method that would call the X11 window-manager functionality for move-sheet?
3:49:49
loke
But... you can do it with mostly CLIM-only calls (plus CLIM-INTERNALS::TOP-LEVEL-SHEET-PANE-P)
3:52:25
beach
No, the graft corresponds to the X11 screen as I recall. It would have to be the pane that has a graft as its parent.
3:54:58
beach
I would not be opposed to exposing a certain number of extensions (like finding the top-level sheet) in the clim-extensions package.
3:55:15
loke
I'd like the popup with completions to show up next to the cursor where you're typing. Thus I need to fing out the screen coordinates of the cursor in a DREI editor
3:56:08
loke
(I guess it's useful if you have your hand on the mouse all the time and there is no keyboard control, as was the case with the traidional menu)
3:57:34
loke
And... I have a final question (for now): Is there a function that I can call that causes a scrollable viewport to scroll such that a given output record is in view?
3:58:36
beach
You would have to find the position and size of that output record and call scroll-extent to make it visible.
4:09:22
loke
beach: given a pane (that lives inside a scollpane), how can I determine the visible area and adjust the scrolling?
4:10:06
beach
The visible area is the region of the viewport-pane, but you don't need to know that. You should be able to just call scroll-extent.
4:15:51
loke
But to do that I need to know by how to scroll, so I need to know the current visible subsection?
4:17:37
loke
If the thing that I want to make visible is above the visible area, then I need to make it visible on top. And vice versa. In other words, I need to scrol the minimal amount of space to make the thing visible.
4:17:57
loke
In order to do that, I need to know where the thing is realtive to the extent prior to scrolling.
4:19:53
loke
beach: liek I said: I need to know precisely where to scroll, and that location depends on where the scroll _was_
4:20:48
loke
if the selected menu entry is above the viewport, then I want to scroll up so that the m,enu entry is on top
4:22:42
beach
It is the region of the viewport pane in its parent (the main pane) that determines what is visible.
4:24:08
beach
If the pane pane is part of a scroller pane, this returns the region of the pane's viewport.
4:37:51
loke
It's a bit annoying since the DREI instance doesn't actually know anything about where teh buffer/cursor is.
4:39:16
beach
I will be a bit busy today. It's Wednesday, so my favorite coauthor is coming over for lunch. I will go riding my bicycle (for exercise), then go to the store, then cook for her, then have lunch, then work with her, then rest.
4:39:18
loke
Well, i set a breakpoint and looked at the class... The only refernce from the cursor to the concrete visualisation is via the “OBSERVERS” member
5:14:25
beach
I would if I had some use for symbolic calculations. I don't have that right now. But I would be willing to test it for you if you want. I would only be able to do some simple stuff though, I'm afraid.
5:15:53
loke
I'm primarily building this because I want to build something like this, and the times when I _do_ need the maths stuff, ti's nice that it's pure lisp
5:16:20
beach
OK. I'll see what I can do. Today, I am a bit preoccupied with other stuff, but you should remind me later.
5:27:14
loke
I really like the way you can browse files in the CLIM-Listener, so I was thuinking of bringing that in
5:28:02
beach
I am asking because it would be too bad if my effort on Second Climacs were to be duplicated.
5:28:55
loke
I intend to add editing capability to climaxima. I will do that by leveraging an editing editor. Either DREI or Second Climacs.
5:29:53
loke
Second Climacs wuld be neat, but then there is th eproblem of DREI already being used in climaxima. So... what I _REALLY_ want to do is to use 2climacs instead of drei for all editing.
5:31:19
loke
Which is also why I'd like you to have a look at the work so far. You might have an idea as to how drei can be replaced.
5:31:55
loke
For example, the completion feature I've built into climaxima really should be provided by second climacs.
5:33:04
loke
it's hooked into DREI right now, but only in the sense that it's initiated by TAB being added as a keybind in DREI, and that DREI buffer commands are used to modify the buffer when inserting the result.
6:33:06
pillton
loke: I read a paper a while back where the math was so horrific that I thought the paper has to be wrong some where. It was my working to see if it was wrong.
6:34:55
pillton
loke: I usually just step through each line and look at the expressions that are printed.
6:35:56
loke
pillton: Copy&paste is kinda broken (i.e. nonexistent) in CLIM at the moment, so it's hard to test that :-)
6:36:22
pillton
loke: I usually do M-x imaxima and then press C-c C-c on each line to see its output.
6:39:00
pillton
I think imaxima uses TeX to render math. Texput tells maxima how to output certain expressions as TeX.
6:57:19
pillton
To the author's credit, the paper wasn't wrong. I am convinced they used something like Maxima to do the derivations though.
7:15:15
pillton
loke: Have you told Raymond Toy about your work? He is a maintainer for CMUCL and contributes to Maxima.
9:23:11
loke
When constructing panes inside a frame using define-application-frame, how can I say that I want the left pane to have a width of N and the right frame to have the width of M?
9:27:06
beach
Or you can do (horizontally () (scrolling (:width ..) app1) (scrolling (:width ...) app2))