rthrash... thanks... and thanks for the info... yeah I’ve only been working with Firefox and IE for the moment. I’m certainly concerned about Mac users, but I don’t happen to have one at home yet so I usually test things post for it... I expect Safari will be broken till I’ve rewritten the code to something a little more managable as it would be difficult to debug before then...
opengeek... thats interesting cuz thats actually how I had it originally... I had it so that all pages were individual complete pages... however the framework for the site would stall on loading, and the constant reloading of the menu had an irritating visual effect... also having everything reloading made everything jerky because of the page loading time so I opted out of that approach towards the current system even though iframes are not my prefered technique... bookmarking is a problem... I think this could be handled a little bit with some custom scripts for bookmarking or deliciousing (word?) the page... but you’re right its a bit of a technology issue... lesser of two evils as it were...
that reminds me of something interesting that I was running into... the ability to share a library script like scriptaculous across multiple files... what I’d like to do is load scriptaculous in the main file once... then have the individual pages (or an external library) control the DOM for all the transitions in different frames... now admittedly I haven’t played with it too much so maybe its very simple and already exists... does anyone know if this can be done? target elements outside of the active frame with Scriptaculous? Here’s a couple of horrible examples...
New Effect.Opacity(top.main_content.loader, ... // targets the "loader" in the "main_content" frame of the top level
New Effect.Opacity(_parent.top_navigation, ... // targets the "top_navigation" of the parent frame
You get the idea... it would be really nice to do that as then I wouldn’t need to worry about justifying the filesize of the library... just include it in a hidden frame or something and manipulate the DOM through Ajax or the like...
Again thanks for the comments!
Cheers,
Owen