CyberYoshi64
commented
1 year ago It is possible, but very tedious with LiquidFenrir/bcmatools; you gotta have to stitch an XML together that makes up bclyt's. The main issue that prevented that was makerom not having support to build e-Manuals. I had to modify it to build such. Then the other issue is the setup of the CIA, it just uses a one-shot makerom to build the CIA, e-manuals and other goodies would need the main CXI to be built, then be combined as CCI/CIA
Is your feature request related to a problem? Please describe. It would be real nice if there was some usage instructions for the app itself, or at least some simple descriptions of the icons used in the Universal Updater app for 3DS. For example, what does the microSD symbol on the side of Available Downloads list element means? Does it mean it's already downloaded? Or does it mean something entirely different? There is no explanation anywhere and when I saw it first time I was honestly confused and a bit scared that if I touch it something weird and unexpected would happen. I've seen my fair share of UI designs before and one thing I learned it to never assume what something does unless there is a documentation.
What about the icons at the bottom of the selected app info? While pressing on the "post-it note" yields changelog and "picture" icon shows a screenshot, you can obviously find out by tapping on them. What about the "star"? Honestly, there is zero explanation of it and I actually only found out its purpose a minute ago by going to Search and Filters (I never had a need to use it so I never went inside, alright?). Before that I had really no idea what it does, I thought it would mark the app on the top screen with a chosen symbol, but nope.
Describe the solution you'd like: A couple of screenshots on a github/website with descriptions of what each icon does or represent would be great. This would also help those who are not as savvy with computers. An actual usage manual would require more effort, but would be ideal.
Describe alternatives you've considered: Do nothing, just let users figure it all out themselves.
If there is an actual documentation then I must have missed it and I'll admit to being a dimwit if there is one.