2015-04-17, 11:37
Thanks for the comprehensiv answer.
Im yet more a coder than a designer so i dont think im experienced enough to answer on programm structure. But! To me, from a practical point, a single resource addon (one for all plattforms, one for controller) sounds better. The downside maybe that its not that modular and easy to extent.
Anyway, so you want me to help with the platform schema? Coding-wise or just information wise?
Your list of resources seems pretty good already, I could fill your PlatformInfo struct etc..
One question though, shouldnt the platform ID mapping be part of the scraper? Or do you want to hardcode it in the core?
Im yet more a coder than a designer so i dont think im experienced enough to answer on programm structure. But! To me, from a practical point, a single resource addon (one for all plattforms, one for controller) sounds better. The downside maybe that its not that modular and easy to extent.
Anyway, so you want me to help with the platform schema? Coding-wise or just information wise?
Your list of resources seems pretty good already, I could fill your PlatformInfo struct etc..
One question though, shouldnt the platform ID mapping be part of the scraper? Or do you want to hardcode it in the core?