This is a biggie. Here should go considerations of what the problems are. Main problem seems to be UI-related. How do we make a rotation/scaling interface that isn't confused with the resizing of objects? Do we need to make resizing some else? Note that scaling = resizing, as scaling also changes fonts size, line width etc. The underlying structure should probably just be a transformation matrix. -- LarsClausen - 19 Mar 2004 For the rotate interface, I think that InkScape? do the right thing. Click on the selected object and the resize handle change to a rotate/shear. We might find something similar for scaling. -- HubertFiguiere - 19 Mar 2004 Rotation requires a number of structural additions to ensure that renderers get things right and that that objects that talk to each other (like autorouting) understand each other correctly. Not sure if this should be in 1.0. -- LarsClausen - 13 Sep 2004 Some stray thoughts: Rectangles and ellipses are probably the most difficult to rotate, as rotation would change from a 'render box' call to 'render polygon' call. Similarly for UML objects etc. One possible solution is to have the 'renderer' really render into something SVG-like that can easily rotate. For connection points and handles, the position needs to be updated. Probably easiest to do this at DiaObject? level by adding a set of 'rotated' positions to be updated with a dia_object_update_data function. See also bug #100866 on bugzilla. -- LarsClausen - 07 Nov 2005
| Edit -:- Attach -:- Ref-By -:- Printable -:- More |