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

Save options for the image saving #55

Closed
Viza74 opened this Issue Jul 30, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@Viza74

Viza74 commented Jul 30, 2018

  • save double sized
  • save for twitter = at least one transparent pixel in the image, so twitter keeps it as a png, and not doing a recompress to jpg.

Low priority of course, can be easily done in an editor after export.
And don't even know where to put it UI-wise in the program...

@nurpax nurpax added this to the 0.2 milestone Jul 30, 2018

@nurpax

This comment has been minimized.

Show comment
Hide comment
@nurpax

nurpax Jul 30, 2018

Owner

Yes. There's plenty of other options too, like should PETSCII .c export save multiple screens or just the currently selected one.

I would've done some of this already if I had a good clean UI layout in mind for this.

When the user clicks on export (from menus or if there was a button), should the UI popup a modal on top of the editor with options for that particular export type? Or should it navigate the UI to a different route with the export options? The export dialog potentially needs also a thumnail list of screens so that the user can select which screens to export, in case he wants more than one.

The same applies to import too. For example, the .c format can contain multiple frames. I'd like it to be possible to choose ones ones to bring in and whether.

Maybe I'll go with a modal first. I consider this pretty important for the next releases because a bunch of things are being held back behind the lack of this UI component.

Owner

nurpax commented Jul 30, 2018

Yes. There's plenty of other options too, like should PETSCII .c export save multiple screens or just the currently selected one.

I would've done some of this already if I had a good clean UI layout in mind for this.

When the user clicks on export (from menus or if there was a button), should the UI popup a modal on top of the editor with options for that particular export type? Or should it navigate the UI to a different route with the export options? The export dialog potentially needs also a thumnail list of screens so that the user can select which screens to export, in case he wants more than one.

The same applies to import too. For example, the .c format can contain multiple frames. I'd like it to be possible to choose ones ones to bring in and whether.

Maybe I'll go with a modal first. I consider this pretty important for the next releases because a bunch of things are being held back behind the lack of this UI component.

@Esshahn Esshahn modified the milestones: 0.2, backlog Aug 4, 2018

@nurpax nurpax referenced this issue Aug 5, 2018

Closed

Import/export settings handling #72

2 of 2 tasks complete
@nurpax

This comment has been minimized.

Show comment
Hide comment
@nurpax

nurpax Aug 5, 2018

Owner

@Viza74 Here's a screencap of how I'm planning to do these settings: https://youtu.be/Q66c2vFPn6w

Owner

nurpax commented Aug 5, 2018

@Viza74 Here's a screencap of how I'm planning to do these settings: https://youtu.be/Q66c2vFPn6w

@nurpax nurpax closed this in b65dcae Aug 8, 2018

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