Drew wrote:
I have read over your outline document and have a few comments, changes.
Regarding using the Getting Started chapter on Base as a seed. I agree.
Xforms - They are not supported within the Base file, but I would add a
section 5.4 Working with XForms I think.
( XForms most likely deserve a separate manual )
OK. Yes, seems important to mention them. Lots of people want to
get data into their databases from forms on the Web, by whatever
means works.
Chapter 4 Data Output
You dropped any mention of the new Sun Report Builder (SRB).
If I am correct, I suspect this to be the most used functionality in the
Base module, over time.
My ( stale and limited ) experience with MS Access was that in general
office setting the reporting features where far and away the main use.
Agreed, it's important and must be included. I may be confused
about what's what. Is SRB the same as what I called "Report
Designer" in Chapter 6? If Report Builder should go into Ch 4
instead of Ch6, I have no objection. I don't know enough about
these tools to determine where best to cover them.
I suspect on some topics we'll end up doing what Michele Zarri
and I did when writing the Impress Guide: reshuffle what's in
various chapters after the topics have been written.
Chapter 7
7.1 Working with Macros
Thanks for all the extra info, Drew. I'm totally out of my depth
in this area, so I'm glad you and Andrew know about this stuff.
There are two individuals that I know of working on independent Base
guides. I contacted both about volunteering to work on this document - I
am hopeful they will respond.
Thank you!
For myself - I believe at this moment the most important thing to get
together is a good manual for the new report builder. I suppose there is
no actual way to have anything 'official' ready by the time 2.3 releases
but there should be something.
I agree, this is important. Thank you for taking this on.
In this regard ( and falling the category
of put or shut up ) I have started by taking the Specifications
document, with the latest updates, as a starting point. At this point
all I have done is break into a slightly different structure and started
removing the 'geek talk' and replacing it with I hope is more user
centric language. I also have been compiling a list of functions taken
form the OASIS documentation and noting which of these are available
from within the SRB. My plan is to move this function document to the
new SRB page on the wiki ( per the developers request ) - but it should
also be incorporated into the manual I believe.
I don't know enough about this feature (or the likely volume and
technical level of the documentation) to say at this point, but
two levels of doco might be needed or appropriate: basic and
advanced. Perhaps with the advanced stuff being on the wiki or in
a separate document (but not in the manual). Of course, we can
decide this later, after the material is written.
So, what do you think is the best way to proceed? I could create a page
on the wiki, with the new outline. And start moving the sections into
this. I could take what I have in an Writer file and put it up to the
OOoAuthors site.
I am very much leaning towards the wiki page - simply for the time
issue regarding the upcoming release. The fact is the pre-release package
is already garnering active use and specific questions coming into the
user forum at an increasing rate.
Since everything will end up on the wiki eventually, if you want
to start there, I have no objection. My view: whatever works for
producing good docs quickly, do it! If the other people you
mentioned whom you've contacted are happy to work on the wiki,
even better.
Despite my personal preference for ODT files, I'm not sure there
is any advantage (and maybe some confusion) in having both wiki
and ODT files of the same material at this stage, although the
outline on the OOoAuthors site should be amended to point to the
wiki for the latest version.
Walter, I'm looking forward to your views. It sounds like you and
Drew will be the most active people on this project for awhile,
with Andrew coming in later when he has the time. I'm sure you
guys will be able to sort out an outline and working method (wiki
or whatever) amongst yourselves; certainly you all have a lot
more knowledge than I do about the subject matter and the needs
of users. My main role is to nag people if I haven't heard
anything in awhile. ;-)
--Jean
