FROM : I. Savant
DATE : Mon Nov 26 21:35:56 2007
> I disagree with the previous answers. I see no problem with 31 subviews from a performance perspective. Things like cursor rects and event handling will be nicer and simpler if each "day" is its own view.
I disagree with your disagreement and raise you a pedantic correction. ;-)
First, the pedantic correction. Scott Anguish enjoyed correcting me
by saying that's not really Core Animation but layer backed views. I
countered with: "... which in turn uses Core Animation, hence
'CABasicAnimation' ..." but he has yet to recant.
Your move, Anguish.
< To all but Scott who knows better, that is, of course, a joke. ;-) >
I still tend to think of the calendar itself as a control and the
days as cells. There's nothing stopping you from using
"core-layer-animated-backed-views" ( :-P ) in the scenarios you've
suggested, but I can't disagree that it'd be easier to use a prototype
view and perhaps an NSCollectionView.
The drag and drop scenario, however, really wouldn't be any 'easier'
just because they're separate views. It's "dragged from another view
into myself and this is the day I represent" versus "dragged from
another day's rect into this day's rect amongst the days I represent".
Either way works just fine.
--
I.S.
... who - in all seriousness - bows to the far-superior skills of
those he's currently harassing ...
DATE : Mon Nov 26 21:35:56 2007
> I disagree with the previous answers. I see no problem with 31 subviews from a performance perspective. Things like cursor rects and event handling will be nicer and simpler if each "day" is its own view.
I disagree with your disagreement and raise you a pedantic correction. ;-)
First, the pedantic correction. Scott Anguish enjoyed correcting me
by saying that's not really Core Animation but layer backed views. I
countered with: "... which in turn uses Core Animation, hence
'CABasicAnimation' ..." but he has yet to recant.
Your move, Anguish.
< To all but Scott who knows better, that is, of course, a joke. ;-) >
I still tend to think of the calendar itself as a control and the
days as cells. There's nothing stopping you from using
"core-layer-animated-backed-views" ( :-P ) in the scenarios you've
suggested, but I can't disagree that it'd be easier to use a prototype
view and perhaps an NSCollectionView.
The drag and drop scenario, however, really wouldn't be any 'easier'
just because they're separate views. It's "dragged from another view
into myself and this is the day I represent" versus "dragged from
another day's rect into this day's rect amongst the days I represent".
Either way works just fine.
--
I.S.
... who - in all seriousness - bows to the far-superior skills of
those he's currently harassing ...






Cocoa mail archive

