Workflow aka Aare status?

I read this thread:


http://forum.world.st/Aare-questions-td5063745.html


And it seems a lot of work has been done since Max/NetStyle posted the code here:

https://github.com/Netstyle/Workflow


In Stef's repo here:

https://github.com/Ducasse/Workflow


Is  anyone else working on it / publishing code for it?  


Thanks

Paul

Hi Paul,

I did nothing more since what was discussed in this thread.

This is still something I’m interested in but it’s not a priority at the moment.

The work done since Max published it was to make it work (it’s was mainly about the removal of Omnibase dependancies). BTW, removing was « easy » but Rare was relying a lot on logging action/activity (Omnibase) and generating Seaside web UI (through Magritte) we do not have that anymore.

The actual state/limitation for me if I remember well, is :
- there is « only » a « manual » completion of tasks (someone has to declare a task completed). To me, it needs to be able to declare « software tasks ».
- manual completion was achieved through Web UI (anActivation complete). I think we need a more generic UI mechanism (Annoucement?)
- I also would need delegated subtasks (to other images ).
- I think it would need some kind of scheduler/orchestrator.

For what purposes you need Workflow ?

HTH,

Cédrick

cedreek wrote
> it’s was mainly about the removal of Omnibase dependancies)… and
> generating Seaside web UI (through Magritte) we do not have that anymore.

I'm curious - what was the motivation to remove those two dependencies?



-----
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

> Le 23 juin 2018 à 15:50, Sean P. DeNigris <[hidden email]> a écrit :
>
> cedreek wrote
>> it’s was mainly about the removal of Omnibase dependancies)… and
>> generating Seaside web UI (through Magritte) we do not have that anymore.

It was not really a choice. Netstyle submitted it that way I guess.

Still I find this is better to have something more generic with different persistance choice (voyage ?) and Magritte as it was also only seaside.

The problem is that now the package by itself is not really usable as the web interface + logging was very central.

My 2 cents,

Cedrick

>>
>>
>>> it’s was mainly about the removal of Omnibase dependancies)… and
>>> generating Seaside web UI (through Magritte) we do not have that anymore.
>
> It was not really a choice. Netstyle submitted it that way I guess.

And what we did was mainly to remove remaining trace of these dependencies (and understand).