KJThaDon said:
mrmcpowned said:
Well, as I have no PS4 controller to test with, my answers on that are of a theoretical nature. As for the PS4 image, yes, that's part of a list of controller faces I'll be making for the viewer. As I'm currently a student, I don't have as much time to be rigorously working on this, so I work on the controller faces in my off time.
No problem, thanks for taking the time to look at it. Everything works as the 360 controller except the "middle" and "touchpad" buttons. Would you be willing to make this open source so we can add to it?
I have web development and programming knowledge and also Photoshop. I can produce a ps4 controller if needed. I am just not sure how you have it setup.
Thanks!
Well, the Guide/PS buttons and touchpad as of now will not work due to the constraints of the gamepad API. Whenever the W3C decides to update said API, and when browsers begin to push that implementation, I'll be able to look into it. Though, to be honest, I don't see the Guide/PS buttons getting any support, since if they were of importance, there'd be data for it already.
I appear to have been wrong. According to the W3Cs documentation, the
guide/PS button is mapped to button 16. I'll have to do some minor css/html tweaking to have that show. The touchpad is still pretty up in the air as I'm not sure how the gamepad API will be handling that, if it the W3C ever decides to that is.
Edit: Seems that's the working draft of the gamepad API, so as of now, there is no button 16, but there will be.
As for the open source part, the source is in fact "open", I just don't have it uploaded to a repository anywhere. Any web scraper will do if you're looking to download the Gamepad Viewer for local editing and whatnot.
For the code setup, a quick view through the source and CSS files should give you a gist of what I've been doing. Using chrome's dev tools helps as well; it's what I use when fine tuning the asset placement.