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

[WIP] Prototype of Minimal Workflow-Centric UI #9030

Closed
wants to merge 3 commits into from

Conversation

jmchilton
Copy link
Member

@jmchilton jmchilton commented Nov 22, 2019

Experimental prototype developed based on discussions at the ELIXIR Biohackathon 2019 around convergence of Galaksio and other projects aimed at providing simpler workflow interfaces.

A full report of the discussion and action items for the Galaxy framework are contained in the following document.

http://bit.ly/simplified-workflow-ui

@nsoranzo
Copy link
Member

Thanks @TKlingstrom for proposing the Biohackathon 2019 project and for supporting the merge of Galaksio concepts upstream!

@jmchilton jmchilton changed the title [WIP] Prototype of Minimal Galaxy Runner [WIP] Prototype of Minimal Workflow-Centric UI Nov 22, 2019
masthead_show_workflows: true,
masthead_show_workflows: true,
masthead_show_activities: false,
masthead_show_scratchbook: true,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we would introduce hide_masthead_analysis instead the default would be false per definition and most of these values would not have to be initialized/specified when building the masthead. Also the naming would be more consistent with the parameters above.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The problem with a meta property like that is that we've discussed per role display of features in the UI. Might be better to just break everything down now? Then we can do view_default && role_default for each option? But maybe that could be pushed down a layer? All this code will be obsoleted by #9071 - I'll revisit this and try both after that is integrated and I redo this.

@afgane
Copy link
Contributor

afgane commented Aug 11, 2020

I just came across this PR and wanted to add some thoughts about the layout of the workflow list. The layout may not necessarily be in scope of this PR but maybe a good to open some discussion about the ideas. Here are some mockup drawings that have been annotated and are hopefully self sufficient.

image

image

@bgruening
Copy link
Member

@afgane that looks cool. Is the right-hand side is only shown when something is selected? What is in this place when nothing is selected? Is the workflow-list moving to the left when you select something? Are multiple-selects allowed?

@afgane
Copy link
Contributor

afgane commented Aug 13, 2020

Is the right-hand side is only shown when something is selected? What is in this place when nothing is selected?

Either way. We could have an info panel similar to how Google Docs has it that is toggled with a button and is empty (or shows some instructional text, advertises a feature, etc.) until a workflow is selected at which point it populates with details specific to the workflow.

Alternatively, it could be like Box where the panel is always shown and has two tabs for sharing and details.
image

Is the workflow-list moving to the left when you select something?

It just narrows the view. If you look at John's screenshot above, that page is way too sparse as is.

Are multiple-selects allowed?

What is a scenario where you would select multiple workflows? Regardless, sure, they panel can just say "Multiple workflows selected".

@nsoranzo nsoranzo marked this pull request as draft September 17, 2022 06:52
@jmchilton jmchilton closed this Jan 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

6 participants