Prince of Persia in JavaScript
51–60 of 237 posts
Re: Prince of Persia in JavaScript
#52Earlier quoted context omitted.
This is a constant gripe for me. If you're going to play audio on your website, you really should provide a volume control.
Why? You have global volume control, music players have it. To me it's the same as asking every website for brightness adjustment bar or font size control.
Re: Prince of Persia in JavaScript
#53Volume buttons please.
Re: Prince of Persia in JavaScript
#54Re: Prince of Persia in JavaScript
#55Earlier quoted context omitted.
The prince doesn't stop on a dime, this was a design choice. This recreated version plays the same as it did on OG hardware. If you're having difficulty, focus on holding and releasing the inputs and think of it as applying acceleration, where you want to release before you want the object to stop.
The controls are very similar to the original, however there's somethings you can't do like step then crouch.
Re: Prince of Persia in JavaScript
#56Re: Prince of Persia in JavaScript
#57Re: Prince of Persia in JavaScript
#58Earlier quoted context omitted.
Why? You have global volume control, music players have it. To me it's the same as asking every website for brightness adjustment bar or font size control.
Because we don't want to have to readjust everything else around your special snowflake site?
If it's some music/podcast isn't it more handy to have a known volume knob on that instead of finding one on every website?
I don't care about the right opinion. I'm just curious about scenarios where lack of volume control is a problem.
Re: Prince of Persia in JavaScript
#59Re: Prince of Persia in JavaScript
#60Earlier quoted context omitted.
Because we don't want to have to readjust everything else around your special snowflake site?
I mean it sincerely. Are you listening to something else while using a website with sound? I usually just pause the music. If it's some music/podcast isn't it more handy to have a known volume knob on that instead of finding one on every website? I don't care about the right opinion. I'm just curious about scenarios where lack of volume control is a problem.
I know where my computer's volume controls are - and if I have a keyboard with volume controls, that's what they work on. I almost never want to touch a specific app's or website's volume control... unless its volume is way too soft even at max system volume.
Basically, I don't need a gazillion interfaces. One suffices. Just don't go out of your way to make that generic, system-wide interface insufficient for your app and it'll be fine.