On 2009 May 20, at 18:45, Kyle Sluder wrote:
Your desire for hard and fast rules disturbs me. There are not
distinct use cases for every technology. Transient properties are
useful for certain things, often as a component of some larger trade-
off.
Thanks, Kyle. I'm trying to identify
Jerry Krinock (je...@ieee.org) on 2009-05-20 9:32 PM said:
>Thanks, Mike. I see the advantages you get from making them transient
>are --
>
>1. Knowing that you saved your users a little hard disk space.
>2. Not having to clear their values when the document is reloaded.
Why do you put "a litt
On Wed, May 20, 2009 at 9:32 PM, Jerry Krinock wrote:
> Are there any other advantages?
Your desire for hard and fast rules disturbs me. There are not
distinct use cases for every technology. Transient properties are
useful for certain things, often as a component of some larger
trade-off. Why
On 2009 May 20, at 01:29, Mike Abdullah wrote:
I find transient attributes extremely useful sometimes for
properties which you want in the undo stack, but not persisted to
disk. For example data caches, or session-specific UI properties.
Thanks, Mike. I see the advantages you get from mak
I find transient attributes extremely useful sometimes for properties
which you want in the undo stack, but not persisted to disk. For
example data caches, or session-specific UI properties.
Mike.
On 20 May 2009, at 04:20, Jerry Krinock wrote:
After working through another issue caused by m
After working through another issue caused by my use of a transient
property, I just searched the whole Core Data Programming Guide for
"transient".
I found four disadvantages of using transient properties vs. one
advantage. The advantage is not having to write custom accessor
methods to
