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?
|
- RE: [Dynapi-Dev] Document... rulin tontraeger
- Re: [Dynapi-Dev] Document... Doug Melvin
- RE: [Dynapi-Dev] Docu... Laszlo Teglas
- Re: [Dynapi-Dev] Documentatio... Doug Melvin
- Re: [Dynapi-Dev] Documentation Pro... Doug Melvin
- Re: [Dynapi-Dev] Documentatio... Richard Bennett
- RE: [Dynapi-Dev] Document... Laszlo Teglas
- FW: [Dynapi-Dev] Documentation Pro... Laszlo Teglas
- FW: [Dynapi-Dev] Documentation Pro... Laszlo Teglas
- RE: [Dynapi-Dev] Documentation Pro... Strolia-Davis Christopher Contr MSG MAM
- Re: [Dynapi-Dev] Documentation Pro... Laszlo Teglas
- Re: [Dynapi-Dev] Documentatio... Doug Melvin
- Re: [Dynapi-Dev] Documentatio... Richard Bennett
- RE: [Dynapi-Dev] Document... Laszlo Teglas
- Re[2]: [Dynapi-Dev] D... Robert Rainwater
- Re: Re[2]: [Dynap... Matt Fair
- RE: Re[2]: [... Laszlo Teglas
- Re[4]: [... Robert Rainwater
- RE: Re[4... Laszlo Teglas
- Re[6]: [... Robert Rainwater
- RE: Re[6... Laszlo Teglas