Hi all, I'm new to this list. I'm a programmer and a every day user of Inkscape to build SVG files to use in my applications.
I think that having a inkscapec.exe is nicer, since most of the users might find strange to start inkscape and a console window pop-up. So if a user needs to get the output, then it would run inkscapec.exe. It seems a nice solution.
Another option is to redirect the output to a file. In this case it can be nice, since we would get a log file with out any effort. The log file could be saved on the program folder.
On Tue, May 26, 2009 at 9:35 PM, Jasper van de Gronde < th.v.d.gronde@...528...> wrote:
Yann Papouin wrote:
inkscape.exe can be used in command line, for a .bat file for example ?
Yes, but that's not what this discussion was about (and you don't even have to compile it as a console application for that). The problem is that Inkscape prints debug messages to stdout. On Linux you can easily see these by starting Inkscape from a shell, but on Windows you won't see them, even if you start Inkscape from the commandline. This prevents most Windows users from using this potentially valuable debugging resource.
There are two things you can do to remedy the situation. One is to compile Inkscape as a console application. This doesn't change it's behaviour at all, except that Windows does attach a console to its stdout. The other is to run it through inkscapec.exe. The latter is much easier for non-developers.
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel