In another thread, Gary wrote, > If that is part of Draw, I'd like to see a new chapter or so on it.
This brings up an important question: for which extensions should we include instructions in the user guides (not just a pointer to the extension itself)?
Thus far we haven't attempted to include instruction on extensions in our books, but it may be time to start making a few exceptions... at least for the major extensions like PDF import, Drew Jensen's Report Runner, and the Sun Report Builder (may be others; I haven't done a thorough search through the extensions).
When a major feature is available only as an extension (not integrated into OOo), a section or chapter in the books for each affected OOo component would be very helpful to users, I think.
Should we include instructions on any other extensions? I'm thinking of André Schnabel's Template Changer (http://extensions.services.openoffice.org/project/templatechanger), which sounds great (much in demand by technical writers, amongst others), though I haven't tried it yet. I'm sure I've spotted some others.
--Jean
