Re: SheetObjectGraphic (arrows, lines, rectangles, ellipses)
- From: Noemi Farkas <jgoldberg home com>
- To: Lutz M?ller <urc8 rz uni-karlsruhe de>
- Cc: gnumeric-list gnome org
- Subject: Re: SheetObjectGraphic (arrows, lines, rectangles, ellipses)
- Date: Fri, 10 Aug 2001 21:04:20 -0400
On Sat, Aug 11, 2001 at 04:49:20AM +0200, Lutz M?ller wrote:
You can configure those objects now (right click on it). Printing is
implemented (ok, the objects aren't printed where they are supposed to
be, but that's a question of fine-tuning).
Good work, thanks.
Issues that still persist:
(1) You cannot print objects when "--without-bonobo" because the
printing mechanism relies on bonobo. You can still create/save/load
those objects. Weird.
This should be fixed. The bonobo nature of the printing is left
over from gnumeric's early status as a test bed for Bonobo.
(2) How do we handle overlapping items?!? Right now, it isn't handled at
all, which means you can easily get different results on screen and on
paper. That's bad. Should I implement "Raise" and "Lower" (right click
menu) and save the level?
(3) Redo/Undo to be implemented.
By this I assume you mean undo/redo for object property changes.
Your recent work to enable support for move/resize/create/delete is
a good starting point. However, the next stage may require a Bonobo
interface akin to Zoom for remotely managing an undo/redo stack.
I've got some rough work in my tree that will implement persistence
in the standard case for Bonobo objects. However, all of the
sheet-object work should be viewed as a work in progress. As you
have seen thus far there are still lots of questions remaining to be
answered. Many of which will require gnome-2.0 features.
- Clipboard support
- Configuration undo/redo
- Better layout and semantics for menu/tool-bar merging
- How to handle them for the non-gui build
- Which structured file format we'll select to store them
- A generic mechanism for storing dependencies from the objects
back to the workbook. The Dependent mechanism gives us an
api, but there is no generic persistence mechanism.
- How to address dependencies from the Sheet out to the objects.
eg we will want access to the fit parameters from a graph back
in the sheet.
I've handled this for graphs only for the case of vectors.
Thanks for your continued work in this area.
Jody
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]