USB networking and an on-device scraper (ScreenScraper)

Ouverte
#135 7 commentaires 1 réaction 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
cpp

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
C++
Étoiles
54
Forks
8
Merge moyen
16 j 19 h
PR mergées (30 j)
4

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de CodeZombie/goodluckOS

Toutes les issues de CodeZombie/goodluckOS

Issues similaires

Plus d'issues C++

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.