mainly seconds store
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 3402
Really Simple CalDAV Store 0.8.0
Really Simple CalDAV Store project is a server implementation of the CalDAV protocol for storing calendaring resources. more>>
Really Simple CalDAV Store project is a server implementation of the CalDAV protocol for storing calendaring resources (iCalendar format) on a remote shared server.
An increasing number of calendar clients support the maintenance of shared remote calendars through CalDAV including Mozilla Calendar (Sunbird/Lightning), Evolution, Mulberry, and soon Apples iCal.
The Really Simple CalDAV Store supports basic delegation of read/write access among calendar users and multiple users or clients reading and writing the same calendar entries over time.
Enhancements:
- Lots of improvements were made to CalDAV specification compliance, especially around privacy of tasks and events.
- Two new translations of the administration interface were added (Polish and Hungarian).
- Support for authentication against an LDAP backend was added along with a number of performance, security, and bugfixes.
<<lessAn increasing number of calendar clients support the maintenance of shared remote calendars through CalDAV including Mozilla Calendar (Sunbird/Lightning), Evolution, Mulberry, and soon Apples iCal.
The Really Simple CalDAV Store supports basic delegation of read/write access among calendar users and multiple users or clients reading and writing the same calendar entries over time.
Enhancements:
- Lots of improvements were made to CalDAV specification compliance, especially around privacy of tasks and events.
- Two new translations of the administration interface were added (Polish and Hungarian).
- Support for authentication against an LDAP backend was added along with a number of performance, security, and bugfixes.
Download (0.31MB)
Added: 2007-06-05 License: GPL (GNU General Public License) Price:
880 downloads
Email::Store 0.24
Email::Store is a framework for database-backed email storage. more>>
Email::Store is a framework for database-backed email storage.
SYNOPSIS
use Email::Store dbi:mysql:mailstore;
Email::Store->setup; # Do this once
Email::Store::Mail->store( $rfc822 );
Email::Store::Mail->retrieve( $msgid );
...
Email::Store is the ideal basis for any application which needs to deal with databases of email: archiving, searching, or even storing mail for implementing IMAP or POP3 servers.
Email::Store itself is a very lightweight framework, meaning it does not provide very much functionality itself; in effect, it is merely a Class::DBI interface to a database schema which is designed for storing email. Incidentally, if you dont know much about Class::DBI, youre going to need to in order to get much out of this.
Despite its minimalist nature, Email::Store is incredibly powerful. Its power comes from its extensibility, through plugin modules and hooks which allow you to add new database tables and concepts to the system, and so access the mail store from a "different direction". In a sense, Email::Store is a blank canvas, onto which you can pick and choose (or even write!) the plugins which you want for your application.
For instance, the core Email::Store::Entity plugin module addresses the idea of "people" in the email universe, allowing you to search for mails to or from particular people; (despite their changing names or email addresses) Email::Store::Thread interfaces Email::Store to Mail::Thread allowing you to navigate mails by their position in a mail thread; the planned non-core Email::Store::Plucene module plugs into the indexing process and stores information about emails in a Plucene search index for quick retrieval later, and so on.
<<lessSYNOPSIS
use Email::Store dbi:mysql:mailstore;
Email::Store->setup; # Do this once
Email::Store::Mail->store( $rfc822 );
Email::Store::Mail->retrieve( $msgid );
...
Email::Store is the ideal basis for any application which needs to deal with databases of email: archiving, searching, or even storing mail for implementing IMAP or POP3 servers.
Email::Store itself is a very lightweight framework, meaning it does not provide very much functionality itself; in effect, it is merely a Class::DBI interface to a database schema which is designed for storing email. Incidentally, if you dont know much about Class::DBI, youre going to need to in order to get much out of this.
Despite its minimalist nature, Email::Store is incredibly powerful. Its power comes from its extensibility, through plugin modules and hooks which allow you to add new database tables and concepts to the system, and so access the mail store from a "different direction". In a sense, Email::Store is a blank canvas, onto which you can pick and choose (or even write!) the plugins which you want for your application.
For instance, the core Email::Store::Entity plugin module addresses the idea of "people" in the email universe, allowing you to search for mails to or from particular people; (despite their changing names or email addresses) Email::Store::Thread interfaces Email::Store to Mail::Thread allowing you to navigate mails by their position in a mail thread; the planned non-core Email::Store::Plucene module plugs into the indexing process and stores information about emails in a Plucene search index for quick retrieval later, and so on.
Download (0.027MB)
Added: 2006-06-28 License: Perl Artistic License Price:
1215 downloads
second hand icons
second hand icons is inspired by the superb litho icons by anthony piraino. more>>
second hand icons is inspired by the superb litho icons by anthony piraino.
-- THIS SET IS ABANDONED --
Everyone is welcomed to pick it up and continue the work. im sorry, i just cant do it now. please, read the readme file.
<<less-- THIS SET IS ABANDONED --
Everyone is welcomed to pick it up and continue the work. im sorry, i just cant do it now. please, read the readme file.
Download (0.70MB)
Added: 2006-07-05 License: GPL (GNU General Public License) Price:
1217 downloads
Email::Store::DBI 0.254
Email::Store::DBI is a Perl module for database backend to Email::Store. more>>
Email::Store::DBI is a Perl module for database backend to Email::Store.
SYNOPSIS
use Email::Store dbi:...;
This class is a subclass of Class::DBI and contains means for Email::Store-based programs to register what DSN they wish to use. It also provides for building database tables from schemas embedded in the DATA section of plug-in modules, using Class::DBI::DATA::Schema.
"Email::Store" is the ideal basis for any application which needs to deal with databases of email: archiving, searching, or even storing mail for implementing IMAP or POP3 servers.
"Email::Store" itself is a very lightweight framework, meaning it does not provide very much functionality itself; in effect, it is merely a Class::DBI interface to a database schema which is designed for storing email. Incidentally, if you dont know much about "Class::DBI", youre going to need to in order to get much out of this.
Despite its minimalist nature, "Email::Store" is incredibly powerful. Its power comes from its extensibility, through plugin modules and hooks which allow you to add new database tables and concepts to the system, and so access the mail store from a "different direction". In a sense, "Email::Store" is a blank canvas, onto which you can pick and choose (or even write!) the plugins which you want for your application.
For instance, the core "Email::Store::Entity" plugin module addresses the idea of "people" in the email universe, allowing you to search for mails to or from particular people; (despite their changing names or email addresses) "Email::Store::Thread" interfaces "Email::Store" to "Mail::Thread" allowing you to navigate mails by their position in a mail thread; the planned non-core "Email::Store::Plucene" module plugs into the indexing process and stores information about emails in a Plucene search index for quick retrieval later, and so on.
<<lessSYNOPSIS
use Email::Store dbi:...;
This class is a subclass of Class::DBI and contains means for Email::Store-based programs to register what DSN they wish to use. It also provides for building database tables from schemas embedded in the DATA section of plug-in modules, using Class::DBI::DATA::Schema.
"Email::Store" is the ideal basis for any application which needs to deal with databases of email: archiving, searching, or even storing mail for implementing IMAP or POP3 servers.
"Email::Store" itself is a very lightweight framework, meaning it does not provide very much functionality itself; in effect, it is merely a Class::DBI interface to a database schema which is designed for storing email. Incidentally, if you dont know much about "Class::DBI", youre going to need to in order to get much out of this.
Despite its minimalist nature, "Email::Store" is incredibly powerful. Its power comes from its extensibility, through plugin modules and hooks which allow you to add new database tables and concepts to the system, and so access the mail store from a "different direction". In a sense, "Email::Store" is a blank canvas, onto which you can pick and choose (or even write!) the plugins which you want for your application.
For instance, the core "Email::Store::Entity" plugin module addresses the idea of "people" in the email universe, allowing you to search for mails to or from particular people; (despite their changing names or email addresses) "Email::Store::Thread" interfaces "Email::Store" to "Mail::Thread" allowing you to navigate mails by their position in a mail thread; the planned non-core "Email::Store::Plucene" module plugs into the indexing process and stores information about emails in a Plucene search index for quick retrieval later, and so on.
Download (0.028MB)
Added: 2006-10-03 License: Perl Artistic License Price:
1117 downloads
Apache-Storage 1.00
Apache::Storage is Perl module containing simple functions to store and retrieve information from within the Apache process. more>>
Apache::Storage is Perl module containing simple functions to store and retrieve information from within the Apache process.
<<less Download (0.004MB)
Added: 2005-08-24 License: GPL (GNU General Public License) Price:
1521 downloads
Node Director 4.2.1
Node Director project is a system management application for centralized user and host management. more>>
Node Director project is a system management application for centralized user and host management in small to medium sized Unix / Linux / (Windows) system environments.
Main features:
- user management; templates and user classes make creation of users easy
- delegation of routine administration tasks
- data storage via LDAP - clients can directly bind to the LDAP database server
- flexible directory and name services - manages NIS, DNS, static DHCP entries, Samba users, LDAP ? LDAP transformations, file based databases like /etc/passwd, /etc/group, /etc/hosts, ...
- single account / password across multiple systems and applications
- software distribution
- service configuration (e.g. sendmail, bind, ntp, ...) via template mechanism
- customizable actions on events like e.g. account creation, password change, host configuration change, ... where actions include home directory creation, service restart, execution of arbitrary commands on target system and many many more
The Director is currently mainly deployed on Linux systems and therefore supports Linux best. Most Unix systems are not directly supported but the Director will work. There is some limitted functionality for Windows machines, too.
The Node Director requires an LDAP accessible database engine, such as the free OpenLDAP or the SUN / Netscape Directory Server. Virtually, any directory server that implements LDAP v2 or v3 and allows custom schema extensions should do, the development team uses OpenLDAP, and the Director has been successfully tested with the Sun Java System Directory Server 5.2.
The Director is in no means meant as a mere frontend for editing arbitrary data in LDAP accessible directory trees. It rather is a system management software storing its information via LDAP in RFC-compliant objects. The difference is that when you work with the Director you will never care about LDAP specific things like attributes, DNs, object classes, whatever (unless you want, of course). You will work with lists (e.g. of users) and forms (e.g. a single user account).
Anyway, the data is stored in an LDAP tree. While the Director comes with a number of means of updating name services like DNS, the system password/account database, Samba, etc. clients can directly bind via LDAP to the data store and access account / host records (e.g. via nss_ldap).
<<lessMain features:
- user management; templates and user classes make creation of users easy
- delegation of routine administration tasks
- data storage via LDAP - clients can directly bind to the LDAP database server
- flexible directory and name services - manages NIS, DNS, static DHCP entries, Samba users, LDAP ? LDAP transformations, file based databases like /etc/passwd, /etc/group, /etc/hosts, ...
- single account / password across multiple systems and applications
- software distribution
- service configuration (e.g. sendmail, bind, ntp, ...) via template mechanism
- customizable actions on events like e.g. account creation, password change, host configuration change, ... where actions include home directory creation, service restart, execution of arbitrary commands on target system and many many more
The Director is currently mainly deployed on Linux systems and therefore supports Linux best. Most Unix systems are not directly supported but the Director will work. There is some limitted functionality for Windows machines, too.
The Node Director requires an LDAP accessible database engine, such as the free OpenLDAP or the SUN / Netscape Directory Server. Virtually, any directory server that implements LDAP v2 or v3 and allows custom schema extensions should do, the development team uses OpenLDAP, and the Director has been successfully tested with the Sun Java System Directory Server 5.2.
The Director is in no means meant as a mere frontend for editing arbitrary data in LDAP accessible directory trees. It rather is a system management software storing its information via LDAP in RFC-compliant objects. The difference is that when you work with the Director you will never care about LDAP specific things like attributes, DNs, object classes, whatever (unless you want, of course). You will work with lists (e.g. of users) and forms (e.g. a single user account).
Anyway, the data is stored in an LDAP tree. While the Director comes with a number of means of updating name services like DNS, the system password/account database, Samba, etc. clients can directly bind via LDAP to the data store and access account / host records (e.g. via nss_ldap).
Download (3.0MB)
Added: 2006-09-01 License: GPL (GNU General Public License) Price:
1149 downloads
Safe and SafeDesktop 2.2.6
Safe and SafeDesktop project are created so that a user need not remember all her login names and passwords. more>>
Safe and SafeDesktop project are created so that a user need not remember all her login names and passwords.
What is Safe?
Nowadays, every person is forced to remember lots of sensitive data to interact with machines during daily life. For instance, automatic teller machines ask for numerical passwords and email accounts are protected by using loginnames and passwords. For many good reasons passwords should be difficult to guess and every password should be used for one account only. In reality, this makes it quite difficult for the average person to remember all the different passwords. Hence, people tend to choose easy to remember passwords and many persons re-use their passwords in such a way that the same password is used for many accounts. Even worse, it is quite common to write down passwords and stick the note to a screen frame. All these facilitations of remembrance lower the burden for hackers to get access to sensitive data and abuse computers.
The idea behind Safe is that a user must not remember all her loginnames and passwords. Instead, the user utilizes her cell phone to store sensitive data in an encrypted way. Only one root password is required to be remembered to get access to the data.
This concept works pretty well, because nowadays, cell phones are ubiquitous. Usually, cell phone owners carry the phones in their pocket regardless where they are going. So, running Safe on a cell phone means that passwords have no longer be to remembered and can be chosen as difficult as it can be. The only requirement is that the cell phone in question supports J2ME applications.
What is SafeDesktop?
SafeDesktop provides the same features as Safe does but it runs on desktop machines. Java is also used for the implementation of SafeDesktop. This allows SafeDesktop to be executed on almost all modern desktop operating systems (e.g., Microsoft Windows, Linux).
A synchronization mechanism is part of SafeDesktop to keep the data synchronized between Safe and SafeDesktop.
How does it work?
First, a MD5 hash of the root password is stored and compared with the users input, that is requested at applications startup. If the hash of the users input is equal with the stored hash, the user input is used as key to decrypt the data.
Second, a IDEA cipher is used in CBC mode (of operation) to store data in an encrypted way. The password that the user entered at startup, is used as a key for the IDEA cipher.
Version restrictions:
- Safe and SafeDesktop have their limits. The limits are inherent - they came from the IDEA cipher, the hardware, the operating system and all the other parts that are used as a blackbox.
- But remember, there are things you can do to push the limits: review the source code of Safe and SafeDesktop. Even more security relevant: Select a difficult to remember, long and random root password. With Safe and SafeDesktop you have only to remember one password, so, make it difficult for the opposer to get access to your sensitive data.
Enhancements:
- An IPv6 problem has been fixed (no exception will be thrown when the machine uses IPv6).
- Exception handling has been improved (error messages provide hints as to what went wrong).
- A minor bug has been fixed (mainly how and when Alerts are shown).
<<lessWhat is Safe?
Nowadays, every person is forced to remember lots of sensitive data to interact with machines during daily life. For instance, automatic teller machines ask for numerical passwords and email accounts are protected by using loginnames and passwords. For many good reasons passwords should be difficult to guess and every password should be used for one account only. In reality, this makes it quite difficult for the average person to remember all the different passwords. Hence, people tend to choose easy to remember passwords and many persons re-use their passwords in such a way that the same password is used for many accounts. Even worse, it is quite common to write down passwords and stick the note to a screen frame. All these facilitations of remembrance lower the burden for hackers to get access to sensitive data and abuse computers.
The idea behind Safe is that a user must not remember all her loginnames and passwords. Instead, the user utilizes her cell phone to store sensitive data in an encrypted way. Only one root password is required to be remembered to get access to the data.
This concept works pretty well, because nowadays, cell phones are ubiquitous. Usually, cell phone owners carry the phones in their pocket regardless where they are going. So, running Safe on a cell phone means that passwords have no longer be to remembered and can be chosen as difficult as it can be. The only requirement is that the cell phone in question supports J2ME applications.
What is SafeDesktop?
SafeDesktop provides the same features as Safe does but it runs on desktop machines. Java is also used for the implementation of SafeDesktop. This allows SafeDesktop to be executed on almost all modern desktop operating systems (e.g., Microsoft Windows, Linux).
A synchronization mechanism is part of SafeDesktop to keep the data synchronized between Safe and SafeDesktop.
How does it work?
First, a MD5 hash of the root password is stored and compared with the users input, that is requested at applications startup. If the hash of the users input is equal with the stored hash, the user input is used as key to decrypt the data.
Second, a IDEA cipher is used in CBC mode (of operation) to store data in an encrypted way. The password that the user entered at startup, is used as a key for the IDEA cipher.
Version restrictions:
- Safe and SafeDesktop have their limits. The limits are inherent - they came from the IDEA cipher, the hardware, the operating system and all the other parts that are used as a blackbox.
- But remember, there are things you can do to push the limits: review the source code of Safe and SafeDesktop. Even more security relevant: Select a difficult to remember, long and random root password. With Safe and SafeDesktop you have only to remember one password, so, make it difficult for the opposer to get access to your sensitive data.
Enhancements:
- An IPv6 problem has been fixed (no exception will be thrown when the machine uses IPv6).
- Exception handling has been improved (error messages provide hints as to what went wrong).
- A minor bug has been fixed (mainly how and when Alerts are shown).
Download (MB)
Added: 2007-08-02 License: GPL (GNU General Public License) Price:
823 downloads
SiG Information Generator 0.1.0
SiG Information Generator provides a class for persistant objects in PHP. more>>
SiG Information Generator provides a class for persistant objects in PHP.
SiG allows developers to create, store, retrieve, and search any custom PHP object. Using the Node base class one can create hierachies of related classes. It has been repackaged as a Wordpress Plugin.
SiG is written in PHP. PHP (PHP: Hypertext Preprocessor) is a reflective programming language originally designed for producing dynamic Web pages.[1] PHP is used mainly in server-side scripting, but can be used from a command line interface or in standalone graphical applications. Textual User Interfaces can also be created using ncurses.
The sole implementation is produced by The PHP Group and released under the PHP License. It is considered to be free software by the Free Software Foundation[2]. This implementation serves to define a de facto standard for PHP, as there is no formal specification.
<<lessSiG allows developers to create, store, retrieve, and search any custom PHP object. Using the Node base class one can create hierachies of related classes. It has been repackaged as a Wordpress Plugin.
SiG is written in PHP. PHP (PHP: Hypertext Preprocessor) is a reflective programming language originally designed for producing dynamic Web pages.[1] PHP is used mainly in server-side scripting, but can be used from a command line interface or in standalone graphical applications. Textual User Interfaces can also be created using ncurses.
The sole implementation is produced by The PHP Group and released under the PHP License. It is considered to be free software by the Free Software Foundation[2]. This implementation serves to define a de facto standard for PHP, as there is no formal specification.
Download (0.15MB)
Added: 2007-03-06 License: GPL (GNU General Public License) Price:
962 downloads
Raine 0.43.4
Raine is a M68000 and M68020 arcade game emulator. more>>
Raine is a M68000 and M68020 arcade game emulator.
Raine is an emulator, it emulates some M68000 and M68020 arcade games and is mainly focused on Taito and Jaleco games hardware.
It started as an experiment with the Rainbow Islands romset, dumped by Aracorn/Romlist. Raine can emulate many nice games now, and new games (previously unemulated) are appearing weekly.
Sound is also getting better, mainly thanks to the work of Hiromitsu Shioya
<<lessRaine is an emulator, it emulates some M68000 and M68020 arcade games and is mainly focused on Taito and Jaleco games hardware.
It started as an experiment with the Rainbow Islands romset, dumped by Aracorn/Romlist. Raine can emulate many nice games now, and new games (previously unemulated) are appearing weekly.
Sound is also getting better, mainly thanks to the work of Hiromitsu Shioya
Download (1.7MB)
Added: 2006-09-10 License: Freeware Price:
1172 downloads
jIRleeCh 1.3
jIRleeCh is a Java IRC client that is mainly used to ease the acquisition of XDCC packs. more>>
jIRleeCh project is a Java IRC client that is mainly used to ease the acquisition of XDCC packs.
It relieves the user from the need to know and type IRC commands to get XDCC Bot files or to use multiple tools and plugins to do so. It has an easy-to-use GUI interface with all the basic IRC client features.
It parses packetnews.com to search for packs. No IRC knowledge is needed to use it, as it automatically connects to a network, channel, and queues a pack.
<<lessIt relieves the user from the need to know and type IRC commands to get XDCC Bot files or to use multiple tools and plugins to do so. It has an easy-to-use GUI interface with all the basic IRC client features.
It parses packetnews.com to search for packs. No IRC knowledge is needed to use it, as it automatically connects to a network, channel, and queues a pack.
Download (1.0MB)
Added: 2006-10-19 License: GPL (GNU General Public License) Price:
1104 downloads
IAM OPML Parser Class 1.0
IAM OPML Parser Class parses an OPML file (provided its URL) and returns an array. more>>
IAM OPML Parser Class parses an OPML file (provided its URL) and returns an array.
OPML (Outline Processor Markup Language) is an XML format for outlines. Originally developed by Radio UserLand as a native file format for an outliner application, it has since been adopted for other uses, the most common being to exchange lists of web feeds (RSS) between web feed aggregators. The OPML specification defines an outline as a hierarchical, ordered list of arbitrary elements. The specification is fairly open which makes it suitable for many types of list data.
The XML elements in an OPML document are:
< opml version=”1.0″ > This is the root element. It must contain the version attribute and one head and one body element. Currently, there’s active work in OML 2.0, which is mainly aimed at solving some of v1.o’s shortcomings.
< head > Contains metadata. May include any of these optional elements: title, dateCreated, dateModified, ownerName, ownerEmail, expansionState, vertScrollState, windowTop, windowLeft, windowBottom, windowRight. Each element is a simple text element. dateCreated and dateModified contents conform to the date-time format specified in RFC 822. expansionState contains a comma-separated list of line numbers that should be expanded o and size of the display window. An OPML processor may ignore all the head sub-elements. If the outline is opened inside another outline then the processor must ignore the window elements.
< body > Contains the content of the outline. Must have one or more outline elements.
< outline > Represents a line in the outline. May contain any number of arbitrary attributes. Common attributes include text and type. The outline element may contain any number of outline sub-elements. While there are many tools to create and/or read OPML files, there are few PHP libraries/functions to work with these files.
This PHP class parses an OPML file (provided its URL) and returns an array with all the parsed data. This array contains, for each of the OPML file’s elements the following attributes: link_url, link_name, link_target, link_description, link_rss, created (date of creation), type (link type: RSS, HTML, etc.). The class uses file_get_contents() to retrieve the contents of the OPML file and then the XML extension is used to parse and store the file’s data in an associative array, where each outline element is stored using a different array index. The array has the following structure:
0 : Array:
{
names => Preface
urls => http://www.php.net/manual/en/preface.php
targets =>
feeds =>
descriptions =>
created => Nov 28 2005 21:05:49 GMT
type => link
}
1 : Array:
{
names => I. Getting started
urls =>
targets =>
feeds =>
descriptions =>
created =>
type =>
}
<<lessOPML (Outline Processor Markup Language) is an XML format for outlines. Originally developed by Radio UserLand as a native file format for an outliner application, it has since been adopted for other uses, the most common being to exchange lists of web feeds (RSS) between web feed aggregators. The OPML specification defines an outline as a hierarchical, ordered list of arbitrary elements. The specification is fairly open which makes it suitable for many types of list data.
The XML elements in an OPML document are:
< opml version=”1.0″ > This is the root element. It must contain the version attribute and one head and one body element. Currently, there’s active work in OML 2.0, which is mainly aimed at solving some of v1.o’s shortcomings.
< head > Contains metadata. May include any of these optional elements: title, dateCreated, dateModified, ownerName, ownerEmail, expansionState, vertScrollState, windowTop, windowLeft, windowBottom, windowRight. Each element is a simple text element. dateCreated and dateModified contents conform to the date-time format specified in RFC 822. expansionState contains a comma-separated list of line numbers that should be expanded o and size of the display window. An OPML processor may ignore all the head sub-elements. If the outline is opened inside another outline then the processor must ignore the window elements.
< body > Contains the content of the outline. Must have one or more outline elements.
< outline > Represents a line in the outline. May contain any number of arbitrary attributes. Common attributes include text and type. The outline element may contain any number of outline sub-elements. While there are many tools to create and/or read OPML files, there are few PHP libraries/functions to work with these files.
This PHP class parses an OPML file (provided its URL) and returns an array with all the parsed data. This array contains, for each of the OPML file’s elements the following attributes: link_url, link_name, link_target, link_description, link_rss, created (date of creation), type (link type: RSS, HTML, etc.). The class uses file_get_contents() to retrieve the contents of the OPML file and then the XML extension is used to parse and store the file’s data in an associative array, where each outline element is stored using a different array index. The array has the following structure:
0 : Array:
{
names => Preface
urls => http://www.php.net/manual/en/preface.php
targets =>
feeds =>
descriptions =>
created => Nov 28 2005 21:05:49 GMT
type => link
}
1 : Array:
{
names => I. Getting started
urls =>
targets =>
feeds =>
descriptions =>
created =>
type =>
}
Download (0.002MB)
Added: 2007-07-23 License: Freeware Price:
823 downloads
Bio::PrimarySeqI 1.4
Bio::PrimarySeqI is a Perl Interface definition for a Bio::PrimarySeq. more>>
Bio::PrimarySeqI is a Perl Interface definition for a Bio::PrimarySeq.
SYNOPSIS
# Bio::PrimarySeqI is the interface class for sequences.
# If you are a newcomer to bioperl, you should
# start with Bio::Seq documentation. This
# documentation is mainly for developers using
# Bioperl.
# to test this is a seq object
$obj->isa("Bio::PrimarySeqI") ||
$obj->throw("$obj does not implement the Bio::PrimarySeqI interface");
# accessors
$string = $obj->seq();
$substring = $obj->subseq(12,50);
$display = $obj->display_id(); # for human display
$id = $obj->primary_id(); # unique id for this object,
# implementation defined
$unique_key= $obj->accession_number();
# unique biological id
# object manipulation
eval {
$rev = $obj->revcom();
};
if( $@ ) {
$obj->throw(-class => Bio::Root::Exception,
-text => "Could not reverse complement. ".
"Probably not DNA. Actual exceptionn$@n",
-value => $@);
}
$trunc = $obj->trunc(12,50);
# $rev and $trunc are Bio::PrimarySeqI compliant objects
This object defines an abstract interface to basic sequence information - for most users of the package the documentation (and methods) in this class are not useful - this is a developers only class which defines what methods have to be implmented by other Perl objects to comply to the Bio::PrimarySeqI interface. Go "perldoc Bio::Seq" or "man Bio::Seq" for more information on the main class for sequences.
PrimarySeq is an object just for the sequence and its name(s), nothing more. Seq is the larger object complete with features. There is a pure perl implementation of this in Bio::PrimarySeq. If you just want to use Bio::PrimarySeq objects, then please read that module first. This module defines the interface, and is of more interest to people who want to wrap their own Perl Objects/RDBs/FileSystems etc in way that they "are" bioperl sequence objects, even though it is not using Perl to store the sequence etc.
This interface defines what bioperl consideres necessary to "be" a sequence, without providing an implementation of this. (An implementation is provided in Bio::PrimarySeq). If you want to provide a Bio::PrimarySeq compliant object which in fact wraps another object/database/out-of-perl experience, then this is the correct thing to wrap, generally by providing a wrapper class which would inheriet from your object and this Bio::PrimarySeqI interface. The wrapper class then would have methods lists in the "Implementation Specific Functions" which would provide these methods for your object.
<<lessSYNOPSIS
# Bio::PrimarySeqI is the interface class for sequences.
# If you are a newcomer to bioperl, you should
# start with Bio::Seq documentation. This
# documentation is mainly for developers using
# Bioperl.
# to test this is a seq object
$obj->isa("Bio::PrimarySeqI") ||
$obj->throw("$obj does not implement the Bio::PrimarySeqI interface");
# accessors
$string = $obj->seq();
$substring = $obj->subseq(12,50);
$display = $obj->display_id(); # for human display
$id = $obj->primary_id(); # unique id for this object,
# implementation defined
$unique_key= $obj->accession_number();
# unique biological id
# object manipulation
eval {
$rev = $obj->revcom();
};
if( $@ ) {
$obj->throw(-class => Bio::Root::Exception,
-text => "Could not reverse complement. ".
"Probably not DNA. Actual exceptionn$@n",
-value => $@);
}
$trunc = $obj->trunc(12,50);
# $rev and $trunc are Bio::PrimarySeqI compliant objects
This object defines an abstract interface to basic sequence information - for most users of the package the documentation (and methods) in this class are not useful - this is a developers only class which defines what methods have to be implmented by other Perl objects to comply to the Bio::PrimarySeqI interface. Go "perldoc Bio::Seq" or "man Bio::Seq" for more information on the main class for sequences.
PrimarySeq is an object just for the sequence and its name(s), nothing more. Seq is the larger object complete with features. There is a pure perl implementation of this in Bio::PrimarySeq. If you just want to use Bio::PrimarySeq objects, then please read that module first. This module defines the interface, and is of more interest to people who want to wrap their own Perl Objects/RDBs/FileSystems etc in way that they "are" bioperl sequence objects, even though it is not using Perl to store the sequence etc.
This interface defines what bioperl consideres necessary to "be" a sequence, without providing an implementation of this. (An implementation is provided in Bio::PrimarySeq). If you want to provide a Bio::PrimarySeq compliant object which in fact wraps another object/database/out-of-perl experience, then this is the correct thing to wrap, generally by providing a wrapper class which would inheriet from your object and this Bio::PrimarySeqI interface. The wrapper class then would have methods lists in the "Implementation Specific Functions" which would provide these methods for your object.
Download (4.7MB)
Added: 2006-09-23 License: Perl Artistic License Price:
1126 downloads
Smack PubSub Extensions 1.2
Smack PubSub Extensions is a set of extensions to smack. more>>
Smack PubSub Extensions is a set of extensions to smack.
The extensions mainly include support for JEP-0060 aka PubSub but there are also a few utitlity classes. Please refer to the maven-generated documentation for further information.
<<lessThe extensions mainly include support for JEP-0060 aka PubSub but there are also a few utitlity classes. Please refer to the maven-generated documentation for further information.
Download (0.031MB)
Added: 2006-09-11 License: BSD License Price:
1143 downloads
LindeX Retriever 0.10
LindeX Retriever is a collection of Perl scripts that get LindeX Market Data from the Linden Lab (Second Life) feed. more>>
LindeX Retriever is a collection of Perl scripts that get LindeX Market Data from the Linden Lab (Second Life) feed.
It can filter them using XML::XPath, and store them using rrdtool.
Output example:
[root@database ~]# perl lindex.pl
1169545518
<<lessIt can filter them using XML::XPath, and store them using rrdtool.
Output example:
[root@database ~]# perl lindex.pl
1169545518
Download (0.002MB)
Added: 2007-01-23 License: GPL (GNU General Public License) Price:
1004 downloads
Simple Aggregator 1.1
Simple Aggregator is a web-based news aggregator. more>>
Simple Aggregator is a Web-based news aggregator. It retrieves feeds using Mark Pilgrims Ultra Liberal feed Parser, making full use of its advanced features. It stores the feeds in a MySQL database, and displays news via a PHP frontend.
Enhancements:
- the backend is now ready for categories (planned for the next release)
- the feedsloader script now uses threads for much better performance
- the feedsloader script now periodically cleans up read entries
- the feedsloader script now traps feed encoding errors
- added OPML import and export for feeds
- moved CSS style sheets to a common external file
- small fixes mainly to the user menu links
<<lessEnhancements:
- the backend is now ready for categories (planned for the next release)
- the feedsloader script now uses threads for much better performance
- the feedsloader script now periodically cleans up read entries
- the feedsloader script now traps feed encoding errors
- added OPML import and export for feeds
- moved CSS style sheets to a common external file
- small fixes mainly to the user menu links
Download (0.016MB)
Added: 2005-04-26 License: MIT/X Consortium License Price:
1641 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 mainly seconds store 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
