Re: [chlor-develop] CSegment

[<chl...@li...>]

> This is the common performance-memory dilemma. As a bounding box is  
> often cheap to calculate, it's not always the best solution to keep  
> a cached boundary box. We should be able to make a choice per class  
> basis, this should not be fixed for all classes by using a base class.

I don't know how expensive exact bounding boxes are for (cubic)  
beziers to calculate. I'd say not too cheap. I don't know what you  
mean be base class. The bounding box stuff is only defined by a  
protocol.

> NSNotification,...). I don't have a problem leaving the objects  
> mutable, but in very controlled manner. Each object should be able  
> to keep its state consistent whatever changes are made. This is the  
> only way to keep the application in a consistent state as we move  
> on and the application grows.

Agreed. We should find a compromise between data exposing and an  
excessive API. We're not too far away from that.

Bye,
Lenny