RE: [Dynapi-Dev] Documentation Project

[Strolia-Davis Christopher Contr MSG MAM]

Here is one way in which you could save multiple data files that could potentially be converted to XML later if desired.   You can create a different .js file for each topic containing the data that you need, and either -Load the .js file dynamically (not as easy, but more fun). -Have different pages that already have the different datafiles loaded with a <SCRIPT SRC='javascript:void(0);'></SCRIPT>, or whatever   Here is an example to help stir up some ideas:   DynLayerDoc.js   var Data = "{     Feature:"DynLayer",     Description:"Dynamic Layer Manipulation",     Details:"The dynLayer library. . .",     Example:"http://www.richardinfo.com/examples/php/examples.html",     SubData: [         {             Feature:"moveTo(x,y)",             Description:"Moves the DynLayer to the position in x and y",             Details:"moveTo allows the developer to . . .",             Example: "http://...",             SubData[]         },         {             Feature:"setHTML",             Description:"Sets the HTML inside the DynLayer",             Details:"setHTML allows the developer to. . .",             Example: "http://...",             SubData[]         }     ] }     -----Original Message----- From: Laszlo Teglas [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 15, 2001 5:12 PM To: [EMAIL PROTECTED] Subject: RE: [Dynapi-Dev] Documentation Project I like the idea. Lets look at the requirements:     1) One XHTML file that displays the widget (No problem)     2) One DynAPI widget that displays the data (Little coding and debugging, No problem)     3) One massive data file (Or many smaller data files) - This implies the following:         a) we can't use a database because we need a server side scripting engine to extract the data. this can't be done because we want the docs to be available offline locally independent of a server         b) we can't really use a massive data file either think of the consequences: accessing the page online for the first time with a standard modem would require many minutes, maybe tens of minutes. Think about all the intro module docs, all the reference docs, all the example docs, and the tutorial docs, being downloaded all at once whether you want it or not. Just not an option.         c) using many smaller data files may be viable if we can figure out how to make the widget access the required files on demand. I'm not sure how this would be done. Any Ideas?