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

Import/export markers and routes #17

Closed
steinbro opened this issue Jun 20, 2023 · 8 comments
Closed

Import/export markers and routes #17

steinbro opened this issue Jun 20, 2023 · 8 comments

Comments

@steinbro
Copy link
Member

@bramd suggested in the chat that one way to export markers from Soundscape is to add them to a route, then export as a JSON file. Can we add functionality to import these into Openscape?

See also: microsoft/soundscape#17 (comment)

@RDMurray
Copy link
Contributor

I can confirm that this method works for soundscape. I shared a route with all my markers by email, deleted all my soundscape data, and then opened the .soundscape file from the email. It restored all the markers.

The only reason the same thing doesn't work with openscape is that the file extension changed to .openscape, probably as a result of find/replace.

I propose that we revert the file extension to .soundscape to enable compatibility with soundscape and soundscape for everyone in the future.

@RDMurray
Copy link
Contributor

it's set in info.plist line 182

@steinbro
Copy link
Member Author

Pull request? :)

@RDMurray
Copy link
Contributor

It turns out not to be as straight forward as I thought. To export a UTTypeIdentifier you have to be the authoritative source of information about the file type. Creating a new UTTypeIdentifier with the .soundscape extension seems to override the original soundscape one, preventing soundscape from opening it's own route files. If we import the UTTypeIdentifier from soundscape, that will presumably only work while soundscape is still installed, although I haven't tested this. Does anyone know the correct solution?

@towebo
Copy link

towebo commented Jun 29, 2023

An app can register to handle a certain file extention and if an user taps on a file with that extention a list of alternatives will be presented. If Openscape registers for both .soundscape and .openscape it will be able to handle both of them while Soundscape only wakes up if it's a .soundscape file.

@steinbro
Copy link
Member Author

@RDMurray I think breaking old Soundscape isn't problematic, since it's being deprecated and Openscape is meant to replace it.

@Oliver2213 this issue is closed by dc585fc right?

@Oliver2213
Copy link
Member

Yes. I added support for importing .soundscape files (with identifier soundscape.doc), as well as our own .openscape (io.openscape.doc). We export .openscape, but can import from the sunset app's files as well.
I've set our role for soundscape.doc to "Default", but Openscape still shows up only under the "more" option for me when I would hope it would be presented closer to the start.

@steinbro
Copy link
Member Author

Closing since problems with the implementation are covered in separate issues, e.g. #49.

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

No branches or pull requests

4 participants