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

Should we rename lsdsng-import/export? #90

Open
stijnfrishert opened this issue Nov 9, 2020 · 3 comments
Open

Should we rename lsdsng-import/export? #90

stijnfrishert opened this issue Nov 9, 2020 · 3 comments
Assignees
Labels

Comments

@stijnfrishert
Copy link
Owner

stijnfrishert commented Nov 9, 2020

While export does actually still export lsdsng's, import can be used to import both lsdsng's as well as sav's.

Moreover, the names are a bit long and cumbersome. What about lsdj-import and lsdj-export?

Opinions, @urbster1?

@stijnfrishert
Copy link
Owner Author

stijnfrishert commented Nov 9, 2020

Though there's also lsdj-wavetable-import to take into account. maybe we should go with

lsdj-song-import
lsdj-song-export
lsdj-wave-import

Two of these are longer than the original, but also somewhat clearner.

@urbster1
Copy link
Collaborator

urbster1 commented Nov 10, 2020 via email

@stijnfrishert
Copy link
Owner Author

There's a new format? Yes, let's chat. Always found lsdsng had its problems.

@stijnfrishert stijnfrishert removed this from the v2.1.0 milestone Nov 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants