Opened 7 years ago
Closed 7 years ago
#16534 closed enhancement (wontfix)
Improve startup time
| Reported by: | anonymous | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | |
| Keywords: | template_report; usability | Cc: |
Description
What steps will reproduce the problem?
- Run JOSM
What is the expected result?
After the user clicks the icon on his desktop to start JOSM it is there (nearly) immediately to let him do his job quickly.
What happens instead?
On Windows and macOS/OS X platforms JOSM takes a minute or so to be even in a runnable state. It bothers the user with a lot of internal information that might be useful for debugging purposes of a developer but is completely useless for end users.
This happens even if no additional plugins are loaded.
It has been occurring for long.
With respect to some network error messages on startup JOSM seems to access network resources which might not be necessary if the user wants to work offline (see bug #12455). Access the network when it is actually needed.
Attachments (0)
Change History (7)
comment:1 by , 7 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:2 by , 7 years ago
comment:3 by , 7 years ago
The issue is too broad, it's like "make JOSM better". We already put a lot of effort to improve the startup time. Practical suggestions/ideas are welcome, but a vague ticket like this is useless.
comment:4 by , 7 years ago
Ok, so I make it a bit clearer:
- Please check whether every step needs to be really done at startup time or whether it can be postponed to the time it is actually needed. This especially applies to runtimewise expensive features such as network access.
- Postpone initializiation for seldomly used features to later.
- Consider activating plug-ins at runtime without having to load and activating them at startup (this would also improve the plug-in handling user experience).
- If JOSM is in a minimal usable state to do basic or frequent tasks, then show the GUI and let the user do his job.
- Hide JOSM's internal messages from the user. Change your point of view on the GUI and see it with the eyes of a mapper. If a splash screen is necessary at all, then prefer a standard progress bar (not an indeterminate progressbar, because this doesn't tell the user much about the actual progress). For some guidance see for instance the Human Interface Guidelines from Microsoft, Apple or GNOME. If you need the messages for debugging purposes, please use an internal log mechanism.
I hope I could shed some more light on this issue.
comment:5 by , 7 years ago
| Resolution: | invalid |
|---|---|
| Status: | closed → reopened |
| Summary: | Start JOSM quicker → Improve startup time |
Many things you list are already implemented, I'm not sure if we can improve things further, but at least the ticket is more precise now.
comment:6 by , 7 years ago
| Type: | defect → enhancement |
|---|
comment:7 by , 7 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | reopened → closed |
Your suggestions actually go in the direction Windows was going years ago and which I hate. Instead of taking the time it takes, you propose to hide and delay. The result will be like for Windows: that we earlier show the workbench, but it then takes time to actually get usuable. No thanks. We already delay these initializations, which aren't needed usually.
Also I see no reason to hide the messages. This way the users actually sees that a lot is done instead of only seeing a meaningless progress bar. Nobody expects from normal users that they must understand these texts.
For the general idea to check the times: We do that all the time.
JOSM is complex, there is no way around this.
What makes this bug an "invalid" bug? The problems described here are actual problems that hamper users in their work and I didn't report them unconsidered.