V3 Designer Features - Githubissues

elsa-workflows / elsa-core

A .NET workflows library

https://v3.elsaworkflows.io/

MIT License

6.09k stars 1.11k forks source link

V3 Designer Features #2647

Open sfmskywalker opened 2 years ago

sfmskywalker commented 2 years ago

The following list is taken from this issue:

[x] Display port labels (inbound + outbound)
[ ] Display connection labels (same text as outbound port)
[x] Highlight connection upon hover
[ ] Double-click on connected outbound port takes you to destination activity
[ ] Double-click on connected inbound port displays list of inbound activities. Clicking any one of them will take you to it
[ ] Ability to add auto-connected activity. Can't use double-click because that takes you to destination activity if there is one, but perhaps just by start dragging and then releasing mouse button to invoke inline activity picker
[ ] Tool button to invoke auto-layout
[ ] Tool button to auto-layout diagram automatically whenever activities are added/removed

tomy2105 commented 2 years ago

"Ability to add auto-connected activity. Can't use double-click because that takes you to destination activity if there is one, but perhaps just by start dragging and then releasing mouse button to invoke inline activity picker"

I'm still locked in mode that outcome can be connected to single activity only (think forking should be done by fork activity only). In this scenario, maybe double clicking on outcome that is not connected yet could invoke inline activity picker (or any other auto-connect logic).

CalaxDev commented 2 years ago

Is there going to be a way to manually trigger/debug workflows in the designer at some point?

Is it possible to define a certain set of variable requirements which are passed into the workflow? Like, in a way that a workflow can only be executed with predefined variables like - "string Id, SomeClass myObject"

zhangtingwz commented 2 years ago

Please think about whether to add text content to support the languages of various countries

stevenuecke7 commented 2 years ago

@sfmskywalker have you thought about coding the V3 designer in Blazor instead of using StencilJS?

sfmskywalker commented 2 years ago

@stevenuecke7 I did. A lot :) Bottom line is that I want to do it in Blazor now that I am aware of the fact that one can actually embed Blazor in other SPA apps written with e.g. Angular and React. But I already started with StencilJS and customers are eagerly waiting for V3 to be usable.

I'll probably start working on porting the designer to Blazor after things settle down after the initial release of 3.0. We'll see.

helloxubo commented 1 year ago

@sfmskywalker X6 is very great. V3 Designer will use it?

sfmskywalker commented 1 year ago

X6 is a great library. Elsa 3 is using it and hopefully soon Elsa 2 will use it too.

helloxubo commented 1 year ago

X6 is a great library. Elsa 3 is using it and hopefully soon Elsa 2 will use it too.

That's great. I'm looking forward to it!