Difference between revisions of "Development/Tutorials/QtDOM Tutorial"

Jump to: navigation, search
(wikify a bit)
(Make the code a bit shorted (neglect accessors and setter functions and make the member variables public, instead).)
Line 41: Line 41:
 
       mDate(d), mName(n), mComment(c) {}
 
       mDate(d), mName(n), mComment(c) {}
 
   ~Holiday() {}
 
   ~Holiday() {}
  QDate date() { return mDate; }
+
 
  QString name() { return mName; }
+
  QString comment() { return mComment; }
+
protected:
+
 
   QDate mDate;
 
   QDate mDate;
 
   QString mName, mComment;
 
   QString mName, mComment;
Line 54: Line 51:
 
   HolidaySet( const QString &c ) : mCountry( c ) {}
 
   HolidaySet( const QString &c ) : mCountry( c ) {}
 
   ~HolidaySet() {}
 
   ~HolidaySet() {}
  void setCountry( const QString &c ) { mCountry = c; }
 
  void setName( const QString &n ) { mName = n; }
 
  void setComment( const QString &c ) { mComment = c; }
 
  QString country() { return mCountry; }
 
  QString name() { return mName; }
 
  QString comment() { return mComment; }
 
  
  void setHolidays( const QList<Holiday> &h ) { mHolidays = h; }
 
  QList<Holiday> holidays() { return mHolidays; }
 
 
protected:
 
 
   QString mCountry, mName, mComment;
 
   QString mCountry, mName, mComment;
 
   QList<Holiday> mHolidays;
 
   QList<Holiday> mHolidays;
 
}
 
}
 
</code>
 
</code>
 +
 +
In production code, you would not make the member variables public and directly access them, but rather add accessors and setter functions:
 +
<code cppqt>
 +
QDate date() { return mDate; }
 +
void setDate( const QDate& date ) { mDate = date; }
 +
</code>
 +
To save space, I decided to neglect that rule of thumb here in this example. As this is a tutorial for XML and Qt DOM, I want to concentrate on the basics of Qt DOM and not on a good general programming style.
  
 
As there are only so many sensible names, sooner or later you will find out that you will use the same tagname or attribute name for different cases with different meanings. That is the point where namespaces come in.
 
As there are only so many sensible names, sooner or later you will find out that you will use the same tagname or attribute name for different cases with different meanings. That is the point where namespaces come in.

Revision as of 13:44, 12 January 2007

Contents

Creating and loading XML files with QtDOM

Short introduction to XML

XML is a general structured format to store and exchange hierarchical data.

If you know HTML, you'll find XML quite similar (in fact, after some small modifications, a HTML file is a valid XML file): XML uses nested tags of the form <tagname>...</tagname> for tags with contents and <tagname/> for tags without content. Each tag can contain other tags, and the tag itself can have attributes of the form <tagname attribute=value>...</tagname>.

The name of the tags is not restricted (unlike HTML, which only defines a given set of proper HTML tags), so you can choose whatever name fits your name.

As an example, let us assume that you want to store holiday information into a file and use Qt to load or modify it. To get a feeling for how XML looks like, here is one possible format for such a holiday file: <?xml version='1.0' encoding='UTF-8'?> <holidayset country="at">

 <name>Holidays for Austria</name>
 <comment>This is an example and by far not complete.</comment>
 <holiday>
   <name>New Year's Day</name>
   <date>2007-01-01</date>
   <comment>Happy new year!</comment>
 </holiday>
 <holiday>
   <name>Christmas</name>
   <date>2007-12-24</date>
 </holiday>

</holidayset> This file defines a holiday set for Austria (notice the country="at" attribute to the holidayset tag). The holiday set, enclosed in <holidayset>...</holidayset> contains two holidays, each enclosed with <holiday>...</holiday>. Each of these holiday elements contains the settings for that holiday enclosed in appropriately named tag.

Notice that we did use the same tag <name> inside the <holidayset> and inside the <holiday> tags. Also note that we implicitly used specially formated (ISO-formatted) contents for the date tags, without yet specifying it. Also note that we used quite generic names for the tags, which might become a problem with complexer structure, when we want to use the same name for different purposes.

We will use this example throughout this tutorial. In our application, we want to store the holiday set in the following class:

class Holiday { public:

 Holiday( const QDate &d, const QString &n, 
          const QString &c = QString() ) 
     mDate(d), mName(n), mComment(c) {}
 ~Holiday() {}
 QDate mDate;
 QString mName, mComment;

}

class HolidaySet { public:

 HolidaySet( const QString &c ) : mCountry( c ) {}
 ~HolidaySet() {}
 QString mCountry, mName, mComment;
 QList<Holiday> mHolidays;

}

In production code, you would not make the member variables public and directly access them, but rather add accessors and setter functions: QDate date() { return mDate; } void setDate( const QDate& date ) { mDate = date; } To save space, I decided to neglect that rule of thumb here in this example. As this is a tutorial for XML and Qt DOM, I want to concentrate on the basics of Qt DOM and not on a good general programming style.

As there are only so many sensible names, sooner or later you will find out that you will use the same tagname or attribute name for different cases with different meanings. That is the point where namespaces come in.

Creating a simple XML file with QtDOM

Loading a simple XML file

XML Namespaces

<?xml version='1.0' encoding='UTF-8'?> <h:holidays xmlns:h="http://www.example.com/kde/QtDOM/Example">

 <h:holiday country="at">
   <h:name>New Year's Day</h:name>
   <h:date>2007-01-01</h:date>
   <h:comment></h:comment>
 </h:holiday>
 <h:holiday>
   <h:name>Christmas</h:name>
   <h:date>2007-12-24</h:date>
 </h:holiday>

</h:holidays>


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal