Changes between Version 14 and Version 15 of APP_LAYOUT_MYDOGGY_R1
- Timestamp:
- 07/23/09 15:22:40 (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
APP_LAYOUT_MYDOGGY_R1
v14 v15 42 42 * UML diagram:[[BR]] [[Image(source:branches/private/peko/sophie2-mydoggy-refactoring/doc/uml-design-diagrams/mydoggy-module-uml.png, 90%)]] 43 43 * As described in the diagram we have two base classes for layout elements and these are the simple MDLayoutElement and a MDCompoundLayoutElement. The only difference is that the compound elements has a list property of subElements and a ToolWindowManager. Before that the "subElements" were defined in every implementor of the MDCompoundLayoutElement. The MDManageable interface is to point out that some layout component has a tool window manager. The ToolWindowManager is something that actually lays out the elements and is a class of mydoggy library. 44 44 * MDMainWindow is now divided into two implementations with common things extracted in a super class. Two two implementations will provide different types of components: 45 * MDWindow - common things like flaps, documents windows etc. 46 * MDFrameWindow - providing a JFrame as a global container. The former MDMainWindow. 47 * MDAppletWindow - providing a JApplet as a global container. The implementation of this class will be done in the implementation phase. It is mentioned here as an outline. 48 * The MDDocumentWindow is as described in [wiki:APP_LAYOUT_MYDOGGY_R0] and is not refactored since it behaves properly. 45 49 * Changesets: 46 50 * [changeset:4471] - a bugfix of the core logging module (provided by deni). It will be nice if it is included along with this task.