On 10/11/06, Alan Horkan <horkana@...44...> wrote:
I'm not saying there shouldn't be a page in the user manual explaining it but that it might not be important enough to have a menu item, rather than having one menu item pointing to the manual or website.
Perhaps in 1.0, it will be incorporated into the manual. But for now I think it's worthwhile to push it a bit more aggressively.
Might just mean the command line arguments are not very user friendly.
Yeah, and that is exactly the way to make them more friendly... or at least discoverable :)
together with many other command line utilities. However I dont think anyone would disagree that it might be useful if the user interface provided a way to achieve a batch task like exporting each layer of a document as a seperate image.
Yes, I agree. An extension might handle that.
On the contrary, for many users who are already familiar with the program, it's the most important information in the entire menu.
I would think people (adminstrators?) would read the release notes before or while downloading the new version. The Changelog and News files provide even more information.
The Changelog has been abandoned, and the NEWS file is actually a copy of the Release Notes.
It is great that the release notes are of such high quality and provide good descriptions but shouldn't this information really be in the manual and tutorials?
Developers are not interested - and should not be forced - to update the manual once they add a new feature. Manual is a very different kind of writing, differently structured and with a different requirements. A developer has the obligation to describe exactly what features he has added to the program, completely and detailedly, nothing more nothing less. A manual is a wrong place for this information; the Release Notes are the correct intended place. Later, the manual author(s) would update the manual based on the Release Notes, by placing it in a proper place, rewriting for easier understanding, adding examples etc.
Links are great if you have an internet connection, but if you dont the time wasted by firing up a web browser to nowhere can be very slow and annoying.
Yes, some of the things can be shipped with the program - such as the man page and rel notes in HTML. But for the manual, I don't think we have the permission from the author to do that. And the SVG spec is too big to be included.