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
After discussions at UCL with @robertcannon, we have decided that ComponentReferences are just adding entropy to LEMS, since all the cases where they are used can be straightforwardly implemented using Child(ren)s. Relates to #32.
The text was updated successfully, but these errors were encountered:
With this decision in mind, it seems that all attributes in a <Component> definition should correspond to parameter values, isn't that right @robertcannon ? That will greatly simplify our lives, as we can bind the "any" attributes to something else than String.
Yes, I think you're right, for the free ones. You've still got "type" and "extends" and possibly others with fixed names in future, but for normal components, the others would just set parameter values.
Though they won't necessarily all be physical quantities - the network stuff has xpath-like node selectors attribute values too.
After discussions at UCL with @robertcannon, we have decided that ComponentReferences are just adding entropy to LEMS, since all the cases where they are used can be straightforwardly implemented using Child(ren)s. Relates to #32.
The text was updated successfully, but these errors were encountered: