|
| Re: Predefined UI Layout [message #2025 is a reply to message #1999] |
Mon, 12 December 2005 15:28   |
 James Moody
Messages: 61
Registered: July 2009 |
Member |
|
|
Hi Bruno,
There are two approaches to constructing processes in general:
One is where the process is defined by creating a number of nodes and
connecting them together (like in a flowchart). Tools that use this
approach usually allow a free-form layout of activities by the user.
The other is highly structured and uses a number of container activities
to define the execution path. This places constraints on where
activities can appear visually because, by virtue of their parentage,
they form a hierarchy rather than a flat diagram.
This point is simply to reinforce that, because BPEL is in the latter
category, the editor will do much of the layout automatically. For
example, the user will not be able to place children of a sequence in an
arbitrary (x,y) location on the canvas; the editor will do a constrained
layout such that the child activities appear top-to-bottom in the order
of their execution inside the sequence.
Hope this helps.
james
Bruno Wassermann wrote:
> Hi,
>
> In the proposal it says that the visual represenation of BPEL worklfows
> should have a "predefined UI layout". What exactly does this mean?
>
> Regards,
>
> -- Bruno
>
>
|
|
|
| Re: Predefined UI Layout [message #2067 is a reply to message #2025] |
Wed, 04 January 2006 16:53 |
Eclipse User |
|
|
|
Originally posted by: none.us.ibm.com
James, I've created a new prototype editor that includes a LayoutManager
that wrappers DirectedGraphLayout. I uses editpolicies that allow the user
to rearrange the order of nodes on each row, while the overall placement is
still calculated by DGL. Also, the entire diagram animates the transition
between layouts. We recently released Animator to draw2d. Using it simply
requires a few hooks provided that the layouts behave in a standard way. I
haven't gotten to the compound version yet though, and long edges can not be
manually reordered yet.
"James Moody" <James_Moody@ca.ibm.com> wrote in message
news:dnk4vp$sab$1@news.eclipse.org...
> Hi Bruno,
>
> There are two approaches to constructing processes in general:
>
> One is where the process is defined by creating a number of nodes and
> connecting them together (like in a flowchart). Tools that use this
> approach usually allow a free-form layout of activities by the user.
>
> The other is highly structured and uses a number of container activities
> to define the execution path. This places constraints on where activities
> can appear visually because, by virtue of their parentage, they form a
> hierarchy rather than a flat diagram.
>
> This point is simply to reinforce that, because BPEL is in the latter
> category, the editor will do much of the layout automatically. For
> example, the user will not be able to place children of a sequence in an
> arbitrary (x,y) location on the canvas; the editor will do a constrained
> layout such that the child activities appear top-to-bottom in the order of
> their execution inside the sequence.
>
> Hope this helps.
>
> james
>
> Bruno Wassermann wrote:
>> Hi,
>>
>> In the proposal it says that the visual represenation of BPEL worklfows
>> should have a "predefined UI layout". What exactly does this mean?
>>
>> Regards,
>>
>> -- Bruno
|
|
|
|
Powered by
FUDForum. Page generated in 0.01577 seconds
] 
Search
Help
Register
Login
Home
