I see things a bit differently than you. Basic actually has two different “parts”. One is the Components (i.e. Label, List, Dropdown, etc.) and the other is “core” functionality and optional functionality (i.e. UIBase, Group, many beads, views etc.)
The first part of Basic is not really core, but the second part is. I don’t see the benefit of pulling out the “core” part of Basic and put it into the Core library. I definitely don’t see a benefit to duplicating these core pieces in other component sets. My $0.02, Harbs > On May 9, 2018, at 7:15 PM, Carlos Rovira <[email protected]> wrote: > > Regarding the motivations: Royale has many libraries that are somewhat the > core. One is Core (of course) and then others orbit but are optional > (Collections, Binding, Network,...) depending of your needs you link one or > another. > > Then we have ui sets (Basic, Jewel, MDL, CreateJS, Flat,...). Until now all > sets was Basic dependent.
