A Document Moving Store for Active Client Pages
(Page 1 of 4 )
Welcome to the fourth part of a twelve-part series that explains how to create Active Client Pages. In this part of the series, I explain the meaning of a moving store and how you come up with one.
The Initial Store for the Document Phase
The initial store comes with the master page. It consists of JavaScript variables and/or JavaScript arrays and/or JavaScript object properties. It is good to put this in a script at the bottom of the master page. You should design any of your pages in ACP so that it is rendered as it arrives at the browser.
The store has data that is needed for all the pages in the session. It can also have HTML pages in string forms.
The Moving of the Store
Assume that you have your master page in front of you. The next page to be loaded (created from the master page), should have containing HTML elements to hold the values of the store in the master page. An Input Text element can hold the value of a variable. A table element can hold the values of an array. An HTML object can hold the values of a JavaScript object (I hardly use this last feature).
The value for the display properties for these HTML elements should be "none;" in this way they will not be displayed and they will not occupy space. Code in the master page will copy the values from the master page to the loaded page. In this way you move the store (indirectly) into the next page (document). In a similar way, you can move the store from the second page into the third page; then from the third page into the fourth page; and so on.
Why move the Store?
A loaded page cannot access values in any previous page. This means that no loaded page can access values in the master page. On the other hand, a page can access HTML contents in the immediate page that it has loaded. This is why the store has to be moving as new pages are loaded.
Next: How does the User correct an Error in a Previous Page? >>
More JavaScript Articles
More By Chrysanthus Forcha
/ 2 
