• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Group rotation
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Group rotation


  • Subject: Re: Group rotation
  • From: Graham Cox <email@hidden>
  • Date: Thu, 8 May 2008 11:06:17 +1000

I don't think it makes the more classic approach wrong - it's just another way to crack that particular nut, with its own advantages (and probably disadvantages too, like more code, more dependency between classes, possibly lower performance, I don't know - but there's no "one true way" to do it).

But either way, grouping is an exercise in concatenating transforms, basically.

I'm intrigued by your allusions to shadow drawing, I've had a lot of problems with that too - it's a performance killer.

Regarding flowing text around objects, do you have a function for breaking an arbitrary shape into a series of line rectangles that you'd be prepared to share with the world?



G.


On 8 May 2008, at 3:31 am, Gordon Apple wrote:

This is a major advantage of separating the drawing (rendering) code
from the data model instead of having objects draw themselves (not to
mention cross-platform). Our renderer object is recursive (and could be a
shared object if not for the deficiencies in shadow rendering -- a story for
another time). When we replace objects with a group object, all the
transforms automatically work. Grouping can be nested to any level. Since
we only have one "Shape" type, groups can also take on object
characteristics such as fills, content, text, etc. This especially works
well for using group objects for sophisticated text containers where text
flows around contained objects.


I know that about every example of drawing has subclassed objects that
draw themselves. IMHO, that is the wrong approach. There are just too many
advantages to separating the object rendering and making it part of the C or
V part of MVC instead of the M.



_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Re: Group rotation (From: Gordon Apple <email@hidden>)

  • Prev by Date: Re: BLOBs, MySQL, hex. Oh my
  • Next by Date: Re: BLOBs, MySQL, hex. Oh my
  • Previous by thread: Re: Group rotation
  • Next by thread: Re: Group rotation
  • Index(es):
    • Date
    • Thread