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

Allow settings import/export #551

Open
jwdebelius opened this issue Nov 18, 2021 · 6 comments
Open

Allow settings import/export #551

jwdebelius opened this issue Nov 18, 2021 · 6 comments

Comments

@jwdebelius
Copy link

Hi!

I really appreciate empress. I'm wondering if it would be possible to introduce one of my favorite features from emperor. I really liked the ability to export/import a settings file that would configure the display with the colors, annotations, rotation, and scale. It can take like 10-15 minutes to get things exactly the way I want as I annotate several layers of data. I'd love to see a similar thing in the future to support my erm... laziness?

@fedarko
Copy link
Collaborator

fedarko commented Nov 19, 2021

Thanks @jwdebelius -- I agree, this would be extremely useful to have in EMPress! We've had this on the docket for a while; I think we could maybe merge this with #131?

From what I remember, we were originally planning to focus on refactoring some of EMPress' code to make programmatically setting the application state easier, and then implement this sort of import/export functionality afterwards. At this point, though, it might make sense to go for the "quick-and-dirty" version of this sooner? Not sure what other folks' thoughts are on this. At least personally, I have much less time this year than last year to focus on EMPress' codebase (still have a few PRs I need to go review/merge...).

@jwdebelius
Copy link
Author

I think it, sorry! 😳

And I totally understand how that happens! I hope things are going well. It's just a feature I'll anxiously await, when it gets here

@gibsramen
Copy link
Collaborator

At this point, though, it might make sense to go for the "quick-and-dirty" version of this sooner?

@fedarko I think this would be best. I can take a stab at a rudimentary version of this in the next couple of weeks but no promises.

@fedarko
Copy link
Collaborator

fedarko commented Nov 25, 2021

@jwdebelius No worries at all!!! It's always useful for us to know what planned features will be helpful for users to have; this is a reminder for me to get back to work ;)

@gibsramen that would be super dope, thanks! Hit me up if you want to try to pair-program this or something. We might be able to knock this out in a day or two (although I also have finals coming up soon so, uh, ditto on the no promises thing from my end)

@ElDeveloper
Copy link
Member

ElDeveloper commented Dec 1, 2021 via email

@justinshaffer
Copy link

Thanks for the great tool! I wanted to express my enthusiasm for this functionality - looking forward to seeing it implemented.

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

No branches or pull requests

5 participants