| || |
Frame Organization for Classic/Open Agent
Our current AUT is a web application that provides access to lab results information to doctors offices. We currently support IE7.
Our main application pages have certain "somewhat" static navigational elements that we would like to slice out of the frame and maintain separately. These elements include objects for our "Main Navigation", "Sub Navigation" elements around different workflows, application search textfields, and a Footer.
How we normally frame our view, is to declare an entire page, including the static navigation pieces, and keep all of declared objects in the separate windows. The problem we have noticed is that we have references to the same navigation objects in different windows in our frame. So if one navigation element changes, we sometimes have to go and find the navigation objects in the separate window declarations to make the change.
To help reduce or eliminate this additional maintenance, we were thinking about slicing out these elements and maintaining them separately from the main content panels.
Has anyone tried this for either the classic or open agents?
Has anyone successfully implemented this type of organization?
Are there any drawbacks to organizing the page in this fashion?
What i was thinking was creating a custom class that contains all the objects. That way we could just derive from the class and inherit all the objects when we create the window.
Any thoughts are much appreciated.
Re: Frame Organization for Classic/Open Agent
In that my suggestion, create your own customize window and inherance those property like for example
My window declaration like
Now i created one customize window declaration like
Browser MycustomizedFrame : MyFristnativation,Mysecondnativation
Let me know if any correction in that