Export Run Time Page Script.

[Roboblue]

Since AMS can export a design time created page (.xpg) that can be used in another project at design time, can we have an export feature that will export the design time created page to a script that can be loaded at RUN TIME?

Or, even add an action (load.xpg) that would allow the .xpg to be used at RUN TIME in addition to design time?

I have a project (an interactive magazine) that will have over a hundred pages. Instead of having 100 full pages, I would like to only have one page and load the page from a script.
Problem is, each page is totally different in types and quantity of objects.
I would like to build a separate project that would allow me to create these pages in design time, then export them to be used in other projects.
I would "bundle" the page script (or .xpg) with the resource files and just unzip them into the next project's directory structure so just the script (or load.xpg action) has to be called.
With the script method. the problem is getting the page into script. Each object's table would have to be manually created for each page. A HUGH amount of time.
In design time, the tables would be built as the object is attributed anyway, so would it not be easy to export it as a script?
With the load.xpg action, it would be even easier.

[Dermot]

To be honest I don't see the advantage. If you have to build each page at design time then you might as well just have the pages there at runtime. It's all just saved as xml anyway so whether they are seperate files or all compiled into one it won't make any difference. I just don't see how it would help. You still have to put the same amount of work into creating the pages so saving each page as a script and then loading it at runtime is just complicating the whole thing.

[Roboblue]

The advantage to me is not having a project with 111 pages to go through on the design stage.
Now, I haven't built a project that had more than about 30 pages, but I noticed a small slowdown with that and it was confusing to keep up with that when debugging and editing.
Will it slowdown the action of the app if it has 110+ pages?
I assumed it would.

[Darryl]

Thanks for the suggestion. REF: 17261

To answer your question regarding the number of pages and performance, since each page is loaded when accessed, the number of pages shouldn't have much effect on runtime performance.