even fields
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 3012
Crimson Fields 0.5.1
Crimson Fields is a tactical war game in the tradition of Battle Isle. more>>
Crimson Fields project is a tactical war game in the tradition of Battle Isle.
The outcome of the war lies in your hands. You decide which units are sent to the front lines, and when to unleash the reserves. Your mission objectives range from defending strategically vital locations to simply destroying all enemy forces in the area. Protect supply convoys or raid enemy facilities to uncover technological secrets or fill your storage bays so you can repair damaged units or build new ones in your own factories. Lead your troops to victory!
Tools are available to create custom maps and campaigns. You can also play the original Battle Isle maps if you have a copy of the game.
You can pit yourself against another human player either in hot-seat mode in front of the same machine or via e-mail, or against the computer.
Crimson Fields is distributed under the terms of the GNU General Public License (GPL). It has been developed and tested on Intel architecture with Linux, but it shouldnt be too hard to make it compile and run on other operating systems as well. So far it has been reported to work with Linux, various flavours of BSD, Sun Solaris, MacOS X, BeOS, and MS Windows.
<<lessThe outcome of the war lies in your hands. You decide which units are sent to the front lines, and when to unleash the reserves. Your mission objectives range from defending strategically vital locations to simply destroying all enemy forces in the area. Protect supply convoys or raid enemy facilities to uncover technological secrets or fill your storage bays so you can repair damaged units or build new ones in your own factories. Lead your troops to victory!
Tools are available to create custom maps and campaigns. You can also play the original Battle Isle maps if you have a copy of the game.
You can pit yourself against another human player either in hot-seat mode in front of the same machine or via e-mail, or against the computer.
Crimson Fields is distributed under the terms of the GNU General Public License (GPL). It has been developed and tested on Intel architecture with Linux, but it shouldnt be too hard to make it compile and run on other operating systems as well. So far it has been reported to work with Linux, various flavours of BSD, Sun Solaris, MacOS X, BeOS, and MS Windows.
Download (0.78MB)
Added: 2007-01-24 License: GPL (GNU General Public License) Price:
1005 downloads
Tie::FieldVals 0.40
Tie::FieldVals is an array tie for a file of enhanced Field:Value data. more>>
Tie::FieldVals is an array tie for a file of enhanced Field:Value data.
SYNOPSIS
use Tie::FieldVals;
use Tie::FieldVals::Row;
# tie the array
my @records;
my $recs_obj = tie @records, Tie::FieldVals, datafile=>$datafile;
# object methods
my @field_names = $recs_obj->field_names();
This is a Tie object to map the records in an enhanced Field:Value data file into an array. Each file has multiple records, each record has its values defined by a Field:Value pair, with the enhancements that (a) the Value part can extend over more than one line (because the Field names are predefined) and (b) Fields can have multiple values by repeating the Field:Value part for a given field.
Because of its use of the Tie::File module, access to each record is reasonably fast. The Tie::File module also ensures that (a) the whole file doesnt have to be read into memory (b) record changes are written to the file straight away (c) record changes dont require the whole file to be rewritten, just the part of the file after the change.
The advantage of this setup is that one can have useful data files which are plain text, human readable, human editable, and at the same time able to be accessed faster than using XML (I know, I wrote a version of my reporting software using XML data, and even the fastest XML parsers werent as fast as this setup, once there were a reasonable number of records). This also has advantages over a simpler setup where values are given one per line with no indication of what value belongs to what field; the problems with that is that it is harder to fix corrupted data by hand, and it is harder to add new fields, and one cant have multi-line data.
It is likewise better than a CSV (Comma-Separated Values) file, because again, with a CSV file, the data is positional and therefore harder to fix and harder to change, and again one cant have multi-line data.
This module is both better and worse than file-oriented databases like DB_File and its variants and extensions (such as MLDBM). This module does not require that each record have a unique key, and the fact that a DBM file is binary makes it not only less correctable, but also less portable. On the downside, this module isnt as fast.
Naturally, if ones data needs are more complex, it is probably better to use a fully-fledged database; this is oriented towards those who dont wish to have the overhead of setting up and maintaining a relational database server, and wish to use something more straightforward.
This comes bundled with other support modules, such as the Tie::FieldVals::Row module. The Tie::FieldVals::Select module is for selecting and sorting a sub-set from a Tie::FieldVals array, and the Tie::FieldVals::Join is a very simple method of joining two files on a common field.
This distribution includes the fv2xml script, which converts a Tie::FieldVals data file into an XML file, and xml2fv which converts an XML file into a Tie::FieldVals data file.
<<lessSYNOPSIS
use Tie::FieldVals;
use Tie::FieldVals::Row;
# tie the array
my @records;
my $recs_obj = tie @records, Tie::FieldVals, datafile=>$datafile;
# object methods
my @field_names = $recs_obj->field_names();
This is a Tie object to map the records in an enhanced Field:Value data file into an array. Each file has multiple records, each record has its values defined by a Field:Value pair, with the enhancements that (a) the Value part can extend over more than one line (because the Field names are predefined) and (b) Fields can have multiple values by repeating the Field:Value part for a given field.
Because of its use of the Tie::File module, access to each record is reasonably fast. The Tie::File module also ensures that (a) the whole file doesnt have to be read into memory (b) record changes are written to the file straight away (c) record changes dont require the whole file to be rewritten, just the part of the file after the change.
The advantage of this setup is that one can have useful data files which are plain text, human readable, human editable, and at the same time able to be accessed faster than using XML (I know, I wrote a version of my reporting software using XML data, and even the fastest XML parsers werent as fast as this setup, once there were a reasonable number of records). This also has advantages over a simpler setup where values are given one per line with no indication of what value belongs to what field; the problems with that is that it is harder to fix corrupted data by hand, and it is harder to add new fields, and one cant have multi-line data.
It is likewise better than a CSV (Comma-Separated Values) file, because again, with a CSV file, the data is positional and therefore harder to fix and harder to change, and again one cant have multi-line data.
This module is both better and worse than file-oriented databases like DB_File and its variants and extensions (such as MLDBM). This module does not require that each record have a unique key, and the fact that a DBM file is binary makes it not only less correctable, but also less portable. On the downside, this module isnt as fast.
Naturally, if ones data needs are more complex, it is probably better to use a fully-fledged database; this is oriented towards those who dont wish to have the overhead of setting up and maintaining a relational database server, and wish to use something more straightforward.
This comes bundled with other support modules, such as the Tie::FieldVals::Row module. The Tie::FieldVals::Select module is for selecting and sorting a sub-set from a Tie::FieldVals array, and the Tie::FieldVals::Join is a very simple method of joining two files on a common field.
This distribution includes the fv2xml script, which converts a Tie::FieldVals data file into an XML file, and xml2fv which converts an XML file into a Tie::FieldVals data file.
Download (0.053MB)
Added: 2007-08-21 License: Perl Artistic License Price:
794 downloads
Resizeable Form Fields 0.2.1
Resizeable Form Fields is an extension which allows you to resize HTML form fields, including textareas, select boxes and more. more>>
Resizeable Form Fields is an extension which allows you to resize HTML form fields, including textareas, select boxes and more.
Resize HTML form fields, including textareas, select boxes, text fields, and iframes.
<<lessResize HTML form fields, including textareas, select boxes, text fields, and iframes.
Download (0.004MB)
Added: 2007-04-04 License: MPL (Mozilla Public License) Price:
937 downloads
Eclipse Fieldviewer 1.0.0
Eclipse FieldViewer is a structured viewer component that displays data entry fields for model objects. more>>
Eclipse FieldViewer is a structured viewer component that displays data entry fields for model objects in a user defined, form based layout.
Eclipse FieldViewer is similar to the TableViewer component from JFace. Eclipse Fieldviewer separates the model from viewers in a similar way using Content- and Labelproviders to bind the data to the fields of the viewer. A Fieldviewer can display an array of similar elements. Unlike a tableviewer only a single element is shown at a time. The layout of the fields is not predefined as in a tableviewer.
This widget can be used in software using other JFace components (eg RCP applications).
Main features:
- interface similar to that of a JFace-TableViewer()
- ContentProvider(), LabelProvider() and Font-/ColorProvider()
- fields can display text and/or image
- ViewerSorter() and ViewerFilter()
- semi-automatic layout for simple requirements
- fully configurable layout of fields if necessary
- editable fields using standard CellEditors
Unlike a table viewer the Eclipse Fieldviewer is not a widget that has very unique features by itself. An experienced programmer can easily create the fields from scratch or use a tool for this task.
An Eclipse Fieldviewer widget is nice if you have to display data from a database where the user decides which element to display. It is also very well suited if you combine a Tableviewer()/TreeViewer() with a FieldViewer() and the user can decide how he wants the data displayed. Editable fields in these widgets use CellEditors to change the contents of the underlying model so the corresponding code can be reused and is not specifically tied to a single field.
<<lessEclipse FieldViewer is similar to the TableViewer component from JFace. Eclipse Fieldviewer separates the model from viewers in a similar way using Content- and Labelproviders to bind the data to the fields of the viewer. A Fieldviewer can display an array of similar elements. Unlike a tableviewer only a single element is shown at a time. The layout of the fields is not predefined as in a tableviewer.
This widget can be used in software using other JFace components (eg RCP applications).
Main features:
- interface similar to that of a JFace-TableViewer()
- ContentProvider(), LabelProvider() and Font-/ColorProvider()
- fields can display text and/or image
- ViewerSorter() and ViewerFilter()
- semi-automatic layout for simple requirements
- fully configurable layout of fields if necessary
- editable fields using standard CellEditors
Unlike a table viewer the Eclipse Fieldviewer is not a widget that has very unique features by itself. An experienced programmer can easily create the fields from scratch or use a tool for this task.
An Eclipse Fieldviewer widget is nice if you have to display data from a database where the user decides which element to display. It is also very well suited if you combine a Tableviewer()/TreeViewer() with a FieldViewer() and the user can decide how he wants the data displayed. Editable fields in these widgets use CellEditors to change the contents of the underlying model so the corresponding code can be reused and is not specifically tied to a single field.
Download (0.055MB)
Added: 2006-06-22 License: Eclipse Public License Price:
1229 downloads
Sort::Fields 0.90
Sort::Fields is a Perl module that can sort lines containing delimited fields. more>>
Sort::Fields is a Perl module that can sort lines containing delimited fields.
SYNOPSIS
use Sort::Fields;
@sorted = fieldsort [3, 2n], @lines;
@sorted = fieldsort +, [-1, -3, 0], @lines;
$sort_3_2n = make_fieldsort [3, 2n], @lines;
@sorted = $sort_3_2n->(@lines);
Sort::Fields provides a general purpose technique for efficiently sorting lists of lines that contain data separated into fields.
Sort::Fields automatically imports two subroutines, fieldsort and make_fieldsort, and two variants, stable_fieldsort and make_stable_fieldsort. make_fieldsort generates a sorting subroutine and returns a reference to it. fieldsort is a wrapper for the make_fieldsort subroutine.
The first argument to make_fieldsort is a delimiter string, which is used as a regular expression argument for a split operator. The delimiter string is optional. If it is not supplied, make_fieldsort splits each line using /s+/.
The second argument is an array reference containing one or more field specifiers. The specifiers indicate what fields in the strings will be used to sort the data. The specifier "1" indicates the first field, "2" indicates the second, and so on. A negative specifier like "-2" means to sort on the second field in reverse (descending) order. To indicate a numeric rather than alphabetic comparison, append "n" to the specifier. A specifier of "0" means the entire string ("-0" means the entire string, in reverse order).
The order in which the specifiers appear is the order in which they will be used to sort the data. The primary key is first, the secondary key is second, and so on.
fieldsort [1, 2], @data is roughly equivalent to make_fieldsort([1, 2])->(@data). Avoid calling fieldsort repeatedly with the same sort specifiers. If you need to use a particular sort more than once, it is more efficient to call make_fieldsort once and reuse the subroutine it returns.
stable_fieldsort and make_stable_fieldsort are like their "unstable" counterparts, except that the items that compare the same are maintained in their original order.
EXAMPLES
Some sample data (in array @data):
123 asd 1.22 asdd
32 ewq 2.32 asdd
43 rewq 2.12 ewet
51 erwt 34.2 ewet
23 erww 4.21 ewet
91 fdgs 3.43 ewet
123 refs 3.22 asdd
123 refs 4.32 asdd
# alpha sort on column 1
print fieldsort [1], @data;
123 asd 1.22 asdd
123 refs 3.22 asdd
123 refs 4.32 asdd
23 erww 4.21 ewet
32 ewq 2.32 asdd
43 rewq 2.12 ewet
51 erwt 34.2 ewet
91 fdgs 3.43 ewet
# numeric sort on column 1
print fieldsort [1n], @data;
23 erww 4.21 ewet
32 ewq 2.32 asdd
43 rewq 2.12 ewet
51 erwt 34.2 ewet
91 fdgs 3.43 ewet
123 asd 1.22 asdd
123 refs 3.22 asdd
123 refs 4.32 asdd
# reverse numeric sort on column 1
print fieldsort [-1n], @data;
123 asd 1.22 asdd
123 refs 3.22 asdd
123 refs 4.32 asdd
91 fdgs 3.43 ewet
51 erwt 34.2 ewet
43 rewq 2.12 ewet
32 ewq 2.32 asdd
23 erww 4.21 ewet
# alpha sort on column 2, then alpha on entire line
print fieldsort [2, 0], @data;
123 asd 1.22 asdd
51 erwt 34.2 ewet
23 erww 4.21 ewet
32 ewq 2.32 asdd
91 fdgs 3.43 ewet
123 refs 3.22 asdd
123 refs 4.32 asdd
43 rewq 2.12 ewet
# alpha sort on column 4, then numeric on column 1, then reverse
# numeric on column 3
print fieldsort [4, 1n, -3n], @data;
32 ewq 2.32 asdd
123 refs 4.32 asdd
123 refs 3.22 asdd
123 asd 1.22 asdd
23 erww 4.21 ewet
43 rewq 2.12 ewet
51 erwt 34.2 ewet
91 fdgs 3.43 ewet
# now, splitting on either literal period or whitespace
# sort numeric on column 4 (fractional part of decimals) then
# numeric on column 3 (whole part of decimals)
print fieldsort (?:.|s+), [4n, 3n], @data;
51 erwt 34.2 ewet
43 rewq 2.12 ewet
23 erww 4.21 ewet
123 asd 1.22 asdd
123 refs 3.22 asdd
32 ewq 2.32 asdd
123 refs 4.32 asdd
91 fdgs 3.43 ewet
# alpha sort on column 4, then numeric on the entire line
# NOTE: produces warnings under -w
print fieldsort [4, 0n], @data;
32 ewq 2.32 asdd
123 asd 1.22 asdd
123 refs 3.22 asdd
123 refs 4.32 asdd
23 erww 4.21 ewet
43 rewq 2.12 ewet
51 erwt 34.2 ewet
91 fdgs 3.43 ewet
# stable alpha sort on column 4 (maintains original relative order
# among items that compare the same)
print stable_fieldsort [4], @data;
123 asd 1.22 asdd
32 ewq 2.32 asdd
123 refs 3.22 asdd
123 refs 4.32 asdd
43 rewq 2.12 ewet
51 erwt 34.2 ewet
23 erww 4.21 ewet
91 fdgs 3.43 ewet
<<lessSYNOPSIS
use Sort::Fields;
@sorted = fieldsort [3, 2n], @lines;
@sorted = fieldsort +, [-1, -3, 0], @lines;
$sort_3_2n = make_fieldsort [3, 2n], @lines;
@sorted = $sort_3_2n->(@lines);
Sort::Fields provides a general purpose technique for efficiently sorting lists of lines that contain data separated into fields.
Sort::Fields automatically imports two subroutines, fieldsort and make_fieldsort, and two variants, stable_fieldsort and make_stable_fieldsort. make_fieldsort generates a sorting subroutine and returns a reference to it. fieldsort is a wrapper for the make_fieldsort subroutine.
The first argument to make_fieldsort is a delimiter string, which is used as a regular expression argument for a split operator. The delimiter string is optional. If it is not supplied, make_fieldsort splits each line using /s+/.
The second argument is an array reference containing one or more field specifiers. The specifiers indicate what fields in the strings will be used to sort the data. The specifier "1" indicates the first field, "2" indicates the second, and so on. A negative specifier like "-2" means to sort on the second field in reverse (descending) order. To indicate a numeric rather than alphabetic comparison, append "n" to the specifier. A specifier of "0" means the entire string ("-0" means the entire string, in reverse order).
The order in which the specifiers appear is the order in which they will be used to sort the data. The primary key is first, the secondary key is second, and so on.
fieldsort [1, 2], @data is roughly equivalent to make_fieldsort([1, 2])->(@data). Avoid calling fieldsort repeatedly with the same sort specifiers. If you need to use a particular sort more than once, it is more efficient to call make_fieldsort once and reuse the subroutine it returns.
stable_fieldsort and make_stable_fieldsort are like their "unstable" counterparts, except that the items that compare the same are maintained in their original order.
EXAMPLES
Some sample data (in array @data):
123 asd 1.22 asdd
32 ewq 2.32 asdd
43 rewq 2.12 ewet
51 erwt 34.2 ewet
23 erww 4.21 ewet
91 fdgs 3.43 ewet
123 refs 3.22 asdd
123 refs 4.32 asdd
# alpha sort on column 1
print fieldsort [1], @data;
123 asd 1.22 asdd
123 refs 3.22 asdd
123 refs 4.32 asdd
23 erww 4.21 ewet
32 ewq 2.32 asdd
43 rewq 2.12 ewet
51 erwt 34.2 ewet
91 fdgs 3.43 ewet
# numeric sort on column 1
print fieldsort [1n], @data;
23 erww 4.21 ewet
32 ewq 2.32 asdd
43 rewq 2.12 ewet
51 erwt 34.2 ewet
91 fdgs 3.43 ewet
123 asd 1.22 asdd
123 refs 3.22 asdd
123 refs 4.32 asdd
# reverse numeric sort on column 1
print fieldsort [-1n], @data;
123 asd 1.22 asdd
123 refs 3.22 asdd
123 refs 4.32 asdd
91 fdgs 3.43 ewet
51 erwt 34.2 ewet
43 rewq 2.12 ewet
32 ewq 2.32 asdd
23 erww 4.21 ewet
# alpha sort on column 2, then alpha on entire line
print fieldsort [2, 0], @data;
123 asd 1.22 asdd
51 erwt 34.2 ewet
23 erww 4.21 ewet
32 ewq 2.32 asdd
91 fdgs 3.43 ewet
123 refs 3.22 asdd
123 refs 4.32 asdd
43 rewq 2.12 ewet
# alpha sort on column 4, then numeric on column 1, then reverse
# numeric on column 3
print fieldsort [4, 1n, -3n], @data;
32 ewq 2.32 asdd
123 refs 4.32 asdd
123 refs 3.22 asdd
123 asd 1.22 asdd
23 erww 4.21 ewet
43 rewq 2.12 ewet
51 erwt 34.2 ewet
91 fdgs 3.43 ewet
# now, splitting on either literal period or whitespace
# sort numeric on column 4 (fractional part of decimals) then
# numeric on column 3 (whole part of decimals)
print fieldsort (?:.|s+), [4n, 3n], @data;
51 erwt 34.2 ewet
43 rewq 2.12 ewet
23 erww 4.21 ewet
123 asd 1.22 asdd
123 refs 3.22 asdd
32 ewq 2.32 asdd
123 refs 4.32 asdd
91 fdgs 3.43 ewet
# alpha sort on column 4, then numeric on the entire line
# NOTE: produces warnings under -w
print fieldsort [4, 0n], @data;
32 ewq 2.32 asdd
123 asd 1.22 asdd
123 refs 3.22 asdd
123 refs 4.32 asdd
23 erww 4.21 ewet
43 rewq 2.12 ewet
51 erwt 34.2 ewet
91 fdgs 3.43 ewet
# stable alpha sort on column 4 (maintains original relative order
# among items that compare the same)
print stable_fieldsort [4], @data;
123 asd 1.22 asdd
32 ewq 2.32 asdd
123 refs 3.22 asdd
123 refs 4.32 asdd
43 rewq 2.12 ewet
51 erwt 34.2 ewet
23 erww 4.21 ewet
91 fdgs 3.43 ewet
Download (0.005MB)
Added: 2007-05-21 License: Perl Artistic License Price:
887 downloads
UnHide fields 0.2 for Firefox
UnHide fields provides this extension allow you to view and edit hidden fields content. more>>
UnHide fields provides this extension allow you to view and edit hidden fields content.
In computer science, data that has several parts can be divided into fields. For example, a computer may represent todays date as three distinct fields: the day, the month and the year.
Programming languages usually have a record data type to represent composite data types as a series of fields. An array of boolean values can be represented as a bit field.
<<lessIn computer science, data that has several parts can be divided into fields. For example, a computer may represent todays date as three distinct fields: the day, the month and the year.
Programming languages usually have a record data type to represent composite data types as a series of fields. An array of boolean values can be represented as a bit field.
Download (0.013MB)
Added: 2007-04-13 License: MPL (Mozilla Public License) Price:
926 downloads
fields::aliased 1.05
fields::aliased is a Perl module that can create aliases for object fields. more>>
fields::aliased is a Perl module that can create aliases for object fields.
SYNOPSIS
package MyPackage;
use strict;
use fields qw($scalar @array %hash);
sub new {
my $class = shift;
my $self = fields::new($class);
return $self;
}
sub mymethod {
my MyPackage $self = shift;
use fields::aliased qw($self $scalar @array %hash);
$scalar = 1;
@array = (2 .. 4);
%hash = (one => 1, two => 2);
}
This module is a companion to the fields module, which allows efficient handling of instance variables with checking at compile time. It goes one step further and actually creates lexical aliases to the instance values, which can make code not only easier to type, but easier to read as well.
Declarations
You declare the fields using the fields pragma, as always.
use fields qw($scalar @array %hash nosigil);
Each field name may be preceded by a type sigil to indicate which kind of variable it is. Names without the type sigil are treated as scalars.
For names beginning with an underscore, see "PRIVATE FIELDS" below.
Constructors
You call fields::new to create the object.
my $self = fields::new($class);
Usage
In each method that uses the individual fields, you add a line similar to the following:
use fields::aliased qw($self $scalar @array %hash nosigil);
That is, list the variable being used for the object reference, and then the names of the fields that you are going to use in this method. fields::aliased takes care of declaring the appropriate Perl lexical variables and linking them to the appropriate field. You only need to specify the fields you are actually going to use, including any inherited from superclasses.
<<lessSYNOPSIS
package MyPackage;
use strict;
use fields qw($scalar @array %hash);
sub new {
my $class = shift;
my $self = fields::new($class);
return $self;
}
sub mymethod {
my MyPackage $self = shift;
use fields::aliased qw($self $scalar @array %hash);
$scalar = 1;
@array = (2 .. 4);
%hash = (one => 1, two => 2);
}
This module is a companion to the fields module, which allows efficient handling of instance variables with checking at compile time. It goes one step further and actually creates lexical aliases to the instance values, which can make code not only easier to type, but easier to read as well.
Declarations
You declare the fields using the fields pragma, as always.
use fields qw($scalar @array %hash nosigil);
Each field name may be preceded by a type sigil to indicate which kind of variable it is. Names without the type sigil are treated as scalars.
For names beginning with an underscore, see "PRIVATE FIELDS" below.
Constructors
You call fields::new to create the object.
my $self = fields::new($class);
Usage
In each method that uses the individual fields, you add a line similar to the following:
use fields::aliased qw($self $scalar @array %hash nosigil);
That is, list the variable being used for the object reference, and then the names of the fields that you are going to use in this method. fields::aliased takes care of declaring the appropriate Perl lexical variables and linking them to the appropriate field. You only need to specify the fields you are actually going to use, including any inherited from superclasses.
Download (0.008MB)
Added: 2007-05-14 License: Perl Artistic License Price:
894 downloads
Field Designer 0.6.2
The Field Designer is a program for designing sub-air paintball fields. more>>
The Field Designer is a program for designing sub-air paintball fields. Field Designer helps you to prepare for a paintball tournament or fun game, or simply to get an overview of a field. Field owners can use it to provide online layouts of their fields.
Main features:
- Delete Figure
- Editable properties
- Default XML Encoding
- Tippie figure
- Tombstone figure
- Export a JPG picture of the field
- Povray Export
- Copy and Paste
- Context menu
- Tactics plugin
- Rotate figures
- 3D field walking
Enhancements:
- A tactics editor was added, allowing you to develop your tactics directly in the field designer.
- Real units of measure can be used, so 32px will represent whatever unit of measure you define.
- When you create a new field layout, you can set the size of the field, which will be shown while drawing the field.
- Fields can be exported to SVG, BMP, JPEG, or PDF.
- The last page of the field creation wizard does not work correctly under Win32.
<<lessMain features:
- Delete Figure
- Editable properties
- Default XML Encoding
- Tippie figure
- Tombstone figure
- Export a JPG picture of the field
- Povray Export
- Copy and Paste
- Context menu
- Tactics plugin
- Rotate figures
- 3D field walking
Enhancements:
- A tactics editor was added, allowing you to develop your tactics directly in the field designer.
- Real units of measure can be used, so 32px will represent whatever unit of measure you define.
- When you create a new field layout, you can set the size of the field, which will be shown while drawing the field.
- Fields can be exported to SVG, BMP, JPEG, or PDF.
- The last page of the field creation wizard does not work correctly under Win32.
Download (15MB)
Added: 2006-02-27 License: Eclipse Public License Price:
1338 downloads
Mail::Message::Field 2.072
Mail::Message::Field contains one line of a message header. more>>
Mail::Message::Field contains one line of a message header.
INHERITANCE
Mail::Message::Field
is a Mail::Reporter
Mail::Message::Field is extended by
Mail::Message::Field::Fast
Mail::Message::Field::Flex
Mail::Message::Field::Full
SYNOPSIS
my $field = Mail::Message::Field->new(From => fish@tux.aq);
print $field->name;
print $field->body;
print $field->comment;
print $field->content; # body & comment
$field->print(*OUT);
print $field->string;
print "$fieldn";
print $field->attribute(charset) || us-ascii;
This implementation follows the guidelines of rfc2822 as close as possible, and may there produce a different output than implementations based on the obsolete rfc822. However, the old output will still be accepted.
These objects each store one header line, and facilitates access routines to the information hidden in it. Also, you may want to have a look at the added methods of a message:
my @from = $message->from;
my $sender = $message->sender;
my $subject = $message->subject;
my $msgid = $message->messageId;
my @to = $message->to;
my @cc = $message->cc;
my @bcc = $message->bcc;
my @dest = $message->destinations;
my $other = $message->get(Reply-To);
<<lessINHERITANCE
Mail::Message::Field
is a Mail::Reporter
Mail::Message::Field is extended by
Mail::Message::Field::Fast
Mail::Message::Field::Flex
Mail::Message::Field::Full
SYNOPSIS
my $field = Mail::Message::Field->new(From => fish@tux.aq);
print $field->name;
print $field->body;
print $field->comment;
print $field->content; # body & comment
$field->print(*OUT);
print $field->string;
print "$fieldn";
print $field->attribute(charset) || us-ascii;
This implementation follows the guidelines of rfc2822 as close as possible, and may there produce a different output than implementations based on the obsolete rfc822. However, the old output will still be accepted.
These objects each store one header line, and facilitates access routines to the information hidden in it. Also, you may want to have a look at the added methods of a message:
my @from = $message->from;
my $sender = $message->sender;
my $subject = $message->subject;
my $msgid = $message->messageId;
my @to = $message->to;
my @cc = $message->cc;
my @bcc = $message->bcc;
my @dest = $message->destinations;
my $other = $message->get(Reply-To);
Download (0.58MB)
Added: 2007-07-13 License: Perl Artistic License Price:
833 downloads
Mail::Field 1.74
Mail::Field is a base class for manipulation of mail header fields. more>>
Mail::Field is a base class for manipulation of mail header fields.
SYNOPSIS
use Mail::Field;
$field = Mail::Field->new(Subject, some subject text);
print $field->tag,": ",$field->stringify,"n";
$field = Mail::Field->subject(some subject text);
Mail::Field is a base class for packages that create and manipulate fields from Email (and MIME) headers. Each different field will have its own sub-class, defining its own interface.
This document describes the minimum interface that each sub-class should provide, and also guidlines on how the field specific interface should be defined.
<<lessSYNOPSIS
use Mail::Field;
$field = Mail::Field->new(Subject, some subject text);
print $field->tag,": ",$field->stringify,"n";
$field = Mail::Field->subject(some subject text);
Mail::Field is a base class for packages that create and manipulate fields from Email (and MIME) headers. Each different field will have its own sub-class, defining its own interface.
This document describes the minimum interface that each sub-class should provide, and also guidlines on how the field specific interface should be defined.
Download (0.047MB)
Added: 2006-06-29 License: Perl Artistic License Price:
1218 downloads
Class::Struct::FIELDS 1.1
Class::Struct::FIELDS module combine Class::Struct, base and fields. more>>
Class::Struct::FIELDS module combine Class::Struct, base and fields.
SYNOPSIS
(This page documents Class::Struct::FIELDS v.1.1.)
use Class::Struct::FIELDS;
# declare struct, based on fields, explicit class name:
struct (CLASS_NAME => { ELEMENT_NAME => ELEMENT_TYPE, ... });
use Class::Struct::FIELDS;
# declare struct, based on fields, explicit class name
# with inheritance:
struct (CLASS_NAME => [qw(BASE_CLASSES ...)],
{ ELEMENT_NAME => ELEMENT_TYPE, ... });
package CLASS_NAME;
use Class::Struct::FIELDS;
# declare struct, based on fields, implicit class name:
struct (ELEMENT_NAME => ELEMENT_TYPE, ...);
package CLASS_NAME;
use Class::Struct::FIELDS;
# declare struct, based on fields, implicit class name
# with inheritance:
struct ([qw(BASE_CLASSES ...)], ELEMENT_NAME => ELEMENT_TYPE, ...);
package MyObj;
use Class::Struct::FIELDS;
# declare struct with four types of elements:
struct (s => $, a => @, h => %, x => &, c => My_Other_Class);
$obj = new MyObj; # constructor
# scalar type accessor:
$element_value = $obj->s; # element value
$obj->s (new value); # assign to element
# array type accessor:
$ary_ref = $obj->a; # reference to whole array
$ary_element_value = $obj->a->[2]; # array element value
$ary_element_value = $obj->a (2); # same thing
$obj->a->[2] = new value; # assign to array element
$obj->a (2, newer value); # same thing
# hash type accessor:
$hash_ref = $obj->h; # reference to whole hash
$hash_element_value = $obj->h->{x}; # hash element value
$hash_element_value = $obj->h (x); # same thing
$obj->h->{x} = new value; # assign to hash element
$obj->h (x, newer value); # same thing
# code type accessor:
$code_ref = $obj->x; # reference to code
$obj->x->(...); # call code
$obj->x (sub {...}); # assign to element
# regexp type accessor:
$regexp = $obj->r; # reference to code
$string =~ m/$obj->r/; # match regexp
$obj->r (qr/ ... /); # assign to element
# class type accessor:
$element_value = $obj->c; # object reference
$obj->c->method (...); # call method of object
$obj->c (My_Other_Class::->new); # assign a new object
Class::Struct::FIELDS exports a single function, struct. Given a list of element names and types, and optionally a class name and/or an array reference of base classes, struct creates a Perl 5 class that implements a "struct-like" data structure with inheritance.
The new class is given a constructor method, new, for creating struct objects.
Each element in the struct data has an accessor method, which is used to assign to the element and to fetch its value. The default accessor can be overridden by declaring a sub of the same name in the package. (See Example 2.)
Each elements type can be scalar, array, hash, code or class.
<<lessSYNOPSIS
(This page documents Class::Struct::FIELDS v.1.1.)
use Class::Struct::FIELDS;
# declare struct, based on fields, explicit class name:
struct (CLASS_NAME => { ELEMENT_NAME => ELEMENT_TYPE, ... });
use Class::Struct::FIELDS;
# declare struct, based on fields, explicit class name
# with inheritance:
struct (CLASS_NAME => [qw(BASE_CLASSES ...)],
{ ELEMENT_NAME => ELEMENT_TYPE, ... });
package CLASS_NAME;
use Class::Struct::FIELDS;
# declare struct, based on fields, implicit class name:
struct (ELEMENT_NAME => ELEMENT_TYPE, ...);
package CLASS_NAME;
use Class::Struct::FIELDS;
# declare struct, based on fields, implicit class name
# with inheritance:
struct ([qw(BASE_CLASSES ...)], ELEMENT_NAME => ELEMENT_TYPE, ...);
package MyObj;
use Class::Struct::FIELDS;
# declare struct with four types of elements:
struct (s => $, a => @, h => %, x => &, c => My_Other_Class);
$obj = new MyObj; # constructor
# scalar type accessor:
$element_value = $obj->s; # element value
$obj->s (new value); # assign to element
# array type accessor:
$ary_ref = $obj->a; # reference to whole array
$ary_element_value = $obj->a->[2]; # array element value
$ary_element_value = $obj->a (2); # same thing
$obj->a->[2] = new value; # assign to array element
$obj->a (2, newer value); # same thing
# hash type accessor:
$hash_ref = $obj->h; # reference to whole hash
$hash_element_value = $obj->h->{x}; # hash element value
$hash_element_value = $obj->h (x); # same thing
$obj->h->{x} = new value; # assign to hash element
$obj->h (x, newer value); # same thing
# code type accessor:
$code_ref = $obj->x; # reference to code
$obj->x->(...); # call code
$obj->x (sub {...}); # assign to element
# regexp type accessor:
$regexp = $obj->r; # reference to code
$string =~ m/$obj->r/; # match regexp
$obj->r (qr/ ... /); # assign to element
# class type accessor:
$element_value = $obj->c; # object reference
$obj->c->method (...); # call method of object
$obj->c (My_Other_Class::->new); # assign a new object
Class::Struct::FIELDS exports a single function, struct. Given a list of element names and types, and optionally a class name and/or an array reference of base classes, struct creates a Perl 5 class that implements a "struct-like" data structure with inheritance.
The new class is given a constructor method, new, for creating struct objects.
Each element in the struct data has an accessor method, which is used to assign to the element and to fetch its value. The default accessor can be overridden by declaring a sub of the same name in the package. (See Example 2.)
Each elements type can be scalar, array, hash, code or class.
Download (0.018MB)
Added: 2007-07-11 License: Perl Artistic License Price:
835 downloads
hReview WordPress Plugin 0.2
hReview WordPress Plugin is a plugin that allows for the easy entry of hReview microformat content for reviews in WordPress. more>>
hReview WordPress Plugin is a plugin that allows for the easy entry of hReview microformat content for reviews in WordPress 2.0.x pages and posts.
The plugin adds a button to the editor that pops up a form with basic review fields, then inserts the contents of the fields back into the editor using markup compatible with hReview.
<<lessThe plugin adds a button to the editor that pops up a form with basic review fields, then inserts the contents of the fields back into the editor using markup compatible with hReview.
Download (0.012MB)
Added: 2006-12-05 License: GPL (GNU General Public License) Price:
1053 downloads
Agendaroids 2002.03.07
Agendaroids is an Asteroids clone for the Agenda VR3 PDA. more>>
Agendaroids is an "Asteroids" clone for the Agenda VR3 PDA.
Agendaroids is a game where you maneuver a space ship in a field of asteroids, and shoot at them to break them into smaller pieces.
It uses vector-based graphics with fixed-point trigonometry, so it runs well even on the FPU-less VR3, but it also runs on any other Xlib-based system.
Main features:
- Smooth vector graphics
- Dark-on-light display; better for greyscale LCD screens
- Light-on-dark display for monitors and color LCDs
- Looks really cool with the backlight on!
- Rotating asteroids
- Fast, table-based trigonometric functions
- Agenda-friendly key controls (as well as PC keyboard alternative)
- Sound effects (via piezo buzzer)
- Pause and resume (even if you quit)
- ... and more!
<<lessAgendaroids is a game where you maneuver a space ship in a field of asteroids, and shoot at them to break them into smaller pieces.
It uses vector-based graphics with fixed-point trigonometry, so it runs well even on the FPU-less VR3, but it also runs on any other Xlib-based system.
Main features:
- Smooth vector graphics
- Dark-on-light display; better for greyscale LCD screens
- Light-on-dark display for monitors and color LCDs
- Looks really cool with the backlight on!
- Rotating asteroids
- Fast, table-based trigonometric functions
- Agenda-friendly key controls (as well as PC keyboard alternative)
- Sound effects (via piezo buzzer)
- Pause and resume (even if you quit)
- ... and more!
Download (0.042MB)
Added: 2006-11-25 License: GPL (GNU General Public License) Price:
1064 downloads
Mail::Message::Head::FieldGroup 2.069
Mail::Message::Head::FieldGroup is a Perl module with a sub set of fields in a header. more>>
Mail::Message::Head::FieldGroup is a Perl module with a sub set of fields in a header.
INHERITANCE
Mail::Message::Head::FieldGroup
is a Mail::Reporter
Mail::Message::Head::FieldGroup is extended by
Mail::Message::Head::ListGroup
Mail::Message::Head::ResentGroup
Mail::Message::Head::SpamGroup
Some fields have a combined meaning: a set of fields which represent one intermediate step during the transport of the message (a resent group, implemented in Mail::Message::Head::ResentGroup), fields added by mailing list software (implemented in Mail::Message::Head::ListGroup), or fields added by Spam detection related software (implemented by Mail::Message::Head::SpamGroup). Each set of fields can be extracted or added as group with objects which are based on the implementation in this class.
<<lessINHERITANCE
Mail::Message::Head::FieldGroup
is a Mail::Reporter
Mail::Message::Head::FieldGroup is extended by
Mail::Message::Head::ListGroup
Mail::Message::Head::ResentGroup
Mail::Message::Head::SpamGroup
Some fields have a combined meaning: a set of fields which represent one intermediate step during the transport of the message (a resent group, implemented in Mail::Message::Head::ResentGroup), fields added by mailing list software (implemented in Mail::Message::Head::ListGroup), or fields added by Spam detection related software (implemented by Mail::Message::Head::SpamGroup). Each set of fields can be extracted or added as group with objects which are based on the implementation in this class.
Download (0.57MB)
Added: 2007-01-11 License: Perl Artistic License Price:
1016 downloads
Unhide Passwords 1.1.3.1
Unhide Passwords shows the contents of password fields in cleartext (instead of the asterisks), to make that process a bit easie more>>
If you arent concerned about someone looking over your shoulder and stealing your passwords, why hassle with those obfuscated password fields, where you never know whether you typed your 30 character code correctly or not...
Unhide Passwords shows the contents of password fields in cleartext (instead of the asterisks), to make that process a bit easier.
<<lessUnhide Passwords shows the contents of password fields in cleartext (instead of the asterisks), to make that process a bit easier.
Download (0.010MB)
Added: 2007-07-24 License: MPL (Mozilla Public License) Price:
695 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 even fields 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