php /
asp / cgi / jsp / cfm / perl
these
all require server side engines. Thus they can not be viewed from
anywhere. They can only be viewed when served up by a server. I have
mentioned in my earlier comment, that "We want the document to be viewable
offline locally, therefore we can't use any server side script to include the
navigation system."
I
believe this is one of the reasons why Sun uses frames for it's extensive
documentations of the Java API:
NanoFace =;^)
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Michael Pemberton
Sent: November 14, 2001 4:48 PM
To: [EMAIL PROTECTED]
Subject: RE: [Dynapi-Dev] Documentation Project>Using frames may also help when we want to update different formats of the >documentation. i.e. pdf files can be set up to list the content files >consecutively without the need to strip out the navsys from every page. We >could then replicate the navsys as a table of contents. (I haven't actually >tried this, I'm just thinking out loud) I don't know much about Win2PDF. >Does it take a graphical snap shot, or does it copy the text of the document >and format it into pdf? If it copies the text, does it ignore HTML tags? >What would it do to a navsys that is made up of tags mixed with content?>I vote for Frames =;^)
This is not really needed. It is quite possible, using php / asp / cgi to include the common navigation code automatically. This means that if written in a specific way, it is then possible to override the inclusion of such code. This would allow for easy conversion by simply stripping the "include" calls made in the content files.
Get your FREE download of MSN Explorer at http://explorer.msn.com
_______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://www.mail-archive.com/[email protected]/
