The sequence of chapters in the draft Calc Guide seems wrong (illogical) to me, but I don't have a clear idea of what would be a better (more logical) sequence.

Here is the current sequence:

1. Introducing Calc
2. Entering, editing, and formatting data
3. Using functions and creating formulas
4. Creating charts and graphs
5. Printing, e-mailing, exporting
6. Using the DataPilot
7. Data analysis (using scenarios, goal seek, solver, others)
8. Using graphics in Calc
9. Linking Calc data: Sharing data in and out of Calc
10. Using styles and templates
11. Sharing and reviewing documents
12. Calc macros
13. Calc as a simple database
14. Setting up and customizing Calc
A: Keyboard shortcuts
B: Description of functions
C: Calc error codes

In particular, Ch8 on graphics and Ch10 on styles and templates seem out of order, dumped in the middle of the chapters on working with data. If we assume that most users won't go beyond fairly simple use of spreadsheets, then putting Chs 8 & 10 just before or after Ch5 would be logical. And what about Ch 3? Should it stay where it is, or go after Chs 5, 8 & 10? Any thoughts, suggestions?

Now is a good time to change the sequence if we're going to, while we're editing for other purposes (so changed references can be caught now) and before the first edition of the book is finalised and the translators get to work with it.

Here is one alternative sequence:

1. Introducing Calc
2. Entering, editing, and formatting data
3. Creating charts and graphs
4. Using styles and templates
5. Using graphics in Calc
6. Printing, e-mailing, exporting
7. Using functions and creating formulas
8. Using the DataPilot
9. Data analysis (using scenarios, goal seek, solver, others)
10. Linking Calc data: Sharing data in and out of Calc
11. Sharing and reviewing documents
12. Calc macros
13. Calc as a simple database
14. Setting up and customizing Calc
A: Keyboard shortcuts
B: Description of functions
C: Calc error codes

Aside: Chapter titles may need improvement, too. Again, suggestions welcome.

--Jean

Reply via email to