>
> Most of my Core Data entities have a Data blob attribute which is actually
> and archived dictionary of "extra data." Each user's per-document view
> configuration is stored under keys within each blob. The Data blobs start
> out nil which just defaults to something reasonable in each view.
Let me explain how I solved the same problem:
I have an application that stores large data files via Core Data. Multiple
users access the same data at different times, and each user has a preferred
way of visualizing the data. E.g. starting point, filter sets, color coding,
etc. all differ f
On Mon, Mar 9, 2009 at 4:04 PM, Karolis Ramanauskas wrote:
>> STOP IT.
>>
>> That's right. Stop it.
>>
>> No no, just just stop it.*
>
> I needed that, ;)
Sometimes a comically cold splash of water helps. ;-)
> I can't come up with a better way either, I've been
> sitting and reading al
>
> STOP IT.
>
> That's right. Stop it.
>
> No no, just just stop it.*
I needed that, ;) I can't come up with a better way either, I've been
sitting and reading all this morning, my platonic MVC ideal a little
diminished... Perhaps this could be one-to-many relationship so I could
associat
On Mon, Mar 9, 2009 at 3:04 PM, Karolis Ramanauskas wrote:
> Well, perhaps I didn't explain it well enough.
That's usually the case with technical posts. :-) You know your
project well. Nobody else does, though.
> Let's say, in the future I
> want to have a different View. In that case specif
Thanks Sean, Benjamin and I. Savant for your responses so far,
>You could use the various setMetadata: methods of NSPersistentStore
and NSPersistentStoreCoordinator.
I thought metadata was meant to make stores searchable with spotlight? Is
this the correct usage? I claim ignorance here :)
>You co
On Mon, Mar 9, 2009 at 1:49 PM, Karolis Ramanauskas wrote:
> I have Core Data Document Based app. Core Data
> model contains entities that describe graph objects (nodes).
...
> Of course I should be able to
> drag them around the screen all that stuff. But this is purely user
> interface stuff I
> While I do realize that I will have to get this data into the Managed
> Context somehow in order for it to be stored automatically with the
> document, I want to be able to make my model completely and utterly UI
> independent.
You could have a NodeViewState, joined to the Node by a relationship
On 3/9/09 12:49 PM, Karolis Ramanauskas said:
>What is the best way to store the coordinates, colors, all that UI
>stuff using core data?
You could use the various setMetadata: methods of NSPersistentStore and
NSPersistentStoreCoordinator.
--
_
Good Day,
I'm in a MVC-induced contradiction here. I've read the archives and found
good answers to many of my questions, however it seems one thing kind of
escaped from being answered. I have Core Data Document Based app. Core Data
model contains entities that describe graph objects (nodes). Of c
10 matches
Mail list logo
