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

Windows GUI #63

Open
pgaskin opened this issue Jun 14, 2021 · 3 comments
Open

Windows GUI #63

pgaskin opened this issue Jun 14, 2021 · 3 comments
Assignees

Comments

@pgaskin
Copy link
Owner

pgaskin commented Jun 14, 2021

No description provided.

@pgaskin pgaskin self-assigned this Jun 14, 2021
@pgaskin
Copy link
Owner Author

pgaskin commented Jun 14, 2021

Some ideas:

https://excalidraw.com/#json=6553667784146944,WckCXdTcnWCjwbrYK4kMww

@pgaskin
Copy link
Owner Author

pgaskin commented Jun 14, 2021

Some considerations:

  • How will directories be kept track of in the file list, since pathtransform has different behaviour for them?
  • Maybe I should just have completely different path logic for the GUI version?
  • Or should I have it show the directory as a clickable list item, and the files in it listed underneath as read-only items?
  • Or should I change the GUI and have it convert immediately when you drag files on it instead of using a queue? This would be much simpler to write, but it'd be more confusing to use.
    • Or do I do a combination of this and my original idea by having a split pane with the added files on the left and a preview on the right? This might be the best option since it keeps the code free from dealing with two-way interaction with the file list, and it prevents the UI from becoming confusing or buggy with overlapping directories (since pathtransform considers all inputs holistically rather than providing a list of files for each input). The only disadvantage is a slightly more cluttered interface.
  • Something else?

@ArieKindicator
Copy link

ArieKindicator commented May 7, 2023

A GUI is a good idea, and will feel more intuitive to most users.
For consideration. Why develop a (stand-alone app/executable file) GUI when you can also use a web browser for this purpose? After all, you've already developed the web application. And easier to maintain.

The locally running file (i.e. kepubify-windows-64bit.exe) opens a web browser and then performs all the tasks locally. No Internet connection is required.

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

2 participants