On Thu, 7 Oct 1999, James Henstridge wrote:
> I was just asking about this because someone suggested it a while back.
> If it helps flesh out some of the sheets (such as the network sheets or
> flowcharts), it may be worth it.
Yeah, i totally support it.
> Here are some other changes I think may be worth looking at for the next
> release of dia:
>
> - Move the page size/zoom selectors from the print dialog to a page setup
> dialog, and save the settings with the actual diagram. Probably also
> allow changing of the margins here.
Yeah. I'd like a fit-to-page button too.
> - When paginating the diagram for printing, make the origin fall on a page
> boundary, and show the page breaks on the diagram (this would just be a
> simple modification on the current grid display code).
Do you mean something like "print preview"?
> - Instead of using dlopen directly, use gmodule to load the object
> libraries. This way we don't have to worry about whether underscores
> are prepended to symbols, and dia will have a better chance of working
> on systems that don't support dlopen.
Yes.
> - Maybe move the files installed in the home directory to a .dia
> subdirectory:
> ~/.diarc -> ~/.dia/diarc
> ~/.dia_shapes/ -> ~/.dia/shapes/
> ~/.dia_libs/ -> ~/.dia/lib/ or ~/.dia/objects/
> This should cut down on clutter in the home directory. The ~/.dia
> heirachy could be created the first time a user runs dia.
Looks good to me.
> I think it would be a good idea to get a new tarball release out some
> time. The current CVS version is much better than the last released
> tarball (undo, custom shapes, printing, SVG export, more objects,
> line style selector in toolbox, etc).
Yes. I totally agree. Only i haven't had much time... I'll really try to
finish some stuff.
I'll add my list of stuff that must/should be done before release.
Right now I've been stalling on undo for "UML - Class" for some time. That
is a pretty ugly part, and it'll be a bit complex. But when thats done the
rest is pretty simple.
/ Alex
Anyway, heres the list:
Fix before release:
===================
Properties dialog crash.
use g_modules instead of dlopen()
last part (marked todo in paginate_psprint.c) of print_save.diff dialog
stuff.
bigger main window on startup.
zigzagline defaults to three segments?
Diagram load problem. Connections give errors.
Undo:
=====
Left to finish is (in approximate order of implementation):
* Undoing a property-change needs to change the values in the properties
window.
* Bug: Keyboard accels must be disabled whilst dragging an object or
handle, else stuff can crash easily by deleting (Ctrl-X) while dragging.
Objects undo:
=============
* These should be fairly easy. Just create an ObjectState derived
struct and add get/set_state functions. (1)
* Needs to be changed to the new OrthConn interface. Check Zigzagline for
more info. (2)
UML:
UML/class.c
UML/class_dialog.c
Complicated. Needs to implement it's own Undo/Redo code, since
adding/removing methods and attributes can change the number of
handles.
Network:
network/bus.c
Complicated. Needs to be changed so that adding/removing handles is done
via object menus. These need to handle undo/redo.
FS:
All these objects have object menus. These need to be updated so that
they can be undoed. I'm also a bit uncertain about this usage of
the object menus. Probably needs some discussion.
FS/flow.c
Needs (1)
FS/flow-ortho.c
Needs (1) and (2)
FS/flow-poly.c
Not currently used. Maybe it needs to be added to be added to fs.c.
FS/function.c
Needs (1)
