Jean Hollis Weber wrote:
hmmm...I know that in an earlier email I said that I would help and
didn't care if I got any credit...OK, that was a bit over stated...I
guess I do kind of care after all.
I would never take anything away from Andrew, but the outline and
comments you mention where put up by me.
LOL - I know - Drew / Andrew - it can be a little confusing..anyway, no
harm, no foul as they say.
I've probably said this before, but one problem with a book such as
this is: how much to teach about relational databases themselves,
versus just explaining how to use the tools provided in OOo Base.
Obviously our main requirement is to cover OOo's tools, but I do like
the idea of including some instruction on database design as well. Dan
Lewis's "Getting Started with Base" chapter is great in that respect.
How to strike a balance is a real trick, isn't it.
For example you mention covering the basics of relational database
theory - well, you can use Base to create a flat database just as easily
as a relational one, and in fact I would bet that the vast majority of
people falling into my fist category above will end up doing just that.
Then there is a real problem in that there are at least three distinct
user types.
First is the person that uses the database development part of it to
create a very simple database for personal use.
Second, the person using the database to development database
applications for others to use.
Finally, those that will be using those database applications created by
the second person.
A model I like is the GnuCash Tutorial and Concepts Guide,
http://svn.gnucash.org/docs/guide/
Most of the chapters are divided into three parts: basic concepts,
instructions for using the program, and examples of use. It's a good
way to combine background and tutorial information with reference info
in one book, without jumbling it all up together. I think something
like this might work really well for a book on OOo Base. What do
others think?
There is an attempt to do something like this with the outline on the wiki.
First a quick overview of the components found in a Base file. ( tables,
queries, forms, reports )
Next an overview of the wizards that allow a user to quickly create
these components.
Then an overview of the designers ( editors ) for these same components.
At each of these steps more of the 'theory' of relational databases can
be introduced as needed. For real in depth discussion however I would
simply offer a list of references, this type of information has been
covered in great detail by others already. Not to mention that Base can
connect to a variety of DBMS engines and each will have slightly unique
features.
Finally, there should be a section on writing macros (scripts) and this
will need to be a large section as Base is missing many of the user
friendly features found in other desktop database front end tools.
Actually, I would go one further - it would be a great help if the
scripts described in the manual could be compiled into a library ( or
libraries ) that could be distributed along with it. Anyway, I think I
already mentioned that on the wiki page.
I'll try to find time to work on another iteration of the outline, but
if anyone reading this wants to have a go before I get to it -- please
do!
On a related topic: do we want to develop this book using the wiki as
the source document, or as .odt files as we've done with the other
books? There are pros and cons to each approach, given that we do want
to have the book in several forms when it's done: .odt, .pdf, and
wiki. What do you think? Personally I prefer .odt, at least once we
get past the outline stage and into the real writing.
I think an odt file needs to be the baseline document, also
Drew
