2014-08-21, 05:57
you'll notice the only functional difference is that RetroPlayer is no longer connected to any input. I've re-written the joystick API two or three times, and the end result was never satisfactory because I couldn't separate the input from retroplayer. now, with input gone, the complexity of retroplayer is greatly reduced, leading to more maintainable code.
putting as much code as possible behind APIs is generally a good strategy. i learned this rather late in the development of retroplayer, so there are still quite a few parts that are entangled. however, looking at this diagram, i think i'm on the right track - components are finally only communicating with their API, and not with other components
putting as much code as possible behind APIs is generally a good strategy. i learned this rather late in the development of retroplayer, so there are still quite a few parts that are entangled. however, looking at this diagram, i think i'm on the right track - components are finally only communicating with their API, and not with other components