ModelMethod naming consistency #262
Description
My preliminary though is the current implementation in #237 is best, it is effectively TypeModelMethod but we drop the Method for conciseness. In some cases e.g., ForceField() I would even want to drop Model, although I am open to putting it back in.
To the point about ModelMethodElectronic, I agree we should change it for consistency... ElectronicModel? Although, here we are talking about an abstract class I think, the shortened "natural" form is more important for the used classes IMO