I committed the first compile-time define for proprietary player compatibility. This is buried into a .cpp file, and specific to a single feature (handling of textfields using device fonts) http://gnashdev.org/wiki/index.php/DeviceFonts#Differences_with_proprietary_player_implementation
Thinking about the general problem, we likely want a define in the config.h driving compatibility issues as a whole. The problem would be handling differences between different version of the proprietary player, and we know a few of them (no wiki page yet, but making one could be a good start). What do you think we should do when there are differences between proprietary player (pp) versions ? I guess some differences would be documented out there on the web, while some others might be just considered temporary bugs. Usually, a flash coder willing to handle such differences, has to check for precise player version (including architecture), so any 'emulation' we'd implement should be advertised with a pp-compatible version string too. Implementing multiple emulation modes would also be challenging (emulate this version on this system, that version on that system). Do we really want to go there ? Comments welcome. --strk; () ASCII Ribbon Campaign /\ Keep it simple! _______________________________________________ Gnash-dev mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnash-dev
