Best way to integrate ProfoundUI with existing website desig

[Bryan641]

We've already got a website up & running with several applications, but want to start using ProfoundUI for new applications. Mostly, this consists of including our standard heading, which is not static html. It includes a login form and a dynamically built menu. I've already got ProfoundUI running in our existing Apache instance. What techniques can you recommend?

Here's what I've tried:
1. Include our current standard headings in an AJAX container, but the javascripts aren't being executed, apparently.

2. Include our current std headings in an iframe doesn't work well because the menu is a drop-down that would need to extend past the bottom of the iframe.

3. Create a cgi pgm that includes our standard headings, then pulls the ProfoundUI application into a DIV using AJAX doesn't appear to work. No errors, no application running either.

4. Create a cgi pgm that includes our standard headings, then pulls the ProfoundUI application into an iframe. This works, but I was hoping to have the ProfoundUI application be more in control, maybe even replacing the other product eventually.

Any other ideas?

--Bryan

[David]

I think maybe the best solution is to modify the "start.html" page that Profound UI uses and include the standard headers as a server-side include (SSI).

Profound UI uses an HTML page at /www/profoundui/htdocs/profoundui/userdata/html/start.html

This page is just a blank HTML page that loads in the Profound UI JavaScript libraries. It has a single <div> element where Profound UI renders the application content.

You can format this page any way that you'd like and this is the ideal way to include "header"-type content that is to display on every screen.

From this page you can use an SSI to call the CGI program which outputs the headings.

[Bryan641]

Thanks. Once I copy/modify start.html to start.shtml, would the best practice be to change the Alias statement to force references to "start.html" to use "start.shtml" ?
(I'll let you know how it works out once I get a window to stop/restart my Apache instances.)

[David]

Your best bet is to make your own separate copy of "start.html" in your own location within the "userdata" folder structure.

When you install an update to Profound UI it will refresh all "shipped" files, so you'll want to be working with your own copy.

You'll then want to update the Alias directive in the configuration to point to your file.

I don't believe the .shtml extension is necessary for SSI in the IBM HTTP Server. All that you should need to do is add the Options +Includes and SetOutputFilter Includes to the <Directory> block for the folder.

[Bryan641]

I've opted to load our standard headings by adding a <div> section and an ajax call to load it within our copy of start.html and that's working very well. Trying to call the program via cgi using ssi raised some other issues I didn't want to deal with right now.

Thanks!
Bryan