• 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
Property List Serialization in Sketch
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Property List Serialization in Sketch


  • Subject: Property List Serialization in Sketch
  • From: Gordon Apple <email@hidden>
  • Date: Wed, 09 Jan 2008 21:52:53 -0600

    Sketch uses property list serialization rather than encodeWithCoder,
encodeObject:forKey:, etc.  Is there any particular advantage/disadvantage
to this?  Don't they ultimately do the same thing?  If it is to set up all
the KVOs, couldn't the same thing be done either way?

    I should mention that I use only one type of graphic object class for
everything, differentiated only by the content of a properties dictionary.
(In fact, now that I've done it, I don't know why I didn't just make that
class a subclass of NSMutableDictionary.)

_______________________________________________

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

  • Follow-Ups:
    • Re: Property List Serialization in Sketch
      • From: Jean-Daniel Dupas <email@hidden>
    • Re: Property List Serialization in Sketch
      • From: Jerry Krinock <email@hidden>
  • Prev by Date: Re: Daemon application with System Preferences Pane
  • Next by Date: Re: Capturing the Content of a IKImageBrowserView
  • Previous by thread: Re: Creating a Core Data App from a non Core Data Project
  • Next by thread: Re: Property List Serialization in Sketch
  • Index(es):
    • Date
    • Thread