Page History

...

This child page for "User Guides Revisited" is an attempt to think about this new structure for user documentation.

Basics plus examples

We can start from the very basic, highlighting common features between all apps. The very beginning for the user guides should talk about those common features and how handle them and only when the basis are set, provide examples for each app.

...

A "theoretical" comparison between direct formatting and styles, and why stiles styles are preferred.

A description of what templates are and why they are useful. Highlight the fact that on AOO makes extensive use of styles.

Quick examples of style and template definition on main AOO apps (Writer, Calc, Draw/Impress)

Now, to the detail

With that background, it is now possible to start with each app documentation. At this point it will be a lot easier to explain how stiles styles work on Writer (the next stilestyle/linked with/etcetera property) or any other app.

Task oriented documentation

A common scenario implies working on several components at the same time. It is now the moment to explain how to transfer data from one app to the other (OLE, DDE links...), how to work with a chart on Calc or Writer, how to pick data from databases...

Advanced features

Graphite fonts
Master documents
Mail merge

BASE Features

Using Base with the embedded HSQLDB and as a front end to other RDB's

…

Anything else?