Does it ever make sense to specify multiple project factories for the same file extension within a package? We have several project types for which we want to have the same file extension, though it's not clear if they will be implemented as flavors of one another. We're using MPF. A little bit of experimentation seems to indicate there's not really a notion of "priority" when opening a project file of our type in the absence of flavors. So, it has me thinking the proper design here is a single factory that uses info from the template (or project file) to choose which ProjectNode-derived class to instantiate (if, in fact, we need more than one ProjectNode-derived class).
Any advice is much appreciated.