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

Handle situation where user changes manifest while they have active build/runtime terminals #104

Open
SeaDve opened this issue Feb 28, 2022 · 14 comments
Labels
enhancement New feature or request

Comments

@SeaDve
Copy link
Collaborator

SeaDve commented Feb 28, 2022

See #94 review comments

@bilelmoussaoui
Copy link
Owner

I think we could display the used SDK versions for those terminals on their title if possible?

@bilelmoussaoui
Copy link
Owner

It doesn't handle the situation at all but at least it is clear in case you are using two manifests with one on stable/other on nightly runtime

@SeaDve
Copy link
Collaborator Author

SeaDve commented Mar 1, 2022

I think we could display the used SDK versions for those terminals on their title if possible?

I have been thinking about that too. That's possible, but we again have long naming issues :(

What about <runtime> <runtime-version> for runtime (e.g. Flatpak: org.gnome.Platform 41 Terminal) and <AppId> Build for build (e.g. Flatpak: org.some.App Build Terminal)

We could also maybe emit the Flatpak: prefix as we already have the package icon

@bilelmoussaoui
Copy link
Owner

I would go with Flatpak: org.gnome.Platform//41 for runtime terminal, Flatpak: org.gnome.App for build terminal

@SeaDve
Copy link
Collaborator Author

SeaDve commented Mar 1, 2022

Won't Flatpak: org.gnome.App be confused with something that was run with flatpak run --comand=sh <AppId>

@bilelmoussaoui
Copy link
Owner

Won't Flatpak: org.gnome.App be confused with something that was run with flatpak run --comand=sh <AppId>

that is what the build terminal do :) it just adds the finish-args and passes --devel as well

@SeaDve
Copy link
Collaborator Author

SeaDve commented Mar 1, 2022

ohhhhh, good to know

@bilelmoussaoui
Copy link
Owner

Both running the app and the build terminal go through the runInRepo function, with different commands to run

@SeaDve
Copy link
Collaborator Author

SeaDve commented Mar 1, 2022

image
The Flatpak: prefix kinda feels repetitive for me (at least when they are opened consecutively)

@SeaDve
Copy link
Collaborator Author

SeaDve commented Mar 1, 2022

image
The labels are also somehow lost after a restart

@bilelmoussaoui
Copy link
Owner

image
The Flatpak: prefix kinda feels repetitive for me (at least when they are opened consecutively)

Maybe we could drop the prefix, can we have tooltips there though?

@bilelmoussaoui
Copy link
Owner

image The labels are also somehow lost after a restart

Maybe there is some kind of event to register for, for the created terminals so we can restore them properly? or maybe even just opt-out of the restore if possible...

@SeaDve
Copy link
Collaborator Author

SeaDve commented Mar 1, 2022

Maybe we could drop the prefix, can we have tooltips there though?

Oddly, there seems none. Tooltips only replicates the name

@SeaDve
Copy link
Collaborator Author

SeaDve commented Mar 3, 2022

API for opting out for restoring is currently on testing

@bilelmoussaoui bilelmoussaoui added the enhancement New feature or request label Apr 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants