Is there any way to integrate an flash mp3 player into a html site where an reload wouldn't stop music playing or make it start from beginning.
I wouldn't want to use ajax for the rest of the site cause it's not SEO friendly, and also pop-ups are not a good solution cause every browser nowdays blocks them.
AJAX can be made SEO friendly as long as you create distinct urls for the pages you are pulling in. One solution I have seen to this is to use a pop up for the player, and they are easily unblocked.
without pop-ups, ajax, or a full flash site, there is no way to prevent this.
You could have a container page that plays the MP3, and contains a 100% wide, 100% high IFRAME that embeds the actual site. However, this has numerous SEO and usability implications that you can look up under the keyword of "frames."
You could use frames. Put the player in a frame of its own and only change the other(s). But I think a reload would still reload all the frames unless you loaded the page then redirected so that clicking the reload button in the browser only reloaded the redirected page.
You're going to jump through some hoops and have to do some things that are not SEO friendly to get this to work. If you get it to work at all.
Related
My basic problem: Having an html5 video (or else, just needs to be a video) played in a loop on an iPad Device. As soon as someone touches it, an InVision Prototype should be displayed.
In addition the loading time of the InVision Prototype should be as fast as possible (in the best case the user does not even recognize it's InVision).
What i learned so far:
InVision does not allow Videos.
Loading InVision in an iFrame and displaying the Video above it until it was clicked, does not work out, since InVision seems to forcibly forward the user within the prototype which leads to forwarding the top level navigation (so the browser displaying the html file with the video and the iFrame).
Using the sandbox attribute to prohibit forwarding works out - but results in the prototype not working anymore. (Loading won't complete).
Just forwarding the User to InVision as soon as the Video is clicked works out - but then the prototype is loaded which takes at least around 20s, crushing the users experience.
Besides the obvious of "not using InVision" any clever hacks out there?
I just recreated a prototype with roundabout 100 screens in Proto.io, having the video in front. Works like a charm.
Is there any way to create a frame that loads a website other than using iFrame?
Picture this: Me, having a website and wanting to frame a blog into it, although when I use iframe the website displays correctly (for most of the part) but the links within the iframe website don't work.
I've seen many fixes although none have worked for me thus far, I'd greatly appreciate as much help as I may gain. Thank you to anyone who answers correctly!
There's a frame HTML tag, but is deprecated under HTML5 and works almost the same as iframe. The only difference is that a frame divides the entire window and an iframe is an inline frame.
So, no, the only way is using iframes. You have to correct your blog to work with iframes (If you want).
If you don't own the iframed blog, then using iframes is not a good way to work because, for example, you don't know if they are going to add iframe breaker codes in the future, so the best way is to add a link to open in a new window/tab.
I am creating a HTML5 visualizer for a splash page. In my original briefing I was asked to make the page pick up whatever audio was coming out of the pc's speakers. My first question is, is this possible? I am assuming it that it is not as the ability to pick up microphone input seems to have only just been implemented.
My second option was to get the page to pick up whatever audio the browser was kicking out (on other tabs). Does anyone know how this might be done on, lets say, chrome?
I hope this is a good question. I am very new to website development.
What is the use of the <bgsound> tag in HTML?
It is a non-standard tag which instructs the browser to load and play a sound file (famously, at least in the mid-90's, a MIDI file) while the user is browsing your site.
Except in a few very special cases, the real purpose is to time how fast the user can find his browser's "close" or "back" button. Seriously, don't use it, on almost every site sound is unwelcome.
If you do decide to use it, you'll want to consider marquee and blink as well. Also an animated-GIF construction worker "under construction" sign and purple text on a dark green background.
If you want to give the user an option of playing music on your site (e.g., because its a music site), I suggest that a flash widget is your best bet. Depending on the site, it may or may not be appropriate to auto-play the music. Alternatively, you could use the new HTML5 audio element (though support is lacking).
update: As pointed out by Adam Brown, HTML5 audio is now supported almost everywhere and should be used instead of Flash.
tells the browser to play a particular sound when the page is loaded.
link:
http://www.htmlcodetutorial.com/sounds/sounds_famsupp_18.html
The other answers are all wrong. This tag is used to get the user to close the page instantly.
A "background sound" is a sound that starts to play automatically when the web page is loaded.
This attribute is used to define what the source of the sound is. Insert the file name and file path if necessary here.
http://www.abiglime.com/webmaster/reference/html/tags/bgsound.htm
If I embed a video demonstrating my application in my home page, will it slow down the page to a considerable amount?
I tried, and checked that it takes almost 1 sec, to load the preview of the video.
And as the video stream will not be downloaded until, the video is clicked, the total video do not have to get downloaded.
Is it recommended to embed a video in the home page? Or should I just keep it in a different page and put a link in the home page.
If you are embedding a flash flv video then yes, it could slow the page load down. This is because the page will need to load the flash plugin in order to get the content size, etc and render the initial frame etc.
Doesn't mean it's a bad thing though. It won't be an extreme slowdown (flash is pretty highly optimised nowadays), so instead evaluate on how it looks rather than performance unless you are trying to eke out every dreg of performance on your page load :)
Here one way you can have your cake and eat it too:
Don't put the flash player on the page that you will load by default....
Put in an image that looks like the player instead (it should be much lighter) .
If / when your user clicks on the player image, load in the flash player and play.
Every object you add to a page can slow down the page's loading time. In general don't include anything if the load time isn't worth the added benefit of having that item.
That being said, you can optimize the page by doing some tricks so that the page renders and THEN the flash video loads. You could pre-generate a thumbnail of the flash player/video and put it on the page in the same place as the video, then on page load use javascript (jquery: $(document).ready()) to create the flash object. This may improve the perceived performance. Even better, you could defer loading the video until the user clicks a button or something.
Everything you embed will slow down the page's initial load.
You have several options: (A) embed the video in its native format (mpeg, avi, etc) or (B) convert it into Flash. A good thing about flash is that it's near universal and highly optimized, so loading the flash plugin takes little time.
The whole video needn't load for the page to finish loading (only the player), so if we're just talking about 1 video, it would make sense to embed it in the page so as to provide a better user experience.
Have a look at both of Mr. Shiny and New's points. They're valid as well.