wsdl file
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 197
gFast File 0.1.1
gFast File is a file manager like Nautilus or Konkeror. more>>
gFast File is a file manager like Konqueror or Nautilus. You can work with your files with classical operations: Copy, Move, Rename and Open like others but with gFast File you have a work queue with all your operations. gFast File work to complete all task without your attention.
gFast File is programmed with MONO, C#, GTK# and Glade.
Main features:
- Written in MONO and GTK.
- Under GNU License
- History with all the directories that you visited.
- Bookmarks with your favourites directories.
- Work queue, with Copy, Move and Delete operations. Work without your attention
- Easily add new targets to open files editing know_files.xml file.
<<lessgFast File is programmed with MONO, C#, GTK# and Glade.
Main features:
- Written in MONO and GTK.
- Under GNU License
- History with all the directories that you visited.
- Bookmarks with your favourites directories.
- Work queue, with Copy, Move and Delete operations. Work without your attention
- Easily add new targets to open files editing know_files.xml file.
Download (0.81MB)
Added: 2006-11-08 License: GPL (GNU General Public License) Price:
1082 downloads
wsdlpull 1.14
wsdlpull is an efficient C++ Web services library that includes a standards compliant WSDL parser API. more>>
wsdlpull is a C++ WSDL Library. wsdlpull project includes a WSDL Parser , a XSD Schema
Parser and Validator and XML Parser and serializer and an API for dynamic WSDL inspection and invocation.
wsdlpull uses the xml pull api to parse a WSDL1.1 document. This makes wsdlpull highly efficient which is why you can process and invoke a WSDL in no time.
The parser provides APIs to access various WSDL elements such as operations,messages,bindings,port types. Although wsdlpull is based on the pull parsing style of xml parsing the API is meant to be semantically as close as possible to the standard API for parsing WSDL, namely WSDL4J.
The invocation API allows you to dynamically inspect and invoke a web service. Unlike other toolkits there is no need to generate stubs or type serializers. Writing a web service client involves providing the WSDL URL ,setting the operation ,the input types and getting back the results in just one step.
The schema parser and validator provides an API for parsing XSD schema documents and validating their xml instance documents. The schema parser is used to parse the types section of the WSDL document.
The Xml parser and serializer provide a C++ implementation of the XML Pull API . WSDL processing, XSD schema processing ,creating SOAP messages all use the parser and serializer.
Enhancements:
- Several new features were added, including the ability to validate multiple occurences of choice elements, a new -p option to print port types of a wsdl, a -g option in the wsdl tool to generate soap message, and an experimental -g option in the schema tool to generate instances.
- Fixes were also made for a schema:import bug and for a type reference in an imported schema which is defined in same wsdl file but under another namespace.
<<lessParser and Validator and XML Parser and serializer and an API for dynamic WSDL inspection and invocation.
wsdlpull uses the xml pull api to parse a WSDL1.1 document. This makes wsdlpull highly efficient which is why you can process and invoke a WSDL in no time.
The parser provides APIs to access various WSDL elements such as operations,messages,bindings,port types. Although wsdlpull is based on the pull parsing style of xml parsing the API is meant to be semantically as close as possible to the standard API for parsing WSDL, namely WSDL4J.
The invocation API allows you to dynamically inspect and invoke a web service. Unlike other toolkits there is no need to generate stubs or type serializers. Writing a web service client involves providing the WSDL URL ,setting the operation ,the input types and getting back the results in just one step.
The schema parser and validator provides an API for parsing XSD schema documents and validating their xml instance documents. The schema parser is used to parse the types section of the WSDL document.
The Xml parser and serializer provide a C++ implementation of the XML Pull API . WSDL processing, XSD schema processing ,creating SOAP messages all use the parser and serializer.
Enhancements:
- Several new features were added, including the ability to validate multiple occurences of choice elements, a new -p option to print port types of a wsdl, a -g option in the wsdl tool to generate soap message, and an experimental -g option in the schema tool to generate instances.
- Fixes were also made for a schema:import bug and for a type reference in an imported schema which is defined in same wsdl file but under another namespace.
Download (0.63MB)
Added: 2007-08-05 License: LGPL (GNU Lesser General Public License) Price:
811 downloads
idl2wsdl 0.41
idl2wsdl is an IDL compiler to WSDL (Web Services Description Language). more>>
idl2wsdl is an IDL compiler to WSDL (Web Services Description Language).
SYNOPSIS
idl2wsdl [options] spec.idl
OPTIONS
All options are forwarded to C preprocessor, except -b -h -i -q -s -t -v -x.
With the GNU C Compatible Compiler Processor, useful options are :
-D name
-D name=definition
-I directory
-I-
-nostdinc
Specific options :
-b base uri
Specify a base uri for location of import.
-h
Display help.
-i directory
Specify a path for import (only for IDL version 3.0).
-q
Generate qualified elements.
-s (xsd|rng)
Specify the schema used. By default xsd.
-t
Generate tabulated XML (beautify for human).
-v
Display version.
-x
Enable export (only for IDL version 3.0).
idl2wsdl parses the given input file (IDL) and generates :
a WSDL file spec.wsdl following the CORBA to WSDL/SOAP Interworking Specification (WS-I comformant soap binding).
idl2wsdl is a Perl OO application what uses the visitor design pattern. The parser is generated by Parse::Yapp.
idl2wsdl needs XML::DOM module.
idl2wsdl needs a cpp executable.
<<lessSYNOPSIS
idl2wsdl [options] spec.idl
OPTIONS
All options are forwarded to C preprocessor, except -b -h -i -q -s -t -v -x.
With the GNU C Compatible Compiler Processor, useful options are :
-D name
-D name=definition
-I directory
-I-
-nostdinc
Specific options :
-b base uri
Specify a base uri for location of import.
-h
Display help.
-i directory
Specify a path for import (only for IDL version 3.0).
-q
Generate qualified elements.
-s (xsd|rng)
Specify the schema used. By default xsd.
-t
Generate tabulated XML (beautify for human).
-v
Display version.
-x
Enable export (only for IDL version 3.0).
idl2wsdl parses the given input file (IDL) and generates :
a WSDL file spec.wsdl following the CORBA to WSDL/SOAP Interworking Specification (WS-I comformant soap binding).
idl2wsdl is a Perl OO application what uses the visitor design pattern. The parser is generated by Parse::Yapp.
idl2wsdl needs XML::DOM module.
idl2wsdl needs a cpp executable.
Download (0.016MB)
Added: 2007-05-31 License: Perl Artistic License Price:
545 downloads
Pod::WSDL 0.05
Pod::WSDL is a Perl module that creates WSDL documents from (extended) pod. more>>
Pod::WSDL is a Perl module that creates WSDL documents from (extended) pod.
SYNOPSIS
use Pod::WSDL;
my $pod = new Pod::WSDL(source => My::Server,
location => http://localhost/My/Server,
pretty => 1,
withDocumentation => 1);
print $pod->WSDL;
Parsing the pod
How does Pod::WSDL work? If you instantiate a Pod::WSDL object with the name of the module (or the path of the file, or an open filehandle) providing the web service like this
my $pwsdl = new Pod::WSDL(source => My::Module,
location => http://my.services.location/on/the/web);
Pod::WSDL will try to find My::Module in @INC, open the file, parse it for WSDL directives and prepare the information for WSDL output. By calling
$pwsdl->WSDL;
Pod::WSDL will output the WSDL document. Thats it.
When using Pod::WSDL, the parser expects you to do the following:
Put the pod directly above the subroutines which the web services client is going to call. There may be whitespace between the pod and the sub declaration but nothing else.
Use the =begin/=end respectively the =for directives according to standard pod: anything between =begin WSDL and =end will be treated as pod. Anything composing a paragraph together with =for WSDL will be treated as pod.
Any subroutine not preceeded by WSDL pod will be left unmentioned. Any standard pod will be ignored (though, for an exception to this, see the section on own complex types below).
The individual instructions for Pod::WSDL always begin with a keyword, like _RETURN or _DOC or _FAULT. After this different things may follow, according to the specific type of instruction. The instruction may take one or more lines - everything up to the next line beginning with a keyword or the end of the pod is belonging to the current instruction.
Describing Methods
How do we use Pod::WSDL? In describing a web services method we have to say something about parameters, return values and faults. In addition you might want to add some documentation to these items and to the method itself.
<<lessSYNOPSIS
use Pod::WSDL;
my $pod = new Pod::WSDL(source => My::Server,
location => http://localhost/My/Server,
pretty => 1,
withDocumentation => 1);
print $pod->WSDL;
Parsing the pod
How does Pod::WSDL work? If you instantiate a Pod::WSDL object with the name of the module (or the path of the file, or an open filehandle) providing the web service like this
my $pwsdl = new Pod::WSDL(source => My::Module,
location => http://my.services.location/on/the/web);
Pod::WSDL will try to find My::Module in @INC, open the file, parse it for WSDL directives and prepare the information for WSDL output. By calling
$pwsdl->WSDL;
Pod::WSDL will output the WSDL document. Thats it.
When using Pod::WSDL, the parser expects you to do the following:
Put the pod directly above the subroutines which the web services client is going to call. There may be whitespace between the pod and the sub declaration but nothing else.
Use the =begin/=end respectively the =for directives according to standard pod: anything between =begin WSDL and =end will be treated as pod. Anything composing a paragraph together with =for WSDL will be treated as pod.
Any subroutine not preceeded by WSDL pod will be left unmentioned. Any standard pod will be ignored (though, for an exception to this, see the section on own complex types below).
The individual instructions for Pod::WSDL always begin with a keyword, like _RETURN or _DOC or _FAULT. After this different things may follow, according to the specific type of instruction. The instruction may take one or more lines - everything up to the next line beginning with a keyword or the end of the pod is belonging to the current instruction.
Describing Methods
How do we use Pod::WSDL? In describing a web services method we have to say something about parameters, return values and faults. In addition you might want to add some documentation to these items and to the method itself.
Download (0.027MB)
Added: 2007-02-21 License: Perl Artistic License Price:
975 downloads
File 4.21
File attempts to classify files depending on their contents and prints a description if a match is found. more>>
File is the open source implementation of the file command used on almost every free operating system (OpenBSD, Linux, FreeBSD, NetBSD) and also on systems that use free software (including OS/2, DOS, MS Windows, etc.).
The file command, if youre not familiar with it, is a command-line tool that tells you in words what kind of data a file contains. Unlike MS-Windows, UNIX and other systems dont rely on filename extentions to tell you the type of a file, but look at the files actual contents. This is, of course, more reliable, but requires a bit of I/O.
The original file command shipped with Bell Labs UNIX but was unavailable in source form to the masses before Ians reimplementation.
This file command (and magic file) was originally written by Ian Darwin (who still contributes occasionally) and is now maintained by a group of developers lead by Christos Zoulas.
Whos using it?
Every known BSD distribution (FreeBSD, NetBSD, OpenBSD, Darwin/Mac OS X, etc)
Every known Linux distribution
The Apache httpd server mod_mime_magic module uses the file commands innards to make file type guessing more reliable under Apache HTTPD.
<<lessThe file command, if youre not familiar with it, is a command-line tool that tells you in words what kind of data a file contains. Unlike MS-Windows, UNIX and other systems dont rely on filename extentions to tell you the type of a file, but look at the files actual contents. This is, of course, more reliable, but requires a bit of I/O.
The original file command shipped with Bell Labs UNIX but was unavailable in source form to the masses before Ians reimplementation.
This file command (and magic file) was originally written by Ian Darwin (who still contributes occasionally) and is now maintained by a group of developers lead by Christos Zoulas.
Whos using it?
Every known BSD distribution (FreeBSD, NetBSD, OpenBSD, Darwin/Mac OS X, etc)
Every known Linux distribution
The Apache httpd server mod_mime_magic module uses the file commands innards to make file type guessing more reliable under Apache HTTPD.
Download (0.53MB)
Added: 2007-05-25 License: GPL (GNU General Public License) Price:
535 downloads
Get File 1.2.2
Get File is a Firefox extension that can get a file from an URL. more>>
Get File is a Firefox extension that can get a file from an URL.
To use this extension, go in File menu and choose "Get a File".
Ive also developed a french freeware for supervision of your computer.
http://www.pastouchexp.info/
<<lessTo use this extension, go in File menu and choose "Get a File".
Ive also developed a french freeware for supervision of your computer.
http://www.pastouchexp.info/
Download (0.014MB)
Added: 2007-07-09 License: MPL (Mozilla Public License) Price:
875 downloads
SOAP::WSDL 1.20
SOAP::WSDL is a Perl module. more>>
SOAP::WSDL is a Perl module.
SYNOPSIS
use SOAP::WSDL;
my $soap=SOAP::WSDL->new( wsdl => http://server.com/ws.wsdl )
->proxy( http://myurl.com);
$soap->wsdlinit;
my $som=$soap->call( method => [
{ name => value },
{ name => value } ]);
SOAP::WSDL provides decent WSDL support for SOAP::Lite. It is built as a add-on to SOAP::Lite, and will sit on top of it, forwarding all the actual request-response to SOAP::Lite - somewhat like a pre-processor.
WSDL support means that you dont have to deal with those bitchy namespaces some web services set on each and every method call parameter.
It also means an end to that nasty
SOAP::Data->name( Name )->value(
SOAP::Data->name( Sub-Name)->value( Subvalue )
);
encoding of complex data. (Another solution for this problem is just iterating recursively over your data. But that doesnt work if you need more information [e.g. namespaces etc] than just your data to encode your parameters).
And it means that you can use ordinary hashes for your parameters - the encording order will be derived from the WSDL and not from your (unordered) data, thus the problem of unordered perl-hashes and WSDL >sequence< definitions is solved, too. (Another solution for the ordering problem is tying your hash to a class that provides ordered hashes - Tie::IxHash is one of them).
<<lessSYNOPSIS
use SOAP::WSDL;
my $soap=SOAP::WSDL->new( wsdl => http://server.com/ws.wsdl )
->proxy( http://myurl.com);
$soap->wsdlinit;
my $som=$soap->call( method => [
{ name => value },
{ name => value } ]);
SOAP::WSDL provides decent WSDL support for SOAP::Lite. It is built as a add-on to SOAP::Lite, and will sit on top of it, forwarding all the actual request-response to SOAP::Lite - somewhat like a pre-processor.
WSDL support means that you dont have to deal with those bitchy namespaces some web services set on each and every method call parameter.
It also means an end to that nasty
SOAP::Data->name( Name )->value(
SOAP::Data->name( Sub-Name)->value( Subvalue )
);
encoding of complex data. (Another solution for this problem is just iterating recursively over your data. But that doesnt work if you need more information [e.g. namespaces etc] than just your data to encode your parameters).
And it means that you can use ordinary hashes for your parameters - the encording order will be derived from the WSDL and not from your (unordered) data, thus the problem of unordered perl-hashes and WSDL >sequence< definitions is solved, too. (Another solution for the ordering problem is tying your hash to a class that provides ordered hashes - Tie::IxHash is one of them).
Download (0.014MB)
Added: 2006-09-15 License: Perl Artistic License Price:
1142 downloads
C++ WSDL Parser 1.9.3
C++ WSDL Parser is an efficient C++ Web services library. more>>
C++ WSDL Parser is an efficient C++ Web services library that includes a standards compliant WSDL parser API, a Schema parser and validator, an XML parser and serializer, and an API for dynamically inspecting and invoking WSDL Web services.
Enhancements:
- Many WSDLs can now be dynamically invoked.
- Added documentation (doxygen for the API).
- Better error reporting when types are found missing.
<<lessEnhancements:
- Many WSDLs can now be dynamically invoked.
- Added documentation (doxygen for the API).
- Better error reporting when types are found missing.
Download (0.56MB)
Added: 2005-10-06 License: LGPL (GNU Lesser General Public License) Price:
1483 downloads
Daizu::File 0.3
Daizu::File is a Perl class representing files in working copies. more>>
Daizu::File is a Perl class representing files in working copies.
Each object of this class represents a particular file in a Daizu CMS working copy (a record in the wc_file table).
METHODS
Note that all the functions which return the value of a Subversion property will strip leading and trailing whitespace, and treat a value which is empty or entirely whitespace as if it wasnt set at all.
Daizu::File->new($cms, $file_id)
Return a new Daizu::File object for the file with the specified ID number.
$file->data
Return a reference to a string containing the file data (content).
$file->wc
Return a Daizu::Wc object representing the working copy in which this file lives.
$file->guid_uri
Return the GUID URI for this file.
$file->directory_path
Returns the path of a directory, either the same as the file if its a directory itself, or the path of its parent directory, or if its at the top level.
$file->permalink
Returns the first URL generated by the file, which will be the URL you want to link to most of the time. For articles this will always be the normal HTML version of the article, even if there are also other URLs available for it, and it will always be the first page of multipage articles. For non-article files there is no guarantee about what this will return, but most will only generate a single URL anyway, and for those that dont generators are likely to return the most linkable URL first.
The URL returned is an absolute URL provided as a URI object.
Returns nothing if the file doesnt generate any URLs.
There are some cases where this might not be what you want. For example, the root directory of a website using Daizu::Gen will either not generate a URL at all, or will generate one for a Google sitemap XML file, neither of which is likely to be useful for linking. To get the URL of the website you would probably need to find a file called something like _index.html. On the other hand, the Daizu::Gen::Blog generator will give you a sensible URL for the blog homepage if you call this on its root directory.
$file->urls_in_db($method, $argument)
Return a list of the URLs (plain strings, each an absolute URI) of the file which have the specified method and argument values, drawing from the url table in the database.
$file->article_urls
Return information about the URLs which the file should have, if it is an article. Fails if it isnt.
<<lessEach object of this class represents a particular file in a Daizu CMS working copy (a record in the wc_file table).
METHODS
Note that all the functions which return the value of a Subversion property will strip leading and trailing whitespace, and treat a value which is empty or entirely whitespace as if it wasnt set at all.
Daizu::File->new($cms, $file_id)
Return a new Daizu::File object for the file with the specified ID number.
$file->data
Return a reference to a string containing the file data (content).
$file->wc
Return a Daizu::Wc object representing the working copy in which this file lives.
$file->guid_uri
Return the GUID URI for this file.
$file->directory_path
Returns the path of a directory, either the same as the file if its a directory itself, or the path of its parent directory, or if its at the top level.
$file->permalink
Returns the first URL generated by the file, which will be the URL you want to link to most of the time. For articles this will always be the normal HTML version of the article, even if there are also other URLs available for it, and it will always be the first page of multipage articles. For non-article files there is no guarantee about what this will return, but most will only generate a single URL anyway, and for those that dont generators are likely to return the most linkable URL first.
The URL returned is an absolute URL provided as a URI object.
Returns nothing if the file doesnt generate any URLs.
There are some cases where this might not be what you want. For example, the root directory of a website using Daizu::Gen will either not generate a URL at all, or will generate one for a Google sitemap XML file, neither of which is likely to be useful for linking. To get the URL of the website you would probably need to find a file called something like _index.html. On the other hand, the Daizu::Gen::Blog generator will give you a sensible URL for the blog homepage if you call this on its root directory.
$file->urls_in_db($method, $argument)
Return a list of the URLs (plain strings, each an absolute URI) of the file which have the specified method and argument values, drawing from the url table in the database.
$file->article_urls
Return information about the URLs which the file should have, if it is an article. Fails if it isnt.
Download (0.41MB)
Added: 2006-11-29 License: Perl Artistic License Price:
1059 downloads
WSDL::Generator 0.02
WSDL::Generator is a Perl module to generate wsdl file automagically. more>>
WSDL::Generator is a Perl module to generate wsdl file automagically.
SYNOPSIS
use WSDL::Generator;
my $wsdl = WSDL::Generator->new($init);
Foo->a_method($param};
print $wsdl->get(Foo);
You know folks out there who use another language than Perl (huh?) and you want to release a SOAP server for them
1/ thats very kind of you
2/ you need to generate a wsdl file
3/ this module can help
Because Perl is dynamically typed, it is a fantastic language to write SOAP clients, but that makes perl not-so-easy to use as SOAP server queried by statically typed languages such as Delphi, Java, C++, VB...
These languages need a WSDL file to communicate with your server.
The WSDL file contains all the data structure definition necessary to interact with the server.
It contains also the namespace and URL as well.
<<lessSYNOPSIS
use WSDL::Generator;
my $wsdl = WSDL::Generator->new($init);
Foo->a_method($param};
print $wsdl->get(Foo);
You know folks out there who use another language than Perl (huh?) and you want to release a SOAP server for them
1/ thats very kind of you
2/ you need to generate a wsdl file
3/ this module can help
Because Perl is dynamically typed, it is a fantastic language to write SOAP clients, but that makes perl not-so-easy to use as SOAP server queried by statically typed languages such as Delphi, Java, C++, VB...
These languages need a WSDL file to communicate with your server.
The WSDL file contains all the data structure definition necessary to interact with the server.
It contains also the namespace and URL as well.
Download (0.67MB)
Added: 2007-06-14 License: Perl Artistic License Price:
865 downloads
Pod::WSDL::Doc 0.05
Pod::WSDL::Doc is a Perl module that represents the WSDL pod for the documentation of methods (internal use only). more>>
Pod::WSDL::Doc is a Perl module that represents the WSDL pod for the documentation of methods (internal use only).
SYNOPSIS
use Pod::WSDL::Doc;
my $doc = new Pod::WSDL::Doc(_DOC This method is for blah ...);
This module is used internally by Pod::WSDL. It is unlikely that you have to interact directly with it. If that is the case, take a look at the code, it is rather simple.
METHODS
new
Instantiates a new Pod::WSDL::Attr. The method needs one parameter, the documentation string from the pod. Please see SYNOPSIS or the section "Pod Syntax" in the description of Pod::WSDL.
<<lessSYNOPSIS
use Pod::WSDL::Doc;
my $doc = new Pod::WSDL::Doc(_DOC This method is for blah ...);
This module is used internally by Pod::WSDL. It is unlikely that you have to interact directly with it. If that is the case, take a look at the code, it is rather simple.
METHODS
new
Instantiates a new Pod::WSDL::Attr. The method needs one parameter, the documentation string from the pod. Please see SYNOPSIS or the section "Pod Syntax" in the description of Pod::WSDL.
Download (0.027MB)
Added: 2007-03-10 License: Perl Artistic License Price:
958 downloads
File::stat 0.1
File::stat is a by-name interface to Perls built-in stat() functions. more>>
File::stat is a by-name interface to Perls built-in stat() functions.
SYNOPSIS
use File::stat;
$st = stat($file) or die "No $file: $!";
if ( ($st->mode & 0111) && $st->nlink > 1) ) {
print "$file is executable with lotsa linksn";
}
use File::stat qw(:FIELDS);
stat($file) or die "No $file: $!";
if ( ($st_mode & 0111) && $st_nlink > 1) ) {
print "$file is executable with lotsa linksn";
}
This modules default exports override the core stat() and lstat() functions, replacing them with versions that return "File::stat" objects. This object has methods that return the similarly named structure field name from the stat(2) function; namely, dev, ino, mode, nlink, uid, gid, rdev, size, atime, mtime, ctime, blksize, and blocks.
You may also import all the structure fields directly into your namespace as regular variables using the :FIELDS import tag. (Note that this still overrides your stat() and lstat() functions.) Access these fields as variables named with a preceding st_ in front their method names. Thus, $stat_obj->dev() corresponds to $st_dev if you import the fields.
To access this functionality without the core overrides, pass the use an empty import list, and then access function functions with their full qualified names. On the other hand, the built-ins are still available via the CORE:: pseudo-package.
<<lessSYNOPSIS
use File::stat;
$st = stat($file) or die "No $file: $!";
if ( ($st->mode & 0111) && $st->nlink > 1) ) {
print "$file is executable with lotsa linksn";
}
use File::stat qw(:FIELDS);
stat($file) or die "No $file: $!";
if ( ($st_mode & 0111) && $st_nlink > 1) ) {
print "$file is executable with lotsa linksn";
}
This modules default exports override the core stat() and lstat() functions, replacing them with versions that return "File::stat" objects. This object has methods that return the similarly named structure field name from the stat(2) function; namely, dev, ino, mode, nlink, uid, gid, rdev, size, atime, mtime, ctime, blksize, and blocks.
You may also import all the structure fields directly into your namespace as regular variables using the :FIELDS import tag. (Note that this still overrides your stat() and lstat() functions.) Access these fields as variables named with a preceding st_ in front their method names. Thus, $stat_obj->dev() corresponds to $st_dev if you import the fields.
To access this functionality without the core overrides, pass the use an empty import list, and then access function functions with their full qualified names. On the other hand, the built-ins are still available via the CORE:: pseudo-package.
Download (14.2MB)
Added: 2007-04-27 License: Perl Artistic License Price:
910 downloads
X File Explorer 1.00
X File Explorer is a file manager for the X Window System. more>>
X File Explorer (Xfe) is an MS-Explorer like file manager for X. X File Explorer is based on the popular, but discontinued, X Win Commander, originally developed by Maxim Baranov.
Xfe aims to be the file manager of choice for all the Unix addicts!
Why another file manager when the excellent Konqueror or Nautilus exist on Linux systems? The answer is quite simple : these file managers are very good, features rich and look wonderful, but they are like a brontosaurus when you are a console addict and only want to copy some files or delete it. Another problem is that they require either the whole Gnome or KDE desktops to be installed on your system!
On the contrary, Xfe is small, very rapid and only requires the FOX library to be fully functional. It can be launched from the command line in a fraction of second, and can efficiently complete the set of command line tools.
Main features:
- Four different file manager styles (one panel, two panels, tree list and one panel, tree list and two panels)
- Integrated text viewer (X File View, xfv)
- Integrated RPM viewer / installer / uninstaller (X File Query, xfq)
- Status line
- File associations
- Auto save registry
- Right mouse click pop-up menu in tree list and file list
- Change file(s) attributes
- Mount/Unmount devices (for Linux only)
- Toolbar
- Bookmarks (up to 20)
- Color schemes (GNOME, KDE, Windows...)
- Drag and Drop ( ctrl -> copy, shift -> move, alt -> symlink )
- Create / Extract archives (tar, zip, gzip, bzip2, compress formats are supported)
- Tool tips for long file names
- Progress bars or dialogs for lengthy file operations
- Image preview as thumbnails
- Ability to enqueue multimedia files (open command)
Key bindings:
- Help - F1
- View - F3, return
- Edit - F4
- Copy - F5, ctrl-c
- Cut - ctrl-x
- Paste - ctrl-v
- Move - F6, ctrl-d
- Rename - ctrl-n
- Delete - F8, del, ctrl-del
- Symlink - ctrl-s
- New file - F2
- New folder - F7
- Properties - F9
- Tree and one panel - ctrl-F1
- Tree and two panels - ctrl-F2
- One panel - ctrl-F3
- Two panels - ctrl-F4
- Hidden files - ctrl-F5
- Hidden folders - ctrl-F6
- Execute - ctrl-e
- Go home - ctrl-h
- Go up - backspace
- Terminal - ctrl-t
- Console file manager - ctrl-k
- Refresh - ctrl-r
- Select all - ctrl-a
- Deselect all - ctrl-z
- Invert selection - ctrl-i
- Add bookmark - ctrl-b
- Mount (Linux only) - ctrl-m
- Unmount (Linux only) - ctrl-u
- Quit - ctrl-q
<<lessXfe aims to be the file manager of choice for all the Unix addicts!
Why another file manager when the excellent Konqueror or Nautilus exist on Linux systems? The answer is quite simple : these file managers are very good, features rich and look wonderful, but they are like a brontosaurus when you are a console addict and only want to copy some files or delete it. Another problem is that they require either the whole Gnome or KDE desktops to be installed on your system!
On the contrary, Xfe is small, very rapid and only requires the FOX library to be fully functional. It can be launched from the command line in a fraction of second, and can efficiently complete the set of command line tools.
Main features:
- Four different file manager styles (one panel, two panels, tree list and one panel, tree list and two panels)
- Integrated text viewer (X File View, xfv)
- Integrated RPM viewer / installer / uninstaller (X File Query, xfq)
- Status line
- File associations
- Auto save registry
- Right mouse click pop-up menu in tree list and file list
- Change file(s) attributes
- Mount/Unmount devices (for Linux only)
- Toolbar
- Bookmarks (up to 20)
- Color schemes (GNOME, KDE, Windows...)
- Drag and Drop ( ctrl -> copy, shift -> move, alt -> symlink )
- Create / Extract archives (tar, zip, gzip, bzip2, compress formats are supported)
- Tool tips for long file names
- Progress bars or dialogs for lengthy file operations
- Image preview as thumbnails
- Ability to enqueue multimedia files (open command)
Key bindings:
- Help - F1
- View - F3, return
- Edit - F4
- Copy - F5, ctrl-c
- Cut - ctrl-x
- Paste - ctrl-v
- Move - F6, ctrl-d
- Rename - ctrl-n
- Delete - F8, del, ctrl-del
- Symlink - ctrl-s
- New file - F2
- New folder - F7
- Properties - F9
- Tree and one panel - ctrl-F1
- Tree and two panels - ctrl-F2
- One panel - ctrl-F3
- Two panels - ctrl-F4
- Hidden files - ctrl-F5
- Hidden folders - ctrl-F6
- Execute - ctrl-e
- Go home - ctrl-h
- Go up - backspace
- Terminal - ctrl-t
- Console file manager - ctrl-k
- Refresh - ctrl-r
- Select all - ctrl-a
- Deselect all - ctrl-z
- Invert selection - ctrl-i
- Add bookmark - ctrl-b
- Mount (Linux only) - ctrl-m
- Unmount (Linux only) - ctrl-u
- Quit - ctrl-q
Download (1.6MB)
Added: 2007-07-17 License: GPL (GNU General Public License) Price:
839 downloads
PostScript::File 1.01
PostScript::File is a Perl base class for creating Adobe PostScript files. more>>
PostScript::File is a Perl base class for creating Adobe PostScript files.
SYNOPSIS
use PostScript::File qw(check_tilde check_file
incpage_label incpage_roman);
Simplest
An hello world program:
use PostScript::File;
my $ps = new PostScript::File();
$ps->add_to_page( Letter,
height => 500,
width => 400,
bottom => 30,
top => 30,
left => 30,
right => 30,
clip_command => stroke,
clipping => 1,
eps => 1,
dir => ~/foo,
file => "bar",
landscape => 0,
headings => 1,
reencode => ISOLatin1Encoding,
font_suffix => -iso,
errors => 1,
errmsg => Failed:,
errfont => Helvetica,
errsize => 12,
errx => 72,
erry => 300,
debug => 2,
db_active => 1,
db_xgap => 120,
db_xtab => 8,
db_base => 300,
db_ytop => 500,
db_color => 1 0 0 setrgbcolor,
db_font => Times-Roman,
db_fontsize => 11,
db_bufsize => 256,
);
<<lessSYNOPSIS
use PostScript::File qw(check_tilde check_file
incpage_label incpage_roman);
Simplest
An hello world program:
use PostScript::File;
my $ps = new PostScript::File();
$ps->add_to_page( Letter,
height => 500,
width => 400,
bottom => 30,
top => 30,
left => 30,
right => 30,
clip_command => stroke,
clipping => 1,
eps => 1,
dir => ~/foo,
file => "bar",
landscape => 0,
headings => 1,
reencode => ISOLatin1Encoding,
font_suffix => -iso,
errors => 1,
errmsg => Failed:,
errfont => Helvetica,
errsize => 12,
errx => 72,
erry => 300,
debug => 2,
db_active => 1,
db_xgap => 120,
db_xtab => 8,
db_base => 300,
db_ytop => 500,
db_color => 1 0 0 setrgbcolor,
db_font => Times-Roman,
db_fontsize => 11,
db_bufsize => 256,
);
Download (0.022MB)
Added: 2006-09-26 License: Perl Artistic License Price:
1124 downloads
File::Util 3.22
File::Util is an easy, versatile, portable file handling module. more>>
File::Util is an easy, versatile, portable file handling module.
File::Util provides a comprehensive toolbox of utilities to automate all kinds of common tasks on file / directories. Its purpose is to do so in the most portable manner possible so that users of this module wont have to worry about whether their programs will work on other OSes and machines.
SYNOPSIS
use File::Util;
my($f) = File::Util->new();
my($content) = $f->load_file(foo.txt);
$content =~ s/this/that/g;
$f->write_file(
file => bar.txt,
content => $content,
bitmask => 0644
);
$f->write_file(
file => file.bin, content => $binary_content, --binmode
);
my(@lines) = $f->load_file(randomquote.txt, --as-lines);
my($line) = int(rand(scalar @lines));
print $lines[$line];
my(@files) = $f->list_dir(/var/tmp, qw/ --files-only --recurse /);
my(@textfiles) = $f->list_dir(/var/tmp, --pattern=.txt$);
if ($f->can_write(wibble.log)) {
my($HANDLE) = $f->open_handle(
file => wibble.log,
mode => append
);
print $HANDLE "Hello World! Its ", scalar localtime;
close $HANDLE
}
my($log_line_count) = $f->line_count(/var/log/httpd/access_log);
print "My file has a bitmask of " . $f->bitmask(my.file);
print "My file is a " . join(, , $f->file_type(my.file)) . " file."
warn This file is binary! if $f->isbin(my.file);
print "My file was last modified on " .
scalar localtime($f->last_modified(my.file));
# ...and _lots_ more
<<lessFile::Util provides a comprehensive toolbox of utilities to automate all kinds of common tasks on file / directories. Its purpose is to do so in the most portable manner possible so that users of this module wont have to worry about whether their programs will work on other OSes and machines.
SYNOPSIS
use File::Util;
my($f) = File::Util->new();
my($content) = $f->load_file(foo.txt);
$content =~ s/this/that/g;
$f->write_file(
file => bar.txt,
content => $content,
bitmask => 0644
);
$f->write_file(
file => file.bin, content => $binary_content, --binmode
);
my(@lines) = $f->load_file(randomquote.txt, --as-lines);
my($line) = int(rand(scalar @lines));
print $lines[$line];
my(@files) = $f->list_dir(/var/tmp, qw/ --files-only --recurse /);
my(@textfiles) = $f->list_dir(/var/tmp, --pattern=.txt$);
if ($f->can_write(wibble.log)) {
my($HANDLE) = $f->open_handle(
file => wibble.log,
mode => append
);
print $HANDLE "Hello World! Its ", scalar localtime;
close $HANDLE
}
my($log_line_count) = $f->line_count(/var/log/httpd/access_log);
print "My file has a bitmask of " . $f->bitmask(my.file);
print "My file is a " . join(, , $f->file_type(my.file)) . " file."
warn This file is binary! if $f->isbin(my.file);
print "My file was last modified on " .
scalar localtime($f->last_modified(my.file));
# ...and _lots_ more
Download (0.041MB)
Added: 2007-08-08 License: Perl Artistic License Price:
808 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 wsdl file 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