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

Improve the UI #12

Open
ross-spencer opened this issue Sep 21, 2020 · 2 comments
Open

Improve the UI #12

ross-spencer opened this issue Sep 21, 2020 · 2 comments

Comments

@ross-spencer
Copy link
Contributor

Using the Skeleton web-framework has made this a little better looking than I can do without, but there are still improvements to be made here. Someone with a better eye might be able to help here.

@gleporeNARA
Copy link

The utility looks very good, but to my eye, the elements are spread out quite a bit. It takes up my entire screen, so possibly reducing the spacing would be a better layout.

I think it would be useful to allow the Extension entry to take multiple extensions (perhaps comma or space separated) and turn them into individual lines in the resulting signature.

I've thought quite a bit about having the Mimetype entry field as a drop-down, with the most popular mime-types at the top, but it might get quite unwieldy, so perhaps just a few popular ones in the drop-down and the others as free entry boxes?

@ross-spencer
Copy link
Contributor Author

ross-spencer commented Oct 2, 2020

I like these suggestions Greg. Thank you.

I've managed to condense the interface a small bit tonight. It was something I was thinking about but I hadn't quite got the full swing of the Skeleton web-framework. I have made a comparison of after and before here:

image

It's not quite as neat as 1.0. Will continue to think about optimizations so we can fit more information on screen.

  • On extensions, definitely! This might be good as a separate issue here actually. It's pretty well defined and in-line with the signature file specification.
  • On mime types. I like that. If we can get the utility to a place where it has a certain "memory" of a PRONOM signature file then I think this will be entirely feasible. I haven't done a count of PRONOM mime's recently.

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

2 participants