Maybe this loading/running screen can have a donate link... Regards. El jue, 25-09-2014 a las 11:10 +0200, Jabiertxo Arraiza Cenoz escribió:

Thanks Martin. You are ok, but still are machines -mine- slow or sometimes overloaded and launch varius instances of inkscape by impacience -mine- people dont help them ;) +1 to the GUI donate/contribute button. Another option in help Menu? About page? Regards, Jabier- El jue, 25-09-2014 a las 11:01 -0400, Martin Owens escribió:

On 25-Sep-2014 08:01, Martin Owens wrote: That's where I stand too. Much better to put the effort into speeding the start up (which is awfully slow on Windows, about 30 seconds on my dual core Athlon X2 desktop) than to provide the end user with eye candy while the program crawls into being. Regards, David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech

On Tue, 2014-09-30 at 01:40 +0200, Johan Engelen wrote: Sure. that goes for any task. But devs will work on what interests them, or what they're being paid for. Paying them just allows the project to demand certain things that are good for the project and not just interesting. Martin,

On 30-9-2014 2:48, Josh Andler wrote: Tbh, on my core-i7, the startup time is long enough to warrant a splash screen. Plus, what is the downside of a splash screen? :) I count 1044 calls to SPPath::build upon starting trunk (after starting it several times). Perhaps it's not the icons, but something is creating a lot of SVG objects. Otoh, the boottime is dominated by something else, because the majority of time is spent before the calls to SPPath::build are performed; the part /with/ calls to SPPath::build appears fast on my machine. -Johan

On 30-9-2014 23:39, Josh Andler wrote: Indeed experimental is quite a bit faster. But when opening a complicated PDF with Inkscape, it can take a minute or so and in that case a splash screen would really be nice. For me, a splash screen makes sense for start times above a second or so. -Johan

I don't like splash screen for the purpose of a splash screen (like ESET do) but I feel your pain if you have a slow computer and you don't know if Inkscape is actually starting up or not. The best solution I've seen to this problem is the one GIMP uses. They have a splash screen _with_ a loading bar for all modules and settings that are loaded during start up. Just as Martin Owens says, something needs to be shown to the user in about 500ms otherwise another instance is started with another double-click on the icon. Martin, what do you mean with a "build flag for a splash screen"? a loading bar just like GIMP? -- Christoffer Holmstedt 2014-10-01 4:38 GMT+02:00 Martin Owens <doctormo@...400...>:

On Tue, Sep 30, 2014, at 03:39 PM, Johan Engelen wrote: Good scenario. One alternative for this use case is to have the base UI come up quickly and then have a separate loading phase where a progress bar might be included. However, I definitely think that we need to keep this specific workflow captured and listed along with other use cases that might pertain to app launching. -- Jon A. Cruz jon@...18...

On 3-10-2014 18:30, Niko Kiirala wrote: From your explanation, I am not missing the point of the argument. It's just that it fails to provide a solution for the problem at hand. The problem is that Inkscape starts too slowly (for some people's taste anyway), and that people (me too) start another instance of Inkscape thinking that the first one is not starting. The proposed solution is a splash screen, to tell people to hang in there and wait a little. The "argument" argues that instead, we should make Inkscape faster. Of course we should. Who can disagree with that? But, how do we do that? How to solve the problem? A statement of the form "Inkscape is too X", is not magically solved with an answer of the form "we should make Inkscape not X". Anyone is very welcome to work on making Inkscape start faster. As Josh pointed out, experimental already starts faster than trunk (for me too). Until we get below 500 ms, say, we can have a splash screen. I see no harm in that. As soon as we can show below 1 sec startup time, we kill the splash screen. I would rather see a splash screen than a (probably one-minute-unresponsive) main screen. But that is just taste. If you manage to get Inkscape's UI showing within half a second, with a "Loading..." text/progressbar on it, that'd be fine for me too. -Johan

I fully agree. Adobe Illustrator uses this approach, beside a launch feedback, the splash screen, with its stage informations, helps to know which part takes the most time to launch. For example, by seeing that fonts take a lot of time to load, you could choose to get rid of some of them in order to speed the software's launch. T.

I have seen programs that use something called a "splash screen" which is an image that is displayed briefly, during the loading of the program. It's displayed, for a few seconds, even if the program loads instantly, without any delay. For example, my internet security program, ESET, uses a splash screen. And ESET is known for its speed. The splash screen is displayed for maybe 2 or 3 seconds. (Granted the speed it's known for is more related to scanning, but it does open almost instantaneously!) For a graphics program, I think this would be an awesome feature. The trick would be deciding how long to display it. Not long enough to annoy folks, but not so fast you can't appreciate the image. I would think a very large image would not be appropriate....unless it was quite simple. But say 400 x 500 pixels (or vice versa) would work. (Maybe there could even be multiple images, with 1 displayed at random, upon opening Inkscape. Maybe the user could populate the file themselves, and/or have the option of using default images. This would make for awesome contests or competitions -- endless possibilities!) Hhmm...I guess for Inkscape, this would happen whenever a new document is opened....right? All the more reason to have mulitple images available! Using such a splash screen / running screen doesn't mean you stop working on loading speed; doesn't mean it's compensating for slow loading, just because it's there. It's just a nice bonus feature! If Inkscape opens behind the image, before it goes away, awesome. If not....better than twiddling your fingers! :-) I think it would at least warrant a new feature request. Of course, I always hesitate before making a new feature request, because it seems sometimes that work on the "bread and butter" part of Inkscape should come first. Or maybe Jabier has some ideas about developing it already??? Thoughts from a loyal Inkscape user :-D -------------------------------------------------- From: "Jabiertxo Arraiza Cenoz" <jabier.arraiza@...2893...> Sent: Thursday, September 25, 2014 3:10 AM To: "inkscape-devel" <inkscape-devel(a)lists.sourceforge.net&gt; Subject: [Inkscape-devel] Running Screen

A quick climate bar/var: http://fc04.deviantart.net/fs70/f/2014/274/f/0/inkscape_climate_by_jabier... Regards. El mié, 01-10-2014 a las 22:05 +0200, Jabiertxo Arraiza Cenoz escribió:

On Thu, 2014-10-02 at 01:44 +0200, Jabiertxo Arraiza Cenoz wrote: You could always upload to your InkSpace ;-) http://inkscape.org/en/person/ Martin,

On Thu, 2014-10-02 at 12:25 +0200, Jabiertxo Arraiza Cenoz wrote: Thanks Jabier, this is a great example for animation in svg. Image tags don't work so well for svg animation ATM (in firefox) but I hope this will change. (anyone know of any good tricks in html?) Martin,

Maybe but is like snow. Also we can alert about the climate change here. El jue, 02-10-2014 a las 19:01 -0600, Brynn escribió: