That said it depends on what exactly you want to do.
Frames do have their uses, but they tend to cause more problems than they solve. Often people want to use them due to a (imho) misplaced belief that users don't like scrolling the page.
OK thats cool, I think CSS seems to be popular so it must have some good uses. The main reason is to have code that is easy to manage and logical. I dont want to end up with spaghetti code or anything. I think all I want to have is a little banner staying a the top of screen, with maybe a few icons underneath (flags of Europe) which change the language dynamically.
Thats basically it.
There are websites using frames to keep playing same music (uninterrupted), by putting <bgsound> tag inside the 'menu' frame. The music just ends neatly when user closes the mother browser window.
I still can't find a non-frame alternative. Ring any bell?
Thanks foamcow. You fixed my unthoughful mistake. Yes, "put <bgsound> in frameset document". Then music is uninterrupted by whatever click (except page reload), and music ended on windows closing. Handsome.
But is background music that bad as you describled?
My experience is nicer, esp. with ligher music, e.g.
Of course, this website would be even nicer if follows your suggestion. (Now it opens a new window for almost every click, in order to continue the music i guess.)
Still, but back to our topic question: It seems FRAME is necessary here?
If I understand you correctly then yes a Frameset would allow you to play music in one frame (or the frameset document) which would be uninterupted by clicks to other pages.
I cannot condone any of this though
1. I don't like frames. They have their uses but tend to make things more complex than necessary. Also, users cannot bookmark individual pages etc. The drawbacks (and advantages) are well documented.
2. Background sound. Generally a bad thing. At least provide an option to turn it off. For instance, some users may be browsing in an office environment and find the sound obtrusive. What does the sound add to the site? Is it fundamental to the site's function or is it just "candy". Is it really necessary? Music has to be VERY good to warrant leaving it playing in the background.
3. Opening each click in a new window. Poor accessibility practice. This can be confusing for some users, as well as potentially being resource intensive on the client machine.
It makes navigation with the browser's back button impossible.
Sorry
I guess, if you must have music and you wish it to be uniterupted then your best bet is to use a frameset. But I would question why it's necessary.. unless you are a composer perhaps.
That site you linked to didn't load correctly. The Java App didn't load and I didn't hear any music.
If you want to provide background sound let the users turn it on. Let the click a button that pops up a small "_blank" window that then has the background sound playing. It is now seperate from the navigation window and can be closed when they nolonger want the music.
The link i referred does work here (Hong Kong, IE6). Interesting if can't reach some countries (U.S.?)
Recently i saw a few elegant websites done without Frame, not even tables (in a general sense 'not so boxy'). All done with css. i guess css ('box model','positioning'... to be specific) is gaining wide acceptance & browsers compatibilty.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.