Skip to content

Conversation

@aman-coder03
Copy link
Contributor

summary

always show the revision ID in view window titles and plot titles.
if a revision name exists, it is appended.

motivation

improves traceability when switching revisions or comparing views.

Fixes #2026


def confirm_action(confirmation_prompt):
def confirm_action(confirmation_prompt, assume_yes=False):
if assume_yes:
Copy link
Member

Choose a reason for hiding this comment

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

please separate this. You have this in a different PR.

database_parser.add_argument("--add_all_to_all_operation", help="adds all users into all other operations",
action="store_true")

db_actions = database_parser.add_mutually_exclusive_group(required=True)
Copy link
Member

Choose a reason for hiding this comment

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

This is not part of the issue.

We split tasks and also PRs do handle only 1 issue.

@aman-coder03
Copy link
Contributor Author

@ReimarBauer i have removed the mscolab.py from this PR
i hope this is more clear now!

@ReimarBauer
Copy link
Member

Please show the ID, this will always work, because a name can be shifted over IDs. If there is a name at an ID then show it too.

The feature is interesting for those comparing images, it gives the possibility to see that there was a change.

@ReimarBauer
Copy link
Member

When I currently try it I can't see the result, have you a different image?

Bildschirmfoto 2026-01-02 um 10 33 20

@ReimarBauer
Copy link
Member

While looking up the servers retrieved data I recognized that we don't have revision information yet implemented. So that is not an easy task.

@aman-coder03
Copy link
Contributor Author

thanks for checking this and for the clarification.
my intention with this PR was to prepare the UI side to display the revision ID.
but I see now that without server-side support the change is not visible yet.
i would be happy to work on that part(server or data flow), so the UI can be fitted properly.

@ReimarBauer
Copy link
Member

Please keep in mind that we only merge when a feature is completely integrated. Otherwise, someone during review might remove code that’s dead (incomplete).

If you want to start working on the server-side code, begin with everything that uses ftml code. ftml is the default format for flighttracks and mscolab. Extend it so that it also works for flight tracks without mscolab. For example, load_from_xml_data, save_to_ftml, load_from_xml_data. For mscolab, you'll then need to adjust the seed for demo and tests.

There’s an example at samples/examples.ftml which is used by test_msui. The tests also require adaptation. All changes must be accompanied by tests so we don’t lose any existing functionality. This is quite extensive, but probably not difficult to implement.

@aman-coder03
Copy link
Contributor Author

thanks for the detailed guidance @ReimarBauer
i will extend the FTML format to include revision information (ID mandatory, name optional), update the loaders/savers so it works both with and without MSColab, adapt the demo seed and tests (including samples/examples.ftml and test_msui), and then apply the UI changes on top.
i will keep everything in this PR and update it step by step with accompanying tests.

Copy link
Member

@ReimarBauer ReimarBauer left a comment

Choose a reason for hiding this comment

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

We are leaving the pull request open for further updates, which will be posted here. Therefore, I am requesting changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

show on the Views which revision is used

2 participants