On Mon, 23 Feb 2009 23:40:23 +0000, John-Mark Bell wrote: > Frames seem to be broken on everything that isn't RISC OS. That's > telling me that the current way they're implemented isn't particularly > portable. Perhaps we should look into this.
That would probably keep one of the Google students quiet for a while :-) Some sort of internal solution is needed, where the core code generates the frames and scrollers, and handles resolving mouse clicks to each frame. The current implementation seems to require a GUI which has some sort of "windows inside windows" approach. I know I can't get my head around how to do that here - I may be able to display each frame's content inside a virtual gadget, which would have to be dynamically added/removed when changing sites or switching tabs, but positioning them is another matter, and resizing them I doubt is possible (using standard BOOPSI/Reaction gadgets anyway... and I don't fancy writing my own gadget class for this, or at all) Currently it uses real windows for each frame, which does the job but looks a mess, especially as they don't disappear when tabbing or interact with each other on resizes. Chris
