USB networking and an on-device scraper (ScreenScraper)

Offen
#135 7 Kommentare 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
25/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
cpp

Rechercherichtung

The proposal spans USB gadget modes, System Settings, a C++ ScreenScraper client, Puppy gamelist.xml support, and CI secrets; it does not name source files or tests. Start by checking the roadmap and the existing USB configuration and Puppy media handling. The author offers to split this into separate changes; done criteria for each part need to be agreed with maintainers.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

USB Networking is on the roadmap, so I tried it on my A33. The data port can become a CDC NCM network adapter, which Windows 10 and 11, macOS, Linux and Android drive with no driver to install. The PC shares its connection with it, or an Android phone does through its Ethernet tethering, with the console on the phone's OTG adapter, and udhcpc on the console takes the address. The A33's USB controller has five endpoints each way, so serial, MTP and NCM don't fit together. It works as a mode instead: Files (serial and MTP, the default) or Network (serial and NCM), switched from System Settings. In the default mode the gadget is the same as today, so it shouldn't bring back the tty trouble from #9.

With the internet there, I wrote a small scraper that runs on the console. It asks ScreenScraper about each game by its CRC and size, writes gamelist.xml plus a gamelist..xml with the descriptions in the interface's language, and downloads the picture, and a video if the user wants one, into media/. It's a small C++ program with no libraries that calls curl, so the image only gains libcurl, curl and the CA bundle, about 750 KB. Each user types their own free ScreenScraper account in System Settings. It's working on my console.

ScreenScraper also requires developer credentials for each piece of software. I asked for them for goodluckOS on their forum and they were granted: https://www.screenscraper.fr/forumsujet.php?frub=12&fsuj=26271

They go in at build time from SS_DEVID and SS_DEVPASSWORD, so the CI would need them as secrets. Would you rather request your own developer account for the project, or use the one I got?

Puppy on main only shows icons/.png, so the scraper also needs Puppy to read gamelist.xml. If you're interested, I can split it into small PRs: USB networking first, then gamelist support in Puppy, then the scraper.

Vorherrschende Sprache
C++
Sterne
54
Forks
8
Ø Merge
16 T. 19 Std.
Gemergte PRs (30 T.)
4

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus CodeZombie/goodluckOS

Alle Issues in CodeZombie/goodluckOS

Ähnliche Issues

Weitere Issues zu C++

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.