Help
Use CSS to be honest, it's alot easier and is soo much more powerful. If you don't know it theres a really good tutorial at www.w3schools.com
Dan
Html Kicks My A**
Back to top
#17
- Member
-
- Group: Members
- Posts: 90
- Joined: 28-September 06
Posted 27 March 2007 - 07:43 AM
Nice div tricks. Whatever happened to frames?
When I first started learning html, I found lots of examples (show source) of the use of tables in what could now be called "traditional" websites. But I got really tired of seeing the header and menu (along the left) reloaded as content changed; even though the menu and header information remained exactly the same.
In the modern world -- there's certainly more than one way to skin this cat. But simply learning how to load content into one frame by specifying it in another (such as click on a menu item) might go a long way for a "traditional" looking website.
When I first started learning html, I found lots of examples (show source) of the use of tables in what could now be called "traditional" websites. But I got really tired of seeing the header and menu (along the left) reloaded as content changed; even though the menu and header information remained exactly the same.
In the modern world -- there's certainly more than one way to skin this cat. But simply learning how to load content into one frame by specifying it in another (such as click on a menu item) might go a long way for a "traditional" looking website.
This post has been edited by Roger F. Gay: 27 March 2007 - 07:46 AM
#18
- Forum Regular
-
- Group: Members
- Posts: 159
- Joined: 09-December 06
- Gender:Male
- Location:Somewhere East of Where You Are (think about it)
Posted 28 March 2007 - 12:02 PM
Roger F. Gay, on Mar 27 2007, 07:43 AM, said:
Nice div tricks. Whatever happened to frames?
When I first started learning html, I found lots of examples (show source) of the use of tables in what could now be called "traditional" websites. But I got really tired of seeing the header and menu (along the left) reloaded as content changed; even though the menu and header information remained exactly the same.
In the modern world -- there's certainly more than one way to skin this cat. But simply learning how to load content into one frame by specifying it in another (such as click on a menu item) might go a long way for a "traditional" looking website.
When I first started learning html, I found lots of examples (show source) of the use of tables in what could now be called "traditional" websites. But I got really tired of seeing the header and menu (along the left) reloaded as content changed; even though the menu and header information remained exactly the same.
In the modern world -- there's certainly more than one way to skin this cat. But simply learning how to load content into one frame by specifying it in another (such as click on a menu item) might go a long way for a "traditional" looking website.
Frames are the devil.
They're rarely used, and when they are they're done poorly - more a designer flaw, but I've never had a need to use frames since I can save space with divs or tables.
#19
- Member
-
- Group: Members
- Posts: 90
- Joined: 28-September 06
Posted 28 March 2007 - 03:03 PM
RADIUM-V Interactive, on Mar 28 2007, 03:02 PM, said:
Frames are the devil.
They're rarely used, and when they are they're done poorly - more a designer flaw, but I've never had a need to use frames since I can save space with divs or tables.
They're rarely used, and when they are they're done poorly - more a designer flaw, but I've never had a need to use frames since I can save space with divs or tables.
Could you elaborate? I've heard similar answers many times but I don't have any trouble doing a good job with frames.
I recall ... in the beginning ... frames were first supported by Microsoft. Netscapers bad-mouthed them a lot. But eventually, every browser supported frames. Possibly too late to avoid a bad reputation and the idea that .... they're just not used.
Frames also came out before many people were used to dom references. Getting / setting a variable with something like:
parent.MenuFrame.menuItem1.innerHTML
can seem a little awkward at first.
