wumpz / jhotdraw Goto Github PK

• makes no sense to make CompositeFigure part of Drawing even if some methods are structurally the same
• not all methods of CompositeFigure are used and so meaningless default implementations are needed

now the ends of a line connection is in the center of a figure, the location of line end is fixed, that is so inconvenience, cannot draw more than one connection line between two figures

• all tracking methods (as lambda)
• modify part of Figure
• insert part of Figure
• delete part of Figure

• four nearly identical implementations of this attribute stuff is there
• since even Figure has attribute methods, why this split AbstractFigure -> AbstractAttributedFigure

core
gui
app

• jhotdraw-action

• at the moment using the view scale and stroke width is used to construct a polygon that is tested against the click point
• the use of GrowStroke does not work for small if there is no scale factor available
• there may be different scale factory for different views the drawing is shown in

• all kinds of writing factories (svg, image) are external
• pollutes Figure API

• much overhead can be removed
• dom storage is much cleaner
• Polygon can be directly derived from this

• only meaninful for composits
• or some special dumping of geometry which makes only sence for special Figures, so the developer could introduce some own impl. without needing this interface method