Currently, the things we need to decide on:
- Homebrew information format:
- how should the homebrew name and metadata be stored? (XML, PARAM.SFO etc)
- package format, PBP was nice, but on the Vita it might be more convenient to go with Zip compressed archives
- icon resolution, the usual one icon and one background image? background image at native resolution, icon at 256x256 for now? (if we use zip, this should be extensible)
- Path formats
- PSM and Unity PSM have different root paths
- VHL can be made to hook functions that take paths and translate the path correctly
- PSM has a 6 directory depth limitation, although this can likely be bypassed using certain methods
- two folders in /Documents/ PLUGINS and APPS
- PLUGINS contains all plugins along with plugin configurations
- APPS contains a folder for each homebrew along with the homebrew inside
- MENU.VELF is stored at /Documents/ for the menu
- Function calls
- VHL has WIP multitasking support
- We don't know of any functions to suspend other threads
- a call to VHL once per loop in the application event loop would allow VHL to automatically suspend and even exit the homebrew if required, another option would be to have VHL hook Vblank
- Exiting - should homebrew be required to have an exit option of their own so execution returns to the menu? or should there be a VHBL like system where a thread constantly checks for a key combination, this ties in directly with the requirement to make calls to VHL
- Memory management
- VHL will eventually automatically handle memory management, but if the menu isn't exited, it'll take up extra resources, however if it's unloaded, we can't have a clean and fast means of pausing a homebrew and returning to the menu.
It's very likely I've missed some critical things, so please feel free to let me know if there's anything else we need to decide on.
// smithsf0x
// Sticky Thread
Advertising