H
Hans
In an in-house ASP site (designed to support IE5.5+ and NN7+) we are using
frames today and I know there are several issues by using frames but I
cannot see a better alternative.
In one frame I have a treeview. This treeview is not static (if the user
clicks on a node it will expand/collapse). It is different for every user.
It is pretty heavy to load. The main frame is loaded every time the user
searches for data etc (which occur often) but the treeview frame is only
reloaded when the user is actually working (clicking) on the treeview.
If I remove the frames I would have to run the pretty heavy code for
building up the non-static treeview for every page (which includes
instantiating COM+ component and database access etc) and this will be much
slower than it is today (at least when I tested). The users want to see the
treeview all the time because they are familiar with that in the windows
client (otherwise a link to a page that shows the treeview could be an
alternative).
This is an in-house site and issues with frames like bookmarking, indexing
etc is not an issue in this case. I don't actually have any problems with
the frames today and the small tests I have done with server side includes
did not perform well.
Is this just an unusual case where frames are the best choice or what
alternatives do I have? I prompted for removing the treeview (and also a
calendar frame) which are used rarely and add links that would open the page
with the treeview/calendar but they insisted that they should be visible all
the time.
Regards
/Hans
frames today and I know there are several issues by using frames but I
cannot see a better alternative.
In one frame I have a treeview. This treeview is not static (if the user
clicks on a node it will expand/collapse). It is different for every user.
It is pretty heavy to load. The main frame is loaded every time the user
searches for data etc (which occur often) but the treeview frame is only
reloaded when the user is actually working (clicking) on the treeview.
If I remove the frames I would have to run the pretty heavy code for
building up the non-static treeview for every page (which includes
instantiating COM+ component and database access etc) and this will be much
slower than it is today (at least when I tested). The users want to see the
treeview all the time because they are familiar with that in the windows
client (otherwise a link to a page that shows the treeview could be an
alternative).
This is an in-house site and issues with frames like bookmarking, indexing
etc is not an issue in this case. I don't actually have any problems with
the frames today and the small tests I have done with server side includes
did not perform well.
Is this just an unusual case where frames are the best choice or what
alternatives do I have? I prompted for removing the treeview (and also a
calendar frame) which are used rarely and add links that would open the page
with the treeview/calendar but they insisted that they should be visible all
the time.
Regards
/Hans