mathog wrote
I fear though that in the case of Inkscape this approach might not be feasible because it may well be trying to do several things at once during startup. This is not very helpful:
00:00.00 Starting 01:56.32 UI initialized 01:56.32 Loading icons 01:56.32 Loading fonts 01:56.32 Loading widgets ... 01:56.32 Started
Well, if the startup is multithreaded you can either show a single progress bar made up of the sum of all the single steps, with no possibility to discriminate every single contribute, or show all operations, each with its percentage (or bar) on the side, so you can see which one is the longest lasting. Or a simpler solution could be outputting something like:
00:00.00 Launching... 00:00.15 Starting UI initialization... 00:00.16 Loading fonts... 00:00.16 Loading widgets... 00:00.16 Loading icons... ... 00:43.50 Widgets loaded. 01:21.32 Fonts loaded. 01:56.32 UI initialized. 01:56.32 Launched.
And maybe save everything to a startup.log file using current date and time instead of deltas. Moreover, if this piece of information is stored on a file, a better looking startup window could take its place: some nice icon coloring up like a bar, a slowly fading image, a slideshow, etc. But this would need a bigger effort so maybe better start with a dirtier and quicker solution, for now.
I often find myself opening Process Explorer to check whether Inkscape is starting so I'm in favor of every possible approach that shows something in a human-friendly time interval after the double click. Of course this doesn't mean that I'm happy spending time looking at a startup log or progress bar so all efforts to get rid of them and speed up the process are welcome. IMHO it's a matter of being polite with the user: "You called me: here I am! Now, please, just wait a minute or two and sorry for being so slow...".
Luca
-- View this message in context: http://inkscape.13.x6.nabble.com/Running-Screen-tp4971605p4971670.html Sent from the Inkscape - Dev mailing list archive at Nabble.com.