Two comments on the xml itself.
1. Probably better not to use <p><code><![CDATA[ ... java code
... ]]></code></p>.
It doesn't do what you think. Instead use <source></source>. It makes the
nice blue box outlining your code, and renders the contents appropriately.
That was the only XML change I made.
2. If you're referencing the developer's guide, link to the part you are
referencing. It's easy to add a link. Just add
<link href="guide-developer.html">Developer's Guide</link>
wherever you reference it. You can even link to specific parts of the doc
by adding the #anchorname to the href. Just like HTML.
dave
-----Original Message-----
From: Steven Cummings [mailto:[EMAIL PROTECTED]
Sent: Friday, November 22, 2002 10:42 AM
To: [EMAIL PROTECTED]
Subject: RE: Documentation contribution
Thanks Dave,
Are there any further suggestions before I make a drive to finish it up? I'm
trying to think of all of the issues involved with xindice-embed without
repeating the developer's guide, so I really feel like I should try to
include some input from one or two other people who are developing different
sorts of embedded applications. For instance, mine is just a replacement
servlet that neglects to deploy xmlrpc access. Is anybody doing anything
along the lines of a desktop app or RMI accessible xmldb? Thanks.
/S
"Dave Viner" <[EMAIL PROTECTED]> wrote:
>If no one objects, i'll commit this to
>src/documentation/content/xdocs/dev/guide-embedding.xml.
>
>I don't use the embedded version, but this documentation looks like a
decent
>first step.
>
>dave
>
>
>-----Original Message-----
>From: Steven Cummings [mailto:[EMAIL PROTECTED]
>Sent: Thursday, November 21, 2002 12:40 PM
>To: [EMAIL PROTECTED]
>Subject: Documentation contribution
>
>
>Hey all,
>
>I'm starting a document to be the "embedding-guide". Right now it's based
on
>my experiences, so I don't know if it's broad enough, or covers all of the
>aspects involved. So if anyone has time I'm asking for suggestions and
>feedback on the following draft. Let me know if you see things that could
be
>improved in the content or structure of it or if there was a more specific
>direction that someone had envisioned for this (currently, it seems as
>though no-one had filled this documenation gap).
>
>Also, while forrest looks like a cool project that I want to learn, I
>haven't had time to actually run it and try it out myself (being a busy MS
>student). So I haven't really tested this document, although it was simple
>enough to follow the examples from CVS. If anyone who could look at this
>will give me suggestions, that would be great. Thanks!
>
>/S
>
>--
>Steven Cummings
>Columbia, MO
>Email: [EMAIL PROTECTED]
>AIM: cummingscs
>ICQ: 3330114
>
>
>__________________________________________________________________
>The NEW Netscape 7.0 browser is now available. Upgrade now!
>http://channels.netscape.com/ns/browsers/download.jsp
>
>Get your own FREE, personal Netscape Mail account today at
>http://webmail.netscape.com/
>
>
--
Steven Cummings
Columbia, MO
Email: [EMAIL PROTECTED]
AIM: cummingscs
ICQ: 3330114
__________________________________________________________________
The NEW Netscape 7.0 browser is now available. Upgrade now!
http://channels.netscape.com/ns/browsers/download.jsp
Get your own FREE, personal Netscape Mail account today at
http://webmail.netscape.com/
