출처: 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.

ㅁ plugin.xml 의 Extensions 탭에서 Add 버튼을 클릭해서 Extension Wizards 탭을 선택한 후,
Splash Hanlder 를 선택합니다.

에이콘 출판사에서 나온 "이클립스 RCP" 책을 기준으로 정리했습니다.

1. RCP 프로젝트에 product 만들기
  - p.113 8장 하이퍼볼라 브랜드 적용
  - Product Configuration 을 생성합니다.

2. RCP Application 패키지 내보내기
  - p.127 9장 하이퍼볼라 패키지 만들기
  - 위에서 만든 product 를 Export 합니다.

3. 자동업데이트 구성하기
  - p.197 14장 자동 업데이트
  - feature project 추가
  - update action 추가
  - 패키지를 다시 내보내기 전에 update site 를 구성해야 함.

4. Update site 구성
  - p.343 21장 플러그인 설치와 업데이트
  - update site 구성 후 feature 추가
  - update site 배포
  - 테스트!!


지금 1,2,3,4 까지 모두 다 진행하였는데 RCP 에서 자동 업데이트 기능을 실행하니 변경사항이 없다고 나오네요..
좀 더 확인을 해야 할 것 같습니다.

ㅁXmlEditor.xml
public class XMLEditor extends TextEditor { private ColorManager colorManager; public XMLEditor() { super(); colorManager = new ColorManager(); setSourceViewerConfiguration(new XMLConfiguration(colorManager)); setDocumentProvider(new XMLDocumentProvider()); } public void dispose() { colorManager.dispose(); super.dispose(); } public void setContent(String content) { if (getEditorInput() instanceof StringEditorInput) { StringEditorInput editorInput = (StringEditorInput) getEditorInput(); editorInput.setContent(content); setInput(editorInput); } } }

ㅁ StringEditorInput.xml
import java.io.ByteArrayInputStream; import java.io.InputStream; import org.eclipse.core.resources.IStorage; import org.eclipse.core.runtime.CoreException; import org.eclipse.core.runtime.IPath; import org.eclipse.jface.resource.ImageDescriptor; import org.eclipse.ui.IPersistableElement; import org.eclipse.ui.IStorageEditorInput; public class StringEditorInput implements IStorageEditorInput, IStorage { protected String content; public StringEditorInput(String content) { this.content = content; } public void setContent(String content) { this.content = content; } public InputStream getContents() throws CoreException { return new ByteArrayInputStream(content.getBytes()); } public IStorage getStorage() { return this; } public IPath getFullPath() { return null; } public boolean isReadOnly() { return true; } public boolean exists() { return true; } public ImageDescriptor getImageDescriptor() { return null; } public String getName() { return "String Editor"; } public IPersistableElement getPersistable() { return null; } public String getToolTipText() { return ""; } @SuppressWarnings("unchecked") public Object getAdapter(Class adapter) { return null; } }


사용하실 때는 xmlEditor.setContent(~~~)