Core data or else?

  • Hi everyone,

    I need to store very little data for an application that I am writing.
    Is a Core Data based approach the best way to go or are there simpler
    ways?

    Thanks

    --
    "I never look back darling, it distracts from the now", Edna Mode (The
    Incredibles)
  • There are plenty of ways of persistently storing data. If you explain
    a little more just what you wish to store we'll be able to provide
    some decent advice.

    Mike.

    On 24 Sep 2007, at 12:09, Devraj Mukherjee wrote:

    > Hi everyone,
    >
    > I need to store very little data for an application that I am writing.
    > Is a Core Data based approach the best way to go or are there simpler
    > ways?
    >
    > Thanks
    >
    > --
    > "I never look back darling, it distracts from the now", Edna Mode (The
    > Incredibles)
  • Am 24.09.2007 um 13:09 schrieb Devraj Mukherjee:

    > Hi everyone,
    >
    > I need to store very little data for an application that I am writing.
    > Is a Core Data based approach the best way to go or are there simpler
    > ways?

    If it's really very little data you need to store, using a property
    list to store data may also be sufficient.
    However, what the _best_ approach is, really depends on you (and your
    application). If writing a CoreData application is easier, you should
    go with that. CoreData also lets you choose the backend, but none of
    that really adds a lot of overhead if your dataset is small.

    If all you need to do is read a piece of data, a plain NSDocument
    based application may be just what you need. If your app is a single-
    window-type of application, you may not even need a document based
    application. Without further information, it's hard to tell which
    would be the best application template to use...

    If there is a chance that your dataset will become larger in the
    future, creating a CoreData application may be the wiser choice.

    HTH,
    </jum>
  • Am 25.09.2007 um 00:51 schrieb Devraj Mukherjee:

    > Hi Mike & Jum,
    >
    > Thanks for your responses. I am writing an application that provides
    > desktop integration for the Asterisk PBX server
    > (http://asterisktools.org). One of the features is a "Call Log", so it
    > keeps a record of Missed, Recd. and Outgoing calls. I am anticipating
    > it will be 20 entries per list, so about 60 rows which can be cleared
    > by the user.
    >
    > The data will be recorded when the call is initiated and will be
    > displayed on a list at the users request. I really don't anticipate
    > the lists to grow because of the nature of the application.
    >
    > What would you suggest I do? Core Data? Or head with an NSDocument
    > style approach?

    First of all, I wouldn't necessarily anticipate the list to remain
    small - I'm sure some users will just never clean the list and it
    keeps growing... Murphy's law.

    This sounds like a good candidate for a CoreData application to me.
    It's not really a document bound application (at least not from the
    user's perspective, since there's probably not a notion of a document
    the user opens - it's more like iTunes: the user starts the
    application and a database is opened without the need for the user to
    navigate to a document file. Also, it's probably a good idea to
    anticipate data growing larger than one may believe is 'useful'.

    For an application of this type, I'd go with a CoreData application
    with an sqlite backend, storing the data in an application-specific
    folder inside Library/Application Support. (which Library folder
    depends on whether the app is a system-wide server or a per-user
    service).

    HTH,
    </jum>

    >
    > Thanks for your time.
    >
    > PS Should have explained myself better in the first instance :)
    >
    > On 9/24/07, Jens Miltner <jum...> wrote:
    >>
    >> Am 24.09.2007 um 13:09 schrieb Devraj Mukherjee:
    >>
    >>> Hi everyone,
    >>>
    >>> I need to store very little data for an application that I am
    >>> writing.
    >>> Is a Core Data based approach the best way to go or are there
    >>> simpler
    >>> ways?
    >>
    >> If it's really very little data you need to store, using a property
    >> list to store data may also be sufficient.
    >> However, what the _best_ approach is, really depends on you (and your
    >> application). If writing a CoreData application is easier, you should
    >> go with that. CoreData also lets you choose the backend, but none of
    >> that really adds a lot of overhead if your dataset is small.
    >>
    >> If all you need to do is read a piece of data, a plain NSDocument
    >> based application may be just what you need. If your app is a single-
    >> window-type of application, you may not even need a document based
    >> application. Without further information, it's hard to tell which
    >> would be the best application template to use...
    >>
    >> If there is a chance that your dataset will become larger in the
    >> future, creating a CoreData application may be the wiser choice.
    >>
    >> HTH,
    >> </jum>
    >>
  • I'd also consider looking at Adium. Their code is open source and
    they have a rather neat system for logging messages which uses a
    reverse XML parser.

    http://boredzo.org/blog/archives/2007-03-03/lmx-10-released

    Mike.

    On 25 Sep 2007, at 09:16, Jens Miltner wrote:

    >
    > Am 25.09.2007 um 00:51 schrieb Devraj Mukherjee:
    >
    >> Hi Mike & Jum,
    >>
    >> Thanks for your responses. I am writing an application that provides
    >> desktop integration for the Asterisk PBX server
    >> (http://asterisktools.org). One of the features is a "Call Log",
    >> so it
    >> keeps a record of Missed, Recd. and Outgoing calls. I am anticipating
    >> it will be 20 entries per list, so about 60 rows which can be cleared
    >> by the user.
    >>
    >> The data will be recorded when the call is initiated and will be
    >> displayed on a list at the users request. I really don't anticipate
    >> the lists to grow because of the nature of the application.
    >>
    >> What would you suggest I do? Core Data? Or head with an NSDocument
    >> style approach?
    >
    > First of all, I wouldn't necessarily anticipate the list to remain
    > small - I'm sure some users will just never clean the list and it
    > keeps growing... Murphy's law.
    >
    > This sounds like a good candidate for a CoreData application to me.
    > It's not really a document bound application (at least not from the
    > user's perspective, since there's probably not a notion of a
    > document the user opens - it's more like iTunes: the user starts
    > the application and a database is opened without the need for the
    > user to navigate to a document file. Also, it's probably a good
    > idea to anticipate data growing larger than one may believe is
    > 'useful'.
    >
    > For an application of this type, I'd go with a CoreData application
    > with an sqlite backend, storing the data in an application-specific
    > folder inside Library/Application Support. (which Library folder
    > depends on whether the app is a system-wide server or a per-user
    > service).
    >
    > HTH,
    > </jum>
    >
    >
    >>
    >> Thanks for your time.
    >>
    >> PS Should have explained myself better in the first instance :)
    >>
    >> On 9/24/07, Jens Miltner <jum...> wrote:
    >>>
    >>> Am 24.09.2007 um 13:09 schrieb Devraj Mukherjee:
    >>>
    >>>> Hi everyone,
    >>>>
    >>>> I need to store very little data for an application that I am
    >>>> writing.
    >>>> Is a Core Data based approach the best way to go or are there
    >>>> simpler
    >>>> ways?
    >>>
    >>> If it's really very little data you need to store, using a property
    >>> list to store data may also be sufficient.
    >>> However, what the _best_ approach is, really depends on you (and
    >>> your
    >>> application). If writing a CoreData application is easier, you
    >>> should
    >>> go with that. CoreData also lets you choose the backend, but none of
    >>> that really adds a lot of overhead if your dataset is small.
    >>>
    >>> If all you need to do is read a piece of data, a plain NSDocument
    >>> based application may be just what you need. If your app is a
    >>> single-
    >>> window-type of application, you may not even need a document based
    >>> application. Without further information, it's hard to tell which
    >>> would be the best application template to use...
    >>>
    >>> If there is a chance that your dataset will become larger in the
    >>> future, creating a CoreData application may be the wiser choice.
    >>>
    >>> HTH,
    >>> </jum>
    >>>

previous month september 2007 next month
MTWTFSS
          1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30
Go to today