Status of NewWave

NH
Norbert Hartl <norbert@hartl.name>
Tue, Nov 19, 2019 4:03 PM

Hi,

as we have this nice little mailing list I like to kick off conversation with an inquiry. Would it be possible to sketch the current state and future plans a bit. I want to participate but I'm a bit lost.

The last two weeks I read a bit the existing code of NewWave. As there were other mention it is currently not clear what should be the usage pattern of the workflow engine. Basic terms are not defined and classes do not have comments. This makes it a bit hard to participate.

Two things I helped a bit are …

...getting a seaside based app to run. The current approach of the usage scenario is that the workflow enigne has a http interface using Teapot server to enable requesting and adding information to the workflow. The seaside app gets a serialized definition of the fields for the flow which it uses to create a HTML form to inquire the data. The return path over the Teapot server is currently not working. It would be good to get this fully running so a first use case is present.

… migrating the current Roassal code to Roassal3. This is a basic script to visualize the workflow. This will be nice to analyze and monitor the flow. As well it could also be a base to create a workflow editor.

I'm willing to spend more time on improving the code but I would need a little bit of help/plan.

What do you think?

Norbert

Hi, as we have this nice little mailing list I like to kick off conversation with an inquiry. Would it be possible to sketch the current state and future plans a bit. I want to participate but I'm a bit lost. The last two weeks I read a bit the existing code of NewWave. As there were other mention it is currently not clear what should be the usage pattern of the workflow engine. Basic terms are not defined and classes do not have comments. This makes it a bit hard to participate. Two things I helped a bit are … ...getting a seaside based app to run. The current approach of the usage scenario is that the workflow enigne has a http interface using Teapot server to enable requesting and adding information to the workflow. The seaside app gets a serialized definition of the fields for the flow which it uses to create a HTML form to inquire the data. The return path over the Teapot server is currently not working. It would be good to get this fully running so a first use case is present. … migrating the current Roassal code to Roassal3. This is a basic script to visualize the workflow. This will be nice to analyze and monitor the flow. As well it could also be a base to create a workflow editor. I'm willing to spend more time on improving the code but I would need a little bit of help/plan. What do you think? Norbert
SK
Sebastijan Kaplar <kaplar@uns.ac.rs>
Wed, Nov 20, 2019 11:55 AM

Hi Norbert,

Pozdrav / Best regards,

Sebastijan Kaplar Fakultet tehničkih nauka Univerzitet u Novom Sadu

On Nov 19, 2019, at 17:03, Norbert Hartl norbert@hartl.name wrote:

Hi,

as we have this nice little mailing list I like to kick off conversation with an inquiry. Would it be possible to sketch the current state and future plans a bit. I want to participate but I'm a bit lost.

Yes I can work on that. However, my wife gave birth to a little girl on Friday, everything is fine but I took a couple of days off to get into the rhythm and get used to everything new.

The last two weeks I read a bit the existing code of NewWave. As there were other mention it is currently not clear what should be the usage pattern of the workflow engine. Basic terms are not defined and classes do not have comments. This makes it a bit hard to participate.

Two things I helped a bit are …

...getting a seaside based app to run. The current approach of the usage scenario is that the workflow enigne has a http interface using Teapot server to enable requesting and adding information to the workflow. The seaside app gets a serialized definition of the fields for the flow which it uses to create a HTML form to inquire the data. The return path over the Teapot server is currently not working. It would be good to get this fully running so a first use case is present.

… migrating the current Roassal code to Roassal3. This is a basic script to visualize the workflow. This will be nice to analyze and monitor the flow. As well it could also be a base to create a workflow editor.

I'm willing to spend more time on improving the code but I would need a little bit of help/plan.

Thank you for the help so far, you helped out a lot. I’ll also send email to everyone I know that was interested in the engine so they can subscribe. And I think Aleksandra (which was with Nina at the conference) did some things that should be merged and she could explain it a bit.

Hi Norbert, -- Pozdrav / Best regards, Sebastijan Kaplar Fakultet tehničkih nauka Univerzitet u Novom Sadu > On Nov 19, 2019, at 17:03, Norbert Hartl <norbert@hartl.name> wrote: > > Hi, > > as we have this nice little mailing list I like to kick off conversation with an inquiry. Would it be possible to sketch the current state and future plans a bit. I want to participate but I'm a bit lost. Yes I can work on that. However, my wife gave birth to a little girl on Friday, everything is fine but I took a couple of days off to get into the rhythm and get used to everything new. > > The last two weeks I read a bit the existing code of NewWave. As there were other mention it is currently not clear what should be the usage pattern of the workflow engine. Basic terms are not defined and classes do not have comments. This makes it a bit hard to participate. > > Two things I helped a bit are … > > ...getting a seaside based app to run. The current approach of the usage scenario is that the workflow enigne has a http interface using Teapot server to enable requesting and adding information to the workflow. The seaside app gets a serialized definition of the fields for the flow which it uses to create a HTML form to inquire the data. The return path over the Teapot server is currently not working. It would be good to get this fully running so a first use case is present. > > … migrating the current Roassal code to Roassal3. This is a basic script to visualize the workflow. This will be nice to analyze and monitor the flow. As well it could also be a base to create a workflow editor. > > I'm willing to spend more time on improving the code but I would need a little bit of help/plan. Thank you for the help so far, you helped out a lot. I’ll also send email to everyone I know that was interested in the engine so they can subscribe. And I think Aleksandra (which was with Nina at the conference) did some things that should be merged and she could explain it a bit. > > What do you think? > > Norbert > -- > Workflow-engine mailing list > Workflow-engine@lists.pharo.org > http://lists.pharo.org/mailman/listinfo/workflow-engine_lists.pharo.org
NH
Norbert Hartl <norbert@hartl.name>
Wed, Nov 20, 2019 3:15 PM

Hi,

Am 20.11.2019 um 12:55 schrieb Sebastijan Kaplar kaplar@uns.ac.rs:

Hi Norbert,

Pozdrav / Best regards,

Sebastijan Kaplar Fakultet tehničkih nauka Univerzitet u Novom Sadu

On Nov 19, 2019, at 17:03, Norbert Hartl <norbert@hartl.name mailto:norbert@hartl.name> wrote:

Hi,

as we have this nice little mailing list I like to kick off conversation with an inquiry. Would it be possible to sketch the current state and future plans a bit. I want to participate but I'm a bit lost.

Yes I can work on that. However, my wife gave birth to a little girl on Friday, everything is fine but I took a couple of days off to get into the rhythm and get used to everything new.

Congratulations. So you have indeed better things to do ;) Take your time it is an interesting adventure from now. My baby girl just turned 6 month today.

The last two weeks I read a bit the existing code of NewWave. As there were other mention it is currently not clear what should be the usage pattern of the workflow engine. Basic terms are not defined and classes do not have comments. This makes it a bit hard to participate.

Two things I helped a bit are …

...getting a seaside based app to run. The current approach of the usage scenario is that the workflow enigne has a http interface using Teapot server to enable requesting and adding information to the workflow. The seaside app gets a serialized definition of the fields for the flow which it uses to create a HTML form to inquire the data. The return path over the Teapot server is currently not working. It would be good to get this fully running so a first use case is present.

… migrating the current Roassal code to Roassal3. This is a basic script to visualize the workflow. This will be nice to analyze and monitor the flow. As well it could also be a base to create a workflow editor.

I'm willing to spend more time on improving the code but I would need a little bit of help/plan.

Thank you for the help so far, you helped out a lot. I’ll also send email to everyone I know that was interested in the engine so they can subscribe. And I think Aleksandra (which was with Nina at the conference) did some things that should be merged and she could explain it a bit.

Ok, good. I just need some kind of a plan so I can plan my time to invest because there is not much.

The first thing I want to do is to refactor the seaside app a bit and clean it. I can directly see struggles here and there with all of that stuff like magritte. I'm also not a big fan to compile the classes in the seaside app. I think it can do easily with the description and a dictionary. Then I would close the gap to the Teapot server. I got it running once with a few bad tweaks. I would make that working if you don't mind.

If I can ask you a favor could you describe me the basic model like

  • Node
  • Event
  • Task
  • Engine
  • Executor
  • Activation
  • Flow
  • ….

this would help me a lot understanding what you are building and these explanations would probably very good class comments ;)

Hope you get some sleep ;)

Norbert

Hi, > Am 20.11.2019 um 12:55 schrieb Sebastijan Kaplar <kaplar@uns.ac.rs>: > > Hi Norbert, > -- > Pozdrav / Best regards, > > Sebastijan Kaplar > Fakultet tehničkih nauka > Univerzitet u Novom Sadu > >> On Nov 19, 2019, at 17:03, Norbert Hartl <norbert@hartl.name <mailto:norbert@hartl.name>> wrote: >> >> Hi, >> >> as we have this nice little mailing list I like to kick off conversation with an inquiry. Would it be possible to sketch the current state and future plans a bit. I want to participate but I'm a bit lost. > Yes I can work on that. However, my wife gave birth to a little girl on Friday, everything is fine but I took a couple of days off to get into the rhythm and get used to everything new. > Congratulations. So you have indeed better things to do ;) Take your time it is an interesting adventure from now. My baby girl just turned 6 month today. >> >> The last two weeks I read a bit the existing code of NewWave. As there were other mention it is currently not clear what should be the usage pattern of the workflow engine. Basic terms are not defined and classes do not have comments. This makes it a bit hard to participate. >> >> Two things I helped a bit are … >> >> ...getting a seaside based app to run. The current approach of the usage scenario is that the workflow enigne has a http interface using Teapot server to enable requesting and adding information to the workflow. The seaside app gets a serialized definition of the fields for the flow which it uses to create a HTML form to inquire the data. The return path over the Teapot server is currently not working. It would be good to get this fully running so a first use case is present. >> >> … migrating the current Roassal code to Roassal3. This is a basic script to visualize the workflow. This will be nice to analyze and monitor the flow. As well it could also be a base to create a workflow editor. >> >> I'm willing to spend more time on improving the code but I would need a little bit of help/plan. > > Thank you for the help so far, you helped out a lot. I’ll also send email to everyone I know that was interested in the engine so they can subscribe. And I think Aleksandra (which was with Nina at the conference) did some things that should be merged and she could explain it a bit. Ok, good. I just need some kind of a plan so I can plan my time to invest because there is not much. The first thing I want to do is to refactor the seaside app a bit and clean it. I can directly see struggles here and there with all of that stuff like magritte. I'm also not a big fan to compile the classes in the seaside app. I think it can do easily with the description and a dictionary. Then I would close the gap to the Teapot server. I got it running once with a few bad tweaks. I would make that working if you don't mind. If I can ask you a favor could you describe me the basic model like - Node - Event - Task - Engine - Executor - Activation - Flow - …. this would help me a lot understanding what you are building and these explanations would probably very good class comments ;) Hope you get some sleep ;) Norbert > >> >> What do you think? >> >> Norbert >> -- >> Workflow-engine mailing list >> Workflow-engine@lists.pharo.org <mailto:Workflow-engine@lists.pharo.org> >> http://lists.pharo.org/mailman/listinfo/workflow-engine_lists.pharo.org > > -- > Workflow-engine mailing list > Workflow-engine@lists.pharo.org > http://lists.pharo.org/mailman/listinfo/workflow-engine_lists.pharo.org
GM
Gordana Milosavljevic <grist@uns.ac.rs>
Fri, Nov 22, 2019 7:40 AM

Hi Norbert,

Thanks a lot for your help!  It's impressive that you have time at all, since you also have a baby.

If I can ask you a favor could you describe me the basic model like

  • Node
  • Event
  • Task
  • Engine
  • Executor
  • Activation
  • Flow
  • ….

this would help me a lot understanding what you are building and these explanations would probably very good class comments ;)

Please find attached the paper from ESUG 2019. I hope it can give some explanations, until Sebastijan become operational again :).

Best regards,

Gordana

-- dr Gordana Milosavljevic, Associate Professor, Computing and Control Department, Faculty of Tecnical Sciences, University of Novi Sad, Serbia, www.informatika.ftn.uns.ac.rs

Hi Norbert, Thanks a lot for your help!  It's impressive that you have time at all, since you also have a baby. > If I can ask you a favor could you describe me the basic model like > > - Node > - Event > - Task > - Engine > - Executor > - Activation > - Flow > - …. > > this would help me a lot understanding what you are building and these > explanations would probably very good class comments ;) > Please find attached the paper from ESUG 2019. I hope it can give some explanations, until Sebastijan become operational again :). Best regards, Gordana -- dr Gordana Milosavljevic, Associate Professor, Computing and Control Department, Faculty of Tecnical Sciences, University of Novi Sad, Serbia, www.informatika.ftn.uns.ac.rs
SK
Sebastijan Kaplar <kaplar@uns.ac.rs>
Fri, Nov 29, 2019 3:38 PM

Hello Norbert,

I’ve just pushed a new commit with added some descriptions for workflow, I’m also attaching uml model for the core in this email. I’ll also continue adding the descriptions. I hope it gets a bit easier, however if you’re interested we can make some time do discuss over discord/skype maybe do some pair programming a bit where I can answer right away any questions you have. And basically to mention, the core package is the one that represents a model, and the engine package is the one that should manipulate/execute that model.

-- Pozdrav / Best regards,

Sebastijan Kaplar Fakultet tehničkih nauka Univerzitet u Novom Sadu

On Nov 22, 2019, at 08:40, Gordana Milosavljevic grist@uns.ac.rs wrote:

Hi Norbert,

Thanks a lot for your help!  It's impressive that you have time at all, since you also have a baby.

If I can ask you a favor could you describe me the basic model like

  • Node
  • Event
  • Task
  • Engine
  • Executor
  • Activation
  • Flow
  • ….

this would help me a lot understanding what you are building and these explanations would probably very good class comments ;)

Please find attached the paper from ESUG 2019. I hope it can give some explanations, until Sebastijan become operational again :).

Best regards,

Gordana

-- dr Gordana Milosavljevic, Associate Professor, Computing and Control Department, Faculty of Tecnical Sciences, University of Novi Sad, Serbia, www.informatika.ftn.uns.ac.rs

<IWST19_paper_19(2).pdf>-- Workflow-engine mailing list Workflow-engine@lists.pharo.org http://lists.pharo.org/mailman/listinfo/workflow-engine_lists.pharo.org

Hello Norbert, I’ve just pushed a new commit with added some descriptions for workflow, I’m also attaching uml model for the core in this email. I’ll also continue adding the descriptions. I hope it gets a bit easier, however if you’re interested we can make some time do discuss over discord/skype maybe do some pair programming a bit where I can answer right away any questions you have. And basically to mention, the core package is the one that represents a model, and the engine package is the one that should manipulate/execute that model. -- Pozdrav / Best regards, Sebastijan Kaplar Fakultet tehničkih nauka Univerzitet u Novom Sadu > On Nov 22, 2019, at 08:40, Gordana Milosavljevic <grist@uns.ac.rs> wrote: > > Hi Norbert, > > Thanks a lot for your help! It's impressive that you have time at all, since you also have a baby. > > >> If I can ask you a favor could you describe me the basic model like >> >> - Node >> - Event >> - Task >> - Engine >> - Executor >> - Activation >> - Flow >> - …. >> >> this would help me a lot understanding what you are building and these explanations would probably very good class comments ;) >> > Please find attached the paper from ESUG 2019. I hope it can give some explanations, until Sebastijan become operational again :). > > Best regards, > > Gordana > > > -- > dr Gordana Milosavljevic, > Associate Professor, > Computing and Control Department, > Faculty of Tecnical Sciences, > University of Novi Sad, Serbia, > www.informatika.ftn.uns.ac.rs > > <IWST19_paper_19(2).pdf>-- > Workflow-engine mailing list > Workflow-engine@lists.pharo.org > http://lists.pharo.org/mailman/listinfo/workflow-engine_lists.pharo.org
NH
Norbert Hartl <norbert@hartl.name>
Wed, Feb 5, 2020 12:06 PM

Hi Sebastijan,

it has been ages since last contact. I'm back since beginning of january and nearly catched up with most stuff that was accumulating on my desk.

Am 29.11.2019 um 16:38 schrieb Sebastijan Kaplar kaplar@uns.ac.rs:

Hello Norbert,

I’ve just pushed a new commit with added some descriptions for workflow, I’m also attaching uml model for the core in this email. I’ll also continue adding the descriptions. I hope it gets a bit easier, however if you’re interested we can make some time do discuss over discord/skype maybe do some pair programming a bit where I can answer right away any questions you have. And basically to mention, the core package is the one that represents a model, and the engine package is the one that should manipulate/execute that model.

Can you send the picture again the resolution is too low? If you use a Mac be aware that there is a selection which quality you want to send with a default that is only suitable for photographs. Having an online session is a good idea. I will scan the available mateial and try to compile a list of better questions.

Norbert

<workflow.png>

Pozdrav / Best regards,

Sebastijan Kaplar Fakultet tehničkih nauka Univerzitet u Novom Sadu

On Nov 22, 2019, at 08:40, Gordana Milosavljevic <grist@uns.ac.rs mailto:grist@uns.ac.rs> wrote:

Hi Norbert,

Thanks a lot for your help!  It's impressive that you have time at all, since you also have a baby.

If I can ask you a favor could you describe me the basic model like

  • Node
  • Event
  • Task
  • Engine
  • Executor
  • Activation
  • Flow
  • ….

this would help me a lot understanding what you are building and these explanations would probably very good class comments ;)

Please find attached the paper from ESUG 2019. I hope it can give some explanations, until Sebastijan become operational again :).

Best regards,

Gordana

-- dr Gordana Milosavljevic, Associate Professor, Computing and Control Department, Faculty of Tecnical Sciences, University of Novi Sad, Serbia, www.informatika.ftn.uns.ac.rs http://www.informatika.ftn.uns.ac.rs/

<IWST19_paper_19(2).pdf>-- Workflow-engine mailing list Workflow-engine@lists.pharo.org http://lists.pharo.org/mailman/listinfo/workflow-engine_lists.pharo.org

Hi Sebastijan, it has been ages since last contact. I'm back since beginning of january and nearly catched up with most stuff that was accumulating on my desk. > Am 29.11.2019 um 16:38 schrieb Sebastijan Kaplar <kaplar@uns.ac.rs>: > > Hello Norbert, > > I’ve just pushed a new commit with added some descriptions for workflow, I’m also attaching uml model for the core in this email. I’ll also continue adding the descriptions. I hope it gets a bit easier, however if you’re interested we can make some time do discuss over discord/skype maybe do some pair programming a bit where I can answer right away any questions you have. > And basically to mention, the core package is the one that represents a model, and the engine package is the one that should manipulate/execute that model. > Can you send the picture again the resolution is too low? If you use a Mac be aware that there is a selection which quality you want to send with a default that is only suitable for photographs. Having an online session is a good idea. I will scan the available mateial and try to compile a list of better questions. Norbert > > <workflow.png> > -- > Pozdrav / Best regards, > > Sebastijan Kaplar > Fakultet tehničkih nauka > Univerzitet u Novom Sadu > >> On Nov 22, 2019, at 08:40, Gordana Milosavljevic <grist@uns.ac.rs <mailto:grist@uns.ac.rs>> wrote: >> >> Hi Norbert, >> >> Thanks a lot for your help! It's impressive that you have time at all, since you also have a baby. >> >> >>> If I can ask you a favor could you describe me the basic model like >>> >>> - Node >>> - Event >>> - Task >>> - Engine >>> - Executor >>> - Activation >>> - Flow >>> - …. >>> >>> this would help me a lot understanding what you are building and these explanations would probably very good class comments ;) >>> >> Please find attached the paper from ESUG 2019. I hope it can give some explanations, until Sebastijan become operational again :). >> >> Best regards, >> >> Gordana >> >> >> -- >> dr Gordana Milosavljevic, >> Associate Professor, >> Computing and Control Department, >> Faculty of Tecnical Sciences, >> University of Novi Sad, Serbia, >> www.informatika.ftn.uns.ac.rs <http://www.informatika.ftn.uns.ac.rs/> >> >> <IWST19_paper_19(2).pdf>-- >> Workflow-engine mailing list >> Workflow-engine@lists.pharo.org >> http://lists.pharo.org/mailman/listinfo/workflow-engine_lists.pharo.org >
SK
Sebastijan Kaplar <kaplar@uns.ac.rs>
Wed, Feb 5, 2020 2:52 PM

Hi Norbert,

good to hear from you. Aleksandra said she’ll update the models we have (she’s on the mailing list, and we had updates). Aleksandra did you maybe managed to do it so you could send it to us? If not I’ll find the old ones and resend it.

I’ve managed to push out some updates since we last heard: I’ve separated model and execution, so it’s possible to have multiple processes running now. Still needs some testing but it’s there. WebApplication now can communicate with our server. If you remember WebApp couldn’t pull, neither push out tasks. So now, web application can actually get the task from server, render it/get component and submit the answer back to the server.

What I’m waiting for now is the user roles part. One of the MSc students wanted to work on that, so we had sessions and discussions and I hope he will finish soon.

Examples are updated in ExampleExecutions class. And there’s also one example that you can try out using the web app:

proc1 := ExampleExecutions returnSimpleProcess. proc2 := ExampleExecutions returnSimpleProcess2.

engine := WaveEngine new. engine addProcess: proc1 name: (proc1 processInstanceId). engine addProcess: proc2 name: (proc2 processInstanceId). engine startTeapotServer. engine startProcess: (proc1 processInstanceId). engine startProcess: (proc2 processInstanceId).

I think everything should be on github. You get to the app:

http://localhost:8080/NewWave-Engine http://localhost:8080/NewWave-Engine

user1, user1 are credentials

Please have in mind that you should initialize WebApp:

FUApplicationRootComponent initialize. FUApplication createDemo.

I think it should work. For everything else I am here and happy to answer.

PS Master is the branch you should look at now.

Pozdrav / Best regards,

Sebastijan Kaplar Fakultet tehničkih nauka Univerzitet u Novom Sadu

On Feb 5, 2020, at 13:06, Norbert Hartl norbert@hartl.name wrote:

Hi Sebastijan,

it has been ages since last contact. I'm back since beginning of january and nearly catched up with most stuff that was accumulating on my desk.

Am 29.11.2019 um 16:38 schrieb Sebastijan Kaplar <kaplar@uns.ac.rs mailto:kaplar@uns.ac.rs>:

Hello Norbert,

I’ve just pushed a new commit with added some descriptions for workflow, I’m also attaching uml model for the core in this email. I’ll also continue adding the descriptions. I hope it gets a bit easier, however if you’re interested we can make some time do discuss over discord/skype maybe do some pair programming a bit where I can answer right away any questions you have. And basically to mention, the core package is the one that represents a model, and the engine package is the one that should manipulate/execute that model.

Can you send the picture again the resolution is too low? If you use a Mac be aware that there is a selection which quality you want to send with a default that is only suitable for photographs. Having an online session is a good idea. I will scan the available mateial and try to compile a list of better questions.

Norbert

<workflow.png>

Pozdrav / Best regards,

Sebastijan Kaplar Fakultet tehničkih nauka Univerzitet u Novom Sadu

On Nov 22, 2019, at 08:40, Gordana Milosavljevic <grist@uns.ac.rs mailto:grist@uns.ac.rs> wrote:

Hi Norbert,

Thanks a lot for your help!  It's impressive that you have time at all, since you also have a baby.

If I can ask you a favor could you describe me the basic model like

  • Node
  • Event
  • Task
  • Engine
  • Executor
  • Activation
  • Flow
  • ….

this would help me a lot understanding what you are building and these explanations would probably very good class comments ;)

Please find attached the paper from ESUG 2019. I hope it can give some explanations, until Sebastijan become operational again :).

Best regards,

Gordana

-- dr Gordana Milosavljevic, Associate Professor, Computing and Control Department, Faculty of Tecnical Sciences, University of Novi Sad, Serbia, www.informatika.ftn.uns.ac.rs http://www.informatika.ftn.uns.ac.rs/

<IWST19_paper_19(2).pdf>-- Workflow-engine mailing list Workflow-engine@lists.pharo.org mailto:Workflow-engine@lists.pharo.org http://lists.pharo.org/mailman/listinfo/workflow-engine_lists.pharo.org

Hi Norbert, good to hear from you. Aleksandra said she’ll update the models we have (she’s on the mailing list, and we had updates). Aleksandra did you maybe managed to do it so you could send it to us? If not I’ll find the old ones and resend it. I’ve managed to push out some updates since we last heard: I’ve separated model and execution, so it’s possible to have multiple processes running now. Still needs some testing but it’s there. WebApplication now can communicate with our server. If you remember WebApp couldn’t pull, neither push out tasks. So now, web application can actually get the task from server, render it/get component and submit the answer back to the server. What I’m waiting for now is the user roles part. One of the MSc students wanted to work on that, so we had sessions and discussions and I hope he will finish soon. Examples are updated in ExampleExecutions class. And there’s also one example that you can try out using the web app: proc1 := ExampleExecutions returnSimpleProcess. proc2 := ExampleExecutions returnSimpleProcess2. engine := WaveEngine new. engine addProcess: proc1 name: (proc1 processInstanceId). engine addProcess: proc2 name: (proc2 processInstanceId). engine startTeapotServer. engine startProcess: (proc1 processInstanceId). engine startProcess: (proc2 processInstanceId). I think everything should be on github. You get to the app: http://localhost:8080/NewWave-Engine <http://localhost:8080/NewWave-Engine> user1, user1 are credentials Please have in mind that you should initialize WebApp: FUApplicationRootComponent initialize. FUApplication createDemo. I think it should work. For everything else I am here and happy to answer. PS Master is the branch you should look at now. -- Pozdrav / Best regards, Sebastijan Kaplar Fakultet tehničkih nauka Univerzitet u Novom Sadu > On Feb 5, 2020, at 13:06, Norbert Hartl <norbert@hartl.name> wrote: > > Hi Sebastijan, > > it has been ages since last contact. I'm back since beginning of january and nearly catched up with most stuff that was accumulating on my desk. > >> Am 29.11.2019 um 16:38 schrieb Sebastijan Kaplar <kaplar@uns.ac.rs <mailto:kaplar@uns.ac.rs>>: >> >> Hello Norbert, >> >> I’ve just pushed a new commit with added some descriptions for workflow, I’m also attaching uml model for the core in this email. I’ll also continue adding the descriptions. I hope it gets a bit easier, however if you’re interested we can make some time do discuss over discord/skype maybe do some pair programming a bit where I can answer right away any questions you have. >> And basically to mention, the core package is the one that represents a model, and the engine package is the one that should manipulate/execute that model. >> > Can you send the picture again the resolution is too low? If you use a Mac be aware that there is a selection which quality you want to send with a default that is only suitable for photographs. Having an online session is a good idea. I will scan the available mateial and try to compile a list of better questions. > > Norbert > >> >> <workflow.png> >> -- >> Pozdrav / Best regards, >> >> Sebastijan Kaplar >> Fakultet tehničkih nauka >> Univerzitet u Novom Sadu >> >>> On Nov 22, 2019, at 08:40, Gordana Milosavljevic <grist@uns.ac.rs <mailto:grist@uns.ac.rs>> wrote: >>> >>> Hi Norbert, >>> >>> Thanks a lot for your help! It's impressive that you have time at all, since you also have a baby. >>> >>> >>>> If I can ask you a favor could you describe me the basic model like >>>> >>>> - Node >>>> - Event >>>> - Task >>>> - Engine >>>> - Executor >>>> - Activation >>>> - Flow >>>> - …. >>>> >>>> this would help me a lot understanding what you are building and these explanations would probably very good class comments ;) >>>> >>> Please find attached the paper from ESUG 2019. I hope it can give some explanations, until Sebastijan become operational again :). >>> >>> Best regards, >>> >>> Gordana >>> >>> >>> -- >>> dr Gordana Milosavljevic, >>> Associate Professor, >>> Computing and Control Department, >>> Faculty of Tecnical Sciences, >>> University of Novi Sad, Serbia, >>> www.informatika.ftn.uns.ac.rs <http://www.informatika.ftn.uns.ac.rs/> >>> >>> <IWST19_paper_19(2).pdf>-- >>> Workflow-engine mailing list >>> Workflow-engine@lists.pharo.org <mailto:Workflow-engine@lists.pharo.org> >>> http://lists.pharo.org/mailman/listinfo/workflow-engine_lists.pharo.org >> >
AM
Aleksandra Mitrović <aleksandramitrovic@uns.ac.rs>
Fri, Feb 7, 2020 12:49 PM

Hi all,

Sorry for the late answer. I'm almost done with a Class diagram, but I can't finish it because I can't figure out some associations between classes and types for the properties, especially method return types. I think that I need some help from Sebastian to complete it. I've created it with Astah professional software, and it has a free version viewer (Astah Viewer http://astah.net/editions/viewer). Soon, I'll share in the form of a .asta file, and if necessary I could export it to some different format.

Best regards,

Aleksandra Mitrovic

On 5.2.2020. 15:52, Sebastijan Kaplar wrote:

Hi Norbert,

good to hear from you. Aleksandra said she’ll update the models we have (she’s on the mailing list, and we had updates). Aleksandra did you maybe managed to do it so you could send it to us? If not I’ll find the old ones and resend it.

I’ve managed to push out some updates since we last heard: I’ve separated model and execution, so it’s possible to have multiple processes running now. Still needs some testing but it’s there. WebApplication now can communicate with our server. If you remember WebApp couldn’t pull, neither push out tasks. So now, web application can actually get the task from server, render it/get component and submit the answer back to the server.

What I’m waiting for now is the user roles part. One of the MSc students wanted to work on that, so we had sessions and discussions and I hope he will finish soon.

Examples are updated in ExampleExecutions class. And there’s also one example that you can try out using the web app:

proc1 := ExampleExecutions returnSimpleProcess. proc2 := ExampleExecutions returnSimpleProcess2.

engine := WaveEngine new. engine addProcess: proc1 name: (proc1 processInstanceId). engine addProcess: proc2 name: (proc2 processInstanceId). engine startTeapotServer. engine startProcess: (proc1 processInstanceId). engine startProcess: (proc2 processInstanceId).

I think everything should be on github. You get to the app:

http://localhost:8080/NewWave-Engine

user1, user1 are credentials

Please have in mind that you should initialize WebApp:

FUApplicationRootComponent initialize. FUApplication createDemo.

I think it should work. For everything else I am here and happy to answer.

PS Master is the branch you should look at now.

Pozdrav / Best regards,

Sebastijan Kaplar Fakultet tehničkih nauka Univerzitet u Novom Sadu

On Feb 5, 2020, at 13:06, Norbert Hartl <norbert@hartl.name mailto:norbert@hartl.name> wrote:

Hi Sebastijan,

it has been ages since last contact. I'm back since beginning of january and nearly catched up with most stuff that was accumulating on my desk.

Am 29.11.2019 um 16:38 schrieb Sebastijan Kaplar <kaplar@uns.ac.rs mailto:kaplar@uns.ac.rs>:

Hello Norbert,

I’ve just pushed a new commit with added some descriptions for workflow, I’m also attaching uml model for the core in this email. I’ll also continue adding the descriptions. I hope it gets a bit easier, however if you’re interested we can make some time do discuss over discord/skype maybe do some pair programming a bit where I can answer right away any questions you have. And basically to mention, the core package is the one that represents a model, and the engine package is the one that should manipulate/execute that model.

Can you send the picture again the resolution is too low? If you use a Mac be aware that there is a selection which quality you want to send with a default that is only suitable for photographs. Having an online session is a good idea. I will scan the available mateial and try to compile a list of better questions.

Norbert

<workflow.png>

Pozdrav / Best regards,

Sebastijan Kaplar Fakultet tehničkih nauka Univerzitet u Novom Sadu

On Nov 22, 2019, at 08:40, Gordana Milosavljevic <grist@uns.ac.rs mailto:grist@uns.ac.rs> wrote:

Hi Norbert,

Thanks a lot for your help!  It's impressive that you have time at all, since you also have a baby.

If I can ask you a favor could you describe me the basic model like

  • Node
  • Event
  • Task
  • Engine
  • Executor
  • Activation
  • Flow
  • ….

this would help me a lot understanding what you are building and these explanations would probably very good class comments ;)

Please find attached the paper from ESUG 2019. I hope it can give some explanations, until Sebastijan become operational again :).

Best regards,

Gordana

-- dr Gordana Milosavljevic, Associate Professor, Computing and Control Department, Faculty of Tecnical Sciences, University of Novi Sad, Serbia, www.informatika.ftn.uns.ac.rs http://www.informatika.ftn.uns.ac.rs/

<IWST19_paper_19(2).pdf>-- Workflow-engine mailing list Workflow-engine@lists.pharo.org mailto:Workflow-engine@lists.pharo.org http://lists.pharo.org/mailman/listinfo/workflow-engine_lists.pharo.org

Hi all, Sorry for the late answer. I'm almost done with a Class diagram, but I can't finish it because I can't figure out some associations between classes and types for the properties, especially method return types. I think that I need some help from Sebastian to complete it. I've created it with Astah professional software, and it has a free version viewer (Astah Viewer <http://astah.net/editions/viewer>). Soon, I'll share in the form of a .asta file, and if necessary I could export it to some different format. Best regards, Aleksandra Mitrovic On 5.2.2020. 15:52, Sebastijan Kaplar wrote: > Hi Norbert, > > good to hear from you. Aleksandra said she’ll update the models we > have (she’s on the mailing list, and we had updates). Aleksandra did > you maybe managed to do it so you could send it to us? If not I’ll > find the old ones and resend it. > > I’ve managed to push out some updates since we last heard: > I’ve separated model and execution, so it’s possible to have multiple > processes running now. Still needs some testing but it’s there. > WebApplication now can communicate with our server. If you remember > WebApp couldn’t pull, neither push out tasks. So now, web application > can actually get the task from server, render it/get component and > submit the answer back to the server. > > What I’m waiting for now is the user roles part. One of the MSc > students wanted to work on that, so we had sessions and discussions > and I hope he will finish soon. > > Examples are updated in ExampleExecutions class. And there’s also one > example that you can try out using the web app: > > proc1 := ExampleExecutions returnSimpleProcess. > proc2 := ExampleExecutions returnSimpleProcess2. > > engine := WaveEngine new. > engine addProcess: proc1 name: (proc1 processInstanceId). > engine addProcess: proc2 name: (proc2 processInstanceId). > engine startTeapotServer. > engine startProcess: (proc1 processInstanceId). > engine startProcess: (proc2 processInstanceId). > > I think everything should be on github. You get to the app: > > http://localhost:8080/NewWave-Engine > > user1, user1 are credentials > > Please have in mind that you should initialize WebApp: > > FUApplicationRootComponent initialize. > FUApplication createDemo. > > I think it should work. For everything else I am here and happy to answer. > > PS Master is the branch you should look at now. > -- > Pozdrav / Best regards, > > Sebastijan Kaplar > Fakultet tehničkih nauka > Univerzitet u Novom Sadu > >> On Feb 5, 2020, at 13:06, Norbert Hartl <norbert@hartl.name >> <mailto:norbert@hartl.name>> wrote: >> >> Hi Sebastijan, >> >> it has been ages since last contact. I'm back since beginning of >> january and nearly catched up with most stuff that was accumulating >> on my desk. >> >>> Am 29.11.2019 um 16:38 schrieb Sebastijan Kaplar <kaplar@uns.ac.rs >>> <mailto:kaplar@uns.ac.rs>>: >>> >>> Hello Norbert, >>> >>> I’ve just pushed a new commit with added some descriptions for >>> workflow, I’m also attaching uml model for the core in this email. >>> I’ll also continue adding the descriptions. I hope it gets a bit >>> easier, however if you’re interested we can make some time do >>> discuss over discord/skype maybe do some pair programming a bit >>> where I can answer right away any questions you have. >>> And basically to mention, the core package is the one that >>> represents a model, and the engine package is the one that should >>> manipulate/execute that model. >>> >> Can you send the picture again the resolution is too low? If you use >> a Mac be aware that there is a selection which quality you want to >> send with a default that is only suitable for photographs. Having an >> online session is a good idea. I will scan the available mateial and >> try to compile a list of better questions. >> >> Norbert >> >>> >>> <workflow.png> >>> -- >>> Pozdrav / Best regards, >>> >>> Sebastijan Kaplar >>> Fakultet tehničkih nauka >>> Univerzitet u Novom Sadu >>> >>>> On Nov 22, 2019, at 08:40, Gordana Milosavljevic <grist@uns.ac.rs >>>> <mailto:grist@uns.ac.rs>> wrote: >>>> >>>> Hi Norbert, >>>> >>>> Thanks a lot for your help!  It's impressive that you have time at >>>> all, since you also have a baby. >>>> >>>> >>>>> If I can ask you a favor could you describe me the basic model like >>>>> >>>>> - Node >>>>> - Event >>>>> - Task >>>>> - Engine >>>>> - Executor >>>>> - Activation >>>>> - Flow >>>>> - …. >>>>> >>>>> this would help me a lot understanding what you are building and >>>>> these explanations would probably very good class comments ;) >>>>> >>>> Please find attached the paper from ESUG 2019. I hope it can give >>>> some explanations, until Sebastijan become operational again :). >>>> >>>> Best regards, >>>> >>>> Gordana >>>> >>>> >>>> -- >>>> dr Gordana Milosavljevic, >>>> Associate Professor, >>>> Computing and Control Department, >>>> Faculty of Tecnical Sciences, >>>> University of Novi Sad, Serbia, >>>> www.informatika.ftn.uns.ac.rs <http://www.informatika.ftn.uns.ac.rs/> >>>> >>>> <IWST19_paper_19(2).pdf>-- >>>> Workflow-engine mailing list >>>> Workflow-engine@lists.pharo.org >>>> <mailto:Workflow-engine@lists.pharo.org> >>>> http://lists.pharo.org/mailman/listinfo/workflow-engine_lists.pharo.org >>> >> > >
AM
Aleksandra Mitrović <aleksandramitrovic@uns.ac.rs>
Sat, Feb 8, 2020 12:19 PM

Hi everyone,

I think that I've finished the first version of the model, it's in the attachment (.asta file, PDF and HTML version).

Some notes for the diagrams:

  • Comments (yellow) - they are suggestions with potential warning label.
  • Comments (red) - they are suggestions with potential error label.
  • Comments (blue) - general notes.
  • In the diagrams you'll see unknown type, that means I didn't recognize a real type.

I hope that it will help everyone on this project.

Aleksandra

On 7.2.2020. 13:49, Aleksandra Mitrović wrote:

Hi all,

Sorry for the late answer. I'm almost done with a Class diagram, but I can't finish it because I can't figure out some associations between classes and types for the properties, especially method return types. I think that I need some help from Sebastian to complete it. I've created it with Astah professional software, and it has a free version viewer (Astah Viewer http://astah.net/editions/viewer). Soon, I'll share in the form of a .asta file, and if necessary I could export it to some different format.

Best regards,

Aleksandra Mitrovic

On 5.2.2020. 15:52, Sebastijan Kaplar wrote:

Hi Norbert,

good to hear from you. Aleksandra said she’ll update the models we have (she’s on the mailing list, and we had updates). Aleksandra did you maybe managed to do it so you could send it to us? If not I’ll find the old ones and resend it.

I’ve managed to push out some updates since we last heard: I’ve separated model and execution, so it’s possible to have multiple processes running now. Still needs some testing but it’s there. WebApplication now can communicate with our server. If you remember WebApp couldn’t pull, neither push out tasks. So now, web application can actually get the task from server, render it/get component and submit the answer back to the server.

What I’m waiting for now is the user roles part. One of the MSc students wanted to work on that, so we had sessions and discussions and I hope he will finish soon.

Examples are updated in ExampleExecutions class. And there’s also one example that you can try out using the web app:

proc1 := ExampleExecutions returnSimpleProcess. proc2 := ExampleExecutions returnSimpleProcess2.

engine := WaveEngine new. engine addProcess: proc1 name: (proc1 processInstanceId). engine addProcess: proc2 name: (proc2 processInstanceId). engine startTeapotServer. engine startProcess: (proc1 processInstanceId). engine startProcess: (proc2 processInstanceId).

I think everything should be on github. You get to the app:

http://localhost:8080/NewWave-Engine

user1, user1 are credentials

Please have in mind that you should initialize WebApp:

FUApplicationRootComponent initialize. FUApplication createDemo.

I think it should work. For everything else I am here and happy to answer.

PS Master is the branch you should look at now.

Pozdrav / Best regards,

Sebastijan Kaplar Fakultet tehničkih nauka Univerzitet u Novom Sadu

On Feb 5, 2020, at 13:06, Norbert Hartl <norbert@hartl.name mailto:norbert@hartl.name> wrote:

Hi Sebastijan,

it has been ages since last contact. I'm back since beginning of january and nearly catched up with most stuff that was accumulating on my desk.

Am 29.11.2019 um 16:38 schrieb Sebastijan Kaplar <kaplar@uns.ac.rs mailto:kaplar@uns.ac.rs>:

Hello Norbert,

I’ve just pushed a new commit with added some descriptions for workflow, I’m also attaching uml model for the core in this email. I’ll also continue adding the descriptions. I hope it gets a bit easier, however if you’re interested we can make some time do discuss over discord/skype maybe do some pair programming a bit where I can answer right away any questions you have. And basically to mention, the core package is the one that represents a model, and the engine package is the one that should manipulate/execute that model.

Can you send the picture again the resolution is too low? If you use a Mac be aware that there is a selection which quality you want to send with a default that is only suitable for photographs. Having an online session is a good idea. I will scan the available mateial and try to compile a list of better questions.

Norbert

<workflow.png>

Pozdrav / Best regards,

Sebastijan Kaplar Fakultet tehničkih nauka Univerzitet u Novom Sadu

On Nov 22, 2019, at 08:40, Gordana Milosavljevic <grist@uns.ac.rs mailto:grist@uns.ac.rs> wrote:

Hi Norbert,

Thanks a lot for your help!  It's impressive that you have time at all, since you also have a baby.

If I can ask you a favor could you describe me the basic model like

  • Node
  • Event
  • Task
  • Engine
  • Executor
  • Activation
  • Flow
  • ….

this would help me a lot understanding what you are building and these explanations would probably very good class comments ;)

Please find attached the paper from ESUG 2019. I hope it can give some explanations, until Sebastijan become operational again :).

Best regards,

Gordana

-- dr Gordana Milosavljevic, Associate Professor, Computing and Control Department, Faculty of Tecnical Sciences, University of Novi Sad, Serbia, www.informatika.ftn.uns.ac.rs http://www.informatika.ftn.uns.ac.rs/

<IWST19_paper_19(2).pdf>-- Workflow-engine mailing list Workflow-engine@lists.pharo.org mailto:Workflow-engine@lists.pharo.org http://lists.pharo.org/mailman/listinfo/workflow-engine_lists.pharo.org

Hi everyone, I think that I've finished the first version of the model, it's in the attachment (.asta file, PDF and HTML version). Some notes for the diagrams: * Comments (yellow) - they are suggestions with potential warning label. * Comments (red) - they are suggestions with potential error label. * Comments (blue) - general notes. * In the diagrams you'll see unknown type, that means I didn't recognize a real type. I hope that it will help everyone on this project. Aleksandra On 7.2.2020. 13:49, Aleksandra Mitrović wrote: > > Hi all, > > Sorry for the late answer. I'm almost done with a Class diagram, but I > can't finish it because I can't figure out some associations between > classes and types for the properties, especially method return types. > I think that I need some help from Sebastian to complete it. I've > created it with Astah professional software, and it has a free version > viewer (Astah Viewer <http://astah.net/editions/viewer>). Soon, I'll > share in the form of a .asta file, and if necessary I could export it > to some different format. > > Best regards, > > Aleksandra Mitrovic > > On 5.2.2020. 15:52, Sebastijan Kaplar wrote: >> Hi Norbert, >> >> good to hear from you. Aleksandra said she’ll update the models we >> have (she’s on the mailing list, and we had updates). Aleksandra did >> you maybe managed to do it so you could send it to us? If not I’ll >> find the old ones and resend it. >> >> I’ve managed to push out some updates since we last heard: >> I’ve separated model and execution, so it’s possible to have multiple >> processes running now. Still needs some testing but it’s there. >> WebApplication now can communicate with our server. If you remember >> WebApp couldn’t pull, neither push out tasks. So now, web application >> can actually get the task from server, render it/get component and >> submit the answer back to the server. >> >> What I’m waiting for now is the user roles part. One of the MSc >> students wanted to work on that, so we had sessions and discussions >> and I hope he will finish soon. >> >> Examples are updated in ExampleExecutions class. And there’s also one >> example that you can try out using the web app: >> >> proc1 := ExampleExecutions returnSimpleProcess. >> proc2 := ExampleExecutions returnSimpleProcess2. >> >> engine := WaveEngine new. >> engine addProcess: proc1 name: (proc1 processInstanceId). >> engine addProcess: proc2 name: (proc2 processInstanceId). >> engine startTeapotServer. >> engine startProcess: (proc1 processInstanceId). >> engine startProcess: (proc2 processInstanceId). >> >> I think everything should be on github. You get to the app: >> >> http://localhost:8080/NewWave-Engine >> >> user1, user1 are credentials >> >> Please have in mind that you should initialize WebApp: >> >> FUApplicationRootComponent initialize. >> FUApplication createDemo. >> >> I think it should work. For everything else I am here and happy to >> answer. >> >> PS Master is the branch you should look at now. >> -- >> Pozdrav / Best regards, >> >> Sebastijan Kaplar >> Fakultet tehničkih nauka >> Univerzitet u Novom Sadu >> >>> On Feb 5, 2020, at 13:06, Norbert Hartl <norbert@hartl.name >>> <mailto:norbert@hartl.name>> wrote: >>> >>> Hi Sebastijan, >>> >>> it has been ages since last contact. I'm back since beginning of >>> january and nearly catched up with most stuff that was accumulating >>> on my desk. >>> >>>> Am 29.11.2019 um 16:38 schrieb Sebastijan Kaplar <kaplar@uns.ac.rs >>>> <mailto:kaplar@uns.ac.rs>>: >>>> >>>> Hello Norbert, >>>> >>>> I’ve just pushed a new commit with added some descriptions for >>>> workflow, I’m also attaching uml model for the core in this email. >>>> I’ll also continue adding the descriptions. I hope it gets a bit >>>> easier, however if you’re interested we can make some time do >>>> discuss over discord/skype maybe do some pair programming a bit >>>> where I can answer right away any questions you have. >>>> And basically to mention, the core package is the one that >>>> represents a model, and the engine package is the one that should >>>> manipulate/execute that model. >>>> >>> Can you send the picture again the resolution is too low? If you use >>> a Mac be aware that there is a selection which quality you want to >>> send with a default that is only suitable for photographs. Having an >>> online session is a good idea. I will scan the available mateial and >>> try to compile a list of better questions. >>> >>> Norbert >>> >>>> >>>> <workflow.png> >>>> -- >>>> Pozdrav / Best regards, >>>> >>>> Sebastijan Kaplar >>>> Fakultet tehničkih nauka >>>> Univerzitet u Novom Sadu >>>> >>>>> On Nov 22, 2019, at 08:40, Gordana Milosavljevic <grist@uns.ac.rs >>>>> <mailto:grist@uns.ac.rs>> wrote: >>>>> >>>>> Hi Norbert, >>>>> >>>>> Thanks a lot for your help!  It's impressive that you have time at >>>>> all, since you also have a baby. >>>>> >>>>> >>>>>> If I can ask you a favor could you describe me the basic model like >>>>>> >>>>>> - Node >>>>>> - Event >>>>>> - Task >>>>>> - Engine >>>>>> - Executor >>>>>> - Activation >>>>>> - Flow >>>>>> - …. >>>>>> >>>>>> this would help me a lot understanding what you are building and >>>>>> these explanations would probably very good class comments ;) >>>>>> >>>>> Please find attached the paper from ESUG 2019. I hope it can give >>>>> some explanations, until Sebastijan become operational again :). >>>>> >>>>> Best regards, >>>>> >>>>> Gordana >>>>> >>>>> >>>>> -- >>>>> dr Gordana Milosavljevic, >>>>> Associate Professor, >>>>> Computing and Control Department, >>>>> Faculty of Tecnical Sciences, >>>>> University of Novi Sad, Serbia, >>>>> www.informatika.ftn.uns.ac.rs <http://www.informatika.ftn.uns.ac.rs/> >>>>> >>>>> <IWST19_paper_19(2).pdf>-- >>>>> Workflow-engine mailing list >>>>> Workflow-engine@lists.pharo.org >>>>> <mailto:Workflow-engine@lists.pharo.org> >>>>> http://lists.pharo.org/mailman/listinfo/workflow-engine_lists.pharo.org >>>> >>> >> >> >