You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 5, 2020. It is now read-only.
We need a clever way to define types. Currently we define "apbs_atom", which is really just a PDBx atom with the addition of charge and radius, in the Controller init method. Additionally we support a plugin defining a new type by having a magic define_types method. Neither of these things is entirely satisfying because they lack transparency, as well as consistency. Consistency is lacking because of the dissimilar ways that the framework defines types vs the plugins. It's not transparent because it's not clear where a given type is defined, nor is it clear which types are defined.
We need a clever way to define types. Currently we define "apbs_atom", which is really just a PDBx atom with the addition of charge and radius, in the Controller init method. Additionally we support a plugin defining a new type by having a magic
define_typesmethod. Neither of these things is entirely satisfying because they lack transparency, as well as consistency. Consistency is lacking because of the dissimilar ways that the framework defines types vs the plugins. It's not transparent because it's not clear where a given type is defined, nor is it clear which types are defined.