I'm operating under the assumption that Hyperspin and Hyperlaunch now use different xmls for their systems list.*
So I posted this on the HS forum here, but the more I thought about it, the more I think it could be viable addition to HyperLaunch itself. The idea is that like me, you may want to use HyperlaunchHQ itself as a front end, while also maintaining the front end of your choice. The benefit is that HLHQ doesn't use menus driven by media etc, so for systems that may not be supported by your front end, HLHQ is a great alternative with a uniform look (I mean making a logo and a little icon can't be too hard, compared to making wheels vids etc).
Ultimately, personally, I want to set up every system I possibly can in Hyperlaunch but not necessarily in my main front end. I'm moving, with the help of Craiganderson, into more obscure systems, etc. But I don't necessarily want to display those systems in Hyperspin. Anyway I just thought it would be cool to have HL be able to essentially control what displayed on your main menu xmls for various front ends. I don't know if all front ends use an XML like Hyperspin's, but it's just a suggestion.
I know it's probably better to handle this particular task on the front end side, and it can't be too difficult to make a third party app to do it, but I think it also might have a place in Hyperlaunch.
Thanks for reading,
Walter
So I posted this on the HS forum here, but the more I thought about it, the more I think it could be viable addition to HyperLaunch itself. The idea is that like me, you may want to use HyperlaunchHQ itself as a front end, while also maintaining the front end of your choice. The benefit is that HLHQ doesn't use menus driven by media etc, so for systems that may not be supported by your front end, HLHQ is a great alternative with a uniform look (I mean making a logo and a little icon can't be too hard, compared to making wheels vids etc).
Ultimately, personally, I want to set up every system I possibly can in Hyperlaunch but not necessarily in my main front end. I'm moving, with the help of Craiganderson, into more obscure systems, etc. But I don't necessarily want to display those systems in Hyperspin. Anyway I just thought it would be cool to have HL be able to essentially control what displayed on your main menu xmls for various front ends. I don't know if all front ends use an XML like Hyperspin's, but it's just a suggestion.
I know it's probably better to handle this particular task on the front end side, and it can't be too difficult to make a third party app to do it, but I think it also might have a place in Hyperlaunch.
Thanks for reading,
Walter
Last edited: