Per Bothner <[email protected]> writes: > On 04/02/2017 02:46 PM, Mathieu Lirzin wrote: >> >> Mathieu Lirzin <[email protected]> writes: >> >>> I have sent a draft of my proposal which can be found here: >>> >>> http://mathieu.lirzin.emi.u-bordeaux.fr/gsoc/texinfo.pdf >> >> I have updated this draft, and tried to do it according to the very >> valuable feedback that has been made. >> >> Since there is less than 19 hours left before the due date, I have sent >> this as my final proposal to Google. > > I don't know if you still can/want to make changes, but I point out: > > - Using AJAX is neither desirable or necessary. AJAX requires an > active webserver, so is inconsistent with serving static pages or > from a file: URL, both of which are requirements.
Right, I overlooked that. > - The solution for handling multi-page manuals using iframe, using > div elements, and adjusting their visibility is implemented and > works great. That is the main contribution of my prototype. > The only change I'd like in this area is a modest extension so any > page can be the start page, not just index.html. OK, IIUC that feature requires including in each sub page a reference to a JavaScript program that opens the different iframes accordingly. If Javascript is not available in the current browser then only the basic page is displayed. > You write "the solution to store the non-displayed pages is not > clear to be yet". > To start out, these pages reside on disk (either locally or on a web > server), either has .html/.xhtml files, or optionally inside > .zio/.epub archive. When the JavaScript needs to load a page, it > creates an iframe, which cause te page to be loaded into the iframe. > If the page corresponding to an iframe needs to be hidden, we set the > css property "display: none" on that case, but all the text and > structure is still there, and can be searched as needed. "is not clear to me yet". What I meant was not about how to store files, but how the data in memory and potentially in the DOM could take a lot of space compare to something like a local browser database cache. Obviously this was unclear. :) I am not familiar with iframe yet, so thank you for your explanation. I have updated my proposal with your corrections. -- Mathieu Lirzin GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37
