mirror of
https://github.com/djhackersdev/bemanitools.git
synced 2026-04-08 18:25:04 -05:00
ee8f2a05fe
The previous implementation just went along with how AVS property models and deals with attributes: attributes are just another type of node that follow the same rules as standard xml nodes/elements. This design already showed several flaws in application as these nodes always had to be referred to with an appended ‘@‘ on the attribute keys. This was mitigated with an “ext” function that hides the whole details of “find the attribute node before reading the attribute” steps. By adding another property_node implementation with mxml, the AVS style abstract layer showed incompatibilities with the “an attribute is a node” approach. mxml doesn’t treat them as a type of node and just addresses them directly using their keys. This is lot simpler and aligns with how handling attribute is done throughout the code thus far. Refactor the property_node interface and the current AVS implementation to also adapt this. Hide the detail that AVS treats attributes as nodes and also the whole “append @“ to the keys notation. |
||
|---|---|---|
| .. | ||
| api | ||
| imports | ||
| main | ||
| sdk | ||
| test | ||