Gerry,
G. Roderick Singleton wrote:
There seems to be some problems with the current DevGuide that are
political and proprietary in nature. Sun produces this guide. While this
can you please elaborate? What kind of problems?
guide has a five year head start, it seems to me that we might be able
to create an acceptable guide and avoid the nonsense.
What do you mean by "nonsense"?
Let's have some ideas. If there are any takers, I can set up a task and
a master document with which to start.
Let me emphasize that producing a Developer's Guide from scratch
is far from being an easy task. The original dev guide (now
1,000+ pages) was created by three full time authors over a period
of several months. Without close relationship to the developers
this is a hard thing to do.
As mentioned in my previous replies (to later postings) we
will open source the dev guide in the mid future but it still
needs a considerable amount of maintenance work. So there will
be loads of opportunities to work on developer docs.
Apart from that, we should start discussing a strategy around
this type of docs instead of just starting off. Even with a
dev guide there are still huge gaps in the dev doc space that
should be identified and closed:
- we have the in-depth dev guide that is very detailed
and highly technical for the geeks among us.
- we also have the (StarOffice) BASIC guide as an entry level doc
- there is Andrew Pitonyak's excellent macro document
- cross references VBA<->BASIC on docs.oo.o
- online help content for BASIC runtime functions
- and the hacker's wiki
This looks sort of unsorted to me. If we could work out a plan
and identify what we would need to complement the existing
docs that would be great. Possible tasks in this area would
encompass
- split up the dev guide to make it less monolithic
- merge BASIC guide and macro information
- create a OOo macro cookbook
- create docs for creating OOo extensions
I confess that some of the tasks depend on Sun open sourcing the
guides and I apologize for the delays but I can assure you that
we're working on this.
Thanks
Frank
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
