Announcement

Collapse
No announcement yet.

[OT - almost] Looking for best way to save App data - is XML OK

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • [OT - almost] Looking for best way to save App data - is XML OK

    Sorry folks if that was asked before - the search did not return any hints.

    I am working on Carputer app for the wife, she is on the road a lot and has different requirements than us (contact management, calendar, etc...). None of the current Palm tools are easy to deal with through touch screen, so I am building a simple app that meets her needs.

    The issue is, what is the best way to save
    1) application setup/configuration data.
    2) the actual contact list / appointments (about 150 names).

    I will be using .NET for the framework and either C++ or VB. Should I go with XML, create my own structure or use a database like Access (overkill ?)

    I do like to keep it standard though since I would love to contribute the App to the public if it turns out OK and useful.

    Any ideas or hints would be appreciated.

    Thanks.

  • #2
    For configuration data, XML is good because it lets you store data in a human readable and modifiable format with just a text editor it is also easily transferable via a file unlike registry settings. I find it takes more to work with then just ini files though if your just going to store simple value pair values. If you have more complicated structure to the data your storing then XML is defnitly the way to go.

    The only reason why you would want to use an access database over XML is if you have some very complicated data manipulation that you would like to do with SQL quieries. You can do quite a bit with just XML and a reader that supports XPath quieries though, so I doubt you would want to introduce the overhead of using access.
    StreetDeck.com Developer (I am Chuck)
    Get StreetDeck at http://www.streetdeck.com
    The Official StreetDeck Forums have moved, please visit us at http://www.streetdeck.com/forum for official support for Streetdeck.

    Comment


    • #3
      XML or INI files should do fine. And there isn't much overhead using an
      access database, as an access database is just JET, which is built into
      the OS. Access is not needed. But if you are doing just simple storage
      and retrieval XML or INI files should do just fine. INI files being the less
      resource intensive.

      Frodo
      [H]4 Life
      My next generation Front End is right on schedule.
      It will be done sometime in the next generation.
      I'm a lesbian too.
      I am for hire!

      Comment


      • #4
        Thanks guys, that was super fast.
        Based on your input, I think XML is the ticket, my data is a bit more complex than .INI but does not require the SQL queries provided by a DB.

        Appreciate your input.

        Comment


        • #5
          Let me know when you get a app like that. I was thinking about doing the same for myself. I need something just like that. If its something I would like I'll throw ya some money for your hard work.

          Thanks.

          Comment


          • #6
            INI files are for 'flat' name/value pairs, XML is for hierachical data (of which a subset is name/value pairs), SQL is not for hierachical, but for relational data. They dont really compete, it really depends on your data.

            XML is highly versatile and well supported by .NET.

            If you have 10,000 contacts and you want to find those that are closest to your current lat/lon ordered by their spatial relationship to you, then a SQL database like Postgres will be perfect, if you need to store the x/y coordinates of the app when it exists, then INI is perfect, if you have anything else... XML.
            .//Daren
            (Epia M10000/C134) (C137/MII 10000) Liliput /Opus 150W/DVD/512MB/80GB/Hummer H1
            MediaCar/CoPilot7/Routis

            Comment


            • #7
              tCoy, thanks for the offer but I would not take money, I have learned a lot on this site and that would be my contribution if it passes the wife's acid test.

              mobileh1, that was my train of thought after reading the first 2 replies, the data is of hierarchical nature, XML will fit the bill.

              Thanks guys

              Comment


              • #8
                Why would this be OT ?
                [H]4 Life
                My next generation Front End is right on schedule.
                It will be done sometime in the next generation.
                I'm a lesbian too.
                I am for hire!

                Comment


                • #9
                  Since the question did not deal directly with Carputer and multimedia/navigation, that is my thought anyway. I just try to avoid steeping on any toes or get any one upset.

                  Comment

                  Working...
                  X