불친절한자수씨

설치

kr.co.vicki.gef.mvc_1.0.0.v20090720-1919.jar

Dependencies 추가

구현

Introduction

Architecture

출처: http://help.eclipse.org/stable/index.jsp?topic=/org.eclipse.gef.doc.isv/guide/guide.html

Moving and Resizing

move interaction

resize interaction

The DragEditPartsTracker extends basic selection behavior to allow the selected parts to be dragged within their graphical viewer. Dragging the selected parts can result in three potential interactions: move, reparent, and clone. All three use theChangeBoundsRequest, which extends GroupRequest to include a size delta, move delta, and mouse location.

While dragging the selection, if the tracker targets the part's original parent, the request is typed as REQ_MOVE. If the target changes, the interaction becomes a reparent. For a reparent, a request of type REQ_ORPHAN is sent to the old parent, while the new target is sent a request of type REQ_ADD. When the CTRL key is pressed (ALT on the Mac), the operation is always a REQ_CLONE, which is only sent to the target part.

All of these requests are related in that they require the target to process a rectangle and a mouse location. The LayoutEditPolicy is responsible for handling each of these request types. For layouts which use constraints, each part's original bounds is taken and modified by the size and move deltas to determine a new bounds, for which a corresponding constraint is found. For index-based layouts, the mouse location is used to establish the new index.

A ContainerEditPolicy can optionally be used to contribute additional commands (not related to the layout) during ADD, ORPHAN, and CLONE requests.

Resizing

Resizing falls under the same category as changing bounds. Note that when resizing either the top or left sides, the location of the part is also changed. Resizing only makes sense for layouts with constraints, such as XYLayout. The ResizableEditPolicy adds up to eight resize handles to its host. When the Selection Tool is clicked on one of these resize handles, a ResizeTracker performs a resize on the selected parts understanding "resize". SHIFT and CTRL key modifiers can be used to constrain the resize operation.

The types of handles available on an editpart depend on the layout manager in which its figure is placed. For example, parts inside a table might have handles for adjusting insets, padding, column span, or other attributes. Some layouts don't need any handles, but four corner handles should be added just to indicate selection. Dragging these handles would be the same as dragging the part itself.

Because of the relationship between handles and layouts, it is recommended that the PRIMARY_DRAG_ROLE editpolicy be installed by the parent's LayoutEditPolicy, which defines abstract methods for this purpose. If a container changes layout managers during editing, typically the layout policy gets swapped with one for the new layout manager. The new policy then replaces the stalePRIMARY_DRAG_ROLE policies on each child.

The MatchSizeAction matches the size of the selected parts to that of the primary selected part's size. This action is implemented in a way similar to manually resizing the individual parts, and it uses the same request and type.

The AlignmentAction uses an AlignmentRequest, which extends ChangeBoundsRequest. When using a ChangeBoundsRequest, the part's current placement in the Control (in absolute coordinates) is passed to the request, which then returns a modified version. Using this pattern, alignment is able to adjust each part's rectangle by different amounts. In most cases, alignment can be treated no differently than a move. This action aligns all selected parts with one of the edges of the primary selected part.

ㅁ 기존의 EditPartFactory
모델이 하나 늘어날 때 마다 if 문이 추가가 됩니다.
public class ElementEditPartFactory implements EditPartFactory { @Override public EditPart createEditPart(EditPart context, Object model) { EditPart part = null; if (model instanceof BodyElement) { part = new BodyElementPart(); } else if (model instanceof RectangleElement) { part = new RectangleElementPart(); } else if (model instanceof TextFieldElement) { part = new TextFieldElementPart(); } else if (model instanceof NumberFieldElement) { part = new NumberFieldElementPart(); } else if (model instanceof CurrencyFieldElement) { part = new CurrencyFieldElementPart(); } else if (model instanceof DateFieldElement) { part = new DateFieldElementPart(); } else if (model instanceof FormatFieldElement) { part = new FormatFieldElementPart(); } else if (model instanceof GridElement) { part = new GridElementPart(); } else if (model instanceof GridColumn) { part = new GridColumnPart(); } part.setModel(model); return part; } }

ㅁ 자동화를 위한 AnnotatedEditPartFactory
package kr.co.vicki.gef.model; import org.eclipse.gef.EditPart; import org.eclipse.gef.EditPartFactory; public class AnnotatedEditPartFactory implements EditPartFactory { @Override public EditPart createEditPart(EditPart context, Object model) { EditPart part = ModelHelper.createEditPart(model.getClass()); if (part != null) part.setModel(model); return part; } }

모델에 @GEFEditPart 어노테이션을 정의하면 모델 추가시에 바로 처리가 가능합니다.
@GEFEditPart(editPartType=BodyElementPart.class) @GEFTreeEditPart(editPartType=BodyElementTreePart.class) public class BodyElement extends BaseElement implements IBeanConvertable { ... }

어노테이션 처리를 위한 클래스는 다음과 같습니다. - ModelHelper
package kr.co.vicki.gef.model; import java.lang.annotation.Annotation; import kr.co.vicki.gef.model.annotations.GEFEditPart; import kr.co.vicki.gef.model.annotations.GEFModelIcon; import kr.co.vicki.gef.model.annotations.GEFTreeEditPart; import org.eclipse.gef.EditPart; public class ModelHelper { /** * 상속 구조에서 어노테이션을 찾습니다. * @param modelClass * @param annotationClass * @return */ @SuppressWarnings("unchecked") private static Annotation getHierachyAnnotation(Class modelClass, Class annotationClass) { Annotation result = null; result = modelClass.getAnnotation(annotationClass); if (result == null) { Class superClass = modelClass.getSuperclass(); if (superClass != null) { return getHierachyAnnotation(superClass, annotationClass); } } return result; } public static EditPart createEditPart(Class modelClass) { GEFEditPart editPart = (GEFEditPart) getHierachyAnnotation(modelClass, GEFEditPart.class); try { if (editPart != null) return editPart.editPartType().newInstance(); } catch (Exception e) { e.printStackTrace(); } return null; } public static EditPart createTreeEditPart(Class modelClass) { GEFTreeEditPart treeEditPart = (GEFTreeEditPart) getHierachyAnnotation(modelClass, GEFTreeEditPart.class); try { if (treeEditPart != null) return treeEditPart.editPartType().newInstance(); } catch (Exception e) { e.printStackTrace(); } return null; } public static String getModelIconImagePath(Class clazz) { GEFModelIcon modelIcon = (GEFModelIcon) clazz.getAnnotation(GEFModelIcon.class); if (modelIcon != null) return modelIcon.imageFilePath(); return null; } }

사용된 라이브러리

kr.co.vicki.gef.model.1.0.0.v20080928.jar

기존의 소스...
public class GridColumnPropertySource implements IPropertySource { private GridColumn gridColumn; public GridColumnPropertySource(GridColumn gridColumn) { this.gridColumn = gridColumn; } @Override public Object getEditableValue() { return null; } @Override public IPropertyDescriptor[] getPropertyDescriptors() { List<IPropertyDescriptor> properties = new ArrayList<IPropertyDescriptor>(); PropertyDescriptor labelTextDescriptor = new TextPropertyDescriptor(GridColumn.PROPERTY_TITLE, "타이틀"); properties.add(labelTextDescriptor); PropertyDescriptor borderSizeDescriptor = new TextPropertyDescriptor(GridColumn.PROPERTY_WIDTH, "너비"); properties.add(borderSizeDescriptor); return properties.toArray(new IPropertyDescriptor[0]); } @Override public Object getPropertyValue(Object id) { if (id.equals(GridColumn.PROPERTY_WIDTH)) return "" + gridColumn.getWidth(); if (id.equals(GridColumn.PROPERTY_TITLE)) return gridColumn.getTitle(); return null; } @Override public boolean isPropertySet(Object id) { return false; } @Override public void resetPropertyValue(Object id) { } @Override public void setPropertyValue(Object id, Object value) { if (id.equals(GridColumn.PROPERTY_WIDTH)) { try { gridColumn.setWidth(Integer.parseInt((String) value)); } catch (NumberFormatException e) {} } else if (id.equals(GridColumn.PROPERTY_TITLE)) { gridColumn.setTitle((String) value); } } }


자동화 처리된 소스...
public class GridColumn extends BaseModel implements IAdaptable, IBeanConvertable { @PropertyDescription(label = "타이틀", category = "컬럼", field = "title") public static final String PROPERTY_TITLE = "grid column title"; @PropertyDescription(label = "너비", category = "컬럼", field = "width") public static final String PROPERTY_WIDTH = "grid column width"; ... }
public class GridColumnPropertySource implements IPropertySource { private GridColumn gridColumn; private PropertySourceHelpers descriptorHelper; public GridColumnPropertySource(GridColumn gridColumn) { this.gridColumn = gridColumn; descriptorHelper = new PropertySourceHelpers(gridColumn.getClass()); } @Override public Object getEditableValue() { return null; } @Override public IPropertyDescriptor[] getPropertyDescriptors() { return descriptorHelper.getPropertyDescriptors(); } @Override public Object getPropertyValue(Object id) { return descriptorHelper.getPropertyValue(gridColumn, id); } @Override public boolean isPropertySet(Object id) { return false; } @Override public void resetPropertyValue(Object id) { } @Override public void setPropertyValue(Object id, Object value) { descriptorHelper.setPropertyValue(gridColumn, id, value); } }

프로퍼티 상수에 PropertyDescription 어노테이션을 정의하여 PropertySourceHelpers 에 처리를 위임합니다.
알아서 PropertyDescriptor 들을 반환해주고 값을 얻어오고 설정을 하게 됩니다.

기존 방식은 한 두개야 머 저렇게 작업하겠지만 몇 십개의 모델과 몇 백개의 프로퍼티를 관리하려면...
무리가 있겠죠...