불친절한자수씨

원래 저는 허광남님의 밥 멘티가 아니였으나 메일로 참여하고 싶다고 졸라서 어제 결정이 된 것이었습니다.

회사에는 잠시 나갔다 온다고 이야기를 한 후 강남에서 분당으로 이동하였습니다.

Map dataMap = ...; ProgressManager progressManager = new ProgressManager(); progressManager.add(new ProgressTimer<Map>(dataMap, 5, 30, "progress message 1") { public void progressRun() { Map dataMap = getData(); ... } }); progressManager.add(new ProgressTimer<Map>(dataMap, 5, 50, "progress message 2") { public void progressRun() { Map dataMap = getData(); ... } }); progressManager.add(new ProgressTimer(5, 85, "progress message 3") { public void progressRun() { ... } }); progressManager.start();

진행할 과정들을 나눈 후에 ProgressTimer 를 구현하여 progressRun 메소드에서 실행하도록 한후 ProgressManager 에 추가하는 방식으로 추가된 순서대로 실행을 하도록 하는 방식입니다. 약간의 딜레이가 있을 경우에는 프로세스가 화면 렌더링을 하기전에 즉, 화면이 멈춰보이는 상태 전에 MessageBox 의 progress 를 업데이트합니다.

추가적으로 생성할 때 내부에서 사용할 객체를 넘겨주기 때문에 필요한 객체를 효과적으로 사용할 수 있습니다.


[#M_관련 소스|접기|ㅁ ProgressManager.java
public class ProgressManager { /** * 처음 시작할 타이머 */ private ProgressTimer firstTimer; /** * 가장 마지막에 추가된 타이머 */ private ProgressTimer lastTimer; /** * ProgressTimer 를 추가합니다. * @param timer 추가할 타이머 */ public void add(ProgressTimer timer) { if (firstTimer == null) { firstTimer = timer; lastTimer = timer; } else { lastTimer.setNextTimer(timer); lastTimer = timer; } } /** * first ProgressTimer를 시작합니다. */ public void start() { if (firstTimer != null) { firstTimer.schedule(firstTimer.getDelayMillis()); } } }


ㅁ ProgressTimer.java
import com.google.gwt.user.client.Timer; import com.gwtext.client.widgets.MessageBox; public abstract class ProgressTimer<T> extends Timer { /** * 타이머에서 사용할 데이터 */ private T data; /** * 타이머 딜레이 */ private int delayMillis; /** * 진행 퍼센테이지 */ private int percentage; /** * 진행 메세지 */ private String message; /** * 다음번에 진행할 타이머 */ private ProgressTimer nextTimer; public ProgressTimer(int delayMilli, int percentage) { this(null, delayMilli, percentage); } public ProgressTimer(T data, int delayMilli, int percentage) { this(data, delayMilli, percentage, percentage + "%"); } public ProgressTimer(int delayMilli, int percentage, String message) { this(null, delayMilli, percentage, message); } public ProgressTimer(T data, int delayMilli, int percentage, String message) { this.data = data; this.delayMillis = delayMilli; this.percentage = percentage; this.message = message; } public T getData() { return data; } public int getDelayMillis() { return delayMillis; } public void setNextTimer(ProgressTimer nextTimer) { this.nextTimer = nextTimer; } public void run() { progressRun(); if (nextTimer != null) { nextTimer.schedule(nextTimer.getDelayMillis()); } else { MessageBox.hide(); } } public abstract void progressRun(); public void schedule(int delayMillis) { MessageBox.updateProgress(percentage, message); super.schedule(delayMillis); } }

출처: 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 를 선택합니다.

기본 케이스입니다.

2009년 1월 15일, 2009 년 IDS&TRUST Kick off 행사가 있었습니다.

해피라이프개발원 조용모 원장님의 열정적인 강연을 들었습니다.
처음에는 목사님 필이나서 약간 거부감이 있었으나 힘들게 살아온 이야기를 들으면서 참 대단하신 분이라는 것을 느꼇습니다.