document
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 1688
Document Library 1.2b2
Document Library is a Web application for document management in larger organizations with a lot of documents. more>>
Document Library is a Web application for document management in larger organizations with a lot of documents.
Organizations deal with numerous documents, such as word processor documents and PDFs. These documents often reside on someones computer and are not network accessible. Versions of documents are hard to track - the same document may be passed around using email in multiple versions over time. In large organizations it therefore becomes important to structure the flow of documents and present them in a common format. This is typically done using a document management system. Document Library is one such document management system.
Information in the Document Library can be accessed using the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH), meaning that besides being open source, the Document Library is also a good example of an open data application. Because it is open data, the Document Library is easier to integrate with other applications, such as the Silva CMS or any other application capable of OAI-PMH harvesting.
Main features:
- Automatic conversion service: using OpenOffice, the Document Library can convert Word documents into PDFs and plain text, PDFs into plain text. The plain text version is important in that it allows for full-text indexing of document contents, and also makes documents more accessible to people with disabilities.
- Publication workflow: documents only become available for harvesting and download after a review process.
- Delegation of control: reviewers ("librarians") can be assigned to particular sections.
- Dynamic access: authors have automatic access to all the documents that list them as an author.
- Versions: multiple versions of the same document can coexist, one public and one under preparation.
- Email reminder functionality: users receive emails of the progress of the document through the workflow.
- OAI-PMH data provider: allows other systems to harvest document metadata using standard protocol.
- Integration with Silva CMS (using OAI-PMH).
- Fast upload and download integration with Apache using Tramline.
- Easy overview screens for librarians.
- Smart file upload user interface: files need to be uploaded only once even if rest of form needs to be amended.
- Document Library is built using the powerful Zope 3 application server platform.
Enhancements:
- Installation was made easier by using zc.buildout.
- Optional LDAP support was added.
- Filesystem storage was integrated with Tramline.
- The conversion provided by OooConv was improved.
- Table rendering was improved using zc.table.
- Zope was updated to 3.3.
<<lessOrganizations deal with numerous documents, such as word processor documents and PDFs. These documents often reside on someones computer and are not network accessible. Versions of documents are hard to track - the same document may be passed around using email in multiple versions over time. In large organizations it therefore becomes important to structure the flow of documents and present them in a common format. This is typically done using a document management system. Document Library is one such document management system.
Information in the Document Library can be accessed using the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH), meaning that besides being open source, the Document Library is also a good example of an open data application. Because it is open data, the Document Library is easier to integrate with other applications, such as the Silva CMS or any other application capable of OAI-PMH harvesting.
Main features:
- Automatic conversion service: using OpenOffice, the Document Library can convert Word documents into PDFs and plain text, PDFs into plain text. The plain text version is important in that it allows for full-text indexing of document contents, and also makes documents more accessible to people with disabilities.
- Publication workflow: documents only become available for harvesting and download after a review process.
- Delegation of control: reviewers ("librarians") can be assigned to particular sections.
- Dynamic access: authors have automatic access to all the documents that list them as an author.
- Versions: multiple versions of the same document can coexist, one public and one under preparation.
- Email reminder functionality: users receive emails of the progress of the document through the workflow.
- OAI-PMH data provider: allows other systems to harvest document metadata using standard protocol.
- Integration with Silva CMS (using OAI-PMH).
- Fast upload and download integration with Apache using Tramline.
- Easy overview screens for librarians.
- Smart file upload user interface: files need to be uploaded only once even if rest of form needs to be amended.
- Document Library is built using the powerful Zope 3 application server platform.
Enhancements:
- Installation was made easier by using zc.buildout.
- Optional LDAP support was added.
- Filesystem storage was integrated with Tramline.
- The conversion provided by OooConv was improved.
- Table rendering was improved using zc.table.
- Zope was updated to 3.3.
Download (0.30MB)
Added: 2006-12-07 License: GPL (GNU General Public License) Price:
1055 downloads
Download (0.45MB)
Added: 2007-02-07 License: GPL (GNU General Public License) Price:
995 downloads
DynaPage::Document 0.90
DynaPage::Document is a Perl module with DynaPage Document container. more>>
DynaPage::Document is a Perl module with DynaPage Document container.
SYNOPSIS:
step1 - document ( create file mydoc.document )
---[content of mydoc-document.info]---
!include.template =- mydoc-template.htmt
my-title =- This is single line
my-head =- Hello World
my-para ==~
This is block
multiline content
blah blah
blah blah
~== my-para
---[content of mydoc-document.info]---
step2 - template ( create file mydoc.template )
---[content of mydoc-template.htmt]---
< html >
< title >[~my-title~]< /title >
< h1 >[~my-head~]< /h1 >
< p >[~my-para~]< /p >
< /html >
---[content of mydoc-template.htmt]---
step3 - open
use DynaPage::Document;
use DynaPage::Document::ext::include;
my $doc = DynaPage::Document->new(
{
RootDir=>.,
Document=>mydoc-document.info,
}
);
step4 - render
print $doc->Render();
---[dump of printed result]---
< html >
< title >This is single line< /title >
< h1 >Hello World< /h1 >
< p > This is block
multiline content
blah blah
blah blah< /p >
< /html >
---[dump of printed result]---
<<lessSYNOPSIS:
step1 - document ( create file mydoc.document )
---[content of mydoc-document.info]---
!include.template =- mydoc-template.htmt
my-title =- This is single line
my-head =- Hello World
my-para ==~
This is block
multiline content
blah blah
blah blah
~== my-para
---[content of mydoc-document.info]---
step2 - template ( create file mydoc.template )
---[content of mydoc-template.htmt]---
< html >
< title >[~my-title~]< /title >
< h1 >[~my-head~]< /h1 >
< p >[~my-para~]< /p >
< /html >
---[content of mydoc-template.htmt]---
step3 - open
use DynaPage::Document;
use DynaPage::Document::ext::include;
my $doc = DynaPage::Document->new(
{
RootDir=>.,
Document=>mydoc-document.info,
}
);
step4 - render
print $doc->Render();
---[dump of printed result]---
< html >
< title >This is single line< /title >
< h1 >Hello World< /h1 >
< p > This is block
multiline content
blah blah
blah blah< /p >
< /html >
---[dump of printed result]---
Download (0.014MB)
Added: 2006-10-03 License: Perl Artistic License Price:
1116 downloads
Document clustering 0.2
Document clustering project is a data mining suite to cluster a document set. more>>
Document clustering project is a data mining suite to cluster a document set. This set of tools was implemented from a series of papers: "Clustering Web Pages Semantically using Combinatorial Topology", "Data mining using granular computing", and "A fast association rule algorithm based on bitmap and granular computing".
Enhancements:
- A bug with hash table has been fixed.
<<lessEnhancements:
- A bug with hash table has been fixed.
Download (0.060MB)
Added: 2007-05-18 License: GPL (GNU General Public License) Price:
906 downloads
Document Archiver 1.0.1
Document Archiver allows automatic archiving of documents. more>>
Document Archiver allows automatic archiving of documents.
The Document Archiver is a standalone Java application which should be scheduled to run nightly to facilitate the automatic archiving of documents in the KnowledgeTree DMS.
The programs checks if any documents are due to be archived, based on the Date or Utilisation criteria set in the web application (e.g. archive after 2 months, or archive 15 days after the last download).
<<lessThe Document Archiver is a standalone Java application which should be scheduled to run nightly to facilitate the automatic archiving of documents in the KnowledgeTree DMS.
The programs checks if any documents are due to be archived, based on the Date or Utilisation criteria set in the web application (e.g. archive after 2 months, or archive 15 days after the last download).
Download (0.54MB)
Added: 2007-02-07 License: Other/Proprietary License Price:
989 downloads
XML::DOM::Document 1.44
XML::DOM::Document is an XML document node in XML::DOM. more>>
XML::DOM::Document is an XML document node in XML::DOM.
XML::DOM::Document extends XML::DOM::Node.
It is the main root of the XML document structure as returned by XML::DOM::Parser::parse and XML::DOM::Parser::parsefile.
Since elements, text nodes, comments, processing instructions, etc. cannot exist outside the context of a Document, the Document interface also contains the factory methods needed to create these objects. The Node objects created have a getOwnerDocument method which associates them with the Document within whose context they were created.
METHODS
getDocumentElement
This is a convenience method that allows direct access to the child node that is the root Element of the document.
getDoctype
The Document Type Declaration (see DocumentType) associated with this document. For HTML documents as well as XML documents without a document type declaration this returns undef. The DOM Level 1 does not support editing the Document Type Declaration.
Not In DOM Spec: This implementation allows editing the doctype. See XML::DOM::ignoreReadOnly for details.
getImplementation
The DOMImplementation object that handles this document. A DOM application may use objects from multiple implementations.
createElement (tagName)
Creates an element of the type specified. Note that the instance returned implements the Element interface, so attributes can be specified directly on the returned object.
DOMExceptions:
INVALID_CHARACTER_ERR
Raised if the tagName does not conform to the XML spec.
createTextNode (data)
Creates a Text node given the specified string.
createComment (data)
Creates a Comment node given the specified string.
createCDATASection (data)
Creates a CDATASection node given the specified string.
createAttribute (name [, value [, specified ]])
Creates an Attr of the given name. Note that the Attr instance can then be set on an Element using the setAttribute method.
Not In DOM Spec: The DOM Spec does not allow passing the value or the specified property in this method. In this implementation they are optional.
Parameters: value The attributes value. See Attr::setValue for details. If the value is not supplied, the specified property is set to 0. specified Whether the attribute value was specified or whether the default value was used. If not supplied, its assumed to be 1.
DOMExceptions:
INVALID_CHARACTER_ERR
Raised if the name does not conform to the XML spec.
createProcessingInstruction (target, data)
Creates a ProcessingInstruction node given the specified name and data strings.
Parameters: target The target part of the processing instruction. data The data for the node.
DOMExceptions:
INVALID_CHARACTER_ERR
Raised if the target does not conform to the XML spec.
createDocumentFragment
Creates an empty DocumentFragment object.
createEntityReference (name)
Creates an EntityReference object.
<<lessXML::DOM::Document extends XML::DOM::Node.
It is the main root of the XML document structure as returned by XML::DOM::Parser::parse and XML::DOM::Parser::parsefile.
Since elements, text nodes, comments, processing instructions, etc. cannot exist outside the context of a Document, the Document interface also contains the factory methods needed to create these objects. The Node objects created have a getOwnerDocument method which associates them with the Document within whose context they were created.
METHODS
getDocumentElement
This is a convenience method that allows direct access to the child node that is the root Element of the document.
getDoctype
The Document Type Declaration (see DocumentType) associated with this document. For HTML documents as well as XML documents without a document type declaration this returns undef. The DOM Level 1 does not support editing the Document Type Declaration.
Not In DOM Spec: This implementation allows editing the doctype. See XML::DOM::ignoreReadOnly for details.
getImplementation
The DOMImplementation object that handles this document. A DOM application may use objects from multiple implementations.
createElement (tagName)
Creates an element of the type specified. Note that the instance returned implements the Element interface, so attributes can be specified directly on the returned object.
DOMExceptions:
INVALID_CHARACTER_ERR
Raised if the tagName does not conform to the XML spec.
createTextNode (data)
Creates a Text node given the specified string.
createComment (data)
Creates a Comment node given the specified string.
createCDATASection (data)
Creates a CDATASection node given the specified string.
createAttribute (name [, value [, specified ]])
Creates an Attr of the given name. Note that the Attr instance can then be set on an Element using the setAttribute method.
Not In DOM Spec: The DOM Spec does not allow passing the value or the specified property in this method. In this implementation they are optional.
Parameters: value The attributes value. See Attr::setValue for details. If the value is not supplied, the specified property is set to 0. specified Whether the attribute value was specified or whether the default value was used. If not supplied, its assumed to be 1.
DOMExceptions:
INVALID_CHARACTER_ERR
Raised if the name does not conform to the XML spec.
createProcessingInstruction (target, data)
Creates a ProcessingInstruction node given the specified name and data strings.
Parameters: target The target part of the processing instruction. data The data for the node.
DOMExceptions:
INVALID_CHARACTER_ERR
Raised if the target does not conform to the XML spec.
createDocumentFragment
Creates an empty DocumentFragment object.
createEntityReference (name)
Creates an EntityReference object.
Download (0.11MB)
Added: 2006-07-14 License: Perl Artistic License Price:
1200 downloads
XML::Mini::Document 1.2.8
XML::Mini::Document is a Perl implementation of the XML::Mini Document API. more>>
XML::Mini::Document is a Perl implementation of the XML::Mini Document API.
SYNOPSIS
use XML::Mini::Document;
use Data::Dumper;
###### PARSING XML #######
# create a new object
my $xmlDoc = XML::Mini::Document->new();
# init the doc from an XML string
$xmlDoc->parse($XMLString);
# You may use the toHash() method to automatically
# convert the XML into a hash reference
my $xmlHash = $xmlDoc->toHash();
print Dumper($xmlHash);
# You can also manipulate the elements like directly, like this:
# Fetch the ROOT element for the document
# (an instance of XML::Mini::Element)
my $xmlRoot = $xmlDoc->getRoot();
# play with the element and its children
# ...
my $topLevelChildren = $xmlRoot->getAllChildren();
foreach my $childElement (@{$topLevelChildren})
{
# ...
}
###### CREATING XML #######
# Create a new document from scratch
my $newDoc = XML::Mini::Document->new();
# This can be done easily by using a hash:
my $h = {
spy => {
id => 007,
type => SuperSpy,
name => James Bond,
email => mi5@london.uk,
address => Wherever he is needed most,
},
};
$newDoc->fromHash($h);
# Or new XML can also be created by manipulating
#elements directly:
my $newDocRoot = $newDoc->getRoot();
# create the < ? xml ? > header
my $xmlHeader = $newDocRoot->header(xml);
# add the version
$xmlHeader->attribute(version, 1.0);
my $person = $newDocRoot->createChild(person);
my $name = $person->createChild(name);
$name->createChild(first)->text(John);
$name->createChild(last)->text(Doe);
my $eyes = $person->createChild(eyes);
$eyes->attribute(color, blue);
$eyes->attribute(number, 2);
# output the document
print $newDoc->toString();
This example would output :
< ?xml version="1.0"?>
< person>
< name>
< first>
John
< /first>
< last>
Doe
< /last>
< /name>
< eyes color="blue" number="2" />
< /person>
The XML::Mini::Document class is the programmers handle to XML::Mini functionality.
A XML::Mini::Document instance is created in every program that uses XML::Mini. With the XML::Mini::Document object, you can access the root XML::Mini::Element, find/fetch/create elements and read in or output XML strings.
<<lessSYNOPSIS
use XML::Mini::Document;
use Data::Dumper;
###### PARSING XML #######
# create a new object
my $xmlDoc = XML::Mini::Document->new();
# init the doc from an XML string
$xmlDoc->parse($XMLString);
# You may use the toHash() method to automatically
# convert the XML into a hash reference
my $xmlHash = $xmlDoc->toHash();
print Dumper($xmlHash);
# You can also manipulate the elements like directly, like this:
# Fetch the ROOT element for the document
# (an instance of XML::Mini::Element)
my $xmlRoot = $xmlDoc->getRoot();
# play with the element and its children
# ...
my $topLevelChildren = $xmlRoot->getAllChildren();
foreach my $childElement (@{$topLevelChildren})
{
# ...
}
###### CREATING XML #######
# Create a new document from scratch
my $newDoc = XML::Mini::Document->new();
# This can be done easily by using a hash:
my $h = {
spy => {
id => 007,
type => SuperSpy,
name => James Bond,
email => mi5@london.uk,
address => Wherever he is needed most,
},
};
$newDoc->fromHash($h);
# Or new XML can also be created by manipulating
#elements directly:
my $newDocRoot = $newDoc->getRoot();
# create the < ? xml ? > header
my $xmlHeader = $newDocRoot->header(xml);
# add the version
$xmlHeader->attribute(version, 1.0);
my $person = $newDocRoot->createChild(person);
my $name = $person->createChild(name);
$name->createChild(first)->text(John);
$name->createChild(last)->text(Doe);
my $eyes = $person->createChild(eyes);
$eyes->attribute(color, blue);
$eyes->attribute(number, 2);
# output the document
print $newDoc->toString();
This example would output :
< ?xml version="1.0"?>
< person>
< name>
< first>
John
< /first>
< last>
Doe
< /last>
< /name>
< eyes color="blue" number="2" />
< /person>
The XML::Mini::Document class is the programmers handle to XML::Mini functionality.
A XML::Mini::Document instance is created in every program that uses XML::Mini. With the XML::Mini::Document object, you can access the root XML::Mini::Element, find/fetch/create elements and read in or output XML strings.
Download (0.034MB)
Added: 2006-09-14 License: Perl Artistic License Price:
1135 downloads
Auto Save Document 1.2.0.28
Auto Save Document is an extension used to store the currently shown document in a separate directory automatically. more>>
Auto Save Document is an extension used to store the currently shown document in a separate directory automatically.
Autosave is a small extension, which can be used to store the currently shown document in a seperate directory automatically when browsing a certain site. You may configure the sites, where all pages will be stored to cache, by adding them to a list. The documents are stored as html-text only (no embedded objects like pictures etc.)
The files are cyclic reused, e.g. if you set the cache size to 100, Autosave will store the document contents to X:/MyCache/Autosave_0.html ... AutoSave_100.html and start again with AutoSave_0.htm when the 101st page is browsed. A small Icon in the statusbar will change its colour each time to indicate a page was written.
If you click this small icon, the current page will be dumped, regardless if the site is in the autosave list or not.
NOTE: this extension is really, really simple! Only plain text is saved, no external .css,.js => the result may look ugly! The one and only intention for this extension is, to save the text for external parsing or similar! Look for Scrapbook etc. in case you want to store more than the plain text!
<<lessAutosave is a small extension, which can be used to store the currently shown document in a seperate directory automatically when browsing a certain site. You may configure the sites, where all pages will be stored to cache, by adding them to a list. The documents are stored as html-text only (no embedded objects like pictures etc.)
The files are cyclic reused, e.g. if you set the cache size to 100, Autosave will store the document contents to X:/MyCache/Autosave_0.html ... AutoSave_100.html and start again with AutoSave_0.htm when the 101st page is browsed. A small Icon in the statusbar will change its colour each time to indicate a page was written.
If you click this small icon, the current page will be dumped, regardless if the site is in the autosave list or not.
NOTE: this extension is really, really simple! Only plain text is saved, no external .css,.js => the result may look ugly! The one and only intention for this extension is, to save the text for external parsing or similar! Look for Scrapbook etc. in case you want to store more than the plain text!
Download (0.009MB)
Added: 2007-04-03 License: MPL (Mozilla Public License) Price:
973 downloads
Personel Document Manager 0.6
Personel Document Manager (or PDM for short) is a simple easy to use document management system. more>>
Personel Document Manager (or PDM for short) is a simple easy to use document management system using platform independent programming to make it work in both worlds, Windows and Linux.
It supports archiving from scanner as well as from file, mailing, editing and printing out of the application using the computers default applications on the running system. So for example, if you choosed Gimp as your favorite program for images in your Operating System, PDM will open a document you want to edit in Gimp -> without any need for configuration.
On this page you can download the Program, access the projects forums and of cause make donations to the project.
<<lessIt supports archiving from scanner as well as from file, mailing, editing and printing out of the application using the computers default applications on the running system. So for example, if you choosed Gimp as your favorite program for images in your Operating System, PDM will open a document you want to edit in Gimp -> without any need for configuration.
On this page you can download the Program, access the projects forums and of cause make donations to the project.
Download (23.7MB)
Added: 2007-08-12 License: GPL (GNU General Public License) Price:
807 downloads
Biblio::Document::Parser 1.10
Biblio::Document::Parser Perl module is a document parsing framework. more>>
Biblio::Document::Parser Perl module is a document parsing framework.
Biblio::Document::Parser provides generic methods that should be overriden by specific parsers. This class should not be used directly, but rather be overridden by specific parsers. Parsers that extend the Document::Parser class should at least override the parse method.
METHODS
$docparser = Biblio::Document::Parser->new()
The new() method creates a new parser instance.
@references = $parser->parse($lines, %options)
The parse() method takes either a content string or an IO::Handle, and returns an array of reference strings.
<<lessBiblio::Document::Parser provides generic methods that should be overriden by specific parsers. This class should not be used directly, but rather be overridden by specific parsers. Parsers that extend the Document::Parser class should at least override the parse method.
METHODS
$docparser = Biblio::Document::Parser->new()
The new() method creates a new parser instance.
@references = $parser->parse($lines, %options)
The parse() method takes either a content string or an IO::Handle, and returns an array of reference strings.
Download (0.19MB)
Added: 2007-04-02 License: Perl Artistic License Price:
935 downloads
KinoSearch::Document::Doc 0.15
KinoSearch::Document::Doc is a Doc object that is akin to a row in a database, in that it is made up of several fields. more>>
KinoSearch::Document::Doc is a Doc object that is akin to a row in a database, in that it is made up of several fields, each of which has a value. Doc objects are only created via factory methods of other classes.
SYNOPSIS
my $doc = $invindexer->new_doc;
$doc->set_value( title => $title );
$doc->set_value( bodytext => $bodytext );
$invindexer->add($doc);
METHODS
set_value get_value
$doc->set_value( title => $title_text );
my $text = $doc->get_value( title );
set_value and get_value are used to modify and access the values of the fields within a Doc object.
set_boost get_boost
$doc->set_boost(2.5);
boost is a scoring multiplier. Setting boost to something other than 1 causes a document to score better or worse against a given query relative to other documents.
<<lessSYNOPSIS
my $doc = $invindexer->new_doc;
$doc->set_value( title => $title );
$doc->set_value( bodytext => $bodytext );
$invindexer->add($doc);
METHODS
set_value get_value
$doc->set_value( title => $title_text );
my $text = $doc->get_value( title );
set_value and get_value are used to modify and access the values of the fields within a Doc object.
set_boost get_boost
$doc->set_boost(2.5);
boost is a scoring multiplier. Setting boost to something other than 1 causes a document to score better or worse against a given query relative to other documents.
Download (0.22MB)
Added: 2007-03-09 License: Perl Artistic License Price:
959 downloads
XML::DOM::DocumentType 1.44
XML::DOM::DocumentType is an XML document type (DTD) in XML::DOM. more>>
XML::DOM::DocumentType is an XML document type (DTD) in XML::DOM.
XML::DOM::DocumentType extends XML::DOM::Node.
Each Document has a doctype attribute whose value is either null or a DocumentType object. The DocumentType interface in the DOM Level 1 Core provides an interface to the list of entities that are defined for the document, and little else because the effect of namespaces and the various XML scheme efforts on DTD representation are not clearly understood as of this writing. The DOM Level 1 doesnt support editing DocumentType nodes.
Not In DOM Spec: This implementation has added a lot of extra functionality to the DOM Level 1 interface. To allow editing of the DocumentType nodes, see XML::DOM::ignoreReadOnly.
<<lessXML::DOM::DocumentType extends XML::DOM::Node.
Each Document has a doctype attribute whose value is either null or a DocumentType object. The DocumentType interface in the DOM Level 1 Core provides an interface to the list of entities that are defined for the document, and little else because the effect of namespaces and the various XML scheme efforts on DTD representation are not clearly understood as of this writing. The DOM Level 1 doesnt support editing DocumentType nodes.
Not In DOM Spec: This implementation has added a lot of extra functionality to the DOM Level 1 interface. To allow editing of the DocumentType nodes, see XML::DOM::ignoreReadOnly.
Download (0.11MB)
Added: 2006-07-17 License: Perl Artistic License Price:
1194 downloads
XML::DOM::Lite::Document 0.10
Document is a XML DOM Lite Document. more>>
Document is a XML DOM Lite Document.
SYNOPSIS
$root = $doc->documentElement;
$node = $doc->getElementById("myid");
# Node creation
$element = $doc->createElement("tagname");
$textnode = $doc->createTextNode("some text");
# XPath
$nlist = $doc->selectNodes("/xpath/expression");
$node = $doc->selectSingleNode("/xpath/expression");
XML::DOM::Lite::Document objects are returned by the Parser and shouldnt generally be instantiated explicitly.
<<lessSYNOPSIS
$root = $doc->documentElement;
$node = $doc->getElementById("myid");
# Node creation
$element = $doc->createElement("tagname");
$textnode = $doc->createTextNode("some text");
# XPath
$nlist = $doc->selectNodes("/xpath/expression");
$node = $doc->selectSingleNode("/xpath/expression");
XML::DOM::Lite::Document objects are returned by the Parser and shouldnt generally be instantiated explicitly.
Download (0.031MB)
Added: 2006-07-14 License: GPL (GNU General Public License) Price:
1197 downloads
Print OpenOffice 2 documents 1
Print OpenOffice 2 documents is a service menu that enables the user to right click on an OpenOffice 2 document and print it. more>>
Print OpenOffice 2 documents is a service menu that enables the user to right click on an OpenOffice 2 document and print it.
<<less Download (MB)
Added: 2006-05-25 License: GPL (GNU General Public License) Price:
1247 downloads
OpenOffice::OODoc::Document 2.027
OpenOffice::OODoc::Document is a top level component for content and layout processing. more>>
OpenOffice::OODoc::Document is a top level component for content and layout processing.
SYNOPSIS
# get an OOo file handler
my $oofile = ooFile("myfile.odt");
# connect a content-focused document interface
my $content = ooDocument
(
file => $oofile,
member => content
);
# connect a style-focused document interface
my $styles = ooDocument
(
file => $oofile,
member => styles
);
# process any content and style element
$content->appendParagraph
(
text => "An additional paragraph",
style => "BlueStyle"
);
$styles->createStyle
(
"BlueStyle",
parent => Text body,
family => paragraph,
properties =>
{
area => text,
fo:color => rgb2oo(blue)
}
);
# commit the changes using the file handler
$oofile->save;
This module defines the top level Document class, which is a connector allowing any kind of content and presentation processing. It inherits from OODoc::XPath, OODoc::Text, OODoc::Styles and OODoc::Image.
The most usual instruction to get access to any member of a document, with the exception if the metadata (meta.xml) should be something like:
my $doc = ooDocument([options]);
This constructor, if successful, returns an object that can be used (according to its "member" option) to process styles, images and text.
This module is designed simply to create objects which include all the functionality of OODoc::Text, OODoc::Image, OODoc::Styles and OODoc::XPath (which should not be called directly by applications).
For example
my $styles = ooDocument(file => "source.odt", member => "styles");
is generally better than
my styles = ooStyles(file => "source.odt");
While OODoc::Document inherits all the methods and properties of these classes, its detailed documentation in essentially provided in the following manual pages:
OpenOffice::OODoc::Text -> text content
OpenOffice::OODoc::Styles -> style & layout
OpenOffice::OODoc::Image -> graphic objects
OpenOffice::OODoc::XPath -> common features & low-level API
For example, the appendParagraph() and createStyle() methods used in the synopsis above are respectively described in OpenOffice::OODoc::Text and OpenOffice::OODoc::Styles.
The present manual page only describes those methods (there are very few) which combine layout and content processing.
<<lessSYNOPSIS
# get an OOo file handler
my $oofile = ooFile("myfile.odt");
# connect a content-focused document interface
my $content = ooDocument
(
file => $oofile,
member => content
);
# connect a style-focused document interface
my $styles = ooDocument
(
file => $oofile,
member => styles
);
# process any content and style element
$content->appendParagraph
(
text => "An additional paragraph",
style => "BlueStyle"
);
$styles->createStyle
(
"BlueStyle",
parent => Text body,
family => paragraph,
properties =>
{
area => text,
fo:color => rgb2oo(blue)
}
);
# commit the changes using the file handler
$oofile->save;
This module defines the top level Document class, which is a connector allowing any kind of content and presentation processing. It inherits from OODoc::XPath, OODoc::Text, OODoc::Styles and OODoc::Image.
The most usual instruction to get access to any member of a document, with the exception if the metadata (meta.xml) should be something like:
my $doc = ooDocument([options]);
This constructor, if successful, returns an object that can be used (according to its "member" option) to process styles, images and text.
This module is designed simply to create objects which include all the functionality of OODoc::Text, OODoc::Image, OODoc::Styles and OODoc::XPath (which should not be called directly by applications).
For example
my $styles = ooDocument(file => "source.odt", member => "styles");
is generally better than
my styles = ooStyles(file => "source.odt");
While OODoc::Document inherits all the methods and properties of these classes, its detailed documentation in essentially provided in the following manual pages:
OpenOffice::OODoc::Text -> text content
OpenOffice::OODoc::Styles -> style & layout
OpenOffice::OODoc::Image -> graphic objects
OpenOffice::OODoc::XPath -> common features & low-level API
For example, the appendParagraph() and createStyle() methods used in the synopsis above are respectively described in OpenOffice::OODoc::Text and OpenOffice::OODoc::Styles.
The present manual page only describes those methods (there are very few) which combine layout and content processing.
Download (0.21MB)
Added: 2006-08-29 License: Perl Artistic License Price:
1152 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above document search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed