-
Notifications
You must be signed in to change notification settings - Fork 3
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
New design for the choice page and merge the two SU wizards #6
Milestone
Comments
vincent-zurczak
added a commit
to vincent-zurczak/petals-studio
that referenced
this issue
Mar 18, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, we have two wizards for service units, one for service providers and one for service consumers. Each wizard has its own choice page, that gathers Petals components by use case (communication protocols, service composition, etc). This page also allows to select the component version to use.
This page is ugly.
That makes the studio look like... its real age. I also think we should rely on the idea users know what is an engine and what is a connector. JBI concepts adds too much complexity. So, maybe we should hide this. Anyway, let's just keep a single wizard for service units, and let's update the choice page: connectors VS. engines, a description of the use case (provides or consumes), plus the choice of the version. That's it.
The text was updated successfully, but these errors were encountered: