So the example:
if ( test path name (get root + "foldername/file.html") = 1)
include ("foldername/file.html")
end ifmakes it immediately clear that you don't need to put a slash after "get root". I know it is in the docs, but even this simple example also demonstrates the need to test a path before including a file.
The other thing I'd like to see is inclusion of all the 4D commands that work in Active4D directly within the documentation. Even if it is only to show the method prototype and the words "works the same as 4D native".
I spent some time yesterday trying to find "test path name" in the Active4D documentation and see how it worked differently to the way it works in 4D. I eventually found it in the introductory text to the System Documents chapter. It didn't have a little section of its own and doesn't appear in the index. I know there is the list of method names in the Active4D documentation, some bold and italic, but that list isn't hyperlinked or page referenced.
Aparajita, I still think the docs are very thorough, but if you want to know why people are asking questions on this list, then maybe this is part of the solution. The demo database is not always the most convenient way to find these answers.
Ari Maniatis
On Monday, May 12, 2003, at 05:51 PM, Mark Howells wrote:
I'd agree that the documentation is excellent, but that it might benefit from the inclusion of more example code. Other programming language manuals or help sites, for example PHP.net or the "Bible" series of books, provide some solid examples of coding techniques and snippets which may be beneficial.
--------------------------> ish group pty ltd 7 Darghan St Glebe 2037 Australia phone +61 2 9660 1400 fax +61 2 9660 7400 http www.ish.com.au | email [EMAIL PROTECTED] PGP fingerprint 08 57 20 4B 80 69 59 E2 A9 BF 2D 48 C2 20 0C C8
