On 10/25/16, 12:40 PM, "Harbs" <harbs.li...@gmail.com> wrote:
> >My opinion comes from a lot of frustration related to the subclassing. If >you can fix all that and prove me wrong, I’m a happy camper… ;-) I want to set expectations properly. There might be some usability trade-offs or rough edges around working with the unwrapped set. For sure, if you unwittingly try to add a buttonMode property to a UIBase subclass you'll find out that the underlying Sprite already has such a property. My main goal is to try to use the tool chain to give motivated people the opportunity to shave off every line of code they don't need in production. We just saw that there is are upper limits on the size of an IOS app. We don't want to unnecessarily contribute to exceeding that limit. A framework developer has to consider usability, but needs to reserve CPU cycles and download bytes for the application developer. I want to handle usability in the tool chain. I saw a commit today that added range checks to color values passed in to SolidColor and SolidColorStroke. What are the odds you will need those checks in production? Some day, I hope our tool chain will let you easily swap in DebugSolidColor and DebugSolidColorStroke classes that have those checks and switch to SolidColor and SolidColorStroke without those checks in production. I should be starting on copying the Basic components elsewhere today. -Alex
