setFrame:method will call the
setFrameSize:method. The later will call
setFrame:on all it's subviews. It will travel down the view hierarchy on all the subviews. Each
setFrame:method will update the tracking areas. Each update on the tracking areas will travel down the view hierarchy on all the subviews. So the tracking areas will be updated many many times.
CPViewand want (initially) to edit/test in an existing app without recompiling Cappuccino with every change. In the past I’ve simply imported an app-local version of the Cappuccino file. Is it possible to use an app-local version which contains only the additions/changes (
CPViewis quite large)?
NSViewvs Cappuccino? There was a discussion some time ago but I don’t remember the details. The SourceList framework I’m porting uses
NSCelland associated compositing methods/constants which don’t seem to be available in Cappuccino. I had hoped to avoid grokking the code completely from entry point onwards but that is what I’m faced with doing now