Oh, I wasn't aware that the PS Button wasn't available; but L + R + Start sounds perfect.hgoel0974 wrote:I think L+R+Start should be easy enough to press?
Also the PS Button is not accessible from PSM
Advertising
Oh, I wasn't aware that the PS Button wasn't available; but L + R + Start sounds perfect.hgoel0974 wrote:I think L+R+Start should be easy enough to press?
Also the PS Button is not accessible from PSM
True, True, I might be the only person who finds it an annoyance, and hey someone might use it better than the game programmers, maybe multi touch hotkeys or something. If you guys need graphics I might be able to help. Especially 3D graphics.hgoel0974 wrote:The problem with that however is that you can't just assume that no one else will use the rear touchpad. Thanks for the suggestion though.
Agreed, its better to not use a custom format. Stick to what we already have to ensure max compatibility for the future, a lot less headaches.hgoel0974 wrote:I believe this makes sense, we should aim for as much compatibility with the existing systems as possible. I suppose that takes care of most of the problems, while keeping compatibility in mind, I suppose it'd be better to use a vblank hook instead of custom function calls. So that leaves the exit comboyifanlu wrote:There's a reason UVL was designed to load SCE ELFs rather than a custom executable format (like .3dsx). That's because in theory any homebrew that UVL can run will also be loadable by the system loader. That means when we get a kernel exploit, there doesn't need to be any recompilation.
So if we wish to keep this theme, the format should also fit with sony's packaging format. That means LiveArea XML for everything. I don't want to use a custom format because it would go unused as soon as a kernel exploit comes out. But if we repurpose existing LiveArea and SFO stuff in a way where after we get a CFW all you have to do is install the homebrew with package installer (sig patched), that would be the best route.
Well, but isn't it confusing to change the exit combo by homebrews? The button combo is a way to force to exit when homebrews get stuck.hgoel0974 wrote:As for the exit combo stuff, I've decided that at least for my loader, the loader will be responsible for the exit checking but the menu/homebrew will have the ability to set the exit combo. Of course this introduces a custom import but since these aren't critical functions that would break a homebrew, it won't matter if they don't get resolved when eventually a kernel exploit is discovered and released.
Well, the homebrew doesn't have to change it, in fact I wouldn't recommend it, but the menu (which is also just a homebrew) can change it, allowing the user to configure that themselves. Since there seems to be confusion about this, the menu is treated as just like any other homebrew, it is NOT built into the loader.173210 wrote:Well, but isn't it confusing to change the exit combo by homebrews? The button combo is a way to force to exit when homebrews get stuck.hgoel0974 wrote:As for the exit combo stuff, I've decided that at least for my loader, the loader will be responsible for the exit checking but the menu/homebrew will have the ability to set the exit combo. Of course this introduces a custom import but since these aren't critical functions that would break a homebrew, it won't matter if they don't get resolved when eventually a kernel exploit is discovered and released.
For the info format, we've agreed on the pkg layout, for the memory management, it's true that it doesn't take long to load a menu again, but there's the problem of having that mix well with the multitasking, the menu should be able to retain its state and be immediately available for the multitasking to be clean. I know multitasking is hard work, but I'm figuring it out, it'd be easier if I could find info for pss_suspend_thread since there doesn't appear to be any other function to suspend a thread AFAIK.173210 wrote:* Homebrew information format
http://vitadevwiki.com/index.php?title=Packages_(.PKG)
Or just you can use only ELF.
* Path formats
Good.
* Function calls
Multitasking is hard work. Can you implement it?
* Exiting
Well, button combination should be an option. VHL can have settings with JSON.
* Memory Management
It doesn't take long to load menu again, at least on HBL. I don't think you have to concern that.
However, you are going to implement multitasking?
So menu will load something like hblconf.txt and change the button combination, right?hgoel0974 wrote:Well, the homebrew doesn't have to change it, in fact I wouldn't recommend it, but the menu (which is also just a homebrew) can change it, allowing the user to configure that themselves. Since there seems to be confusion about this, the menu is treated as just like any other homebrew, it is NOT built into the loader.173210 wrote:Well, but isn't it confusing to change the exit combo by homebrews? The button combo is a way to force to exit when homebrews get stuck.hgoel0974 wrote:As for the exit combo stuff, I've decided that at least for my loader, the loader will be responsible for the exit checking but the menu/homebrew will have the ability to set the exit combo. Of course this introduces a custom import but since these aren't critical functions that would break a homebrew, it won't matter if they don't get resolved when eventually a kernel exploit is discovered and released.