,

Introduction

This article provides an easy way to load and save the parameters of an application in XML format.

XML is a convenient format to deal with the parameters of applications for the following reasons:

It's text, so you can easily check the values and modify them with a classical editor (by the way, IE 5.0 shows XML in a very nice way).

It's based on a tree so you can have your parameters saved in a structured way.

It's platform and language independent.

My goal was not to parse an XML file, but to give an easy way to read and write the data. So the code is based on A simple STL based XML parser by David Hubbard. I would really like to thank him for his parser, it's a very good work! Moreover it saved me a lot of time, even if I made a few modifications in his original code to fulfill my goals.

The code is entirely based on STL. It compiles on linux, too. I guess it will compile on any other platform/compiler that supports STL.

Using the code

Now let's take an example to explain more precisely what you can do with ParamIO. Let's assume you have an application to show some text on the screen in a given color and in a given font (the demo project). The parameters of your application will be the text (1 string), the color (3 values RGB) and the font (1 string for the font name and 1 double for the font size). You want to be able to save those parameters on the disk and load them for a later use. A nice XML file containing those values can look like this:

As you can see, it's very easy. In the write method, the first parameter is a char* that defines the position in the XML tree. This is similar to XPath, but I didn't know XPath at the time I wrote this code, I would have used the '/' instead if I had known. The second parameter gives the value you want to write. write is a templated method so you can write almost any kind of variable, from int to std::string. Reading the file is also straightforward :

You may be surprised by the third parameter of the read method. What does it mean? It's the default value of the parameter you try to read. Imagine you want to read a file like the previous one and the size of the font is not specified, then _fontSize will be automatically set to its default value 12.0. It's a very useful behaviour when you have several versions of a same application and some versions have parameters that didn't exist in older ones. It ensures that you still can read the old files, filling the missing values with default ones. It also lets you load a file that doesn't exist and set all the parameters with their default values.

ParamIO lets you read and write XML coming from streams also, it should be useful if you want some applications to exchange data through sockets for example.

The demo application includes a XML dialog box. With this dialog box (CXML_Dialog), you can visualise and modify any XML tree. I used it a lot, it's working really well. In case your parameter name contains FILENAME inside (e.g FONT_FILENAME), you'll see a button appear, and if you click on it, you'll obtain an open file dialog where you can find your file. I used this CXML_Dialog dialog box a lot and I'm very happy about it, it works really fine. CXML_Dialog uses a class from Easy Navigation Through an Editable List View by Lee Nowotny. I really thank him for the job, it works perfectly.

If you have any comments, suggestions or improvements let me know.

History

20 Nov 2002 : first version with GUI demo, with comparison capabilities

20 June 2003:

modified the website, added src download without the GUI demo

Added support for MFC CString has been added thanks to Paul Kissel : to enable CString read/write, just define _PARAMIO_CSTRING_SUPPORT_ in the compilation options.

Added a method to erase a node or an entire subtree as been added, thanks to Ogi's suggestion.

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

Hi Loren,If you want to see the XML file structured in a tree shape shouldn't be using an XML editor or even IE to view it. Adding extraneous Tab characters to the XML file seems like a realy bad idea to me, and certainly non-portable I would think.

As an aside I don't like static's used in this way unless there is a realy good reason. And where does l come from me wonders?

Thanks for your input. The way I see it is that tabs are like spaces in that they are just "whitespace". Correct me if I'm wrong, but the XML standard does not say that whitespace is not allowed (this is similar in nature to HTML). If an XML parser has problems parsing whitespace then I surely wouldn't want to use it!

Also, this is a class to create config files for applications. Assuming they were going to edit the file manually, I'm not sure who would want to use an XML editor just to hack a few lines in the config file (even still, the tabs should not prevent them from doing this). Notepad should be just fine, and the tabs help with visibility... especially when the config file gets a little on the larger side, and the nesting starts to get out of control.

Neville Franks wrote:...certainly non-portable I would think

On the non-portable issue, as long as the XML parser used by this class can support the tabs (which it does) then there should be no porting issues. But like I said before whitespace (tabs included) should not prevent any other XML parser from correctly reading an XML file either.

Neville Franks wrote:As an aside I don't like static's used in this way unless there is a realy good reason.

How would you have implemented the tabs without using static? I know of another way to do it, but using static made the code MUCH cleaner. However, I'm always willing to learn new things, and would like to hear how you would have implemented this!

Hi Loren,Well maybe I'm being a bit too picky re. the tabs, but it just seems like you are polluting the file to me. You are right that whitespace is ignored and shouldn't cause any problems. That said if you did open it in an XML editor and then saved it, you may well loose the tabs. The other issue is for large XML files, you are just making them that bit larger again.

Re. the static. I don't know enough about the code, however it appears to build a DOM (Tree) and XML_Node includes _parent and getParent(). Where I do stuff like this I climb the tree untill I reach the root, and then you know the depth, which is what I assume nTabCount is about. If that doesn't work and no other generalized solution presents itself I would at least put the static in the XML_Node class, where it can be initialized properly.