Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider Elsa Workflows Studio in Blazor #3810

Closed
GeorgeS2019 opened this issue Mar 18, 2023 · 16 comments
Closed

Consider Elsa Workflows Studio in Blazor #3810

GeorgeS2019 opened this issue Mar 18, 2023 · 16 comments
Assignees
Labels
workflow tooling Improvements to the visual workflow builder

Comments

@GeorgeS2019
Copy link

elsa-workflows-studio

FYI: Azure Design Studio

msedge_dd0BhaHeDS

@GeorgeS2019
Copy link
Author

I would be really nice if the Activity editor could be replaced to use custom Blazor components.

@GeorgeS2019
Copy link
Author

@GeorgeS2019
Copy link
Author

@GeorgeS2019
Copy link
Author

@sfmskywalker
Copy link
Member

Yes, we want to redo the entire designer in Blazor and wrap it in a web component. This wasn't possible (or at least practical from what I could see) in the past, but today, I hear, it's very much supported.

@GeorgeS2019
Copy link
Author

@sfmskywalker

Do follow .NET8 Blazor United, the best low latency web client, perfect for Elsa Worlflows Studio

@GeorgeS2019
Copy link
Author

@jdevillard
Copy link
Contributor

Hello,

Using Blazor could be really nice, but I think that no matter what the language/framework is used, the important thing is it HAS to be interoperable with other technology/framework. Web Component Wrapper is a good thing for this, but interaction with the different part of the designer should also be present (for example, loading/saving/publishing should be handle by external component).

I'm currently working on Web Component Wrapper for Angular (but this should be the same then for React, Vue and others) and I'm currently seeing what is missing for interop.

@GeorgeS2019
Copy link
Author

GeorgeS2019 commented Mar 20, 2023

(for example, loading/saving/publishing should be handle by external component)
This is .NET project, loading/saving/publishing should be handle by external component => can be done as FIRST class citizen with .NET using Blazor.

In terms of Web Technology,

Currently Vue and Blazor (new kid ), then React, then only Angular.

Interoperability between Blazor and React and Angular are available at Microsoft website.

=> It is almost challenging to mix Vue and Blazor, as both are accessing the latest Web Technology Development efficiency.

@jspitman
Copy link

Another feature of the evolution of the designer could be looking at something like adaptive cards (https://adaptivecards.io) for use with activity extensibility. It could be a way for a custom activity developer to include designer activity UI as part of the activity assuming new activities can be added without recompilation of a server.

@sfmskywalker sfmskywalker added the workflow tooling Improvements to the visual workflow builder label Mar 20, 2023
@sfmskywalker
Copy link
Member

Thank you for all the tips and leads, that is looking potentially very useful.

@GeorgeS2019
Copy link
Author

#3852

WASM and Blazor

@sfmskywalker sfmskywalker self-assigned this May 12, 2023
@sfmskywalker
Copy link
Member

@GeorgeS2019 OK if we close this issue ("consider using Blazor")? We considered and and decided to do it 😄

@GeorgeS2019
Copy link
Author

GeorgeS2019 commented Jun 1, 2023

@sfmskywalker it is in progress, others need to track this progress and feedback here 😉
image

@sfmskywalker
Copy link
Member

OK, let's leave it open until we have an MVP with Blazor 👍🏻

@GeorgeS2019
Copy link
Author

Elsa.Studio.Host.Wasm => Blazor work!!!!

msedge_YEZIkQaFYo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
workflow tooling Improvements to the visual workflow builder
Projects
Status: Done
Development

No branches or pull requests

4 participants