ODF::lpOD::Element - Common features available with any ODF element
This manual page describes the odf_element class.
odf_element is implemented in the ODF::lpOD::Element package.
Every XML element (loaded from an existing ODF document or created by any lpOD-based application) is a odf_element. This class is the base class for any document element; its features are inherited by other, more specialized element classes.
An element may be explicitly created using the odf_create_element class constructor (or a the constructor of any derivative of odf_element (such as odf_paragraph, odf_table, etc), then inserted somewhere is an document. However, in most cases, elements are either retrieved in the existing structure or implicitly created ad put in place as children of existing elements through various element-based set_xxx methods (where "xxx" depends on the kind of newly created data).
Among the odf_element methods, we distinguish element methods from context methods, while both kinds of methods belong to odf_element objects. An element method gets or sets one or more properties of the calling element, while a context method uses the calling element as its operating context and may produce effects regarding other elements located somewhere in the hierarchy of the calling element (generally below, and sometimes above). As examples, set_attribute is an element method (it changes an attribute of the current element), while get_element (in its element-based version, that is not the same as its part-based one) retrieves an element somewhere below the current one.
Creates an odf_element from a fragment of XML data or an arbitrary tag. If the given argument is valid XML, its parsed and the new element is created accordingly, possibly with a complex structure. If the argument is a non-XML string, its regarded as a tag (possibly with a namespace prefix), and the new element is created internally without XML parsing.
The new element is not attached to a document; it's free for later use.
odf_create_element is an exported alias; it's implemented by ODF::lpOD::Element::create.
This method returns the first element (if any) matching the given XML tag. It's the most generic context-based retrieval method.
The given tag may be replaced by a regular expression, so the search space will include all the elements whose tags match the expression.
For example, the following instruction (assuming $context is a previously retrieved element) returns the first element that is either a paragraph or a heading (konwing that the correspondig tags are text:p and text:h):
my $text_element = $context->get_element(qr'text:(p|h)');
The allowed options are:
position: The sequential zero-based position of the element among the set of elements matching the given tag; negative positions are counted backward from the end.
attribute: The name of an attribute used as a selection criterium; if this option is set, the value option is required.
value: the value of the selection attribute.
content: a search string (or a regex) restricting the search space to the elements with matching content.
The example below (that combines all the options) returns the 4th level 1 heading before the end of the current context:
attribute => 'outline level',
value => 1,
position => -4
Caution: the get_element method of odf_part is not the same as the get_element method of odf_element.
Returns the full list of elements matching the given tag, whose tags match the given regex.
The attribute and value options are allowed in order to restrict the search.
The next example returns the list of paragraphs whose style is "Standard":
my @std_paragraphs = $context->get_elements(
attribute => 'style name',
value => 'Standard'
This method returns the immediate parent of the calling element. Of course, it returns undef if the context element is itself a root, or if it's not included yet in a document.
Returns the top level element of the document part that contains the calling element.
Returns the odf_document instance to which the element belongs. Returns undef if the element is not attached to a odf_document.
As introduced in ODF::lpOD::Document, the odf_part handlers provide methods that automatically return high level elements that may be the preferred contexts in most cases. The most common one is the root element; its context is the whole document part. The body element, that is sometimes the same as the root one, is a bit more restricted in the document content part (it includes only the content objects, and excludes other objects such as style definitions). Both the root and the body may be got using the part-based get_root and get_body methods.
The following sequence, starting from the creation of a document instance, selects a part, then the root element of the part, than selects the list of table styles defined in the part:
my $doc = odf_get_container("/home/jmg/report.odt");
my $content = $doc->get_content;
my $context = $content->get_root;
my @table_styles = $context->get_element_list(
attribute => 'family',
value => 'table'
Note that in this last example nothing could be found knowing that style elements are not allowed by the ODF specification in the body context.
The methods described in this section allows the user to insert elements (previously existing or not) as children of the calling element.
Insert the given odf_element at a given position, that is defined according to a position parameter, whose possible values are:
FIRST_CHILD: the odf_element will be the first child (default).
LAST_CHILD: the odf_element will be the last child.
NEXT_SIBLING: the odf_element will be inserted just after.
PREV_SIBLING: the odf_element will be inserted just before.
WITHIN: the odf_element will be inserted as a child within the text content; if position is WITHIN, then the offset parameter is required.
offset: specifies the position in the text of the context element where the new child element must be inserted (the position is zero-based).
before: the value of this option, if set, must be another child odf_element of the calling one; the new element will be inserted as the previous sibling of this child element.
after: like before, but the new element will be inserted after the value of this option.
The WITHIN option splits the text content of the container in two parts and inserts the elements between them, at a given offset. So if position is WITHIN, the offset optional parameter is used. By default, if no offset argument is provided, or if the calling element doesn't contain any text, WITHIN produces the same result as FIRST_CHILD. The offset argument must be an integer; it specifies the position of the inserted child element within the text content of the calling element. A zero offset means that the element must be inserted before the 1st character. A negative offset value means that the insert position must be counted down from the end of the text, knowing that -1 is the position just before the last character. Of course, if the insertion must be done after the end of the text, the simplest way is to select LAST_CHILD instead of WITHIN.
If before or after is provided, the other options are ignored. Of course, before and after are mutually exclusive.
The following example inserts a previously existing element between the 4th and the 5th characters of the text of the calling element:
position => WITHIN,
offset => 4
The next example inserts a new empty paragraph before the last paragraph of the calling context:
my $last_p = $context->get_element('text:p', position => -1);
before => $last_p
(Note that smarter methods, described elsewhere, may produce the same results).
Like the first version of insert_element, but the argument is an XML tag (i.e. technically a text string instead of a odf_element instance); in such a case a new element is created then inserted according to the same rules and options.
Like insert_element, but without options; appends the element as the last child of the calling element. So these tow lines are equivalent:
$context->insert_element($elt, position => LAST_CHILD);
The methods introduced in this section are accessors that get or set the own properties of the calling element. However, in some cases they may have indirect consequence on other elements.
Erases the text of an element and all its children.
Returns a copy of the calling element, with all its attributes, its text, and its children elements. Allows the user to copy a high-level structured element (like a section or a table) as well as a single paragraph. The copy is a free element, that may be inserted somewhere in the same document as the prototype, or in another document.
Removes the calling element with all its descendants.
Deletes the attribute whose name is given in argument. Nothing is done if the attribute doesn't exist. The argument may be the exact XML name of the attribute, or an "approximative" name according to the same logic as get_attribute below.
Returns the string value of the attribute having this name. The argument may be the exact XML name of the attribute. However, if a name without namespace prefix is provided, the prefix is automatically supposed to be the same as the prefix of the context element. In addition, any white space or underscore character in the given name is interpreted as a "-". As a consequence, some attributes may be designated without care of the exact XML syntax. As an example, assuming $p is a paragraph, the two instructions below are equivalent, knowing that the namespace prefix of a paragraph is 'text':
$style = $p->get_attribute('text:style-name');
$style = $p->get_attribute('style name');
The attribute values are returned in a character set that depends on the global configuration. See ODF::lpOD::Common for details about the character set handling.
Returns all the attributes of the calling element as a hash ref where keys are the full XML names of the attributes.
Returns the XML tag of the element with its namespace prefix.
Returns the name of the style used by the calling element (this accessor makes sense for objects that may be displayed according to a layout). Returns undef if no style is used.
Note: if your style names contain non-ASCII characters and if your preferred output character set is not utf8, see ODF::lpOD::Common for details about character sets handling.
Returns the text contents of the element as a string. By default this method is not recursive (i.e. it just returns the own text of the element, not the text belonging to children and descendant elements). Such behaviour is not convenient for every possible use case (for example, the text of a paragraph may be partly or entirely split among several low level text containers, while a typical end-user regards this text as a flat string). So, if the optional recursive parameter is provided and set to TRUE, then the method returns the concatenated contents of all the descendants of the given element.
In a default configuration, the character set of the output is utf8. If that is not convenient for you, see the character set handling section in ODF::lpOD::Common.
Returns an XML export of the calling element, allowing the lpOD applications to store and/or transmit particular pieces of documents, and not only full documents. The pretty option is allowed, like with the serialize method of odf_part objects, described in ODF::lpOD::Document.
Note that this XML export is not affected by the content encoding/decoding mechanism that works for user content, so it's character doesn't depend on the custom text output character set possibly selected through the set_output_charset() method introduced in ODF::lpOD::Common.
Sets or changes an attribute of the calling element. The attribute is created if it didn't exist. If the provided value is undef, the attribute is deleted (if it didn't exist, nothing is done). The attribute name may be specified according to the same rules as with get_attribute.
About the character set of the input valules, the same rules as with any text input apply; see the character set handling section in ODF::lpOD::Common.
Sets several attributes at a time. The attributes to change or create must be passed as a hash ref (like the hash ref returned by get_attributes). The attribute names may be provided in simplified form like with set_attribute.
Changes the XML tag of the calling element. Not for usual business; it's a low level technical feature.
Changes or sets the style name of the calling object. Caution: a lot of ODF elements should not have any style, so don't use this accessor unless you know that the calling object needs a style.
Note: if your style names contain non-ASCII characters and if your preferred input character set is not utf8, see ODF::lpOD::Common for details about character sets handling.
Sets the text content of the calling element, replacing any previous content. Example:
my $paragraph = $context->get_element('text:p', position => 15);
$paragraph->set_text("The new content");
The character set of the provided string must comply to the currently active input character set (default is utf8). See the character set handling section in ODF::lpOD::Common if you get troubles about text encoding.
If set_text is called with an empty string, its effect is the same as clear.
Copyright (c) 2010 Ars Aperta, Itaapy, Pierlis, Talend.
This work was sponsored by the Agence Nationale de la Recherche (http://www.agence-nationale-recherche.fr).
lpOD is free software; you can redistribute it and/or modify it under the terms of either:
a) the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. lpOD is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with lpOD. If not, see http://www.gnu.org/licenses/.
b) the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
To install ODF::lpOD, copy and paste the appropriate command in to your terminal.
perl -MCPAN -e shell
For more information on module installation, please visit the detailed CPAN module installation guide.