From: Daniel R. <zup...@ya...> - 2000-10-24 01:53:58
|
--- Eric GAUDET <eg...@in...> wrote: > Don't render frames embeding DwPages in DwPages, but > create an actual browser page for each frame of the > frameset, with the correct width and height. The > user can then place the frames as he wants without > being bugged with having to read a page in a tiny > window. As I think about this, this sounds like a neat approach for re-sizable frames. But bear in mind that not all frames are re-sizable. We'll need to handle both re-sizable AND non-re-sizable frames, IMHO. > We'll also need to add an identifier for the > frameset (say a hash of the url ?), in case the same > target names are used in different framesets. That > doesn't seem pose any problem. Actually, would it not be easier if we simply embedded the DwPages within some master widget that contained the master URL and the master frameset? Also, another problem will surface in the course of this: How on earth do we plan to handle bookmarking, and back/forward buttons for frames? Last time I checked, the W3C HTML specs generally seemed to admit that this was a very messy situation in HTML. In Netscape, they had a HECK of a time with this. Bookmarking was impossible, and back/forward had to be given an ugly hack to handle frames, originally. In this course of thought, yet another thought has occured to me: With so many different languages/protocols (http, ftp, html, xml, xslt, css, JavaScript, etc.), why not make Dillo more generic and modular by breaking the HTML support out into a plugin? Speaking of which, BTW, whatever became of the FTP plugin? ===== Is your JavaScript ready for Nav5 and IE5? Get the latest JavaScript client sniffer at http://developer.netscape.com/docs/examples/javascript/browser_type.html Sincerely, Daniel e-mail: zup...@pe... __________________________________________________ Do You Yahoo!? Yahoo! Messenger - Talk while you surf! It's FREE. http://im.yahoo.com/ |