Some observations:
A class in a local classpath will override a class in the SWC’s class path of the same name.
One might conclude:
- you can override a single class within a SWC with a local class with the same name and change the features of its subclasses
- you could “fix a bug” in a SWC package with the same approac
Tests to come:
- Proofs of this in action with examples
- Proofs of collisions in separate swcs that use the same class paths
- What happens when I use one version of GTween in SWC one and another in SWC two?
- Do I really need to strip all of the code out of my SWCs so I can share from more than one SWC?
- What happens when I use one version of GTween in SWC one and another in SWC two?
Advertisement
