On Wed, Oct 11, 2006 at 02:56:18PM -0300, bulia byak wrote:
The man page or running inkscape --help are the standard places to find command line help, a menu item would be relatively unusual.
It is relatively unusual for a GUI drawing app to have command line operations at all. None of the commercial ones have them AFAIK. Therefore it is justified to mention them in the GUI because otherwise many people (that might benefit from them) will never even think to look for them.
...or will pop on IRC asking where to find docs. We've found that there is a non-trivial category of windows users who want to use inkscape in commandline mode, yet who cannot run man inkscape or inkscape --help (and who do not find the online manpage on our website.) Having the cmdline args defined in the help menu will be much more likely to clue them in.
As well, there are many who - like bulia says - won't realize inkscape can be used from the commandline, and so may entirely miss that category of features.
- Release notes for the current version
Personally I wouldn't consider this as something users would read frequently (more than once even?) and therefore not worth having a menu item.
On the contrary, for many users who are already familiar with the program, it's the most important information in the entire menu. And given the amount of new features in our versions, and their detailed descriptions in the release notes, this menu item will certainly be consulted more than once.
Also keep in mind that this is the definitive location for telling users about "known bugs & workarounds". Having this linked to from the application itself is a very good move.
- SVG 1.1 specification at w3.org
Artists are the target users of Inkscape.
Who says that?
Inkscape's defined mission is to be the best SVG editor. I don't know if it's going to be a terribly useful link for the average user, but it certainly is within scope of our target audience. I suppose there's a risk that its presence will make people think that Inkscape should support 100% of the features listed there, but I expect most people will simply ignore it. ;-)
Also which specification do you link to, there are plenty of variations to choose from and I do think this would be much better served by writing up a page in the documentation.
We use a subset of 1.1, which is why 1.1 is linked. But when we have other profiles such as Tiny, we will make a submenu as Jon Phillips suggested and provide specs for each SVG variety we can handle.
This is definitely a good idea.
Bryce