Bob wrote:
When I moved to abandon my own use of frames last year it was a big step. But I'll certainly never go back. Note that there is still need of <iframe>s, which allow loading of an independent file into a "subsection" of a page. But now I hide those and only use them for data transfer between server and client.
By all means use iFrames if they are the best solution to your problem and (not unreasonably) you don't intend to support NS 4.x. The occasional use is certainly less constraining than having to support an all-frame site. However I can't see how iFrames have any superiority over regular Frames in terms of web semantics (or whatever you call it). They both involve reference to an external page which renders pages with them difficult or impossible to use by command-line neanderths, people with screen readers, and software designed to repurpose the content as xml (As I said before, these people/machines are not the target audience of molecular graphics sites.)
David ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Jmol-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-users
