Right now the WAD loader knows exactly which derived classes to instantiate when it reads a WAD file. In the long run, I don't want the user to have to write deserialization code for each class, but for now, can we ask them to do it but give them a way to arbitrarily extend the factory functionality for the WAD Loader?
Right now the WAD loader knows exactly which derived classes to instantiate when it reads a WAD file. In the long run, I don't want the user to have to write deserialization code for each class, but for now, can we ask them to do it but give them a way to arbitrarily extend the factory functionality for the WAD Loader?