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

Workspace History : libparsec API & bindings #8662

Open
Tracked by #6147
mmmarcos opened this issue Oct 7, 2024 · 0 comments · May be fixed by #8661
Open
Tracked by #6147

Workspace History : libparsec API & bindings #8662

mmmarcos opened this issue Oct 7, 2024 · 0 comments · May be fixed by #8661
Assignees
Labels
A-Client Area: Parsec desktop application I-Rust Impact: Rust-related stuff

Comments

@mmmarcos
Copy link
Contributor

mmmarcos commented Oct 7, 2024

What would be needed:

  • workspace creation date (could be added to workspaceInfo())
  • list a workspace at a given time, similar to workspaceStatEntry() and workspaceStatFolderChildren() with an extra parameter for the datetime
  • something to restore a file:
    • either by providing a function that restore a file from an older state
    • or by having workspaceOpenFile and fdRead able to take a datetime
  • being able to mount a workspace at a given time to access a file. Since the user may try to open the same file at multiple times and compare them, it would be better if the mountpoints where hidden, or at a different location (opening a file at Date1, Date2 and Date3 would result in three mountpoints).
@mmmarcos mmmarcos linked a pull request Oct 7, 2024 that will close this issue
@FirelightFlagboy FirelightFlagboy added I-Rust Impact: Rust-related stuff A-Client Area: Parsec desktop application labels Oct 9, 2024
@Max-7 Max-7 mentioned this issue Oct 16, 2024
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Client Area: Parsec desktop application I-Rust Impact: Rust-related stuff
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants