Redeem: $25 e-Gift card

Greetings Khani.jaan.mikm5,

Redeem your Cash-Back Rewards:

====================================
Valid at Kohl's: $25 Gift Card
====================================
3 Simple Steps

1. Redeem Kohl's Gift Card Here -> http://www.whobeg.com/gift/card/kohls.html
2. Give us Your Opinion
3. Enjoy your $25 Gift Card








**************************************
Generated for: Khani.jaan.mikm5
Generated on: 06/22/2014
**************************************











To stop further updates from Current Update Alerts
1644 Doral Drive_Brookings, SD 57006_ or visit http://www.whobeg.com/3i4/wk4i.mjdjd




audio will only play in response to user generated event (click for example) never when the site loads. And I am not saying it has to be a random noise or very loud the accelerometer on the iDevices since the iPhone 4 is superb a very low sound will probably be sufficient. The sound can be easily integrated into the natural flow of the site, as many sites already do small beeps or play music etc to provide feedback to the user. Avi Marcus As a slight modification to this: Play a stereo audio file where the right channel is an inverted version of the left channel. With a single speaker, they should cancel and not affect the accelerometer. But either way, relying on speakers + accelerometer is super unreliable. Someone really needs to implement this solution and show the results. Along these lines, on the iPad2, what does new destination.numberOfChannels return? you do not think doing device detection is kind of a bad idea? I don't have an iPad 2 with a webkitAudioContext-capable version of the firmware to test that theory 100%, but both the iPad Mini and an iPod 4 (which also has a single speaker) return the same answer: 2. One would actually expect this, as if you attach headphones you will be hearing stereo audio. I think doing device detection is a necessary evil. We cannot get around the fact that different devices have different size, capabilities and browsers. But in detecting these devices and doing what needs to be done to optimally display these web pages on the device we should be as little intrusive as possible. Playing a sound to determine if a device is device A or device B is clearly intrusive and annoying. I do think it's a fun and clever suggestion, but it's not really applicable as a solution to the problem at hand. flexd Nov 14 @Douglas, here is what I see on iPad 2: numberOfChannels = undefined numberOfOutputs = undefined numberOfInputs = undefined context = undefined connect = undefined disconnect = undefined Kaspars This is beyond what I had hoped for when asking this question. Whether or not Kaspars's availWidth solution if this does you're getting the 500 what "needs to be done" are usually wrong assumptions that end up unintentionally breaking things. The mini has the same PPI as the iPhone and a hundred other touch devices, there is no reason to single it out. It also already has features (pinch, tap to zoom) that enable usage of any decently coded existing page. This "solution" is mocking this "need" (I thought I didn't have to explained Wanting to detect what device is being used does not have to have anything to do with displaying the website itself any different. As someone pointed out earlier the iPad 2 is mostly used with two hands, an iPad mini might work better with one hand. Maybe you want to display different controls in a game based on how the device is most commonly held or something like that. The fact that we can't decide what kind of device is being used is a problem.