properties
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 650
Java Properties 0.8.3
Java Properties provides an efficient way to access bean-like properties of Java objects. more>>
Java Properties provides an efficient way to access bean-like properties of Java objects.
In a nutshell, provides an efficient way to access bean-like properties of java objects. Unlike java bean properties, a chain of properties can be specified efficiently, allowing convenient access to properties of nested domain objects.
Runtime class-generation and caching can be used very easily to obviate the need for reflection, without losing the flexibility it provides.
Class Properties It also provides classes which manipulate objects at runtime by using strings to address conceptual variables (think bean properties) in a similar fashion to the java reflection mechanisms.
Class Property example Say we have the following classes:
public class Order {
...
public Customer getCustomer() { ... }
...
}
public class Customer {
...
public Address getAddress() { ... }
...
}
public class Address {
...
public String getLine1() { ... }
public String getLine2() { ... }
...
}
Now, we could do this to access line 1 of the address:
result = order.getCustomer().getAddress().getLine1();
But what if there are nulls? What if we want to compare the first line of the address from two different orders? Whith properties this is really simple:
ClassProperty p = PropertyManager.getProperty(Order.class,"Customer:Address:Line1",true);
result = p.getValue(order);
The idea is simple enough - you use the string "Customer:Address:Line1" to specify a series of getXXX calls. Importantly, it the library handles nulls for you, returning null if any of the objects in the chain are null.
Note, this is not simply a wrapper around java reflection, since it includes non-reflective optimizations by making use of the cojen library to generate class files at runtime to acces these properties.
The real benefit lies in being able to specify which properties you wish to access at runtime. You can even pass this ability on to the users of your library or application. Unlike reflection, class files are generated for the properties, and these files are cached - which means once you have specified a property once, further uses of the same property dont use reflection and are very fast.
Property API vs Java Bean Properties. The property API models accessor/mutator method pairs as conceptual variables called properties. The approach used is similar to, but more flexible than java bean properties, and more performant than reflection if runtime class generation is used. Unlike java bean properties, a chain or path of properties can be specified (and more importantly, turned into bytecode using runtime generation) to traverse a complex tree of objects.
It is simple to create applications portable between different security environments - using runtime generation where allowed, and falling back to reflection where security is tighter.
Dynamic Class Management. The properties package also provides classes to handle the loading (and unloading/reloading) of classes at runtime. It provides a framework useful for dynamically loading runtime-generated classes, for example.
While the property API can happily ignore the dynamic loading framework, it can also make use of it to enable runtime class generation.
<<lessIn a nutshell, provides an efficient way to access bean-like properties of java objects. Unlike java bean properties, a chain of properties can be specified efficiently, allowing convenient access to properties of nested domain objects.
Runtime class-generation and caching can be used very easily to obviate the need for reflection, without losing the flexibility it provides.
Class Properties It also provides classes which manipulate objects at runtime by using strings to address conceptual variables (think bean properties) in a similar fashion to the java reflection mechanisms.
Class Property example Say we have the following classes:
public class Order {
...
public Customer getCustomer() { ... }
...
}
public class Customer {
...
public Address getAddress() { ... }
...
}
public class Address {
...
public String getLine1() { ... }
public String getLine2() { ... }
...
}
Now, we could do this to access line 1 of the address:
result = order.getCustomer().getAddress().getLine1();
But what if there are nulls? What if we want to compare the first line of the address from two different orders? Whith properties this is really simple:
ClassProperty p = PropertyManager.getProperty(Order.class,"Customer:Address:Line1",true);
result = p.getValue(order);
The idea is simple enough - you use the string "Customer:Address:Line1" to specify a series of getXXX calls. Importantly, it the library handles nulls for you, returning null if any of the objects in the chain are null.
Note, this is not simply a wrapper around java reflection, since it includes non-reflective optimizations by making use of the cojen library to generate class files at runtime to acces these properties.
The real benefit lies in being able to specify which properties you wish to access at runtime. You can even pass this ability on to the users of your library or application. Unlike reflection, class files are generated for the properties, and these files are cached - which means once you have specified a property once, further uses of the same property dont use reflection and are very fast.
Property API vs Java Bean Properties. The property API models accessor/mutator method pairs as conceptual variables called properties. The approach used is similar to, but more flexible than java bean properties, and more performant than reflection if runtime class generation is used. Unlike java bean properties, a chain or path of properties can be specified (and more importantly, turned into bytecode using runtime generation) to traverse a complex tree of objects.
It is simple to create applications portable between different security environments - using runtime generation where allowed, and falling back to reflection where security is tighter.
Dynamic Class Management. The properties package also provides classes to handle the loading (and unloading/reloading) of classes at runtime. It provides a framework useful for dynamically loading runtime-generated classes, for example.
While the property API can happily ignore the dynamic loading framework, it can also make use of it to enable runtime class generation.
Download (0.017MB)
Added: 2007-01-10 License: GPL (GNU General Public License) Price:
1017 downloads
MMDS::Properties 1.902
MMDS::Properties Perl module contains flexible properties handling for MMDS. more>>
MMDS::Properties Perl module contains flexible properties handling for MMDS.
use MMDS::Properties;
my $cfg = new MMDS::Properties;
# Preset a property.
$cfg->set_property("config.version", "1.23");
# Parse a properties file.
$cfg->parsefile("config.prp");
# Get a property value
$version = $cfg->get_property("config.version");
# Same, but with a default value.
$version = $cfg->get_property("config.version", "1.23");
# Get the list of subkeys for a property, and process them.
my $aref = $cfg->get_property_keys("item.list");
foreach my $item ( @$aref ) {
if ( $cfg->get_property("item.list.$item") ) {
....
}
}
The property mechanism is modelled after the Java implementation of properties.
In general, a property is a string value that is associated with a key. A key is a series of names (identifiers) separated with periods. Names are treated case insensitive. Unlike in Java, the properties are really hierarchically organized. This means that for a given property you can fetch the list of its subkeys, and so on. Moreover, the list of subkeys is returned in the order the properties were defined.
Property lookup can use a preset property context. If a context ctx has been set using set_context(ctx), get_property(foo.bar) will first try ctx.foo.bar and then foo.bar. get_property(.foo.bar) (note the leading period) will only try ctx.foo.bar and raise an exception if no context was set.
Design goals:
- properties must be hierarchical of unlimited depth;
- manual editing of the property files (hence unambiguous syntax and lay out);
- it must be possible to locate all subkeys of a property in the order they appear in the property file(s);
- lightweight so shell scripts can use it to query properties.
METHODS
new
new is the standard constructor. new doesnt require any arguments, but you can pass it a list of initial properties to store in the resultant properties object.
new
clone is like new, but it takes an existing properties object as its invocant and returns a new object with the contents copied.
WARNING This is not yet a deep copy, so take care.
parsefile file [ , path [ , context ] ]
parsefile reads a properties file and adds the contents to the properties object.
file is the name of the properties file. This file is searched in all elements of path (an array reference) unless the name starts with a slash. Default path is . (current directory).
context can be used to designate an initial context where all properties from the file will be subkeys of.
For the detailed format of properties files see below.
get_property prop [ , default ]
Get the value for a given property prop.
If a context ctx has been set using set_context(ctx), get_property(foo.bar) will first try ctx.foo.bar and then foo.bar. get_property(.foo.bar) (note the leading period) will only try ctx.foo.bar and raise an exception if no context was set.
If no value can be found, default is used.
In either case, the resultant value is examined for references to other properties or environment variables. Such a reference looks like
${name}
${name:default}
name can be the name of an environment variable or property. If name is found in the environment, its value is substituted and the expansion process continues, re-examining the new contents, until no further substitutions can be made. If a non-empty value exists for the property name its value is used in a similar way. Hence an empty value for a property will be ignored. If no value can be found, the default string (not to be confused with the default parameter) will be returned.
As an additional service, a tilde ~ in what looks like a file name will be expanded to ${HOME}.
The method result_in_context can be used to determine how the result was obtained. It will return a non-empty string indicating the context in which the result was found, an emptry string indicating the result was found without context, or undef if no value was found at all.
get_property_noexpand prop [ , default ]
This is like get_property, but does not do any expansion.
gps prop [ , default ]
This is like get_property, but raises an exception if no value could be established.
This is probably the best and safest method to use.
get_property_keys prop
Returns an array reference with the names of the (sub)keys for the given property. The names are unqualified, e.g., when properties foo.bar and foo.blech exist, get_property_keys(foo) would return [bar, blech].
expand value [ , context ]
Perform the expansion as described with get_property.
set_property prop, value
Set the property to the given value.
set_properties prop1 => value1, ...
Add a hash (key/value pairs) of properties to the set of properties.
set_context context
Set the search context. Without argument, clears the current context.
get_context
Get the current search context.
result_in_context
Get the context status of the last search.
Empty means it was found out of context, a string indicates the context in which the result was found, and undef indicates search failure.
dump [ start [ , stream ] ]
Produce a listing of all properties from a given point in the hierarchy and write it to the stream.
stream defaults to *STDOUT.
dumpx [ start [ , stream ] ]
Like dump, but dumps with all values expanded.
<<lessuse MMDS::Properties;
my $cfg = new MMDS::Properties;
# Preset a property.
$cfg->set_property("config.version", "1.23");
# Parse a properties file.
$cfg->parsefile("config.prp");
# Get a property value
$version = $cfg->get_property("config.version");
# Same, but with a default value.
$version = $cfg->get_property("config.version", "1.23");
# Get the list of subkeys for a property, and process them.
my $aref = $cfg->get_property_keys("item.list");
foreach my $item ( @$aref ) {
if ( $cfg->get_property("item.list.$item") ) {
....
}
}
The property mechanism is modelled after the Java implementation of properties.
In general, a property is a string value that is associated with a key. A key is a series of names (identifiers) separated with periods. Names are treated case insensitive. Unlike in Java, the properties are really hierarchically organized. This means that for a given property you can fetch the list of its subkeys, and so on. Moreover, the list of subkeys is returned in the order the properties were defined.
Property lookup can use a preset property context. If a context ctx has been set using set_context(ctx), get_property(foo.bar) will first try ctx.foo.bar and then foo.bar. get_property(.foo.bar) (note the leading period) will only try ctx.foo.bar and raise an exception if no context was set.
Design goals:
- properties must be hierarchical of unlimited depth;
- manual editing of the property files (hence unambiguous syntax and lay out);
- it must be possible to locate all subkeys of a property in the order they appear in the property file(s);
- lightweight so shell scripts can use it to query properties.
METHODS
new
new is the standard constructor. new doesnt require any arguments, but you can pass it a list of initial properties to store in the resultant properties object.
new
clone is like new, but it takes an existing properties object as its invocant and returns a new object with the contents copied.
WARNING This is not yet a deep copy, so take care.
parsefile file [ , path [ , context ] ]
parsefile reads a properties file and adds the contents to the properties object.
file is the name of the properties file. This file is searched in all elements of path (an array reference) unless the name starts with a slash. Default path is . (current directory).
context can be used to designate an initial context where all properties from the file will be subkeys of.
For the detailed format of properties files see below.
get_property prop [ , default ]
Get the value for a given property prop.
If a context ctx has been set using set_context(ctx), get_property(foo.bar) will first try ctx.foo.bar and then foo.bar. get_property(.foo.bar) (note the leading period) will only try ctx.foo.bar and raise an exception if no context was set.
If no value can be found, default is used.
In either case, the resultant value is examined for references to other properties or environment variables. Such a reference looks like
${name}
${name:default}
name can be the name of an environment variable or property. If name is found in the environment, its value is substituted and the expansion process continues, re-examining the new contents, until no further substitutions can be made. If a non-empty value exists for the property name its value is used in a similar way. Hence an empty value for a property will be ignored. If no value can be found, the default string (not to be confused with the default parameter) will be returned.
As an additional service, a tilde ~ in what looks like a file name will be expanded to ${HOME}.
The method result_in_context can be used to determine how the result was obtained. It will return a non-empty string indicating the context in which the result was found, an emptry string indicating the result was found without context, or undef if no value was found at all.
get_property_noexpand prop [ , default ]
This is like get_property, but does not do any expansion.
gps prop [ , default ]
This is like get_property, but raises an exception if no value could be established.
This is probably the best and safest method to use.
get_property_keys prop
Returns an array reference with the names of the (sub)keys for the given property. The names are unqualified, e.g., when properties foo.bar and foo.blech exist, get_property_keys(foo) would return [bar, blech].
expand value [ , context ]
Perform the expansion as described with get_property.
set_property prop, value
Set the property to the given value.
set_properties prop1 => value1, ...
Add a hash (key/value pairs) of properties to the set of properties.
set_context context
Set the search context. Without argument, clears the current context.
get_context
Get the current search context.
result_in_context
Get the context status of the last search.
Empty means it was found out of context, a string indicates the context in which the result was found, and undef indicates search failure.
dump [ start [ , stream ] ]
Produce a listing of all properties from a given point in the hierarchy and write it to the stream.
stream defaults to *STDOUT.
dumpx [ start [ , stream ] ]
Like dump, but dumps with all values expanded.
Download (0.40MB)
Added: 2007-06-08 License: Perl Artistic License Price:
870 downloads
Config::Properties 0.65
Config::Properties is a Perl module to read and write property files. more>>
Config::Properties is a Perl module to read and write property files.
SYNOPSIS
use Config::Properties;
# reading...
open PROPS, "< my_config.props"
or die "unable to open configuration file";
my $properties = new Config::Properties();
$properties->load(*PROPS);
$value = $properties->getProperty( $key );
# saving...
open PROPS, "> my_config.props"
or die "unable to open configuration file for writing";
$properties->setProperty( $key, $value );
$properties->format( %s => %s );
$properties->store(*PROPS, $header );
Config::Properties is a near implementation of the java.util.Properties API. It is designed to allow easy reading, writing and manipulation of Java-style property files.
The format of a Java-style property file is that of a key-value pair seperated by either whitespace, the colon (:) character, or the equals (=) character. Whitespace before the key and on either side of the seperator is ignored.
Lines that begin with either a hash (#) or a bang (!) are considered comment lines and ignored.
A backslash () at the end of a line signifies a continuation and the next line is counted as part of the current line (minus the backslash, any whitespace after the backslash, the line break, and any whitespace at the beginning of the next line).
The official references used to determine this format can be found in the Java API docs for java.util.Properties at http://java.sun.com/j2se/1.5.0/docs/api/java/util/Properties.html.
When a property file is saved it is in the format "key=value" for each line. This can be changed by setting the format attribute using either $object->format( $format_string ) or $object->setFormat( $format_string ) (they do the same thing). The format string is fed to printf and must contain exactly two %s format characters. The first will be replaced with the key of the property and the second with the value. The string can contain no other printf control characters, but can be anything else. A newline will be automatically added to the end of the string. You an get the current format string either by using $object->format() (with no arguments) or $object->getFormat().
If a recent version of module Text::Wrap is available, long lines are conveniently wrapped when saving.
<<lessSYNOPSIS
use Config::Properties;
# reading...
open PROPS, "< my_config.props"
or die "unable to open configuration file";
my $properties = new Config::Properties();
$properties->load(*PROPS);
$value = $properties->getProperty( $key );
# saving...
open PROPS, "> my_config.props"
or die "unable to open configuration file for writing";
$properties->setProperty( $key, $value );
$properties->format( %s => %s );
$properties->store(*PROPS, $header );
Config::Properties is a near implementation of the java.util.Properties API. It is designed to allow easy reading, writing and manipulation of Java-style property files.
The format of a Java-style property file is that of a key-value pair seperated by either whitespace, the colon (:) character, or the equals (=) character. Whitespace before the key and on either side of the seperator is ignored.
Lines that begin with either a hash (#) or a bang (!) are considered comment lines and ignored.
A backslash () at the end of a line signifies a continuation and the next line is counted as part of the current line (minus the backslash, any whitespace after the backslash, the line break, and any whitespace at the beginning of the next line).
The official references used to determine this format can be found in the Java API docs for java.util.Properties at http://java.sun.com/j2se/1.5.0/docs/api/java/util/Properties.html.
When a property file is saved it is in the format "key=value" for each line. This can be changed by setting the format attribute using either $object->format( $format_string ) or $object->setFormat( $format_string ) (they do the same thing). The format string is fed to printf and must contain exactly two %s format characters. The first will be replaced with the key of the property and the second with the value. The string can contain no other printf control characters, but can be anything else. A newline will be automatically added to the end of the string. You an get the current format string either by using $object->format() (with no arguments) or $object->getFormat().
If a recent version of module Text::Wrap is available, long lines are conveniently wrapped when saving.
Download (0.011MB)
Added: 2007-04-12 License: Perl Artistic License Price:
928 downloads
Scalar::Properties 0.12
Scalar::Properties is a Perl module package that contains run-time properties on scalar variables. more>>
Scalar::Properties is a Perl module package that contains run-time properties on scalar variables.
SYNOPSIS
use Scalar::Properties;
my $val = 0->true;
if ($val && $val == 0) {
print "yup, its true alright...n";
}
my @text = (
hello world->greeting(1),
forget it,
hi there->greeting(1),
);
print grep { $_->is_greeting } @text;
my $l = hello world->length;
Scalar::Properties attempts to make Perl more object-oriented by taking an idea from Ruby: Everything you manipulate is an object, and the results of those manipulations are objects themselves.
hello world->length
(-1234)->abs
"oh my god, its full of properties"->index(g)
The first example asks a string to calculate its length. The second example asks a number to calculate its absolute value. And the third example asks a string to find the index of the letter g.
Using this module you can have run-time properties on initialized scalar variables and literal values. The word properties is used in the Perl 6 sense: out-of-band data, little sticky notes that are attached to the value. While attributes (as in Perl 5s attribute pragma, and see the Attribute::* family of modules) are handled at compile-time, properties are handled at run-time.
Internally properties are implemented by making their values into objects with overloaded operators. The actual properties are then simply hash entries.
Most properties are simply notes you attach to the value, but some may have deeper meaning. For example, the true and false properties plays a role in boolean context, as the first example of the Synopsis shows.
Properties can also be propagated between values. For details, see the EXPORTS section below. Here is an example why this might be desirable:
pass_on(approximate);
my $pi = 3->approximate(1);
my $circ = 2 * $rad * $pi;
# now $circ->approximate indicates that this value was derived
# from approximate values
Please dont use properties whose name start with an underscore; these are reserved for internal use.
You can set and query properties like this:
$var->myprop(1)
sets the property to a true value.
$var->myprop(0)
sets the property to a false value. Note that this doesnt delete the property (to do so, use the del_props method described below).
$var->is_myprop, $var->has_myprop
returns a true value if the property is set (i.e., defined and has a true value). The two alternate interfaces are provided to make querying attributes sound more natural. For example:
$foo->is_approximate;
$bar->has_history;
<<lessSYNOPSIS
use Scalar::Properties;
my $val = 0->true;
if ($val && $val == 0) {
print "yup, its true alright...n";
}
my @text = (
hello world->greeting(1),
forget it,
hi there->greeting(1),
);
print grep { $_->is_greeting } @text;
my $l = hello world->length;
Scalar::Properties attempts to make Perl more object-oriented by taking an idea from Ruby: Everything you manipulate is an object, and the results of those manipulations are objects themselves.
hello world->length
(-1234)->abs
"oh my god, its full of properties"->index(g)
The first example asks a string to calculate its length. The second example asks a number to calculate its absolute value. And the third example asks a string to find the index of the letter g.
Using this module you can have run-time properties on initialized scalar variables and literal values. The word properties is used in the Perl 6 sense: out-of-band data, little sticky notes that are attached to the value. While attributes (as in Perl 5s attribute pragma, and see the Attribute::* family of modules) are handled at compile-time, properties are handled at run-time.
Internally properties are implemented by making their values into objects with overloaded operators. The actual properties are then simply hash entries.
Most properties are simply notes you attach to the value, but some may have deeper meaning. For example, the true and false properties plays a role in boolean context, as the first example of the Synopsis shows.
Properties can also be propagated between values. For details, see the EXPORTS section below. Here is an example why this might be desirable:
pass_on(approximate);
my $pi = 3->approximate(1);
my $circ = 2 * $rad * $pi;
# now $circ->approximate indicates that this value was derived
# from approximate values
Please dont use properties whose name start with an underscore; these are reserved for internal use.
You can set and query properties like this:
$var->myprop(1)
sets the property to a true value.
$var->myprop(0)
sets the property to a false value. Note that this doesnt delete the property (to do so, use the del_props method described below).
$var->is_myprop, $var->has_myprop
returns a true value if the property is set (i.e., defined and has a true value). The two alternate interfaces are provided to make querying attributes sound more natural. For example:
$foo->is_approximate;
$bar->has_history;
Download (0.010MB)
Added: 2007-05-21 License: Perl Artistic License Price:
886 downloads
Gnome Splash Properties 0.3.0
Gnome Splash Properties lets you easily setup your splash on GNOME desktop. more>>
Gnome Splash Properties lets you easily setup your splash on GNOME desktop.
Written in Ruby and Ruby-Gnome2 "Gnome Splash Properties" aim to by easy too use. In near future Drag & Drop support is planed.
Gentoo ebuild is available on the web site. Installation: run "ruby setup.rb" in the main folder.
<<lessWritten in Ruby and Ruby-Gnome2 "Gnome Splash Properties" aim to by easy too use. In near future Drag & Drop support is planed.
Gentoo ebuild is available on the web site. Installation: run "ruby setup.rb" in the main folder.
Download (MB)
Added: 2005-11-17 License: GPL (GNU General Public License) Price:
1439 downloads
Glib Binding Properties 0.9.1
Glib Binding Properties is a system that allows developers to bind properties of GLib and GTK+ objects. more>>
Glib Binding Properties library adds an implementation of binding properties to GLib / GTK+ library (it also includes Ada 95 for GtkAda GTK bindings, GtkAda was made by ACT corp.)
Binding properties is automatic synchronizing values of several properties to keep their values correspondingly to each other, so that when a property changes properties bound with it automatically change accordingly. Also bindings with value transformation functions are supported.
Binding properties much reduces development time of desktop applications and increases reliability as frees you from time consuming and error-prone writing callback handlers of property changes. (Probably wrong property change handlers is the most often cause of errors in GUI applications!)
Current version 0.9.1 is an alpha version. Please test it.
<<lessBinding properties is automatic synchronizing values of several properties to keep their values correspondingly to each other, so that when a property changes properties bound with it automatically change accordingly. Also bindings with value transformation functions are supported.
Binding properties much reduces development time of desktop applications and increases reliability as frees you from time consuming and error-prone writing callback handlers of property changes. (Probably wrong property change handlers is the most often cause of errors in GUI applications!)
Current version 0.9.1 is an alpha version. Please test it.
Download (0.32MB)
Added: 2006-03-24 License: LGPL (GNU Lesser General Public License) Price:
1310 downloads
WWW::Webrobot::Properties 0.81
WWW::Webrobot::Properties is a Perl module that implements a config format like java.util.Properties. more>>
WWW::Webrobot::Properties is a Perl module that implements a config format like java.util.Properties.
SYNOPSIS
my $config = WWW::Webrobot::Properties->new(
listmode => [qw(names auth_basic output http_header proxy no_proxy)],
key_value => [qw(names http_header proxy)],
multi_value => [qw(auth_basic)],
structurize => [qw(load mail)],
);
my $cfg = $config->load_file($cfg_name, $cmd_param);
This class implements a config format like java.util.Properties, see http://java.sun.com/j2se/1.3/docs/api/java/util/Properties.html for more docs.
Note: Some features are not implemented but there are some extensions for lists.
EXTENDED FORMAT
Listmode properties may be written
listprop=value0
listprop=value1
listprop=value2
or
listprop.0=value0
listprop.1=value1
listprop.2=value2
These properties are made available as perl-arrays.
<<lessSYNOPSIS
my $config = WWW::Webrobot::Properties->new(
listmode => [qw(names auth_basic output http_header proxy no_proxy)],
key_value => [qw(names http_header proxy)],
multi_value => [qw(auth_basic)],
structurize => [qw(load mail)],
);
my $cfg = $config->load_file($cfg_name, $cmd_param);
This class implements a config format like java.util.Properties, see http://java.sun.com/j2se/1.3/docs/api/java/util/Properties.html for more docs.
Note: Some features are not implemented but there are some extensions for lists.
EXTENDED FORMAT
Listmode properties may be written
listprop=value0
listprop=value1
listprop=value2
or
listprop.0=value0
listprop.1=value1
listprop.2=value2
These properties are made available as perl-arrays.
Download (0.097MB)
Added: 2007-06-15 License: Perl Artistic License Price:
862 downloads
Symlink Properties Plugin 0.12
Symlink Properties Plugin is a plugin for Konqueror. more>>
This is a plugin for the Konqueror file manager, which adds an additional tab to the file properties dialogue allowing the destination of a symbolic link to be viewed and changed.
The plugin is released under the GNU General Public Licence, see the file LICENSE within the distribution archive for further information.
The plugin is installed in much the same way as any other KDE or GNU application; you must have the Qt toolkit and KDE 3.1.2 or later already installed, of course. See the INSTALL file for detailed installation instructions. Once the plugin is installed, see the documentation in the KDE Help Centre for more information.
Enhancements:
- Accelerator key "&Symbolic Link" for tab now clashes with "&Share" (KDE 3.3.2).
- Change accelerator to "S&ymbolic Link".
- Fix download URL in documentation.
<<lessThe plugin is released under the GNU General Public Licence, see the file LICENSE within the distribution archive for further information.
The plugin is installed in much the same way as any other KDE or GNU application; you must have the Qt toolkit and KDE 3.1.2 or later already installed, of course. See the INSTALL file for detailed installation instructions. Once the plugin is installed, see the documentation in the KDE Help Centre for more information.
Enhancements:
- Accelerator key "&Symbolic Link" for tab now clashes with "&Share" (KDE 3.3.2).
- Change accelerator to "S&ymbolic Link".
- Fix download URL in documentation.
Download (0.59MB)
Added: 2005-06-08 License: GPL (GNU General Public License) Price:
1600 downloads
X Window Properties Viewer 0.2
X Window Properties Viewer allows you to select a X window and view/edit its properties. more>>
X Window Properties Viewer project allows you to select a X window and view/edit its properties.
A tree viewer lets to see part or all of the windows tree on your X server.
After selecting a window you can view all of the resources at once or select individual ones for viewing/editing.
Only editing strings is currently supported.
<<lessA tree viewer lets to see part or all of the windows tree on your X server.
After selecting a window you can view all of the resources at once or select individual ones for viewing/editing.
Only editing strings is currently supported.
Download (0.050MB)
Added: 2006-09-30 License: Free To Use But Restricted Price:
1122 downloads
App::Serializer::Properties 0.965
App::Serializer::Properties is a Perl interface for serialization and deserialization. more>>
App::Serializer::Properties is a Perl interface for serialization and deserialization.
SYNOPSIS
use App;
$context = App->context();
$serializer = $context->service("Serializer"); # or ...
$serializer = $context->serializer();
$data = {
an => arbitrary,
collection => [ of, data, ],
of => {
arbitrary => depth,
},
};
$propdata = $serializer->serialize($data);
$data = $serializer->deserialize($propdata);
print $serializer->dump($data), "n";
<<lessSYNOPSIS
use App;
$context = App->context();
$serializer = $context->service("Serializer"); # or ...
$serializer = $context->serializer();
$data = {
an => arbitrary,
collection => [ of, data, ],
of => {
arbitrary => depth,
},
};
$propdata = $serializer->serialize($data);
$data = $serializer->deserialize($propdata);
print $serializer->dump($data), "n";
Download (0.12MB)
Added: 2007-06-21 License: Perl Artistic License Price:
856 downloads
Audio::TagLib::MPEG::Properties 1.42
Audio::TagLib::MPEG::Properties is an implementation of audio property reading for MP3. more>>
Audio::TagLib::MPEG::Properties is an implementation of audio property reading for MP3.
SYNOPSIS
use Audio::TagLib::MPEG::Properties;
my $f = Audio::TagLib::MPEG::File->new("sample file.mp3");
my $i = $f->audioProperties();
print $i->layer(), "n"; # got 3
This reads the data from an MPEG Layer III stream found in the AudioProperties API.
new(PV $file, PV $style = "Average")
Create an instance of MPEG::Properties with the data read from the MPEG::File $file.
DESTROY()
Destroys this MPEG Properties instance.
IV length()
IV bitrate()
IV sampleRate()
IV channels()
see AudioProperties
PV version()
Returns the MPEG Version of the file.
see Audio::TagLib::MPEG::Header
IV layer()
Returns the layer version. This will be between the values 1-3.
BOOL protectionEnabled()
Returns true if the MPEG protection bit is enabled.
PV channelMode()
Returns the channel mode for this frame.
see Audio::TagLib::MPEG::Header
BOOL isCopyrighted()
Returns true if the copyrighted bit is set.
BOOL isOriginal()
Returns true if the "original" bit is set.
<<lessSYNOPSIS
use Audio::TagLib::MPEG::Properties;
my $f = Audio::TagLib::MPEG::File->new("sample file.mp3");
my $i = $f->audioProperties();
print $i->layer(), "n"; # got 3
This reads the data from an MPEG Layer III stream found in the AudioProperties API.
new(PV $file, PV $style = "Average")
Create an instance of MPEG::Properties with the data read from the MPEG::File $file.
DESTROY()
Destroys this MPEG Properties instance.
IV length()
IV bitrate()
IV sampleRate()
IV channels()
see AudioProperties
PV version()
Returns the MPEG Version of the file.
see Audio::TagLib::MPEG::Header
IV layer()
Returns the layer version. This will be between the values 1-3.
BOOL protectionEnabled()
Returns true if the MPEG protection bit is enabled.
PV channelMode()
Returns the channel mode for this frame.
see Audio::TagLib::MPEG::Header
BOOL isCopyrighted()
Returns true if the copyrighted bit is set.
BOOL isOriginal()
Returns true if the "original" bit is set.
Download (1.4MB)
Added: 2006-11-09 License: Perl Artistic License Price:
1082 downloads
Audio::File::AudioProperties 0.10
Audio::File::AudioProperties is a Perl module that can abstract an audio files audio properties. more>>
Audio::File::AudioProperties is a Perl module that can abstract an audio files audio properties.
Audio::File::AudioProperties is the base class for other file format independant audio property classes like Audio::File::Flac::AudioProperties or Audio::File::Ogg::AudioProperties. You should not use this class yourself exept youre writing an own file format dependant subclass.
METHODS
new
Constructor. Creates new Audio::File::AudioProperties object. You shoud not use this method yourself. Its called by the filetype-dependant subclasses of Audio::File::Type automatically.
init
Initializes the object. Its called by the constructor and empty by default. Its ought to be overwritten by subclasses.
length
Returns the length of the audio file in seconds.
bitrate
Returns the bitrate of the file.
sample_rate
Returns the sample rate of the audio file.
channels
Returns the number of channels the audio file has.
all
Get all audio properties.
<<lessAudio::File::AudioProperties is the base class for other file format independant audio property classes like Audio::File::Flac::AudioProperties or Audio::File::Ogg::AudioProperties. You should not use this class yourself exept youre writing an own file format dependant subclass.
METHODS
new
Constructor. Creates new Audio::File::AudioProperties object. You shoud not use this method yourself. Its called by the filetype-dependant subclasses of Audio::File::Type automatically.
init
Initializes the object. Its called by the constructor and empty by default. Its ought to be overwritten by subclasses.
length
Returns the length of the audio file in seconds.
bitrate
Returns the bitrate of the file.
sample_rate
Returns the sample rate of the audio file.
channels
Returns the number of channels the audio file has.
all
Get all audio properties.
Download (0.073MB)
Added: 2006-06-19 License: Perl Artistic License Price:
1222 downloads
Framework for Contact properties 0.1.2
Framework for Contact properties offers quick access to your contacts and also view their status. more>>
Framework for Contact properties offers quick access to your contacts and also view their status.
Short version:
Want quick access to your contacts, or see what their status is? Here you go: Have contact cards floating on the desktop, or list them on Kicker, so things like chatting or emailing to them is only one/two mouse clicks away. Or drop them a file/url!
Long version:
A framework for contacts and services upon them. It consists of two libs, libcontactpropertiescore and libcontactpropertiesgui.
The tarball has additionally some useful examples for services and two applications, a contact cards server and a kicker applet, based on the Contacts menu for kicker.
No translations available.
Please see http://frinring.wordpress.com/2006/07/05/framework-for-contacts-and-services-slowly-getting-shapes/
Then try it and create some own services, to be able to give feedback on the framework(!)
To have your property and services loaded, add a file named "contactpropertiesrc" to "$HOME/.kde/share/config" with this content:
[General]
Properties=birthday,imaddress,emailaddress,homepageurl,phonenumber,address,note,shellname,yourtype
[Property:yourtype]
ActionServices=youraction,youraction2
DefaultActionServices=youraction,youraction2
DataActionServices=yourdataaction,yourdataaction2
DefaultDataActionServices=yourdataaction2,yourdataaction2
StatusServices=yourstatus, yourstatus2
with "your*" adopted to your property and the optional services...
Enhancements:
- applet: sorting of contact lists can be configured
<<lessShort version:
Want quick access to your contacts, or see what their status is? Here you go: Have contact cards floating on the desktop, or list them on Kicker, so things like chatting or emailing to them is only one/two mouse clicks away. Or drop them a file/url!
Long version:
A framework for contacts and services upon them. It consists of two libs, libcontactpropertiescore and libcontactpropertiesgui.
The tarball has additionally some useful examples for services and two applications, a contact cards server and a kicker applet, based on the Contacts menu for kicker.
No translations available.
Please see http://frinring.wordpress.com/2006/07/05/framework-for-contacts-and-services-slowly-getting-shapes/
Then try it and create some own services, to be able to give feedback on the framework(!)
To have your property and services loaded, add a file named "contactpropertiesrc" to "$HOME/.kde/share/config" with this content:
[General]
Properties=birthday,imaddress,emailaddress,homepageurl,phonenumber,address,note,shellname,yourtype
[Property:yourtype]
ActionServices=youraction,youraction2
DefaultActionServices=youraction,youraction2
DataActionServices=yourdataaction,yourdataaction2
DefaultDataActionServices=yourdataaction2,yourdataaction2
StatusServices=yourstatus, yourstatus2
with "your*" adopted to your property and the optional services...
Enhancements:
- applet: sorting of contact lists can be configured
Download (0.55MB)
Added: 2006-12-23 License: GPL (GNU General Public License) Price:
1035 downloads
Audio::TagLib::AudioProperties 1.42
Audio::TagLib::AudioProperties is a simple, abstract interface to common audio properties. more>>
Audio::TagLib::AudioProperties is a simple, abstract interface to common audio properties.
DESCRIPTION
The values here are common to most audio formats. For more specific, codec dependant values, please see see the subclasses APIs. This is meant to compliment the Audio::TagLib::File and Audio::TagLib::Tag APIs in providing a simple interface that is sufficient for most applications.
%_ReadStyle
Reading audio properties from a file can sometimes be very time consuming and for the most accurate results can often involve reading the entire file. Because in many situations speed is critical or the accuracy of the values is not particularly important this allows the level of desired accuracy to be set.
keys %Audio::TagLib::AudioProperties::_ReadStyle lists all available values used in Perl code.
see FLAC::Properties MPC::Properties MPEG::Properties Vorbis::Properties
DESTROY()
Destroys this AudioProperties instance.
length() [pure virtual]
Returns the lenght of the file in seconds.
bitrate() [pure virtual]
Returns the most appropriate bit rate for the file in kb/s. For constant bitrate formats this is simply the bitrate of the file. For variable bitrate formats this is either the average or nominal bitrate.
sampleRate() [pure virtual]
Returns the sample rate in Hz.
channels() [pure virtual]
Returns the number of audio channels.
<<lessDESCRIPTION
The values here are common to most audio formats. For more specific, codec dependant values, please see see the subclasses APIs. This is meant to compliment the Audio::TagLib::File and Audio::TagLib::Tag APIs in providing a simple interface that is sufficient for most applications.
%_ReadStyle
Reading audio properties from a file can sometimes be very time consuming and for the most accurate results can often involve reading the entire file. Because in many situations speed is critical or the accuracy of the values is not particularly important this allows the level of desired accuracy to be set.
keys %Audio::TagLib::AudioProperties::_ReadStyle lists all available values used in Perl code.
see FLAC::Properties MPC::Properties MPEG::Properties Vorbis::Properties
DESTROY()
Destroys this AudioProperties instance.
length() [pure virtual]
Returns the lenght of the file in seconds.
bitrate() [pure virtual]
Returns the most appropriate bit rate for the file in kb/s. For constant bitrate formats this is simply the bitrate of the file. For variable bitrate formats this is either the average or nominal bitrate.
sampleRate() [pure virtual]
Returns the sample rate in Hz.
channels() [pure virtual]
Returns the number of audio channels.
Download (1.4MB)
Added: 2006-06-21 License: Perl Artistic License Price:
1221 downloads
wxPropertyGrid 1.2.8
wxPropertyGrid is a property sheet control for wxWidgets. more>>
wxPropertyGrid is a property sheet control for wxWidgets.
wxPropertyGrid is a specialized two-column grid for editing properties such as strings, numbers, flagsets, string arrays, and colours.
<<lesswxPropertyGrid is a specialized two-column grid for editing properties such as strings, numbers, flagsets, string arrays, and colours.
Download (0.88MB)
Added: 2007-07-09 License: Open Software License Price:
838 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 properties 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
