Am 31.01.2017 um 12:29 schrieb brynn:
Ok, great. In poking around a bit I see a lot of wiki pages being
properly marked as no longer relevant, with pointer to an appropriate page on the Inkscape website. So this all looks quite good.
Yes, they're well marked (I think thanks to Maren).
- I think we need to credit Sylvain and su_v for most of this. Just as I didn't 'tweak the translations page to perfection' - I don't remember ever having changed anything on it. I don't know who wrote it.
The extensions listing pages in the Wiki are a WIP, they're still being checked, so definitely a Wiki thing. I think someone had planned to contact the authors, and to ask them if they would like to publish their extension at inkscape.org... (and if they don't answer, just to publish them there, if they work and licence permits).
There's a fair bit of other extension-related information in the wiki
currently, beyond details on extensions themselves. But I suspect most of that can be folded into some of the other described sections. For instance, docs related to how to write extensions probably would be best housed in a developers' manual.
Yeah, I wouldn't want to lose those. We get so many questions in forums that I can't answer. "Developers' manual".....hhmm. Hhmm.... Almost said "hmmm" again. I guess I think of the entire wiki as being the developers' manual. Is someone actually working on such a thing? I haven't heard about it.
- I'd rather be daring, and put that info about how to write an extension into the user manual part. It's surprisingly well documented, and it's usually advanced users, (like me) who want to write their own extensions to fulfill their specific needs, or to fill in for missing functionality.
These are often not the people who would or could work on the application code itself.
Script extensions, for me, fall into the same category as custom pattern files, icon sets, symbol sets, custom templates, custom filters, custom markers, custom keymaps, palette files, etc. (but most of those don't have easily accessible documentation - we usually give people a link to external tutorials, if there are any).
@Brynn: It's possible to auto-create a 'developer's manual' from special comments (docstrings) in the code. For that, the code needs to be documented inside the code files.
Regards, Maren