Re: Some node questions about audiogames
Re: Some node questions about audiogames 1) Make a directory2) run the followingnpm init3) run the followingnpm install howler --savenpm install webpack --savenpm install electron --saveNote: Oriol uses Percel, but I tried both and preferred Webpack.4) Write an html so that it is loaded via Electron.5) Attach script with unique name in the html.6) make js folder and put your js there.7) Set up webpack so that the build result is written to the unique name you set in the html.8) Read Howler reference for audio, add packages as new features / libraries are required, don't forget to add --save when npm installing.9) Then, it's same as developing web pages!Tips:If you have JS errors, you can press ctrl+shift+i in your electron window. The development console is less accessible than Chrome though; many buttons are unlabeled.I think this info is enough to get started.The reason I didn't use Percel was that it didn't trigger AddEventListener callbacks for some reason. Many sources say that placing the function into window. namespace solves the problem, but it didn't work here. Switching to Webpack solved everything like a charm, so I stopped pursuing. URL: https://forum.audiogames.net/post/513442/#p513442 -- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
Re: Some node questions about audiogames
Re: Some node questions about audiogames 1) Make a directory2) run the followingnpm init3) run the followingnpm install howler --savenpm install webpack --savenpm install electron --saveNote: Oriol uses Percel, but I tried both and preferred Webpack.4) Write an html so that it is loaded via Electron.5) Attach script with unique name in the html.6) make js folder and put your js there.7) Set up webpack so that the build result is written to the unique name you set in the html.8) Read Howler reference for audio, add packages as new features / libraries are required, don't forget to add --save when npm installing.9) Then, it's same as developing web pages!Tips:If you have JS errors, you can press ctrl+shift+i in your electron window. The development console is less accessible than Chrome though; many buttons are unlabeled.I think this info is enough to get started. URL: https://forum.audiogames.net/post/513442/#p513442 -- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
Re: Some node questions about audiogames
Re: Some node questions about audiogames 1) Make a directory2) run the followingnpm init3) run the followingnpm install howler --savenpm install webpack --savenpm install electron --saveNote: Oriol uses Percel, but I tried both and preferred Webpack.4) Write an html so that it is loaded via Electron.5) Attach script with unique name in the html.6) make js folder and put your js there.7) Set up webpack so that the build result is written to the unique name you set in the html.9) Read Howler reference for audio, add packages as new features / libraries are required, don't forget to add --save when npm installing.8) Then, it's same as developing web pages!Tips:If you have JS errors, you can press ctrl+shift+i in your electron window. The development console is less accessible than Chrome though; many buttons are unlabeled.I think this info is enough to get started. URL: https://forum.audiogames.net/post/513442/#p513442 -- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
Re: Some node questions about audiogames
Re: Some node questions about audiogames Hi.I need to put that guide again.anyway, if you are able to get my tempalte to run, the rest is just your own code. Everything you need is, or should be, in the template. Whatever is not in the template, npm can provide you with it.Anyway, feel free to grab the template from my github and poke around the code. I'm sure you'll learn some _javascript_ by doing this.Make sure you get the latest version though, it's no longer on my gitlab but on gitHub, not gitlab anymorehttps://github.com/ogomez92 URL: https://forum.audiogames.net/post/513371/#p513371 -- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
Re: Some node questions about audiogames
Re: Some node questions about audiogames Hi.I need to put that guide again.anyway, if you are able to get my tempalte to run, the rest is just your own code. Everything you need is, or should be, in the template. Whatever is not in the template, npm can provide you with it.Anyway, feel free to grab the template from my github and poke around the code. I'm sure you'll learn some _javascript_ by doing this.Make sure you get the latest version though, it's no my github, not gitlab anymorehttps://github.com/ogomez92 URL: https://forum.audiogames.net/post/513371/#p513371 -- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
Re: Some node questions about audiogames
Re: Some node questions about audiogames I know orial did have a guide, but I can't find it anymore, and that's why I asked here. URL: https://forum.audiogames.net/post/513369/#p513369 -- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
Re: Some node questions about audiogames
Re: Some node questions about audiogames If you ever get it figured out, it would be nice to have a comprehensive guide on it. Nowadays everyone is kinda doing their own thing and knowledge-sharing is out the window. But I've always been interested in making audio games using _javascript_ especially with it's single-threaded nature. It would be far simpler to do it versus in a language like .NET.So once you go through your discovery process, you should really write a guide. URL: https://forum.audiogames.net/post/513348/#p513348 -- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
Re: Some node questions about audiogames
Re: Some node questions about audiogames Aria live regions should work reliably on at least NVDA and Jaws in all browsers, but you might need to set up two of them and alternate because reasons. If you package as Node it's possible to call Tolk or similar.I doubt anyone will get gamepads working reliably anytime soon, but that's more to do with gamepad APIs being a clusterfuck outside the browser in the first place.I'm moving away from the web because WebAudio sort of falls short if you try to use it in as much anger as someone who has now written 3 DSP/3D audio solutions tries to, but I've got most of a Unity-esk game engine in React and Electron that I should really open source at some point, and apart from audio it can be a nice platform. But it will take more effort than (for instance) Python, if only because async programming is challenging.And who knows, maybe Synthizer happens and compiles to webasm as well. But don't hold your breath--that's also not likely because reasons. At least, not for now. URL: https://forum.audiogames.net/post/513342/#p513342 -- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
Re: Some node questions about audiogames
Re: Some node questions about audiogames Find an HTML 5 game engine. Read about making browser games. Use Electron to package those games into downloadable apps, or read about Progressive Web Apps (PWAs) that let you ship installable web apps. Also look into pwabuilder from Microsoft for packaging on Windows 10/Xbox.The web is an interesting platform for games, but you're going to hit more corner cases and will have to do your own research. I have my Godot Asteroids shooter running in the browser, but Firefox fails to detect my gamepad. Chrome detects it fine, but the speechSynthesis API doesn't work there for some reason, despite audio/autoplay working as expected. Anyhow, I won't go into any more detail because you're going to have to become comfortable figuring out lots of this yourself, and I'm still discovering benefits and pitfalls myself. URL: https://forum.audiogames.net/post/513334/#p513334 -- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
