Hi Tammo, Actually i have finished with the xsl transformation of .bpel files into .html on BPELviz but i am not really figuring out how to integrated it on ODE. Please I really need you help. thanks
Regards, Duplex On Fri, Jul 3, 2015 at 2:17 AM, tony pro <tony14...@gmail.com> wrote: > Hi Tammo, > > Here is what i did sofar, It though me quite some time to understand the > BPELviz.xsl code > since i am also writting my exams. > But, finally I understood it very well > and this is what I actually what i did; > > >restructured some components > >add start and end component > >add different activities icons > >add status icons(static) > >add event handler to get activity detail on click action > >start the components linking > >and add a panel that is displaying activity details > > what is remaining > >handling activities status on ODE > >complete the linking > >document and polishing > > **** Get it run and the text ******** > > >clone the repos > >https://github.com/kamdjouduplex/BPELviz > >then just run it using all the normal BPELviz and gradlew commands > >make sure your copy file "dom.jsPlumb-1.7.5-min.js"f found " > https://github.com/kamdjouduplex/BPELviz/tree/master/src/main/resources"; > into your generated directory before open the html file > >that is how it's working for me. The gradle is no copying automatically > the added js file to the generated directory > > > > ***** Please for the rest of the project ********* > >since i already know how the ODE works, > >how JSPlomb works, > >and how the BPELviz works, > >I thing that the rest of the project will be done > >and by the July 10 I will finish with my exams > >after that the only thing i will be doing will only be coding days and > nights > > I will be writing today I will only be connected in the evening. > So, I will appreciate every thing that you can do for me to pass the > mid-term evaluation and the rest will be done > Thanks very much > > Regards, > Duplex > > On Thu, Jun 18, 2015 at 6:12 PM, tony pro <tony14...@gmail.com> wrote: > >> Hello Tammo, >> >> I am sorry for that, I am also having the same issue why scrolling. >> and concerning the approach i am a bit confuse . >> >> Please can you set up a short call for us to be on the same page ? >> my time zone is UTC+1 >> thanks >> Duplex >> >> On Thu, Jun 18, 2015 at 1:54 PM, Tammo van Lessen <tvanles...@gmail.com> >> wrote: >> >>> Hi Duplex, >>> >>> sorry, it took me a bit longer to get a running setup to check your code. >>> At a first glance it looks good, though I noticed some rendering issues >>> when scrolling. Does that also happen on your maschine? >>> >>> However, I'm not entirely sure if you are on the right track, since the >>> data source you are currently using is the wrong one. This is the data >>> that >>> knows the state of certain activities, so either this or the event streak >>> can be used to set the status of the activities rendered in the diagram. >>> The diagram however should not be rendered from this data, but should be >>> rendered from the original BPEL model, which is currently not available >>> via >>> API in the console, but we can add this. >>> >>> Perhaps you know this already and are just playing around with jsPlumb >>> yet, >>> then please disregard this comment. Otherwise I'd suggest the following >>> steps: >>> >>> 1) Take a look at bpelviz and try to improve the generated HTML so that >>> it >>> a) looks a bit more like a process model, i.e. with icons, some room for >>> metadata (start/completion date, status). This task would mainly be >>> tweaking the XSLT script. >>> 2) The special thing in BPEL processes are flows and links. All other >>> activites are blocks and can easily nested, i.e. event in HTML they can >>> be >>> nested divs. Flows however can connect (almost) arbitarary activites, as >>> long as they are somehow a child activity of a <flow>. The idea is to use >>> jsPlumb to render these links between activities. >>> 3) Incorporate such generated HTML artifacts into the console. The idea >>> is >>> that ODE will apply the XSLT script to the BPEL file to generate the HTML >>> file during deployment. Then we implement an API function so that the >>> console can request this HTML. This HTML shall then be displayed on the >>> visuals page in the console, enriched with the data from the activities >>> statuses, i.e. status and timestamps. >>> >>> Does this match also your understanding and can we agree on that? Or do >>> you >>> have a different understanding? Please let me know so that we are sure to >>> be on the same page. We could also set up short call if you like. >>> >>> Thanks, >>> Tammo >>> >>> On Sun, Jun 14, 2015 at 11:56 PM, tony pro <tony14...@gmail.com> wrote: >>> >>> > Hello Tammo, Sathwik. >>> > >>> > I just finished the very basic visual console here is the link to have >>> a >>> > look. >>> > https://github.com/kamdjouduplex/ode-console >>> > >>> > >Also I really need to see how we can reorder the defferent activities >>> in >>> > order so the by rendered them I wiil just concentrate my self on >>> > displayment of component and links without worry about order. >>> > >>> > >or any suggestion or help. >>> > >>> > thanks, >>> > >>> > -- >>> > >>> > + <tony14...@gmail.com>237 70274538 >>> > Univertity of Buea Cameroon >>> > https://kamdjou-resume.firebaseapp.com/ >>> > >>> >>> >>> >>> -- >>> Tammo van Lessen - http://www.taval.de >>> >> >> >> >> -- >> >> + <tony14...@gmail.com>237 70274538 >> Univertity of Buea Cameroon >> https://kamdjou-resume.firebaseapp.com/ >> > > > > -- > > + <tony14...@gmail.com>237 70274538 > Univertity of Buea Cameroon > https://kamdjou-resume.firebaseapp.com/ > -- + <tony14...@gmail.com>237 70274538 Univertity of Buea Cameroon https://kamdjou-resume.firebaseapp.com/
