ObjectWeb Consortium
Search ObjectWeb Mail Archive: 

Advanced Search - Powered by Google


Mail Archive Home | jawe List | May 2004 Index

<--  Date Index  --> <--  Thread Index  -->

Re: [jawe] Start/End bubbles


But if XPDL creator wants one can easily determine start/ends (no matter of 
editor being used), he can give them appropriate names,
but we can't force creator to create start/end activities with fixed names to 
"Start" and "End" or something (in your use case, we
can suggest it, but not fix it). Also, I suppose that every XPDL editor will 
recognize possible start/ends based on number of
incoming/outgoing transitions which should be zero (this is how JaWE does 
it), and then display it in its own way (by coloring them,
adding bubbles, ...).

Regards,
Sasa.

----- Original Message -----
From: "Michael N. Lipp" <mnl@xxxxxx>
To: <jawe@xxxxxxxxxxxxx>
Sent: Tuesday, May 18, 2004 10:30 AM
Subject: Re: [jawe] Start/End bubbles


> Sasa Bojanic wrote:
>
> >Can you explain me the difference among our Start/End bubbles (that are 
> >after all written as ext. attributes), and extended
> >attributes you are mentioning? The only difference I see is that we make 
> >our ext. attributes visually by putting Start/End
bubbles,
> >and you would do it in some activity's property dialog?
> >
> Afaik, start- and end-bubbles in JaWE are currently extended attributes
> *only*, i.e. there are no corresponding activity instances in the
> process description. My understanding of the proposition being discussed
> here recently was to make start- and end-bubbles "real" activities
> (route activities, to be precise) in the process description that are
> "marked" by some extended attribute as representing start- and end-bubbles.
>
> All I'm saying is that, if you do this, I wouldn't restrict the start-
> and end-bubbles to being represented by route activities only; rather
> I'd let the user choose which kind of activity he wants (just as with
> any other activity). So effectively, being a start- or end-bubble
> becomes a display (and editing restriction and verification) property of
> an activity. This extended (JaWE) property will, of course, be ignored
> by other editors. Still, looking at the process description using a
> different editor, or looking at some run-time display of a process'
> activities states, the user has a good chance to recognize the intended
> start- and end-activities by their names (currently, the start- and
> end-bubbles from JaWE -- being extended attributes *only* -- are
> completely ignored and thus not displayed at all by other editors or
> status displays). The costs for this being, of course, that there are
> additional start- and end-activities to be executed at run-time (though
> these are neglectable costs, if the activities actually have an
> implementation, or only little costs, if the activities are of type
> route activity).
>
>  - Michael
>
>
>
>


--------------------------------------------------------------------------------


>
> --
> You receive this message as a subscriber of the jawe@xxxxxxxxxxxxx mailing 
> list.
> To unsubscribe: mailto:jawe-unsubscribe@xxxxxxxxxxxxx
> For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>




<--  Date Index  --> <--  Thread Index  -->

Reply via email to:

Powered by MHonArc.

Copyright © 1999-2005, ObjectWeb Consortium | contact | webmaster.