• 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: user info
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: user info


  • Subject: Re: user info
  • From: Mike Schrag <email@hidden>
  • Date: Thu, 13 Jul 2006 12:41:41 -0400

This is re: EOModeler replacement, if it wasn't clear. I went ahead and made it so it should preserve non-primitive types, but I don't let you edit them for right now. I'll probably do it like real EOModeler does where you edit the property-list-serialized format.

ms

On Jul 13, 2006, at 12:30 PM, Gary Teter wrote:

It's standard practice in WireHose applications to put arrays in userinfo entries in your eomodel. I don't see why dictionaries would be a problem, either. You just have to know what kind of object to cast to when you call entity.userInfo().objectForKey("foo").

On Jul 13, 2006, at 12:48 AM, Mike Schrag wrote:

Does anyone put complex types as values in User Info (complex type = something other than instanceof Number/Boolean/String)? Specifically lists or dictionaries would be the likely possibility?

ms

-- WireHose: Smart metadata and personalization for WebObjects. http://www.wirehose.com/


_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >user info (From: Mike Schrag <email@hidden>)
 >Re: user info (From: Gary Teter <email@hidden>)

  • Prev by Date: Re: SSL / Form Help Please?
  • Next by Date: Re: How to have Xcode open .eomodeld directories with EOModeler
  • Previous by thread: Re: user info
  • Next by thread: Re: user info
  • Index(es):
    • Date
    • Thread