Yeah, displaying it is pretty straightforward. If you look at real
EOModeler, it lets you edit the .plist-form of complex types. So if
you have an NSDictionary as a value, you get "{ key = "value"; key2 =
"value2"; }" as your value, which you can read and write. Probably
the way I will go as well in the mid term. For now, I disable
editing on non-string keys.
ms
On Jul 13, 2006, at 4:46 PM, Ken Anderson wrote:
Mike,
What would change? Are you concerned about displaying the value,
or capturing it? To display, toString() should always work. For
input, I wouldn't worry about anything but strings.
Ken
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 protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/lists%
40anderhome.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
