As described in the other documentation, it is possible to build your web application based on a Frames approach, or a Page approach. The Frames approach has the advantage of being faster in some cases, because less html is required as you move around the application, however it also has the disadvantage of not being very suitable when browsing with a small screen (such as a phone). With the improvements in CSS support, and overall template support, it is desirable in some cases to change the application from using Frames, to one using pages. Fortunately this change is straight-forward, and doesn't not involve much work in the application.
This section will describe the process, by converting example Accounts (31) to example Books (71). Since your application may be slightly different to the example you may, or may not, need to perform all these steps in your own app.
Copy and Paste the xHtml from the FrameHeader procedure into the PageHeaderTag procedure. In the Frame version of the application the header and menu procedures are separate, but in the page based application they are combined.
Go to the Menu extension, CSS tab, TaskPanel tab, set Menu Div to 'nt-left'. This causes the TaskPanel menu to float to the left hand side of the window, and the browses and forms etc to appear to the right of it.
On the menu extension, CSS tab, make sure the option to Wrap Menu in Table is off.
Tip: If you have other xHTML embedded in the PageHeaderTag, make sure that each xHtml entry has a Location set.
The IndexPage is the first procedure the user will see when they go to your site. This is usually a NetWebSource procedure, but it could also be a NetWebForm, NetWebBrowse, or indeed even a static page on the disk. You can inspect your FrameSet procedure to see what is currently being used as the default in the "main" frame. This is usually the starting point for the Index page.
In the Accounts example the starting page is a NetWebForm, so there is nothing to do.
However if your starting page is a NetWebPage then you will
need to add the tags;
<!-- Net:PageHeaderTag -->
and <!-- Net:PageFooterTag --> to the xHtml.
If your starting page is a static html page in the web folder, then you will need to add <!-- Net:PageHeaderTag --> and <!-- Net:PageFooterTag --> to the appropriate places in the page, and make sure the page has <!-- NetWebServer --> on the first line.
Whatever the name of this first procedure, that is the name you must set in the WebServer procedure, in the Default Page setting.