ds_mangaman - Ultimate Nintendo DS Manga Reader GUI Update

[Hwongfish]

Hi everyone!

I’ve always felt that the Nintendo DS is criminally underrated when it comes to being a dedicated manga reader. Think about it: it has two screens built right into the form factor, a precise touchscreen, and when you rotate the console 90 degrees counter-clockwise, it perfectly mimics the ergonomics of holding a real physical tankobon (manga volume).

When held vertically, the D-pad sits perfectly on the bottom, and the shoulder keys (L/R) are in the ideal position for switching chapters. Plus, the touchscreen can be used as a dynamic radar magnifier for reading small text or inspecting details. Such interactions offer a form factor that modern smartphones just can't match.

To prove this, I built ds_mangaman — an open-source, hardware-accelerated 3x Ultra-HD comic book reader for the NDS/NDSL.


New Features & Major Update

We have completely overhauled the asset preprocessing pipeline to make building your custom manga ROMs incredibly simple. You no longer need to manually configure Python, pip, or global environment variables via the command line!

Standalone Desktop GUI Tool: The project now includes a pre-compiled main_gui.exe desktop interface. You can manage your chapters, refresh your library, and compile everything through a clean graphical layout.

Automated Toolchain Setup: The application now actively scans your local environment footprints. If the required devkitPro compilation toolchain is missing, the application will automatically pop up a guided dialog to configure and stitch the ecosystem together behind the scenes.

Automated Closed-Loop Packaging: The builder silently handles NumPy-accelerated image rotation, downscaling, hardware-native 16-bit RGB555 transcoding, and NitroFS filesystem structuring with a single click.

How to Use

Toolchain Setup: Run main_gui.exe. If you don't have devkitPro, let the app guide you through the setup (make sure to keep the mandatory default installation path: C:\devkitPro).

Import Assets: Click Import in the GUI to open assets/jpg_comic/. Create subfolders named with 4-digit integers for your chapters (e.g., 0010 for Chapter 1) and drop your sequential images (.jpg, .png, .webp) inside.

Generate ROM: Hit Refresh in the GUI to view your chapters, select the ones you want to package, and click Gen ROM. Your finished .nds file will be generated instantly in the build/ folder, ready for your flashcard or emulator!

Note: The underlying GNU make toolchain cannot handle directory paths containing spaces. Ensure your root project folder is placed in a clean directory path like C:\ds_mangaman\ or D:\ds_mangaman\.

GitHub Repository: https://github.com/hwfish-error408/ds-mangaman
GitHub Release & Binary Download: https://github.com/hwfish-error408/ds-mangaman/releases

 

[Nikokaro]

Hi. Didn't you already start another thread about this? Anyway, I had a question for you. If I understood correctly, we have to build a new .nds file containing your software and a manga every time. Wasn't it possible to have just one .nds file with your software, that could read manga in PDF or CBZ format directly from the flashcard? That would have been more convenient, in my opinion.
Anyway, thanks for this interesting software.

 

[Egoistamamono]

Waaa still need DKP. I messed up with DKP installation because i downgraded it before and can't download it anymore now.

 

[Hwongfish]

Hi. Didn't you already start another thread about this? Anyway, I had a question for you. If I understood correctly, we have to build a new .nds file containing your software and a manga every time. Wasn't it possible to have just one .nds file with your software, that could read manga in PDF or CBZ format directly from the flashcard? That would have been more convenient, in my opinion.
Anyway, thanks for this interesting software.

first of all, sorry for over-occupying community resources by sending a new thread, I am pretty selfish i admit that, if you know me in person you will know how asshole i am.

Anyway, answering you question: yes I can and probably will. Giving that the old media players homebrew does not support pico flashcart, doing this might bring more attention. However, i personally prefer the create individual .nds way, here's why:
1. the program size (or empty .nds size without any .bin images included) is only 24kb, meaning that multiple .nds file takes only minimal storage of your falshcart.
2. one manga shows up like one app in your flashcart interface, once you open it, you dont need to browse your flash cart before selecting your target manga.
3. the core program does not rely on the flashcart file system, meaning that you can use the same .nds on pico, r4, or even the authentic cart if you know how
Afterall, the main reason is that there's multiple flashcart systems in the market today. I am lazy and assume users are also too lazy to select the flashcart system AND version before generating .nds. Yes, VERSION MATTERS, if you buy a pico flashcart on aliexpress, they sometimes come with an old version of pico firmware.

Post automatically merged: Today at 3:41 AM

Waaa still need DKP. I messed up with DKP installation because i downgraded it before and can't download it anymore now.

oh yeah i can fix that, i can put the devkit in the release pack

update: after seeing reviews on reddit, i plan to switch to blocksds, which is easier and more light weight comparing to dkp. I learned nds dev from the blocksds doc, i switched only because my teammate in a game jam only knows dkp

 

[Egoistamamono]

first of all, sorry for over-occupying community resources by sending a new thread, I am pretty selfish i admit that, if you know me in person you will know how asshole i am.

Anyway, answering you question: yes I can and probably will. Giving that the old media players homebrew does not support pico flashcart, doing this might bring more attention. However, i personally prefer the create individual .nds way, here's why:
1. the program size (or empty .nds size without any .bin images included) is only 24kb, meaning that multiple .nds file takes only minimal storage of your falshcart.
2. one manga shows up like one app in your flashcart interface, once you open it, you dont need to browse your flash cart before selecting your target manga.
3. the core program does not rely on the flashcart file system, meaning that you can use the same .nds on pico, r4, or even the authentic cart if you know how
Afterall, the main reason is that there's multiple flashcart systems in the market today. I am lazy and assume users are also too lazy to select the flashcart system AND version before generating .nds. Yes, VERSION MATTERS, if you buy a pico flashcart on aliexpress, they sometimes come with an old version of pico firmware.

Post automatically merged: Today at 3:41 AM

oh yeah i can fix that, i can put the devkit in the release pack

update: after seeing reviews on reddit, i plan to switch to blocksds, which is easier and more light weight comparing to dkp. I learned nds dev from the blocksds doc, i switched only because my teammate in a game jam only knows dkp

Yeah, that was me to haha...nice pick and good luck ~