noname
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 3
Noname Network 0.1.7
Noname Network provides a powerful file-sharing network. more>>
Noname Network provides a powerful file-sharing network.
The Noname network is a gnutella-based network that features a different and more flexible protocol. The client and network currently support filesharing, but the protocol can be extended to support more features.
<<lessThe Noname network is a gnutella-based network that features a different and more flexible protocol. The client and network currently support filesharing, but the protocol can be extended to support more features.
Download (MB)
Added: 2007-04-05 License: GPL (GNU General Public License) Price:
933 downloads
er2code
er2code is a tool to automatically generate code to make it easier to access a database from your program. more>>
er2code is a tool to automatically generate code to make it easier to access a database from your program. The script takes a database description file as input and generates a directory full of database wrapper files.
The code is generated based on an XML file, and should be pretty database and language neutral. Right now, though, only PHP with a MySQL database is supported.
If you are lucky enough to be using Python for your application, i really recommend SQLObject over er2code, it is much cleaner and works with all kinds of databases.
The project is based on a Database Idea i once had, i thought it was revolutionary then, but i was later proved wrong, again, by the SQLObject guys.
Overview
The focus of this project is to take some of the boring work of off the programmers shoulders. Writing database wrappers is boring and tedious, and as such can be the course of many "sleeping-while-typing" errors.
But on the bright side, boring and tedious often means that the process can be automated, hence this tool.
The main idea of er2code is that each relation (also called table by some people) in the database, is mapped to a class of the same name. This class then contains a number of methods for manipulating the attributes contained in the relation.
The approach taken by er2code is to have a long list of methods (these are called Function in er2code), these functions have some requirements regarding an attribute that must be satisfied in order for the code of the function to generated.
The code of the function contains plain text mixed with identifiers. Each of these identifiers can generate their "value" (a text string) based on the specific attribute they are applied on.
Of course it is not as simple as that, we havent considered constructs, how to delete rows in the table, and how to handle foreign relations, e.g. 1-to-many.
The layout of the a file is a bit like C structs, and a bit like SQL.
Each relation is defined inside its own struct block:
User {
... attributes go here ...
}
This statement will cause a User class to be created.
Each attribute is defined by the name of the attribute, followed by one or more whitespace separated attribute type definers, and terminated by a semicolon.
User {
id serial;
username string(30) default(noname) sort unique index;
password string(40);
email string(100);
}
This will cause the User relation to contain four attributes:
id which is of type serial, an automatically incremented integer that is defined as the primary key.
username which is a 30-character long string, it is defined as sort which means that when a method which lists Users is called, the result should be sorted by this attribute. It also is of type index, which means that it should be possible to find a User based on the value of this attribute.
password is a 40-character string.
email is a 100-character string.
This is all er2code needs to know to create a class for the User relation, and the DataBase class, which is the one you use to connect to the database, and to list and find relations.
If the description above is used with er2code to generate PHP code, it should make it possible to write code like the following:
// Connect to the database.
$db = new DataBase ();
$halfdan = $db->findUserByUsername ( halfdan );
if ( $halfdan != null ) {
print $halfdan->getUsername() . < . $halfdan->getEmail() . >;
}
// List is automatically sorted by username
foreach ( $db->listUser() as $user ) {
print < a href="user.php?id= . $user->getId() . " > . $user->getName() . < /a >;
}
<<lessThe code is generated based on an XML file, and should be pretty database and language neutral. Right now, though, only PHP with a MySQL database is supported.
If you are lucky enough to be using Python for your application, i really recommend SQLObject over er2code, it is much cleaner and works with all kinds of databases.
The project is based on a Database Idea i once had, i thought it was revolutionary then, but i was later proved wrong, again, by the SQLObject guys.
Overview
The focus of this project is to take some of the boring work of off the programmers shoulders. Writing database wrappers is boring and tedious, and as such can be the course of many "sleeping-while-typing" errors.
But on the bright side, boring and tedious often means that the process can be automated, hence this tool.
The main idea of er2code is that each relation (also called table by some people) in the database, is mapped to a class of the same name. This class then contains a number of methods for manipulating the attributes contained in the relation.
The approach taken by er2code is to have a long list of methods (these are called Function in er2code), these functions have some requirements regarding an attribute that must be satisfied in order for the code of the function to generated.
The code of the function contains plain text mixed with identifiers. Each of these identifiers can generate their "value" (a text string) based on the specific attribute they are applied on.
Of course it is not as simple as that, we havent considered constructs, how to delete rows in the table, and how to handle foreign relations, e.g. 1-to-many.
The layout of the a file is a bit like C structs, and a bit like SQL.
Each relation is defined inside its own struct block:
User {
... attributes go here ...
}
This statement will cause a User class to be created.
Each attribute is defined by the name of the attribute, followed by one or more whitespace separated attribute type definers, and terminated by a semicolon.
User {
id serial;
username string(30) default(noname) sort unique index;
password string(40);
email string(100);
}
This will cause the User relation to contain four attributes:
id which is of type serial, an automatically incremented integer that is defined as the primary key.
username which is a 30-character long string, it is defined as sort which means that when a method which lists Users is called, the result should be sorted by this attribute. It also is of type index, which means that it should be possible to find a User based on the value of this attribute.
password is a 40-character string.
email is a 100-character string.
This is all er2code needs to know to create a class for the User relation, and the DataBase class, which is the one you use to connect to the database, and to list and find relations.
If the description above is used with er2code to generate PHP code, it should make it possible to write code like the following:
// Connect to the database.
$db = new DataBase ();
$halfdan = $db->findUserByUsername ( halfdan );
if ( $halfdan != null ) {
print $halfdan->getUsername() . < . $halfdan->getEmail() . >;
}
// List is automatically sorted by username
foreach ( $db->listUser() as $user ) {
print < a href="user.php?id= . $user->getId() . " > . $user->getName() . < /a >;
}
Download (MB)
Added: 2007-02-23 License: GPL (GNU General Public License) Price:
974 downloads
Debug::Trace 0.04
Debug::Trace is a Perl extension to trace subroutine calls. more>>
Debug::Trace is a Perl extension to trace subroutine calls.
SYNOPSIS
perl -MDebug::Trace=foo,bar yourprogram.pl
Debug::Trace instruments subroutines to provide tracing information upon every call and return.
Using Debug::Trace does not require any changes to your sources. Most often, it will be used from the command line:
perl -MDebug::Trace=foo,bar yourprogram.pl
This will have your subroutines foo() and bar() printing call and return information.
Subroutine names may be fully qualified to denote subroutines in other packages than the default main::.
By default, the trace information is output using the standard warn() function.
MODIFIERS
Modifiers can be inserted in the list of subroutines to change the default behavior of this module. All modifiers can be used in three ways:
:name to enable a specific feature.
:noname to disable a specific feature.
:name(value) to set a feature to a specific value. In general, :name is equivalent to :name(1), while :noname corresponds to :name(0).
The following modifiers are recognized:
:warn
Uses warn() to produce the trace output (default). :nowarn Sends trace output directly to STDERR.
:caller
Add basic call information to the trace message, including from where the routine was called, and by whom. This is enabled by default.
:stacktrace
Add a stack trace (call history).
:maxlen(length)
Truncate the length of the lines of trace information to length characters.
The following modifiers can be used to control the way Data::Dumper prints the values of parameters and return values. See also Data::Dumper.
:indent
Controls the style of indentation. It can be set to 0, 1, 2 or 3. Style 0 spews output without any newlines, indentation, or spaces between list items. :indent(0) is the default.
:useqq
When enabled, uses double quotes for representing string values. Whitespace other than space will be represented as [ntr], "unsafe" characters will be backslashed, and unprintable characters will be output as quoted octal integers. This is the default, use :nouseqq to disable.
:maxdepth(depth)
Can be set to a positive integer that specifies the depth beyond which which we dont print structure contents. The default is 2, which means one level of array/hashes in argument lists and return values is expanded. If you use :nomaxdepth or :maxdepth(0), nested structures are fully expanded.
:quotekeys
Controls wether hash keys are always printed quoted. The default is :noquotekeys.
sortkeys
Controls whether hash keys are dumped in sorted order. The default is :nosortkeys.
Modifiers apply only to the subroutines that follow in the list of arguments.
<<lessSYNOPSIS
perl -MDebug::Trace=foo,bar yourprogram.pl
Debug::Trace instruments subroutines to provide tracing information upon every call and return.
Using Debug::Trace does not require any changes to your sources. Most often, it will be used from the command line:
perl -MDebug::Trace=foo,bar yourprogram.pl
This will have your subroutines foo() and bar() printing call and return information.
Subroutine names may be fully qualified to denote subroutines in other packages than the default main::.
By default, the trace information is output using the standard warn() function.
MODIFIERS
Modifiers can be inserted in the list of subroutines to change the default behavior of this module. All modifiers can be used in three ways:
:name to enable a specific feature.
:noname to disable a specific feature.
:name(value) to set a feature to a specific value. In general, :name is equivalent to :name(1), while :noname corresponds to :name(0).
The following modifiers are recognized:
:warn
Uses warn() to produce the trace output (default). :nowarn Sends trace output directly to STDERR.
:caller
Add basic call information to the trace message, including from where the routine was called, and by whom. This is enabled by default.
:stacktrace
Add a stack trace (call history).
:maxlen(length)
Truncate the length of the lines of trace information to length characters.
The following modifiers can be used to control the way Data::Dumper prints the values of parameters and return values. See also Data::Dumper.
:indent
Controls the style of indentation. It can be set to 0, 1, 2 or 3. Style 0 spews output without any newlines, indentation, or spaces between list items. :indent(0) is the default.
:useqq
When enabled, uses double quotes for representing string values. Whitespace other than space will be represented as [ntr], "unsafe" characters will be backslashed, and unprintable characters will be output as quoted octal integers. This is the default, use :nouseqq to disable.
:maxdepth(depth)
Can be set to a positive integer that specifies the depth beyond which which we dont print structure contents. The default is 2, which means one level of array/hashes in argument lists and return values is expanded. If you use :nomaxdepth or :maxdepth(0), nested structures are fully expanded.
:quotekeys
Controls wether hash keys are always printed quoted. The default is :noquotekeys.
sortkeys
Controls whether hash keys are dumped in sorted order. The default is :nosortkeys.
Modifiers apply only to the subroutines that follow in the list of arguments.
Download (0.005MB)
Added: 2007-05-01 License: Perl Artistic License Price:
906 downloads
Secleted [ 0 ] software to compare
- Page: 1 of 1
- 1
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above noname 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