| AxKit-App-TABOO documentation | view source | Contained in the AxKit-App-TABOO distribution. |
AxKit::App::TABOO::Data::Language - Language Data objects for TABOO
use AxKit::App::TABOO::Data::Language;
$type = AxKit::App::TABOO::Data::Language->new(@dbconnectargs);
$type->load(limit => {code => 'no'});
This contains a simple class for ISO 639 language codes.
This class reimplements only one method in addition to the constructor, the rest is inherited from AxKit::App::TABOO::Data.
new(@dbconnectargs)The constructor. Nothing special.
load(what => fields, limit => {code => value, [...]})Nothing very different from other load methods. You would usually load
an object by specifying the mimetype as in the above example.
The data is stored in named fields, and for certain uses, it is good to know them. If you want to subclass this class, you might want to use the same names, see the documentation of AxKit::APP::TABOO::Data for more about this. These are the names of the stored data of this class:
The ISO 639 two-letter code
An expanded name intended for human consumption. Must be in the code's own langugage.
The write_xml() method, implemented in the parent class, can be
used to create an XML representation of the data in the object. The
above names will be used as element names. The xmlelement(),
xmlns() and xmlprefix() methods can be used to set the name of
the root element, the namespace URI and namespace prefix
respectively. Usually, it doesn't make sense to change the default
namespace, prefix, or root element that are
http://www.kjetil.kjernsmo.net/software/TABOO/NS/Language/OutputlanglanguageSee AxKit::App::TABOO.
| AxKit-App-TABOO documentation | view source | Contained in the AxKit-App-TABOO distribution. |