Hi Himasha, thanks for your response! Especially adding the auto-layout when switching on/off the proximity annotations will be pretty cool (aka a powerful feature) of your editor! I will really like it :-)
Your question on my bullet (4): What you explained is fine - i.e. the "Reset" button will only be available before the first "save" on a new diagram will be requested. Which brings up another (minor) question: once a diagram is saved can I select more than one phase and/or arrow for deletion, or do I have to delete one modeling element after the other. Selection more than one would be fine. Thanks again! Best regards, Frank 2015-01-17 3:46 GMT+01:00 Himasha Guruge <himas...@wso2.com>: > Hi Frank, > > Please find below comments/answers regarding the queries. > > 1. Can we add arrow heads to the lines between the phases (aka > individual chevrons)? E.g. in later releases we will likely support to > draw directed graphs without inferring the direction of an arrow from its > geometric position. In this sense, the current diagram [1] is a bit > confusing: is "ship product" a successor/predecessor of "check payment" > and/or "request refund"? > > Yes Frank, I think adding arrow heads will make things > more clear to the user specially in a scenario as you mentioned. The > logic used here to derive the predecessor/successor is to check the > row/column numbers (placement of phases). Therefore it will recognize 'Ship > product' as a successor of 'check payment' and 'ship product' a predecessor > of 'request refund'. Will add arrow heads as requested. > > 2. Can we highlight the whole phase (aka individual chevron) the > properties of which are shown in [2] instead of highlighting the text field? > Will change it as requested. > > 3. What does "reset canvas" in [3] do? Erasing all of the > canvas? Is this is the case, I assume that a dialog pops > up asking the user whether he really wants this, correct? > > Reset canvas is only found in chevron create page, so that > the user can clear the canvas if needed. (Delete all elements). Will add a > dialog popup. > > > 4. When describing [5], you say that "Reset" creates a new > diagram. In this case we should call the button "new". And the > "old" diagram should automatically stored (or you ask the user what to do > with the existing diagram). > > Frank this clear canvas option is only given in create phase page. This > is under the impression that the user wants to remove all elements that he > drew (before clicking on create to save it ) and re draw a new diagram. So > do we need to save the old diagram here? If we still need to, we can let > him save it locally? > > 5.In [4], when will the annotation of a phase be shown close to > it: when I hover over the "+", or when I click the "+"? Is there a button > that allows me to display all annotations at once? > > Annotations are shown when the user clicks on "+" since it > gives more control to the user. Will include a button to display all > annotations. > > 6. In [4], we should not overlay the phases with their > annotations. Instead, they should be shown on top, below, left, > right,... (consistently) of the phase. And, yes, this means that we have > to auto layout the diagram when the proximity > annotations are requests, and we have to restore the diagram as modeled > once display of annotations are switched off. Chevron diagrams are often > presented with proximity annotations, i.e. the cluttering problem that you > mentioned has to be solved (by automatic layouting,e.g. > +1 ,will include it . > > Thanks & Regards, > Himasha > > On Fri, Jan 16, 2015 at 3:54 PM, Frank Leymann <fr...@wso2.com> wrote: > >> Hi Himasha, >> >> great progress! Thanks! :-))) >> >> A few comments/questions: >> >> 1. Can we add arrow heads to the lines between the phases (aka >> individual chevrons)? E.g. in later releases we will likely support to >> draw directed graphs without inferring the direction of an arrow from its >> geometric position. In this sense, the current diagram [1] is a bit >> confusing: is "ship product" a successor/predecessor of "check payment" >> and/or "request refund"? >> 2. Can we highlight the whole phase (aka individual chevron) the >> properties of which are shown in [2] instead of highlighting the text >> field? >> 3. What does "reset canvas" in [3] do? Erasing all of the canvas? >> Is this is the case, I assume that a dialog pops up asking the user >> whether >> he really wants this, correct? >> 4. When describing [5], you say that "Reset" creates a new diagram. >> In this case we should call the button "new". And the "old" diagram should >> automatically stored (or you ask the user what to do with the existing >> diagram). >> 5. In [4], when will the annotation of a phase be shown close to it: >> when I hover over the "+", or when I click the "+"? Is there a button >> that >> allows me to display all annotations at once? >> 6. In [4], we should not overlay the phases with their annotations. >> Instead, they should be shown on top, below, left, right,... >> (consistently) >> of the phase. And, yes, this means that we have to auto layout the diagram >> when the proximity annotations are requests, and we have to restore the >> diagram as modeled once display of annotations are switched off. Chevron >> diagrams are often presented with proximity annotations, i.e. the >> cluttering problem that you mentioned has to be solved (by automatic >> layouting,e.g.). >> >> >> >> Best regards, >> Frank >> >> 2015-01-14 4:02 GMT+01:00 Himasha Guruge <himas...@wso2.com>: >> >>> Hi All, >>> >>> As a progress update, following functionalities are covered for chevron >>> diagram editor. >>> >>> 1. Virtual grid view : Once a user drags and drops an element to the >>> canvas, depending on the x,y coordinates of the element it will be >>> automatically aligned and placed in the most suitable cell of the grid. If >>> the most suitable cell is already occupied the next most suitable(closest) >>> cell will be taken into count. Once placed in a cell , user can swap the >>> elements to other unoccupied cells. Please find screenshot [1] >>> >>> 2. Multiple predecessor/successor connections : Predecessors and >>> successors of each element will be automatically determined based on user >>> drawn connections.Connections can be dragged from either four endpoints of >>> an element. (top,bottom,left,right) Once the diagram is complete, on click >>> of an element will display it's details as table properties.[2] Since >>> these connections drawn between elements can be disturbing,for a clean view >>> , the user is given a choice of switching on/ off the connections. [3] >>> >>> 3. Annotations for each chevron(phase) : As requested, the description >>> content of each chevron will also be displayed closer to the element. ( >>> green + sign button) [4] To avoid clutter user can switch on/off these >>> annotations, and these will also be listed in table properties as well. >>> >>> 4. Resetting canvas is available in chevron diagram create page,which >>> will let the user create an entirely new diagram. [5] >>> >>> [1] >>> https://drive.google.com/a/wso2.com/file/d/0B2gZ09XLMRjKWm8taS1pcUdQMVk/view?usp=sharing >>> >>> [2] >>> https://drive.google.com/a/wso2.com/file/d/0B2gZ09XLMRjKbGVSM3NWVXFuZmc/view?usp=sharing >>> >>> [3] >>> >>> https://drive.google.com/a/wso2.com/file/d/0B2gZ09XLMRjKMGNUc0p1QUkzbkU/view?usp=sharing >>> <https://drive.google.com/a/wso2.com/file/d/0B2gZ09XLMRjKMGNUc0p1QUkzbkU/view?usp=sharing> >>> >>> [4] >>> https://drive.google.com/a/wso2.com/file/d/0B2gZ09XLMRjKVFlHQV94M0d1OEU/view?usp=sharing >>> >>> [5] >>> https://drive.google.com/a/wso2.com/file/d/0B2gZ09XLMRjKTDd0c2dFaVZrRnM/view?usp=sharing >>> <https://drive.google.com/a/wso2.com/file/d/0B2gZ09XLMRjKTDd0c2dFaVZrRnM/view?usp=sharing%E2%80%8B%E2%80%8B%E2%80%8B%E2%80%8B%E2%80%8B%E2%80%8B%E2%80%8B%E2%80%8B%E2%80%8B%E2%80%8B%E2%80%8B%E2%80%8B> >>> >>> Thanks & Regards, >>> Himasha >>> >>> On Mon, Dec 15, 2014 at 10:39 AM, Chathura Ekanayake <chath...@wso2.com> >>> wrote: >>> >>>> Hi Frank, >>>> >>>> Yes, there is a complexity introduced by using a combination of arrows >>>> and column ordering. However, using only the column ordering can limit to >>>> expressiveness too much. On the other hand, if we always use arrows, we can >>>> avoid many of the confusions you have mentioned above. Only confusion left >>>> would be whether multiple incoming (or outgoing) arrows model a OR, XOR or >>>> AND semantic. We have to solve this even if we use column ordering. >>>> >>>> I think we can use the OR semantic here (i.e. one or more predecessors >>>> have to complete). Thus, we can have more flexibility and the exact >>>> behavior can be captured at the next level of refinement. In this model, >>>> the user always to have to draw arrows and can use column ordering as an >>>> abstract way of visualizing relationships. We can provide a button to turn >>>> on/off arrows. When arrows are turned off, column ordering gives an >>>> abstract visualization of chevron relationships. When arrows are turned on, >>>> exact ordering can be viewed. >>>> >>>> Regards, >>>> Chathura >>>> >>>> >>>> On Sat, Dec 13, 2014 at 8:01 AM, Himasha Guruge <himas...@wso2.com> >>>> wrote: >>>>> >>>>> Hi Frank, >>>>> >>>>> Sure, we can set up a brief demo of the initial version next week. :) >>>>> Let me know a free slot from your schedule. >>>>> >>>>> Thanks & Regards, >>>>> Himasha >>>>> >>>>> On Fri, Dec 12, 2014 at 11:28 PM, Frank Leymann <fr...@wso2.com> >>>>> wrote: >>>>>> >>>>>> Hi Himasha, >>>>>> >>>>>> in case you have an initial version of your code running, I would be >>>>>> glad to get a brief demo :-) >>>>>> >>>>>> >>>>>> Best regards, >>>>>> Frank >>>>>> >>>>>> 2014-12-12 9:44 GMT+01:00 Himasha Guruge <himas...@wso2.com>: >>>>>>> >>>>>>> Hi Frank, >>>>>>> >>>>>>> Thanks for the suggestion. As Chathura mentioned, will support both >>>>>>> approaches depending on the scenario. >>>>>>> >>>>>>> Thanks & Regards, >>>>>>> Himasha >>>>>>> >>>>>>> On Fri, Dec 12, 2014 at 1:57 PM, Chathura Ekanayake < >>>>>>> chath...@wso2.com> wrote: >>>>>>>> >>>>>>>> Hi Frank, >>>>>>>> >>>>>>>> Yes, it is better to let users to draw chevron diagrams without >>>>>>>> arrows whenever possible. However, if there is a scenario where only >>>>>>>> some >>>>>>>> chevrons in a column succeeds a chevron in its previous column, we can >>>>>>>> let >>>>>>>> users to indicate that using arrows. Therefore, we can support a >>>>>>>> combination of column ordering and arrows to capture >>>>>>>> predecessor/successor >>>>>>>> relationships. i.e. if arrows are not drawn, all chevrons in a column >>>>>>>> are >>>>>>>> in successor relationship with all chevrons in its previous column. >>>>>>>> >>>>>>>> Regards, >>>>>>>> Chathura >>>>>>>> >>>>>>>> On Thu, Dec 11, 2014 at 11:50 PM, Frank Leymann <fr...@wso2.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi Himasha, >>>>>>>>> >>>>>>>>> very good idea :-) Let me suggest a little variation: >>>>>>>>> >>>>>>>>> People modeling Chevron Diagrams are not really used to use arrows >>>>>>>>> to connect the individual chevrons to indicate (control or data) >>>>>>>>> flow. The >>>>>>>>> flow is defined by the orientation of the diagram (i.e. horizontal or >>>>>>>>> vertical). This would imply to avoid arrows as long as possible - but >>>>>>>>> folks >>>>>>>>> MAY use arrows if they want e.g. because of clarity and >>>>>>>>> comprehensibility. >>>>>>>>> >>>>>>>>> Let's assume a horizontal orientation: each chevron in a column >>>>>>>>> of your grid will be a successor of all chevrons in the immediate >>>>>>>>> preceding >>>>>>>>> column. And all chevrons in the same column can be performed in >>>>>>>>> parallel. >>>>>>>>> And all chevrons of certain column must be "ready" before the >>>>>>>>> chevrons of >>>>>>>>> the succeeding column can be activated. And, yes, this is not really >>>>>>>>> satisfactory because not all chevrons in a certain column have to be >>>>>>>>> performed - but that's an inherent imprecision of Chevron Diagrams >>>>>>>>> because >>>>>>>>> they don't have an operational semantics (by will ;-)). >>>>>>>>> >>>>>>>>> Thus, the Chevron Diagram you draw would be equivalent to the >>>>>>>>> following (ChevronRelations): >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Best regards, >>>>>>>>> Frank >>>>>>>>> >>>>>>>>> 2014-12-11 7:45 GMT+01:00 Himasha Guruge <himas...@wso2.com>: >>>>>>>>> >>>>>>>>>> Hi All, >>>>>>>>>> >>>>>>>>>> The idea is to support multiple relations for the chevrons in >>>>>>>>>> initial chevron diagram editor. As the initial step, the editor >>>>>>>>>> canvas will >>>>>>>>>> include a virtual grid [1] where the chevron elements can be dropped >>>>>>>>>> into. >>>>>>>>>> >>>>>>>>>> When a chevron is dropped to the canvas most suitable cell >>>>>>>>>> location will be retrieved by checking the center position of the >>>>>>>>>> chevron. >>>>>>>>>> In such a scenario where the most suitable cell is already occupied >>>>>>>>>> by >>>>>>>>>> another chevron element, it will be placed in the next most suitable >>>>>>>>>> location. >>>>>>>>>> Once a chevron element is added, it can be swapped between >>>>>>>>>> different cells as long as they are not already occupied. >>>>>>>>>> >>>>>>>>>> Any suggestion/feedback on building the virtual grid would be >>>>>>>>>> appreciated. >>>>>>>>>> >>>>>>>>>> [1] chevronEditor_virtualGrid_mockup >>>>>>>>>> <https://docs.google.com/a/wso2.com/drawings/d/1CJwFQrm4FjKSLS23I0iXWZwLg_D4ddramm62c0q3lAw/edit?usp=sharing> >>>>>>>>>> >>>>>>>>>> Thanks & Regards, >>>>>>>>>> >>>>>>>>>> Himasha Guruge >>>>>>>>>> *Software Engineer* >>>>>>>>>> WS*O2* *Inc.* >>>>>>>>>> Mobile: +94 777459299 >>>>>>>>>> himas...@wso2.com >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Himasha Guruge >>>>>>> *Software Engineer* >>>>>>> WS*O2* *Inc.* >>>>>>> Mobile: +94 777459299 >>>>>>> himas...@wso2.com >>>>>>> >>>>>> >>>>> >>>>> -- >>>>> Himasha Guruge >>>>> *Software Engineer* >>>>> WS*O2* *Inc.* >>>>> Mobile: +94 777459299 >>>>> himas...@wso2.com >>>>> >>>> >>> >>> >>> -- >>> Himasha Guruge >>> *Software Engineer* >>> WS*O2* *Inc.* >>> Mobile: +94 777459299 >>> himas...@wso2.com >>> >> >> > > > -- > Himasha Guruge > *Software Engineer* > WS*O2* *Inc.* > Mobile: +94 777459299 > himas...@wso2.com >
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
