On Mon, Apr 4, 2016 at 3:33 PM, Samitha Chathuranga <sami...@wso2.com> wrote:
> Hi Sameera, > > We have 3 options upto now. > 1- Directly using this app extension in GREG without any code > modifications. > 2- Using the code and modify it as we prefer. > 3- Developing the feature from the scratch. > > But we hope if the 1st option is feasible, there is no mean in going for > others. > > But the problem is that the current view is not exactly what we want. So > need some customizations. In our scenario the tree/graph structure is based > on parent/sub process relationships. (I guess this can be totally done with > this GREG feature). But we want to show some more differentiation to > display predecessor/successor processes relationships. (display which are > the predecessor processes and successor processes of the center process). > This is why we need the customization. We hope to show the latter > relationship via, > a) different colored connectors between processes and/ or > b) different colored icons for such predecessor/successor processes > of that center process. > > Is this possible via directly using this GREG app extension? > Why don't you guys work together and refactor current G-Reg feature into a ES extension ? First go through current G-Reg feature and PC requirements, then separate out what are the generic and specific parts. We should make generic parts into a reusable ES component. Thanks ! > > Thanks. > > On Mon, Apr 4, 2016 at 2:29 PM, Sameera Kannangara <samee...@wso2.com> > wrote: > >> Hi Samith, >> >> G-Reg dependency view displays only governance artifacts and the registry >> associations between them as a graph. >> This feature is developed as an app extension to the ES publisher >> feature, therefore user session management is done via publisher app. >> >> If the processes and sub-processes described in your scenario are >> represented as governance artifacts you can use G-Reg dependency graph >> development code easily to create a solution for your scenario. >> Even if those graph components are not stored as governance artifacts you >> should be able to reuse dependency graph implementation code with a little >> development effort. >> >> Thank you, >> SameeraK. >> >> >> >> On Mon, Apr 4, 2016 at 2:12 PM, Samitha Chathuranga <sami...@wso2.com> >> wrote: >> >>> Hi All, >>> >>> I am going to add a feature into the PC to view associations between >>> processes in a graphical illustration. So all the predecessors, successors, >>> subprocesses of a selected process should be displayed in this view. This >>> would be something like a graph with certain modifications. And when >>> clicking on each item, it should be redirected into that process's detailed >>> viewer page. >>> >>> Anyway I have seen that the GREG has such a this feature that view >>> dependencies of artifacts in store, as follows. >>> >>> [image: view dependencies of the selected asset] >>> >>> So my question is can we re use this feature into the PC for the task I >>> have described above. Or will it be good to adapt it to our purpose, rather >>> than developing from the scratch, using D3 or something else. Will it be >>> effective and efficient to re use/ adapt the same feature for my task? Your >>> comments are appreciated. >>> >>> Thanks >>> >>> -- >>> Samitha Chathuranga >>> Software Engineer, WSO2 Inc. >>> lean.enterprise.middleware >>> Mobile: +94715123761 >>> >>> _______________________________________________ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Sameera Kannangara* >> Software Engineer >> Platform TG; WSO2 Inc. http://wso2.com >> Contact: >> phone: +94719541577 >> Lean . Enterprise . Middleware >> > > > > -- > Samitha Chathuranga > Software Engineer, WSO2 Inc. > lean.enterprise.middleware > Mobile: +94715123761 > -- Sagara Gunathunga Architect; WSO2, Inc.; http://wso2.com V.P Apache Web Services; http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
