Before I begin, let me just say YES, I used AI in the development of this application. No, I will not go into detail (except for the fact that it was directly responsible for the Spanish language file); I don't feel the need to defend or debate that decision. Use it or not, entirely up to you.
What it does:
Click Here For The Repo.
I'd like to introduce my first Switch homebrew project, GarageNX (so titled because it aims to "handle everything under the hood" of the Switch, so to speak). This is my attempt to replicate the functionality of DBI. Yes, there are other title management software applications out there, but many seem to appreciate DBI and as such, I figured it was the best template to work from.
What it does:
- File browser - ranger-style three-column navigation with split-pane copy/move, text and hex viewers (paged for large files), and archive peeking (NSP/XCI content listing).
- Network browser - navigate SMB/NFS shares using the same browser interface.
- Title management - enumerate installed titles; uninstall, move between SD and NAND, reset version requirements, edit metadata, dump, and repack.
- Maintenance tools - clean orphaned records, old updates, placeholders, unused tickets, firmware dumping, version manifests.
- System information - comprehensive firmware, CFW, hardware, battery, and activity reporting.
- Connectivity - USB-MTP, FTP server, and HTTP server with QR-code network sharing.
- Full localization - drop-in language files; no language is second-class.
- Create forwarders - Sphaira handles this functionality well, no need to replicate.
- Launch Homebrew - Once again, Sphaira is the standard here.
- Browse HTTP/FTP/GitHub - saw no need for it. If there is demand, this may come in a future build.
- Look pretty - I felt no need to go overboard with a flashy UI. Plutonium has it's place, it's a wonderful framework and XorTroll is a peach for having created it. That being said, for what I'm trying to accomplish, a very basic, text based SDL2 implementation works just fine.
- Testing - I can only think of so many different ways to test, and they're not necessarily real world scenarios. That's where you come in. Please, have at it and put it through the ringer. Submit any issues to the GitHub.
- Translation - I'd prefer not to rely on AI exclusively for translation; I know it's imperfect and I'd prefer more natural language results than what an AI can look up in a dictionary or online.
- Splash - I previously had an AI generated splash that was...problematic to say the least. Would've put this project in the cross hairs of big N. I am working with an artist to come up with something more appropriate; in the meantime, there's the garish placeholder that is there now.
- Language support - as more translations are completed and verified, they will be added to the repo with haste. I don't want anyone left out in the cold on this; everyone deserves to have well-working software regardless of the language they speak.
- OPTIONAL: Themes - In the future, themes will be external files like the language files (they were at some point and, for reasons escaping me at this very moment, they were integrated into the build); see /source/ui/theme.cpp for the basics. Should be fairly simple to split it back off.
Click Here For The Repo.
Attachments
Last edited by RobZilla10001,
