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

UI improvement starting a crawl #8

Open
Grienauer opened this issue Jan 23, 2020 · 1 comment
Open

UI improvement starting a crawl #8

Grienauer opened this issue Jan 23, 2020 · 1 comment
Assignees

Comments

@Grienauer
Copy link

Currently it is only possible to start a crawl with the enter key after typing the url.
I would suggest a "start crawl" button beside the url input field.

this button can change during crawling to a "stop" crawling button which is currently located under the url bar.

Bildschirmfoto 2020-01-23 um 12 05 58
also I am not quite sure why there are 2 URL fields. maybe we could remove one?

The "start button" will also have the benefit we can restart the crawl… currently with the top url input, this is not possible.

It would simplify the UI a bit :)

@RoyalIcing RoyalIcing self-assigned this Jan 24, 2020
@RoyalIcing
Copy link
Owner

RoyalIcing commented Jan 24, 2020

Hi Grienauer,

Yes absolutely agree with everything you say. The two URL fields are inelegant. The first one is for starting a crawl like you say. I like the Stop button ideal in the toolbar.

This is the point that I was happy was functional enough to fix the problem, which was my number 1 priority. That is, at a point that I can release onto the Mac App Store and have the app work again. So that is done and I believe the problem is fixed. Phew.

Now, I would like to focus on UI improvements that serve the tasks people have. I like your suggestions.

Questions:

  • You said: The "start button" will also have the benefit we can restart the crawl. — Is restarting something you’d like to do? Would you like to have more control over crawling? Currently the status of the crawl is not shown at all in the UI, apart from more rows appearing in the table. While I don’t think it needs to be too heavy, more could be shown and more control given to starting and stopping a crawl here.
  • Do you think it is useful to be able to see the currently viewed URL of the browser? That’s what this second URL field does, as it updates when navigating or double-clicking in the table. But I agree it could be presented much more nicely.

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