[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [gef-dev] Looking for Next Release (3.1?) Requirements
|
Hi, Randy,
I have a request for a simple demo application. Right now what I can
find are just flow and logic application. While I am writing code using
GEF, I have to read through a lot of codes for even simple tasks like
how to get two editparts connected, how to drag and drop editparts, etc.
Well, the red book is definitely a good material but still not detailed
enough. To have a simple but workable demo will help greatly.
Thanks,
Fei
Vadim Gurov wrote:
Hello Randy,
Friday, June 25, 2004, 6:25:08 PM, you wrote:
RH> With 3.0 almost out the door, we will
RH> be prioritizing features and bugs for the next major release of
GEF (and
RH> also the service release 3.0.1). If you have requirements, bring
RH> them up here, or if we get too many reponses, bugzillas are
probably the
RH> more appropriate forum.
RH> Some ideas so far:
RH> - New examples
RH> - Graphical Text support
RH> - Snap bendpoint to grid
RH> - New draw2d layout (table?)
RH> - Improvements to the DirectedGraphLayout
RH> (constraints, optimizations)
1. Redesign whole GEF to avoid VERY HIGH coupling of different components
(Editors, Views, Edit Parts, Palette, Editor Domain). For now, everyone
knows about everyone. Introduce Mediator pattern which must be
listener of all components and actual Controller. Move all logic from
components to Mediator. In all components leave only plain code and
utility methods.
2. Create GEF UML diagrams for static relationships (Conceptual
model written with a help of Class Diagram) and for components
behavior (if all logic will be located in Mediator - only one diagram
needed! And it must be Statechart diagram!). Such set of diagrams will
help not only GEF users, but even GEF developers.
3. Explicitly emphasize states for such components as Tools and Edit
Parts. Visual state of Edit part must be prolongated to it's figure.
Whole state of Edit part must be superposition of underlaying model
element and visual state.
4. Write new good examples which will have all application logic in one
place (logic designer example has logic even in it's Figures! It's
incorrect and not clear).
--
Best regards,
Vadim mailto:vgurov@xxxxxxxxxxxxx
_______________________________________________
gef-dev mailing list
gef-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/gef-dev
