xml output
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 4012
XML::Output 0.03
XML::Output is a Perl module for writing simple XML documents. more>>
XML::Output is a Perl module for writing simple XML documents.
SYNOPSIS
use XML::Output;
open(FH,>file.xml);
my $xo = new XML::Output({fh => *FH});
$xo->open(tagname, {attrname => attrval});
$xo->pcdata(element content);
$xo->close();
close(FH);
ABSTRACT
XML::Output is a Perl module for writing simple XML documents
XML::Output is a Perl module for writing simple XML document. The following methods are provided.
new
$xo = new XML::Output;
Constructs a new XML::Output object.
open
$xo->open(tagname, {attrname => attrval});
Open an element with specified name (and optional attributes)
close
$xo->close;
Close an element
empty
$xo->empty(tagname, {attrname => attrval});
Insert an empty element with specified name (and optional attributes)
pcdata
$xo->pcdata(element content);
Insert text
comment
$xo->comment(comment text);
Insert a comment
xmlstr
print $xo->xmlstr;
Get a string representation of the constructed document
<<lessSYNOPSIS
use XML::Output;
open(FH,>file.xml);
my $xo = new XML::Output({fh => *FH});
$xo->open(tagname, {attrname => attrval});
$xo->pcdata(element content);
$xo->close();
close(FH);
ABSTRACT
XML::Output is a Perl module for writing simple XML documents
XML::Output is a Perl module for writing simple XML document. The following methods are provided.
new
$xo = new XML::Output;
Constructs a new XML::Output object.
open
$xo->open(tagname, {attrname => attrval});
Open an element with specified name (and optional attributes)
close
$xo->close;
Close an element
empty
$xo->empty(tagname, {attrname => attrval});
Insert an empty element with specified name (and optional attributes)
pcdata
$xo->pcdata(element content);
Insert text
comment
$xo->comment(comment text);
Insert a comment
xmlstr
print $xo->xmlstr;
Get a string representation of the constructed document
Download (0.035MB)
Added: 2006-09-07 License: GPL (GNU General Public License) Price:
1144 downloads
xmlenc 0.52
xmlenc provides a light-weight XML output library for Java. more>>
xmlenc provides a light-weight XML output library for Java.
It fills the gap between a light-weight parser like SAX, and a heavy-weight XML output library, like JDOM.
<<lessIt fills the gap between a light-weight parser like SAX, and a heavy-weight XML output library, like JDOM.
Download (0.10MB)
Added: 2007-02-23 License: BSD License Price:
974 downloads
XML::DOM::Lite::XSLT 0.15
XML::DOM::Lite::XSLT is Perl module XSLT engine for XML::DOM::Lite. more>>
[COPYRIGHT]
SYNOPSIS
use XML::DOM::Lite qw(Parser XSLT);
$parser = Parser->new( whitespace => strip );
$xsldoc = $parser->parse($xsl);
$xmldoc = $parser->parse($xml);
$output = XSLT->process($xmldoc, $xsldoc);
<<lessSYNOPSIS
use XML::DOM::Lite qw(Parser XSLT);
$parser = Parser->new( whitespace => strip );
$xsldoc = $parser->parse($xsl);
$xmldoc = $parser->parse($xml);
$output = XSLT->process($xmldoc, $xsldoc);
Download (0.031MB)
Added: 2006-11-30 License: Perl Artistic License Price:
1059 downloads
XML::ValidWriter 0.39
XML::ValidWriter is DOCTYPE driven valid XML output. more>>
XML::ValidWriter is DOCTYPE driven valid XML output.
SYNOPSIS
## As a normal perl object:
$writer = XML::ValidWriter->new(
DOCTYPE => $xml_doc_type,
OUTPUT => *FH
) ;
$writer->startTag( b1 ) ;
$writer->startTag( c2 ) ;
$writer->end ;
## Writing to a scalar:
$writer = XML::ValidWriter->new(
DOCTYPE => $xml_doc_type,
OUTPUT => $buf
) ;
## Or, in scripting mode:
use XML::Doctype NAME => a, SYSTEM_ID => a.dtd ;
use XML::ValidWriter qw( :all :dtd_tags ) ;
b1 ; # Emits < a >< b1 >
c2( attr=>"val" ) ; # Emits < /b1 >< b2 >< c2 attr="val" >
endAllTags ; # Emits < /c2 >< /b2 >< /a >
## If youve got an XML::Doctype object handy:
use XML::ValidWriter qw( :dtd_tags ), DOCTYPE => $doctype ;
## If youve saved a preparsed DTD as a perl module
use FooML::Doctype::v1_0001 ;
use XML::ValidWriter qw( :dtd_tags ) ;
#
# This all assumes that the DTD contains:
#
# < !ELEMENT a ( b1, b2?, b3* ) >
#
# < !ELEMENT b1 ( c1 ) >
# < !ELEMENT b2 ( c2 ) >
#
STATUS
Alpha. Use and patch, dont depend on things not changing drastically.
Many methods supplied by XML::Writer are not yet supplied here.
<<lessSYNOPSIS
## As a normal perl object:
$writer = XML::ValidWriter->new(
DOCTYPE => $xml_doc_type,
OUTPUT => *FH
) ;
$writer->startTag( b1 ) ;
$writer->startTag( c2 ) ;
$writer->end ;
## Writing to a scalar:
$writer = XML::ValidWriter->new(
DOCTYPE => $xml_doc_type,
OUTPUT => $buf
) ;
## Or, in scripting mode:
use XML::Doctype NAME => a, SYSTEM_ID => a.dtd ;
use XML::ValidWriter qw( :all :dtd_tags ) ;
b1 ; # Emits < a >< b1 >
c2( attr=>"val" ) ; # Emits < /b1 >< b2 >< c2 attr="val" >
endAllTags ; # Emits < /c2 >< /b2 >< /a >
## If youve got an XML::Doctype object handy:
use XML::ValidWriter qw( :dtd_tags ), DOCTYPE => $doctype ;
## If youve saved a preparsed DTD as a perl module
use FooML::Doctype::v1_0001 ;
use XML::ValidWriter qw( :dtd_tags ) ;
#
# This all assumes that the DTD contains:
#
# < !ELEMENT a ( b1, b2?, b3* ) >
#
# < !ELEMENT b1 ( c1 ) >
# < !ELEMENT b2 ( c2 ) >
#
STATUS
Alpha. Use and patch, dont depend on things not changing drastically.
Many methods supplied by XML::Writer are not yet supplied here.
Download (0.028MB)
Added: 2006-09-13 License: Perl Artistic License Price:
1137 downloads
WebalizerXML 0.1
WebalizerXML provides a patch for making Webalizer produce XML output. more>>
WebalizerXML provides a patch for making Webalizer produce XML output.
WebalizerXML is a simple patch for Webalizer that makes it possible to generate XML stats instead of regular HTML files.
It is very useful if you want to show your stats using your own templates or graphics.
It works only on Webalizer 2.01-10.
<<lessWebalizerXML is a simple patch for Webalizer that makes it possible to generate XML stats instead of regular HTML files.
It is very useful if you want to show your stats using your own templates or graphics.
It works only on Webalizer 2.01-10.
Download (0.089MB)
Added: 2007-01-30 License: GPL (GNU General Public License) Price:
997 downloads
MARC::XML 0.4
MARC::XML is a subclass of MARC.pm to provide XML support. more>>
MARC::XML is a subclass of MARC.pm to provide XML support.
SYNOPSIS
use MARC::XML;
#read in some MARC and output some XML
$myobject = MARC::XML->new("marc.mrc","usmarc");
$myobject->output({file=>">marc.xml",format=>"xml"});
#read in some XML and output some MARC
$myobject = MARC::XML->new("marc.xml","xml");
$myobject->output({file=>">marc.mrc","usmarc");
MARC::XML is a subclass of MARC.pm which provides methods for round-trip conversions between MARC and XML. MARC::XML requires that you have the CPAN modules MARC.pm and XML::Parser installed in your Perl library. Version 1.04 of MARC.pm and 2.27 of XML::Parser (or later) are required. As a subclass of MARC.pm a MARC::XML object will by default have the full functionality of a MARC.pm object. See the MARC.pm documentation for details.
The XML file that is read and generated by MARC::XML is not associated with a Document Type Definition (DTD). This means that your files need to be well-formed, but they will not be validated. When performing XML->MARC conversion it is important that the XML file is structured in a particular way. Fortunately, this is the same format that is generated by the MARC->XML conversion, so you should be able to be able to move your data easily between the two formats.
<<lessSYNOPSIS
use MARC::XML;
#read in some MARC and output some XML
$myobject = MARC::XML->new("marc.mrc","usmarc");
$myobject->output({file=>">marc.xml",format=>"xml"});
#read in some XML and output some MARC
$myobject = MARC::XML->new("marc.xml","xml");
$myobject->output({file=>">marc.mrc","usmarc");
MARC::XML is a subclass of MARC.pm which provides methods for round-trip conversions between MARC and XML. MARC::XML requires that you have the CPAN modules MARC.pm and XML::Parser installed in your Perl library. Version 1.04 of MARC.pm and 2.27 of XML::Parser (or later) are required. As a subclass of MARC.pm a MARC::XML object will by default have the full functionality of a MARC.pm object. See the MARC.pm documentation for details.
The XML file that is read and generated by MARC::XML is not associated with a Document Type Definition (DTD). This means that your files need to be well-formed, but they will not be validated. When performing XML->MARC conversion it is important that the XML file is structured in a particular way. Fortunately, this is the same format that is generated by the MARC->XML conversion, so you should be able to be able to move your data easily between the two formats.
Download (0.050MB)
Added: 2007-07-17 License: Perl Artistic License Price:
830 downloads
XML::DifferenceMarkup 1.00
XML::DifferenceMarkup is a XML diff and merge. more>>
XML::DifferenceMarkup is a XML diff and merge.
SYNOPSIS
use XML::DifferenceMarkup qw(make_diff);
$parser = XML::LibXML->new();
$parser->keep_blanks(0);
$d1 = $parser->parse_file($fname1);
$d2 = $parser->parse_file($fname2);
$dom = make_diff($d1, $d2);
print $dom->toString(1);
This module implements an XML diff producing XML output. Both input and output are DOM documents, as implemented by XML::LibXML.
The diff format used by XML::DifferenceMarkup is meant to be human-readable (i.e. simple, as opposed to short) - basically the diff is a subset of the input trees, annotated with instruction element nodes specifying how to convert the source tree to the target by inserting and deleting nodes. To prevent name colisions with input trees, all added elements are in a namespace http://www.locus.cz/diffmark (the diff will fail on input trees which already use that namespace).
<<lessSYNOPSIS
use XML::DifferenceMarkup qw(make_diff);
$parser = XML::LibXML->new();
$parser->keep_blanks(0);
$d1 = $parser->parse_file($fname1);
$d2 = $parser->parse_file($fname2);
$dom = make_diff($d1, $d2);
print $dom->toString(1);
This module implements an XML diff producing XML output. Both input and output are DOM documents, as implemented by XML::LibXML.
The diff format used by XML::DifferenceMarkup is meant to be human-readable (i.e. simple, as opposed to short) - basically the diff is a subset of the input trees, annotated with instruction element nodes specifying how to convert the source tree to the target by inserting and deleting nodes. To prevent name colisions with input trees, all added elements are in a namespace http://www.locus.cz/diffmark (the diff will fail on input trees which already use that namespace).
Download (0.056MB)
Added: 2007-08-17 License: Perl Artistic License Price:
798 downloads
XML::Writer 0.601
XML::Writer is a Perl extension for writing XML documents. more>>
XML::Writer is a Perl extension for writing XML documents.
SYNOPSIS
use XML::Writer;
use IO::File;
my $output = new IO::File(">output.xml");
my $writer = new XML::Writer(OUTPUT => $output);
$writer->startTag("greeting",
"class" => "simple");
$writer->characters("Hello, world!");
$writer->endTag("greeting");
$writer->end();
$output->close();
XML::Writer is a helper module for Perl programs that write an XML document. The module handles all escaping for attribute values and character data and constructs different types of markup, such as tags, comments, and processing instructions.
By default, the module performs several well-formedness checks to catch errors during output. This behaviour can be extremely useful during development and debugging, but it can be turned off for production-grade code.
The module can operate either in regular mode in or Namespace processing mode. In Namespace mode, the module will generate Namespace Declarations itself, and will perform additional checks on the output.
Additional support is available for a simplified data mode with no mixed content: newlines are automatically inserted around elements and elements can optionally be indented based as their nesting level.
<<lessSYNOPSIS
use XML::Writer;
use IO::File;
my $output = new IO::File(">output.xml");
my $writer = new XML::Writer(OUTPUT => $output);
$writer->startTag("greeting",
"class" => "simple");
$writer->characters("Hello, world!");
$writer->endTag("greeting");
$writer->end();
$output->close();
XML::Writer is a helper module for Perl programs that write an XML document. The module handles all escaping for attribute values and character data and constructs different types of markup, such as tags, comments, and processing instructions.
By default, the module performs several well-formedness checks to catch errors during output. This behaviour can be extremely useful during development and debugging, but it can be turned off for production-grade code.
The module can operate either in regular mode in or Namespace processing mode. In Namespace mode, the module will generate Namespace Declarations itself, and will perform additional checks on the output.
Additional support is available for a simplified data mode with no mixed content: newlines are automatically inserted around elements and elements can optionally be indented based as their nesting level.
Download (0.022MB)
Added: 2006-09-14 License: Perl Artistic License Price:
1136 downloads
text-vimcolor 0.11
text-vimcolor is a command-line program to syntax color a file in HTML, XML or PDF. more>>
text-vimcolor is a command-line program to syntax color a file in HTML, XML or PDF.
SYNOPSIS
$ text-vimcolor --format html --full-page FILENAME > OUTPUT.html
$ text-vimcolor --format xml FILENAME > OUTPUT.xml
$ text-vimcolor --format pdf FILENAME --output OUTPUT.pdf
This program uses the Vim text editor to highlight text according to its syntax, and turn the highlighting into HTML, XML or PDF output. It works with any file type which Vim itself can highlight. Usually Vim will be able to autodetect the file format based on the filename (and sometimes the contents of the file).
Exactly one filename should be given on the command line to name the input file. If none is given input will instead be read from stdin (the standard input).
If Vim cant guess the file type automatically, it can be specified explicitly using the --filetype option. For example:
$ text-vimcolor --format html --filetype prolog foo.pl > foo.html
This program is a command line interface to the Perl module Text::VimColor.
OPTIONS
The following options are understood:
--help
Show a summary of the usage, including a list of options.
--debug
Turns on debugging in the underlying Perl module. This makes it print the command used to run Vim.
--filetype file-type
Set the type of the file explicitly. The file-type argument should be something which Vim will recognise when set with its filetype option. Examples are perl, cpp (for C++) and sh (for Unix shell scripts). These names are case sensitive, and should usually be all-lowercase.
--format output-format
The output format to generate. Must be one of the following:
html
Generate XHTML output, with text marked with elements with class attributes. A CSS stylesheet should be used to define the coloring, etc., for the output. See the --full-page option below.
xml
Output is in a simple XML vocabulary. This can then be used by other software to do further transformations (e.g., using XSLT).
pdf
XML output is generated and fed to the FOP XSL-FO processor, with an appropriate XSL style sheet. The stylesheet uses XSLT to transform the normal XML output into XSL-FO, which is then rendered to PDF. For this to work, the command fop must be available. An output file must be specified with --output with this format.
Full details of the HTML and XML output formats can be found in the documentation for Text::VimColor.
--output output-filename
Specifies the name of the output file (which will end up containing either HTML, XML or PDF). If this option is omitted, the output will be sent to stdout (the standard output). This option is required when the output format is PDF (because of limitations in FOP).
--full-page
When the output format is HTML, this option will make the output a complete HTML page, rather than just a fragment of HTML. A CSS stylesheet will be inserted inline into the output, so the output will be useable as it is.
--no-inline-stylesheet
When the output format is HTML and --fullpage is given, a stylesheet is normally inserted in-line in the output file. If this option is given it will instead be referenced with a element.
--let name=value
When Vim is run the value of name will be set to value using Vims let command. More than one of these options can be set. The value is not quoted or escaped in any way, so it can be an expression. These settings take precedence over --unlet options.
This option corresponds to the vim_let setting and method in the Perl module.
--unlet name
Prevent the value of name being set with Vims let command. This can be used to turn off default settings.
This option corresponds to the vim_let setting and method in the Perl module, when used with a value of undef.
<<lessSYNOPSIS
$ text-vimcolor --format html --full-page FILENAME > OUTPUT.html
$ text-vimcolor --format xml FILENAME > OUTPUT.xml
$ text-vimcolor --format pdf FILENAME --output OUTPUT.pdf
This program uses the Vim text editor to highlight text according to its syntax, and turn the highlighting into HTML, XML or PDF output. It works with any file type which Vim itself can highlight. Usually Vim will be able to autodetect the file format based on the filename (and sometimes the contents of the file).
Exactly one filename should be given on the command line to name the input file. If none is given input will instead be read from stdin (the standard input).
If Vim cant guess the file type automatically, it can be specified explicitly using the --filetype option. For example:
$ text-vimcolor --format html --filetype prolog foo.pl > foo.html
This program is a command line interface to the Perl module Text::VimColor.
OPTIONS
The following options are understood:
--help
Show a summary of the usage, including a list of options.
--debug
Turns on debugging in the underlying Perl module. This makes it print the command used to run Vim.
--filetype file-type
Set the type of the file explicitly. The file-type argument should be something which Vim will recognise when set with its filetype option. Examples are perl, cpp (for C++) and sh (for Unix shell scripts). These names are case sensitive, and should usually be all-lowercase.
--format output-format
The output format to generate. Must be one of the following:
html
Generate XHTML output, with text marked with elements with class attributes. A CSS stylesheet should be used to define the coloring, etc., for the output. See the --full-page option below.
xml
Output is in a simple XML vocabulary. This can then be used by other software to do further transformations (e.g., using XSLT).
XML output is generated and fed to the FOP XSL-FO processor, with an appropriate XSL style sheet. The stylesheet uses XSLT to transform the normal XML output into XSL-FO, which is then rendered to PDF. For this to work, the command fop must be available. An output file must be specified with --output with this format.
Full details of the HTML and XML output formats can be found in the documentation for Text::VimColor.
--output output-filename
Specifies the name of the output file (which will end up containing either HTML, XML or PDF). If this option is omitted, the output will be sent to stdout (the standard output). This option is required when the output format is PDF (because of limitations in FOP).
--full-page
When the output format is HTML, this option will make the output a complete HTML page, rather than just a fragment of HTML. A CSS stylesheet will be inserted inline into the output, so the output will be useable as it is.
--no-inline-stylesheet
When the output format is HTML and --fullpage is given, a stylesheet is normally inserted in-line in the output file. If this option is given it will instead be referenced with a element.
--let name=value
When Vim is run the value of name will be set to value using Vims let command. More than one of these options can be set. The value is not quoted or escaped in any way, so it can be an expression. These settings take precedence over --unlet options.
This option corresponds to the vim_let setting and method in the Perl module.
--unlet name
Prevent the value of name being set with Vims let command. This can be used to turn off default settings.
This option corresponds to the vim_let setting and method in the Perl module, when used with a value of undef.
Download (0.020MB)
Added: 2007-05-31 License: Perl Artistic License Price:
876 downloads
XMLNews::HTMLTemplate 0.01
XMLNews::HTMLTemplate is Perl module for converting NITF to HTML. more>>
XMLNews::HTMLTemplate is Perl module for converting NITF to HTML.
SYNOPSIS
use XMLNews::HTMLTemplate;
my $template = new XMLNews::HTMLTemplate();
$template->readTemplate("mytemplate.html");
$template->applyTemplate("output.html", "story.xml", "story.rdf");
NOTE: this module requires the XML::Parser and XMLNews::Meta modules.
WARNING: this module is not thread-safe or re-entrant.
The XMLNews::HTMLTemplate module provides a simple mechanism for creating HTML pages from XML/NITF news stories and/or XML/RDF metadata files based on a user-supplied template file. The template is a simple HTML file (SGML or XML flavour) using special template commands, which the user includes as processing instructions, as in the following example:
To create an HTML page, you must first create an empty HTMLTemplate object:
my $template = new XMLNews::HTMLTemplate();
Next, you load the HTML template into the object:
$template->readTemplate("mytemplate.html");
Now, you can apply the same compiled template object repeatedly to different XML/NITF and/or XML/RDF documents to generate HTML pages:
$template->applyTemplate("outfile.html", "newsstory.xml", "newsstory.rdf");
<<lessSYNOPSIS
use XMLNews::HTMLTemplate;
my $template = new XMLNews::HTMLTemplate();
$template->readTemplate("mytemplate.html");
$template->applyTemplate("output.html", "story.xml", "story.rdf");
NOTE: this module requires the XML::Parser and XMLNews::Meta modules.
WARNING: this module is not thread-safe or re-entrant.
The XMLNews::HTMLTemplate module provides a simple mechanism for creating HTML pages from XML/NITF news stories and/or XML/RDF metadata files based on a user-supplied template file. The template is a simple HTML file (SGML or XML flavour) using special template commands, which the user includes as processing instructions, as in the following example:
To create an HTML page, you must first create an empty HTMLTemplate object:
my $template = new XMLNews::HTMLTemplate();
Next, you load the HTML template into the object:
$template->readTemplate("mytemplate.html");
Now, you can apply the same compiled template object repeatedly to different XML/NITF and/or XML/RDF documents to generate HTML pages:
$template->applyTemplate("outfile.html", "newsstory.xml", "newsstory.rdf");
Download (0.009MB)
Added: 2006-09-13 License: Perl Artistic License Price:
1136 downloads
PyGNUGK 3.60
PyGNUGK is both a command line tool, a CGI script which can connect to GNU Gatekeepers status port. more>>
PyGNUGK is both a command line tool, a CGI script, and a set of Python classes available as a Python module, which can connect to GNU Gatekeepers status port and return informations about whats there.
PyGNUGK project can currently report the list of registered endpoints and ongoing calls, but more features will be added in the future.
The report can currently be made either in plain text or in XML format.
Command line usage:
$ pygnugk [--xml] [gkhost] [gkport]
* --xml gives an XML report, otherwise plain text is assumed.
* gkhost defaults to localhost.
* gkport defaults to 7000.
CGI usage:
Copy the pygnugk command line tool from /usr/bin to /usr/lib/cgi-bin or create a symlink there.
From your web browser all of these are allowed :
http://yourserver/cgi-bin/pygnugk?host=gkhost&port=gkport
http://yourserver/cgi-bin/pygnugk?host=gkhost&port=gkport&format=xml
http://yourserver/cgi-bin/pygnugk
This one defaults to localhost, port 7000 and format plain
Python module usage:
--- CUT ---
from gnugklib import gnugk
gk = gnugk.GNUGK(host="localhost", port=7000)
# Complete XML output (will grab endpoints and calls automatically) :
print gk.xml()
# Complete text output :
endpoints = gk.getEndPoints()
for endpoint in endpoints :
print endpoint
for call in gk.getCalls() :
print call
# outputs only first endpoint as XML (works with calls too)
if endpoints :
print endpoints[0].xml()
--- CUT ---
Installation:
Download pygnugk from :
http://cortex.unice.fr/~jerome/pygnugk/
and extract it :
$ tar -zxf pygnugk-x.yy.tar.gz
where x.yy is pygnugks version number.
Run the installation script :
$ python setup.py install
This will usually install the pygnugk into /usr/bin and the library into /usr/lib/python2.?/site-packages/gnugk/
Thats all !
NB : if you want to use XML output, you MUST download the jaxml Python module from http://www.librelogiciel.com/software/
If you use a Debian based distribution : apt-get install jaxml
<<lessPyGNUGK project can currently report the list of registered endpoints and ongoing calls, but more features will be added in the future.
The report can currently be made either in plain text or in XML format.
Command line usage:
$ pygnugk [--xml] [gkhost] [gkport]
* --xml gives an XML report, otherwise plain text is assumed.
* gkhost defaults to localhost.
* gkport defaults to 7000.
CGI usage:
Copy the pygnugk command line tool from /usr/bin to /usr/lib/cgi-bin or create a symlink there.
From your web browser all of these are allowed :
http://yourserver/cgi-bin/pygnugk?host=gkhost&port=gkport
http://yourserver/cgi-bin/pygnugk?host=gkhost&port=gkport&format=xml
http://yourserver/cgi-bin/pygnugk
This one defaults to localhost, port 7000 and format plain
Python module usage:
--- CUT ---
from gnugklib import gnugk
gk = gnugk.GNUGK(host="localhost", port=7000)
# Complete XML output (will grab endpoints and calls automatically) :
print gk.xml()
# Complete text output :
endpoints = gk.getEndPoints()
for endpoint in endpoints :
print endpoint
for call in gk.getCalls() :
print call
# outputs only first endpoint as XML (works with calls too)
if endpoints :
print endpoints[0].xml()
--- CUT ---
Installation:
Download pygnugk from :
http://cortex.unice.fr/~jerome/pygnugk/
and extract it :
$ tar -zxf pygnugk-x.yy.tar.gz
where x.yy is pygnugks version number.
Run the installation script :
$ python setup.py install
This will usually install the pygnugk into /usr/bin and the library into /usr/lib/python2.?/site-packages/gnugk/
Thats all !
NB : if you want to use XML output, you MUST download the jaxml Python module from http://www.librelogiciel.com/software/
If you use a Debian based distribution : apt-get install jaxml
Download (0.012MB)
Added: 2007-02-27 License: GPL (GNU General Public License) Price:
969 downloads
XML::Filter::Tee 0.41
XML::Filter::Tee can send SAX events to multiple processor, with switching. more>>
XML::Filter::Tee can send SAX events to multiple processor, with switching.
SYNOPSIS
my $t = XML::Filter::Tee->new(
{ Handler => $h0 },
{ Handler => $h1 },
{ Handler => $h2 },
...
);
## Altering the handlers list:
$t->set_handlers( $h0, $h1, $h2, $h3 );
## Controlling flow to a handler by number and by reference:
$t->disable_handler( 0 );
$t->enable_handler( 0 );
$t->disable_handler( $h0 );
$t->enable_handler( $h0 );
## Use in a SAX machine (though see L and
## L for a more convenient way to build a machine
## like this):
my $m = Machine(
[ Intake => "XML::Filter::Tee" => qw( A B ) ],
[ A => ">>log.xml" ],
[ B => *OUTPUT ],
);
XML::Filter::Tee is a SAX filter that passes each event it receives on to a list of downstream handlers.
Its like XML::Filter::SAXT in that the events are not buffered; each event is sent first to the tap, and then to the branch (this is different from XML::SAX::Dispatcher, which buffers the events). Unlike XML::Filter::SAXT, it allows its list of handlers to be reconfigured (via "set_handlers") and it allows control over which handlers are allowed to receive events. These features are designed to make XML::Filter::Tee instances more useful with SAX machines, but they to add some overhead relative to XML::Filter::SAXT.
The events are not copied, since they may be data structures that are difficult or impossibly to copy properly, like parts of a C-based DOM implementation. This means that the handlers must not alter the events or later handlers will see the alterations.
<<lessSYNOPSIS
my $t = XML::Filter::Tee->new(
{ Handler => $h0 },
{ Handler => $h1 },
{ Handler => $h2 },
...
);
## Altering the handlers list:
$t->set_handlers( $h0, $h1, $h2, $h3 );
## Controlling flow to a handler by number and by reference:
$t->disable_handler( 0 );
$t->enable_handler( 0 );
$t->disable_handler( $h0 );
$t->enable_handler( $h0 );
## Use in a SAX machine (though see L and
## L for a more convenient way to build a machine
## like this):
my $m = Machine(
[ Intake => "XML::Filter::Tee" => qw( A B ) ],
[ A => ">>log.xml" ],
[ B => *OUTPUT ],
);
XML::Filter::Tee is a SAX filter that passes each event it receives on to a list of downstream handlers.
Its like XML::Filter::SAXT in that the events are not buffered; each event is sent first to the tap, and then to the branch (this is different from XML::SAX::Dispatcher, which buffers the events). Unlike XML::Filter::SAXT, it allows its list of handlers to be reconfigured (via "set_handlers") and it allows control over which handlers are allowed to receive events. These features are designed to make XML::Filter::Tee instances more useful with SAX machines, but they to add some overhead relative to XML::Filter::SAXT.
The events are not copied, since they may be data structures that are difficult or impossibly to copy properly, like parts of a C-based DOM implementation. This means that the handlers must not alter the events or later handlers will see the alterations.
Download (0.042MB)
Added: 2007-08-17 License: Perl Artistic License Price:
798 downloads
PyQStat 1.0
PyQStat project is a Python wrapper around QStat, the realtime game server status tool. more>>
PyQStat project is a Python wrapper around QStat, the realtime game server status tool.
PyQStat invokes QStat via os.popen and parses its XML output mode. Although primarily intended as an importable module for integrating QStat functionality into other applications, PyQStat can also be used from the command line.
<<lessPyQStat invokes QStat via os.popen and parses its XML output mode. Although primarily intended as an importable module for integrating QStat functionality into other applications, PyQStat can also be used from the command line.
Download (0.013MB)
Added: 2006-11-27 License: GPL (GNU General Public License) Price:
1062 downloads
XML::EasySQL 1.2
XML::EasySQL is a two-way SQL/XML base class for Perl. more>>
XML::EasySQL is a two-way SQL/XML base class for Perl.
SYNOPSIS
...
# fetch a database row as hash ref
my $data = $db->selectrow_hashref(select * from users where id = 2);
# init the new EasySQL data object
my $data_object = EasySqlChildClass->new({data=>$data});
# get the root XML element
my $xml = $data_object->getXML();
# make changes to the XML document
$xml->username->setString(curtisleefulton);
$xml->bio->setAttr(age, 22);
$xml->bio->city->setString(Portland);
$xml->history->access->setAttr(last, time());
# output entire XML doc as string to STDOUT
print $xml->getDomObj->toString();
# update the database
my $sql = $data_object->getSQL();
my $q = "update users set ".$sql->{users}." where id = 2";
$db->do($q);
Main features:
- Two-way transforms between XML and SQL data
- smart SQL updates: only altered tables are updated
- unlimited tree depth
- multiple SQL tables can merge intone XML tree, then back again
- precise control over how data is translated
- offers either an easy XML interface or plain DOM
- database independent
<<lessSYNOPSIS
...
# fetch a database row as hash ref
my $data = $db->selectrow_hashref(select * from users where id = 2);
# init the new EasySQL data object
my $data_object = EasySqlChildClass->new({data=>$data});
# get the root XML element
my $xml = $data_object->getXML();
# make changes to the XML document
$xml->username->setString(curtisleefulton);
$xml->bio->setAttr(age, 22);
$xml->bio->city->setString(Portland);
$xml->history->access->setAttr(last, time());
# output entire XML doc as string to STDOUT
print $xml->getDomObj->toString();
# update the database
my $sql = $data_object->getSQL();
my $q = "update users set ".$sql->{users}." where id = 2";
$db->do($q);
Main features:
- Two-way transforms between XML and SQL data
- smart SQL updates: only altered tables are updated
- unlimited tree depth
- multiple SQL tables can merge intone XML tree, then back again
- precise control over how data is translated
- offers either an easy XML interface or plain DOM
- database independent
Download (0.011MB)
Added: 2006-09-12 License: Perl Artistic License Price:
1137 downloads
XML::DOM::Lite 0.10
XML::DOM::Lite is a Lite Pure Perl XML DOM Parser Kit. more>>
XML::DOM::Lite is a Lite Pure Perl XML DOM Parser Kit.
SYNOPSIS
# Parser
use XML::DOM::Lite qw(Parser :constants);
$parser = Parser->new( %options );
$doc = Parser->parse($xmlstr);
$doc = Parser->parseFile(/path/to/file.xml);
# strip whitespace (can be about 30% faster)
$doc = Parser->parse($xml, whitespace => strip);
# All Nodes
$copy = $node->cloneNode($deep);
$nodeType = $node->nodeType;
$parent = $node->parentNode;
$name = $node->nodeName;
$xmlstr = $node->xml;
$owner = $node->ownerDocument;
# Element Nodes
$first = $node->firstChild;
$last = $node->lastChild;
$tag = $node->tagName;
$prev = $node->nextSibling;
$next = $node->previousSibling;
$node->setAttribute("foo", $bar);
$foo = $node->getAttribute("foo");
foreach my $attr (@{$node->attributes}) { # attributes as nodelist
# ... do stuff
}
$node->attributes->{foo} = "bar"; # or as hashref (overload)
$liveNodeList = $node->getElementsByTagName("child"); # deep
$node->insertBefore($newchild, $refchild);
$node->replaceChild($newchild, $refchild);
# Text Nodes
$nodeValue = $node->nodeValue;
$node->nodeValue("new text value");
# Processing Instruction Nodes
# CDATA Nodes
# Comments
$data = $node->nodeValue;
# NodeList
$item = $nodeList->item(42);
$index = $nodeList->nodeIndex($node);
$nlist->insertNode($newNode, $index);
$removed = $nlist->removeNode($node);
$length = $nlist->length; # OR scalar(@$nodeList)
# NodeIterator and NodeFilter
use XML::DOM::Lite qw(NodeIterator :constants);
$niter = NodeIterator->new($rootnode, SHOW_ELEMENT, {
acceptNode => sub {
my $n = shift;
if ($n->tagName eq wantme) {
return FILTER_ACCEPT;
} elsif ($n->tagName eq skipme) {
return FILTER_SKIP;
} else {
return FILTER_REJECT;
}
}
);
while (my $n = $niter->nextNode) {
# do stuff
}
# XSLT
use XML::DOM::Lite qw(Parser XSLT);
$parser = Parser->new( whitespace => strip );
$xsldoc = $parser->parse($xsl);
$xmldoc = $parser->parse($xml);
$output = XSLT->process($xmldoc, $xsldoc);
# XPath
use XML::DOM::Lite qw(XPath);
$result = XPath->evaluate(/path/to/*[@attr="value"], $contextNode);
# Document
$rootnode = $doc->documentElement;
$nodeWithId = $doc->getElementById("my_node_id");
$textnode = $doc->createTextNode("some text string");
$element = $doc->createElement("myTagName");
$docfrag = $doc->createDocumentFragment();
$xmlstr = $doc->xml;
$nlist = $doc->selectNodes(/xpath/expression);
$node = $doc->selectSingleNode(/xpath/expression);
# Serializer
use XML::DOM::Lite qw(Serializer);
$serializer = Serializer->new;
$xmlout = $serializer->serializeToString($node);
<<lessSYNOPSIS
# Parser
use XML::DOM::Lite qw(Parser :constants);
$parser = Parser->new( %options );
$doc = Parser->parse($xmlstr);
$doc = Parser->parseFile(/path/to/file.xml);
# strip whitespace (can be about 30% faster)
$doc = Parser->parse($xml, whitespace => strip);
# All Nodes
$copy = $node->cloneNode($deep);
$nodeType = $node->nodeType;
$parent = $node->parentNode;
$name = $node->nodeName;
$xmlstr = $node->xml;
$owner = $node->ownerDocument;
# Element Nodes
$first = $node->firstChild;
$last = $node->lastChild;
$tag = $node->tagName;
$prev = $node->nextSibling;
$next = $node->previousSibling;
$node->setAttribute("foo", $bar);
$foo = $node->getAttribute("foo");
foreach my $attr (@{$node->attributes}) { # attributes as nodelist
# ... do stuff
}
$node->attributes->{foo} = "bar"; # or as hashref (overload)
$liveNodeList = $node->getElementsByTagName("child"); # deep
$node->insertBefore($newchild, $refchild);
$node->replaceChild($newchild, $refchild);
# Text Nodes
$nodeValue = $node->nodeValue;
$node->nodeValue("new text value");
# Processing Instruction Nodes
# CDATA Nodes
# Comments
$data = $node->nodeValue;
# NodeList
$item = $nodeList->item(42);
$index = $nodeList->nodeIndex($node);
$nlist->insertNode($newNode, $index);
$removed = $nlist->removeNode($node);
$length = $nlist->length; # OR scalar(@$nodeList)
# NodeIterator and NodeFilter
use XML::DOM::Lite qw(NodeIterator :constants);
$niter = NodeIterator->new($rootnode, SHOW_ELEMENT, {
acceptNode => sub {
my $n = shift;
if ($n->tagName eq wantme) {
return FILTER_ACCEPT;
} elsif ($n->tagName eq skipme) {
return FILTER_SKIP;
} else {
return FILTER_REJECT;
}
}
);
while (my $n = $niter->nextNode) {
# do stuff
}
# XSLT
use XML::DOM::Lite qw(Parser XSLT);
$parser = Parser->new( whitespace => strip );
$xsldoc = $parser->parse($xsl);
$xmldoc = $parser->parse($xml);
$output = XSLT->process($xmldoc, $xsldoc);
# XPath
use XML::DOM::Lite qw(XPath);
$result = XPath->evaluate(/path/to/*[@attr="value"], $contextNode);
# Document
$rootnode = $doc->documentElement;
$nodeWithId = $doc->getElementById("my_node_id");
$textnode = $doc->createTextNode("some text string");
$element = $doc->createElement("myTagName");
$docfrag = $doc->createDocumentFragment();
$xmlstr = $doc->xml;
$nlist = $doc->selectNodes(/xpath/expression);
$node = $doc->selectSingleNode(/xpath/expression);
# Serializer
use XML::DOM::Lite qw(Serializer);
$serializer = Serializer->new;
$xmlout = $serializer->serializeToString($node);
Download (0.030MB)
Added: 2006-07-14 License: Perl Artistic License Price:
1199 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 xml output 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