Difference between revisions of "DevTools:Code Examples"

Revision as of 06:46, 22 November 2009

This page was started to provoke developers who know how the SWORD API works to post simple, everyday code examples that anyone can use. By "simple", I mean something that can work within a static function if possible.

Examples

C++

Get Modules Example(s)

The following example is for obtaining modules that are installed in the user's SWORD repository. This example also makes slight use of the Qt4 GUI library. The following function takes one parameter, the type of the modules you want to retrieve. Unless stated otherwise, there are up to 4 different types to choose from:

• "Biblical Texts"
• "Commentaries"
• "Lexicons / Dictionaries"
• "Generic Books"

Code

#include <QStringList>
#include <swmgr.h>
#include <swmodule.h>

QStringList getModules(const char* modType)
	{
		QStringList modules;
		SWMgr library;
		ModMap::iterator it;

		for (it = library.Modules.begin(); it != library.Modules.end(); it++)
		{
			SWModule *module = (*it).second;
			if (!strcmp(module->Type(), modType))
				modules << module->Name();
		}

		return modules;
	}

Example Usage

QStringList bibles = getModules("Biblical Texts");

Note: Map and image modules are considered Generic Books. The most consistent way to differentiate between a Generic Book and a map or image module is to look for the configuration entry "Feature":

if (QString(module->getConfigEntry("Feature")) == "Images")
	// do something ...

Get Biblical Book Names Example(s)

Obtaining a list of the canonical books of the Bible doesn't necessarily require any SWORD classes (though in the following example we'll be using SWConfig). A default SWORD installation installs the file abbr.conf at /usr/share/sword/locales.d on a Unix-like system (on Windows it may be located at C:\Program Files\CrossWire\The SWORD Project\locales.d). The syntax of the file is the same as any INI file. Therefore we just need to parse the file for the canonical books; so technically any configuration file parser that can parse INI files will do. The section we want to obtain from abbr.conf is called Text. (Again, the example uses a Qt4 class, QStringList.)

Code #1

#include <QStringList>
#include <swconfig.h>

QStringList getBiblicalBooks()
	{
		QStringList books;
		SWConfig config("/usr/share/sword/locales.d/abbr.conf");
		ConfigEntMap::iterator it;
		for (it = config["Text"].begin(); it != config["Text"].end(); it++)
		{
			books << (*it).first.c_str();
		}

		return books;
	}

After obtaining all the Bible book names, you can obtain their abbreviations with SWConfig, again:

SWConfig config("/usr/share/sword/locales.d/abbr.conf");
const char *GenAbbr = config["Text"]["Genesis"];

But, of course, since it's not necessarily safe to assume that you would have an abbr.conf file lying around, the above example isn't necessarily practical. Nevertheless, hopefully, its existence provided some insight on SWConfig. The more proper way to obtain a list of Biblical, canonical book names is through the use of VerseKey. VerseKey has a public member that stores the number of books for each testament—BMAX. BMAX[0] has the number of Old Testament books, and BMAX[1] has the number of New Testament books, which will be useful for use in a for loop.

Code #2

QStringList getBiblicalBooks()
	{
		QStringList books;
		VerseKey vk;
		for (int b = 0; b < 2; b++)
		{
			// Set the Testament number to retrieve book names from that Testament.
			// Add 1 to b since the Testament numbers don't start at 0.
			vk.setTestament(b+1);
			for (int i = 0; i < vk.BMAX[b]; i++)
			{
				// Add 1 to i since the book numbers don't start at 0.
				vk.setBook(i+1);
				books << vk.getBookName();
			}
		}
		return books;
	}

Python

Java