Skip to content

Conversation

@odeimaiz
Copy link
Member

@odeimaiz odeimaiz commented Jan 29, 2025

What do these changes do?

This PR brings a new UI mode to represent a study: standalone.

When a study is in standalone mode, the small toolbar, the one with the Reload and Maximize/Restore buttons, disappears giving more space to the dynamic service. From now on, the new studies that contain only one dynamic service will start in standalone mode.

In order to go back to the previous (workbench) view, the users will need to go study-menu in the navigation bar (the reload button was also moved here) and click the "Convert to Pipeline" button, this internally changes the ui mode to workbench and the more osparcy view will be shown. This operation can also be done from the dashboard.

Until the export to standalone backend functionality is implemented, the Convert-to-Standalone option will be hidden.

Bonus:

  • Listen to openWallets inter-iframe message

Starting different modes
UI_modes

New project with a dynamic service goes standalone
StartStandalone

New project with a non dynamic service goes workbench
StartWorkbench

Convert standalone -> workbench -> standalone
StartWorkbench

Related issue/s

How to test

Dev-ops checklist

@odeimaiz odeimaiz self-assigned this Jan 29, 2025
@odeimaiz odeimaiz added t:enhancement Improvement or request on an existing feature a:frontend issue affecting the front-end (area group) labels Jan 29, 2025
@odeimaiz odeimaiz added this to the Singularity milestone Jan 29, 2025
Copy link
Member

@pcrespov pcrespov left a comment

Choose a reason for hiding this comment

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

🎉

@odeimaiz odeimaiz added the 🤖-automerge marks PR as ready to be merged for Mergify label Jan 31, 2025
@odeimaiz
Copy link
Member Author

@Mergifyio queue

@mergify
Copy link
Contributor

mergify bot commented Jan 31, 2025

queue

🛑 The pull request has been removed from the queue default

The pull request can't be updated.

You can take a look at Queue: Embarked in merge queue check runs for more details.

In case of a failure due to a flaky test, you should first retrigger the CI.
Then, re-embark the pull request into the merge queue by posting the comment
@mergifyio refresh on the pull request.

Copy link
Member

@sanderegg sanderegg left a comment

Choose a reason for hiding this comment

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

very nice!

Copy link
Contributor

@GitHK GitHK left a comment

Choose a reason for hiding this comment

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

nice

@mergify
Copy link
Contributor

mergify bot commented Feb 3, 2025

This pull request has been removed from the queue for the following reason: pull request branch update failed.

The pull request can't be updated

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.

If you want to requeue this pull request, you need to post a comment with the text: @mergifyio requeue

@odeimaiz
Copy link
Member Author

odeimaiz commented Feb 3, 2025

@Mergifyio requeue

@sonarqubecloud
Copy link

sonarqubecloud bot commented Feb 3, 2025

@mergify
Copy link
Contributor

mergify bot commented Feb 3, 2025

requeue

❌ This pull request head commit has not been previously disembarked from queue.

@odeimaiz odeimaiz enabled auto-merge (squash) February 3, 2025 12:16
@odeimaiz odeimaiz merged commit 1dcd369 into ITISFoundation:master Feb 3, 2025
56 checks passed
@odeimaiz odeimaiz deleted the feature/standalone-projects branch February 3, 2025 12:25
@matusdrobuliak66 matusdrobuliak66 mentioned this pull request Mar 6, 2025
63 tasks
mrnicegyu11 pushed a commit to mrnicegyu11/osparc-simcore that referenced this pull request Mar 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🤖-automerge marks PR as ready to be merged for Mergify a:frontend issue affecting the front-end (area group) t:enhancement Improvement or request on an existing feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants