robin
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 57
RRDTool 1.2.21 / 1.3 Beta 1
RRD is a system to store and display time-series data. more>>
RRD is the Acronym for Round Robin Database. RRD is a system to store and display time-series data (i.e. network bandwidth, machine-room temperature, server load average).
RRDTool project stores the data in a very compact way that will not expand over time, and it presents useful graphs by processing the data to enforce a certain data density.
It can be used either via simple wrapper scripts (from shell or Perl) or via frontends that poll network devices and put a friendly user interface on it.
Whats New in 1.2.21 Stable Release:
- More graph config options.
- An ABS operator for CDEF.
- Several segfaults have been fixed.
- More robust Ruby and Python extension builds.
- Netware and Win32 Makefile updates.
Whats New in 1.3 Beta 1 Development Release:
- Performance was improved with memory mapped IO, fadvise, and madvise.
- Graphing was enhanced by using cairo and pango.
<<lessRRDTool project stores the data in a very compact way that will not expand over time, and it presents useful graphs by processing the data to enforce a certain data density.
It can be used either via simple wrapper scripts (from shell or Perl) or via frontends that poll network devices and put a friendly user interface on it.
Whats New in 1.2.21 Stable Release:
- More graph config options.
- An ABS operator for CDEF.
- Several segfaults have been fixed.
- More robust Ruby and Python extension builds.
- Netware and Win32 Makefile updates.
Whats New in 1.3 Beta 1 Development Release:
- Performance was improved with memory mapped IO, fadvise, and madvise.
- Graphing was enhanced by using cairo and pango.
Download (1.0MB)
Added: 2007-08-08 License: GPL (GNU General Public License) Price:
819 downloads
GNU/Fiwix 0.3.3
GNU/Fiwix is an operating system kernel based on the architecture of UNIX and Linux. more>>
GNU/Fiwix is an operating system kernel based on the architecture of UNIX and Linux.
GNU/Fiwix operating system is designed exclusively for educational purposes, so the kernel code is kept as simple as possible for the benefit of students.
It runs on the 32-bit x86 hardware platform, and is compatible with existing GNU applications.
Main features:
- GRUB Multiboot Specification compliant.
- Fully 32bit protected mode non-preemptive kernel.
- For Intel 80386 processors or higher.
- Real multitask (kernel tasks at level 0).
- Protected task environment (independent memory address per process).
- Interrupt and exception handling.
- Semaphores.
- Signals.
- Virtual memory management up to 4GB.
- Demand paging with Copy-On-Write feature.
- Linux system calls compatibility.
- Linux ELF-386 executable format support (statically and dynamically linked).
- Round-Robin based scheduler algorithm (without priorities).
- VFS with Linux EXT2 filesystem support (read only).
- Keyboard driver with spanish/catalan and english keymaps (hard coded).
- Floppy disk device driver and DMA management.
- IDE/ATA hard disk device driver (read only).
<<lessGNU/Fiwix operating system is designed exclusively for educational purposes, so the kernel code is kept as simple as possible for the benefit of students.
It runs on the 32-bit x86 hardware platform, and is compatible with existing GNU applications.
Main features:
- GRUB Multiboot Specification compliant.
- Fully 32bit protected mode non-preemptive kernel.
- For Intel 80386 processors or higher.
- Real multitask (kernel tasks at level 0).
- Protected task environment (independent memory address per process).
- Interrupt and exception handling.
- Semaphores.
- Signals.
- Virtual memory management up to 4GB.
- Demand paging with Copy-On-Write feature.
- Linux system calls compatibility.
- Linux ELF-386 executable format support (statically and dynamically linked).
- Round-Robin based scheduler algorithm (without priorities).
- VFS with Linux EXT2 filesystem support (read only).
- Keyboard driver with spanish/catalan and english keymaps (hard coded).
- Floppy disk device driver and DMA management.
- IDE/ATA hard disk device driver (read only).
Download (0.46MB)
Added: 2007-08-01 License: Other/Proprietary License Price:
819 downloads
flac2mp3 0.2.9 / 0.3.0 RC1
flac2mp3 project is a tool to convert audio files from flac to mp3 format. more>>
flac2mp3 project is a tool to convert audio files from flac to mp3 format.
<<less Download (0.088MB)
Added: 2007-07-22 License: GPL (GNU General Public License) Price:
605 downloads
NuttX 0.2.8
NuttX project is a real-time embedded operating system (RTOS). more>>
NuttX project is a real-time embedded operating system (RTOS). It has a small footprint that is usable in micro-controller environments. It is fully scalable from tiny (8-bit) to moderate embedded (32-bit) systems. It also aims to be fully compliant to standards, to be fully real time, and to be totally open.
Main features:
Small Footprint
- Usable in all but the tightest micro-controller environments, The focus is on the tiny-to-small, deeply embedded environment.
Rich Feature OS Set
- The goal is to provide most standard POSIX OS interfaces to support a rich multi-threaded development environment.
- NON-GOALS: (1) It is not a goal to provide OS subsystems such as network or USB (but these could obviously be added). (2) There is no MMU-based support for processes. At present, NuttX assumes a flat address space.
Highly Scalable
- Fully scalable from tiny (8-bit) to moderate embedded (32-bit). Scalability with rich feature set is accomplished with: Many tiny source files, link from static libraries, highly configurable, use of weak symbols when available.
Standards Compliance
- NuttX strives to achieve a high degree of standards compliance. The primary governing standards are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOSs are adopted for functionality not available under these standards or for functionaly that is not appropriate for the deeply-embedded RTOS (such as fork()).
- Because of this standards conformance, software developed under other standard OSs (such as Linux) should port easily to NuttX.
Real-Time
- Fully pre-emptible, fixed priority and round-robin scheduling.
Totally Open
- Non-restrictive BSD license.
Enhancements:
- tools/Makefile.mkconfig: Under Cygwin, executable has a different name
- tools/mkdeps.sh & arch/arm/src/Makefile: Corrected a problem makeing dependencies
- tools/zipme.sh: Force directory name to be nuttx-xx.yy.zz
- fs/fs_opendir.c: Correct errors in semaphore usage that can cause deadlock.
- lib/lib_getopt.c: Added getopt() support
- examples/nsh/: NSH now supports cat, mount, umount, and mkdir. ls supports -l -s, and -R
- Added basic OS support to manage environment variables: environment storage, cloning on task creation, sharing on pthread creation, destruction on thread/task exit.
- Add environment variables APIs: environ, getenv, putenv, clearenv, setenv, unsetenv
- Correct an error in realloc() when the block is extended "down" in memory. In this case, the old memory contents need to be copied to the new location and an allocated bit was not being set.
- examples/ostest/: Added an environment variable test.
- examples/nsh/: Break into several files.
- lib/: Added strrchr, basename, dirname
- examples/nsh/: Add cp, rm, rmdir, set, unset commands. echo will now print environment variables.
<<lessMain features:
Small Footprint
- Usable in all but the tightest micro-controller environments, The focus is on the tiny-to-small, deeply embedded environment.
Rich Feature OS Set
- The goal is to provide most standard POSIX OS interfaces to support a rich multi-threaded development environment.
- NON-GOALS: (1) It is not a goal to provide OS subsystems such as network or USB (but these could obviously be added). (2) There is no MMU-based support for processes. At present, NuttX assumes a flat address space.
Highly Scalable
- Fully scalable from tiny (8-bit) to moderate embedded (32-bit). Scalability with rich feature set is accomplished with: Many tiny source files, link from static libraries, highly configurable, use of weak symbols when available.
Standards Compliance
- NuttX strives to achieve a high degree of standards compliance. The primary governing standards are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOSs are adopted for functionality not available under these standards or for functionaly that is not appropriate for the deeply-embedded RTOS (such as fork()).
- Because of this standards conformance, software developed under other standard OSs (such as Linux) should port easily to NuttX.
Real-Time
- Fully pre-emptible, fixed priority and round-robin scheduling.
Totally Open
- Non-restrictive BSD license.
Enhancements:
- tools/Makefile.mkconfig: Under Cygwin, executable has a different name
- tools/mkdeps.sh & arch/arm/src/Makefile: Corrected a problem makeing dependencies
- tools/zipme.sh: Force directory name to be nuttx-xx.yy.zz
- fs/fs_opendir.c: Correct errors in semaphore usage that can cause deadlock.
- lib/lib_getopt.c: Added getopt() support
- examples/nsh/: NSH now supports cat, mount, umount, and mkdir. ls supports -l -s, and -R
- Added basic OS support to manage environment variables: environment storage, cloning on task creation, sharing on pthread creation, destruction on thread/task exit.
- Add environment variables APIs: environ, getenv, putenv, clearenv, setenv, unsetenv
- Correct an error in realloc() when the block is extended "down" in memory. In this case, the old memory contents need to be copied to the new location and an allocated bit was not being set.
- examples/ostest/: Added an environment variable test.
- examples/nsh/: Break into several files.
- lib/: Added strrchr, basename, dirname
- examples/nsh/: Add cp, rm, rmdir, set, unset commands. echo will now print environment variables.
Download (0.45MB)
Added: 2007-07-02 License: BSD License Price:
850 downloads
XML::SAX::Base 1.02
XML::SAX::Base is a base class SAX Drivers and Filters. more>>
XML::SAX::Base is a base Perl class with SAX Drivers and Filters.
SYNOPSIS
package MyFilter;
use XML::SAX::Base;
@ISA = (XML::SAX::Base);
This module has a very simple task - to be a base class for PerlSAX drivers and filters. Its default behaviour is to pass the input directly to the output unchanged. It can be useful to use this module as a base class so you dont have to, for example, implement the characters() callback.
The main advantages that it provides are easy dispatching of events the right way (ie it takes care for you of checking that the handler has implemented that method, or has defined an AUTOLOAD), and the guarantee that filters will pass along events that they arent implementing to handlers downstream that might nevertheless be interested in them.
WRITING SAX DRIVERS AND FILTERS
Writing SAX Filters is tremendously easy: all you need to do is inherit from this module, and define the events you want to handle. A more detailed explanation can be found at http://www.xml.com/pub/a/2001/10/10/sax-filters.html.
Writing Drivers is equally simple. The one thing you need to pay attention to is NOT to call events yourself (this applies to Filters as well). For instance:
package MyFilter;
use base qw(XML::SAX::Base);
sub start_element {
my $self = shift;
my $data = shift;
# do something
$self->{Handler}->start_element($data); # BAD
}
The above example works well as precisely that: an example. But it has several faults: 1) it doesnt test to see whether the handler defines start_element. Perhaps it doesnt want to see that event, in which case you shouldnt throw it (otherwise itll die). 2) it doesnt check ContentHandler and then Handler (ie it doesnt look to see that the user hasnt requested events on a specific handler, and if not on the default one), 3) if it did check all that, not only would the code be cumbersome (see this modules source to get an idea) but it would also probably have to check for a DocumentHandler (in case this were SAX1) and for AUTOLOADs potentially defined in all these packages. As you can tell, that would be fairly painful. Instead of going through that, simply remember to use code similar to the following instead:
package MyFilter;
use base qw(XML::SAX::Base);
sub start_element {
my $self = shift;
my $data = shift;
# do something to filter
$self->SUPER::start_element($data); # GOOD (and easy) !
}
This way, once youve done your job you hand the ball back to XML::SAX::Base and it takes care of all those problems for you!
Note that the above example doesnt apply to filters only, drivers will benefit from the exact same feature.
<<lessSYNOPSIS
package MyFilter;
use XML::SAX::Base;
@ISA = (XML::SAX::Base);
This module has a very simple task - to be a base class for PerlSAX drivers and filters. Its default behaviour is to pass the input directly to the output unchanged. It can be useful to use this module as a base class so you dont have to, for example, implement the characters() callback.
The main advantages that it provides are easy dispatching of events the right way (ie it takes care for you of checking that the handler has implemented that method, or has defined an AUTOLOAD), and the guarantee that filters will pass along events that they arent implementing to handlers downstream that might nevertheless be interested in them.
WRITING SAX DRIVERS AND FILTERS
Writing SAX Filters is tremendously easy: all you need to do is inherit from this module, and define the events you want to handle. A more detailed explanation can be found at http://www.xml.com/pub/a/2001/10/10/sax-filters.html.
Writing Drivers is equally simple. The one thing you need to pay attention to is NOT to call events yourself (this applies to Filters as well). For instance:
package MyFilter;
use base qw(XML::SAX::Base);
sub start_element {
my $self = shift;
my $data = shift;
# do something
$self->{Handler}->start_element($data); # BAD
}
The above example works well as precisely that: an example. But it has several faults: 1) it doesnt test to see whether the handler defines start_element. Perhaps it doesnt want to see that event, in which case you shouldnt throw it (otherwise itll die). 2) it doesnt check ContentHandler and then Handler (ie it doesnt look to see that the user hasnt requested events on a specific handler, and if not on the default one), 3) if it did check all that, not only would the code be cumbersome (see this modules source to get an idea) but it would also probably have to check for a DocumentHandler (in case this were SAX1) and for AUTOLOADs potentially defined in all these packages. As you can tell, that would be fairly painful. Instead of going through that, simply remember to use code similar to the following instead:
package MyFilter;
use base qw(XML::SAX::Base);
sub start_element {
my $self = shift;
my $data = shift;
# do something to filter
$self->SUPER::start_element($data); # GOOD (and easy) !
}
This way, once youve done your job you hand the ball back to XML::SAX::Base and it takes care of all those problems for you!
Note that the above example doesnt apply to filters only, drivers will benefit from the exact same feature.
Download (0.020MB)
Added: 2007-06-21 License: Perl Artistic License Price:
855 downloads
CSS::SAC::ConditionFactory 0.06
CSS::SAC::ConditionFactory Perl module contains the default ConditionFactory. more>>
CSS::SAC::ConditionFactory Perl module contains the default ConditionFactory.
SYNOPSIS
my $cf = CSS::SAC::ConditionFactory->new;
my $cond1 = $cf->create_foo_condition;
my $cond2 = $cf->create_bar_condition;
This is the default ConditionFactory for CSS::SAC. It creates conditions of all types defined in SAC. You may wish to subclass or replace the default ConditionFactory in order to get your own condition objects.
I plan on adding more flexibility to this factory so that one could tell it the classes to use for various conditions, that would avoid enforcing subclassing/recoding for people that only want to replace a family of factory methods.
I know that some of the method names are quite lengthy, but given the great number of possible conditions it helps to have descriptive names.
METHODS
These define the interface that must be adhered to by ConditionFactories. The Java names (given in parens) work too, though the Perl ones are recommended.
CSS::SAC::ConditionFactory->new or $cf->new
Creates a new condition factory object.
$cf->create_and_condition($first,$second) (createAndCondition)
creates a combinator condition of type and
$cf->create_attribute_condition($lname,$ns,$specified,$value) (createAttributeCondition)
creates an attr condition
$cf->create_begin_hyphen_attribute_condition($lname,$ns,$specified,$value) (createBeginHyphenAttributeCondition)
creates a attr condition of type bh
$cf->create_class_condition($ns,$value) (createClassCondition)
creates a attr condition of type class
$cf->create_content_condition($data) (createContentCondition)
creates a content condition
$cf->create_id_condition($value) (createIdCondition)
creates a attr condition of type id
$cf->create_lang_condition($lang) (createLangCondition)
creates a lang condition
$cf->create_negative_condition($cond) (createNegativeCondition)
creates a negative condition
$cf->create_one_of_attribute_condition($lname,$ns,$specified,$value) (createOneOfAttributeCondition)
creates a attr condition of type id
$cf->create_only_child_condition() (createOnlyChildCondition)
creates a only-child condition
$cf->create_only_type_condition() (createOnlyTypeCondition)
creates a only-type condition
$cf->create_or_condition($first,$second) (createOrCondition)
creates a combinator condition of type or
$cf->create_positional_condition($position,$type_node,$same_type) (createPositionalCondition)
creates a positional condition
$cf->create_pseudo_class_condition($ns,$value) (createPseudoClassCondition)
creates a attr condition of type pseudo class
<<lessSYNOPSIS
my $cf = CSS::SAC::ConditionFactory->new;
my $cond1 = $cf->create_foo_condition;
my $cond2 = $cf->create_bar_condition;
This is the default ConditionFactory for CSS::SAC. It creates conditions of all types defined in SAC. You may wish to subclass or replace the default ConditionFactory in order to get your own condition objects.
I plan on adding more flexibility to this factory so that one could tell it the classes to use for various conditions, that would avoid enforcing subclassing/recoding for people that only want to replace a family of factory methods.
I know that some of the method names are quite lengthy, but given the great number of possible conditions it helps to have descriptive names.
METHODS
These define the interface that must be adhered to by ConditionFactories. The Java names (given in parens) work too, though the Perl ones are recommended.
CSS::SAC::ConditionFactory->new or $cf->new
Creates a new condition factory object.
$cf->create_and_condition($first,$second) (createAndCondition)
creates a combinator condition of type and
$cf->create_attribute_condition($lname,$ns,$specified,$value) (createAttributeCondition)
creates an attr condition
$cf->create_begin_hyphen_attribute_condition($lname,$ns,$specified,$value) (createBeginHyphenAttributeCondition)
creates a attr condition of type bh
$cf->create_class_condition($ns,$value) (createClassCondition)
creates a attr condition of type class
$cf->create_content_condition($data) (createContentCondition)
creates a content condition
$cf->create_id_condition($value) (createIdCondition)
creates a attr condition of type id
$cf->create_lang_condition($lang) (createLangCondition)
creates a lang condition
$cf->create_negative_condition($cond) (createNegativeCondition)
creates a negative condition
$cf->create_one_of_attribute_condition($lname,$ns,$specified,$value) (createOneOfAttributeCondition)
creates a attr condition of type id
$cf->create_only_child_condition() (createOnlyChildCondition)
creates a only-child condition
$cf->create_only_type_condition() (createOnlyTypeCondition)
creates a only-type condition
$cf->create_or_condition($first,$second) (createOrCondition)
creates a combinator condition of type or
$cf->create_positional_condition($position,$type_node,$same_type) (createPositionalCondition)
creates a positional condition
$cf->create_pseudo_class_condition($ns,$value) (createPseudoClassCondition)
creates a attr condition of type pseudo class
Download (0.037MB)
Added: 2007-06-20 License: Perl Artistic License Price:
856 downloads
CSS::SAC::LexicalUnit 0.06
CSS::SAC::LexicalUnit is a Perl module that contains SAC units. more>>
CSS::SAC::LexicalUnit is a Perl module that contains SAC units.
SYNOPSIS
use CSS::SAC::LexicalUnit qw(:constants);
foo if $lu->is_type(LU_TYPE_CONSTANT);
In the SAC spec, LexicalUnit is a linked list, that is, you only ever hold one LexicalUnit, and you ask for the next of for the previous one when you want to move on.
Such a model seems awkward, though Im sure it makes sense somehow in Java, likely for a Java-specific reason.
In the Perl implementation, I have changed this. A LexicalUnit is an object that stands on its own and has no next/previous objects. Instead, the $handler->property callback gets called with a LexicalUnitList, which is in fact just an array ref of LexicalUnits.
We also dont differentiate between IntegerValue, FloatValue, and StringValue, its always Value in Perl. This also applies to Parameters and SubValues. Both are called as Value and return an array ref of LexicalUnits.
I added the is_type() method, see CSS::SAC::Condition for advantages of that approach.
CONSTANTS
- ATTR
- CENTIMETER
- COUNTER_FUNCTION
- COUNTERS_FUNCTION
- DEGREE
- DIMENSION
- EM
- EX
- FUNCTION
- GRADIAN
- HERTZ
- IDENT
- INCH
- INHERIT
- INTEGER
- KILOHERTZ
- MILLIMETER
- MILLISECOND
- OPERATOR_COMMA
- OPERATOR_EXP
- OPERATOR_GE
- OPERATOR_GT
- OPERATOR_LE
- OPERATOR_LT
- OPERATOR_MINUS
- OPERATOR_MOD
- OPERATOR_MULTIPLY
- OPERATOR_PLUS
- OPERATOR_SLASH
- OPERATOR_TILDE
- PERCENTAGE
- PICA
- PIXEL
- POINT
- RADIAN
- REAL
- RECT_FUNCTION
- RGBCOLOR
- SECOND
- STRING_VALUE
- SUB_EXPRESSION
- UNICODERANGE
- URI
METHODS
CSS::SAC::LexicalUnit->new($type,$text,$value) or $lu->new($type,$text,$value)
Creates a new unit. The $type must be one of the type constants, the text depends on the type of unit (unit text, func name, etc...), and the value is the content of the lu.
$lu->DimensionUnitText([$dut]) or getDimensionUnitText
get/set the text of the dimension unit (eg cm, px, etc...)
$lu->FunctionName([$fn]) or getFunctionName
get/set the name of the function (eg attr, uri, etc...)
$lu->Value([$value]) or getValue
get/set the value of the lu (which may be another lu, or a lu list)
$lu->LexicalUnitType([$type]) or getLexicalUnitType
get/set the type of the lu
$lu->is_type($lu_constant)
returns true is this lu is of type $lu_constant
<<lessSYNOPSIS
use CSS::SAC::LexicalUnit qw(:constants);
foo if $lu->is_type(LU_TYPE_CONSTANT);
In the SAC spec, LexicalUnit is a linked list, that is, you only ever hold one LexicalUnit, and you ask for the next of for the previous one when you want to move on.
Such a model seems awkward, though Im sure it makes sense somehow in Java, likely for a Java-specific reason.
In the Perl implementation, I have changed this. A LexicalUnit is an object that stands on its own and has no next/previous objects. Instead, the $handler->property callback gets called with a LexicalUnitList, which is in fact just an array ref of LexicalUnits.
We also dont differentiate between IntegerValue, FloatValue, and StringValue, its always Value in Perl. This also applies to Parameters and SubValues. Both are called as Value and return an array ref of LexicalUnits.
I added the is_type() method, see CSS::SAC::Condition for advantages of that approach.
CONSTANTS
- ATTR
- CENTIMETER
- COUNTER_FUNCTION
- COUNTERS_FUNCTION
- DEGREE
- DIMENSION
- EM
- EX
- FUNCTION
- GRADIAN
- HERTZ
- IDENT
- INCH
- INHERIT
- INTEGER
- KILOHERTZ
- MILLIMETER
- MILLISECOND
- OPERATOR_COMMA
- OPERATOR_EXP
- OPERATOR_GE
- OPERATOR_GT
- OPERATOR_LE
- OPERATOR_LT
- OPERATOR_MINUS
- OPERATOR_MOD
- OPERATOR_MULTIPLY
- OPERATOR_PLUS
- OPERATOR_SLASH
- OPERATOR_TILDE
- PERCENTAGE
- PICA
- PIXEL
- POINT
- RADIAN
- REAL
- RECT_FUNCTION
- RGBCOLOR
- SECOND
- STRING_VALUE
- SUB_EXPRESSION
- UNICODERANGE
- URI
METHODS
CSS::SAC::LexicalUnit->new($type,$text,$value) or $lu->new($type,$text,$value)
Creates a new unit. The $type must be one of the type constants, the text depends on the type of unit (unit text, func name, etc...), and the value is the content of the lu.
$lu->DimensionUnitText([$dut]) or getDimensionUnitText
get/set the text of the dimension unit (eg cm, px, etc...)
$lu->FunctionName([$fn]) or getFunctionName
get/set the name of the function (eg attr, uri, etc...)
$lu->Value([$value]) or getValue
get/set the value of the lu (which may be another lu, or a lu list)
$lu->LexicalUnitType([$type]) or getLexicalUnitType
get/set the type of the lu
$lu->is_type($lu_constant)
returns true is this lu is of type $lu_constant
Download (0.037MB)
Added: 2007-06-20 License: Perl Artistic License Price:
856 downloads
CinePaint 0.22.1
CinePaint is painting and retouching software primarily used for motion picture. more>>
CinePaint is painting and retouching software primarily used for motion picture frame-by-frame retouching and dust-busting. CinePaint has been used on many feature films, including THE LAST SAMURAI where it was used to add flying arrows.
CinePaint is different from other painting tools because it supports deep color depth image formats up to 32-bit per channel deep. For comparison, GIMP is limited to 8-bit, and Photoshop to 16-bit.
CinePaint is free open source software. The generosity and commitment of its developers, users and sponsors make CinePaint possible.
<<lessCinePaint is different from other painting tools because it supports deep color depth image formats up to 32-bit per channel deep. For comparison, GIMP is limited to 8-bit, and Photoshop to 16-bit.
CinePaint is free open source software. The generosity and commitment of its developers, users and sponsors make CinePaint possible.
Download (11.5MB)
Added: 2007-06-12 License: GPL (GNU General Public License) Price:
1823 downloads
phpQLAdmin 2.3.7
phpQLAdmin is designed primarily for administration of a QmailLDAP user database. more>>
phpQLAdmin is designed primarily for administration of a QmailLDAP user database, but also has (local/remote) EZMLM management, Bind9/LDAP (using the LDAP SDB driver), QmailLDAP/Controls and Apache Web server management abilities (using the mod_cfg_ldap module).
Version restrictions:
- Lots of Bind9 manager fixes (now supports AFSDB and round-robin pointers).
- Spelling errors in the use of some defines which led to broken user login and creation were fixed.
- The always-broken session handling was fixed.
- Some hardcoded attributes were replaced with corresponding (already existent) defines.
Enhancements:
- This is almost a complete rewrite of the automount manager.
- Small fixes were made in regard to deleting DNS host(s) when removing a Web server virtual host.
- The changing of a record type (from CNAME to A record for example) in the DNS manager was fixed.
- Copying or moving a virtual host from one physical Web server to another is supported.
- A long-standing problem was finally fixed regarding the initial folded branch tree in Opera.
<<lessVersion restrictions:
- Lots of Bind9 manager fixes (now supports AFSDB and round-robin pointers).
- Spelling errors in the use of some defines which led to broken user login and creation were fixed.
- The always-broken session handling was fixed.
- Some hardcoded attributes were replaced with corresponding (already existent) defines.
Enhancements:
- This is almost a complete rewrite of the automount manager.
- Small fixes were made in regard to deleting DNS host(s) when removing a Web server virtual host.
- The changing of a record type (from CNAME to A record for example) in the DNS manager was fixed.
- Copying or moving a virtual host from one physical Web server to another is supported.
- A long-standing problem was finally fixed regarding the initial folded branch tree in Opera.
Download (0.75MB)
Added: 2007-05-11 License: GPL (GNU General Public License) Price:
900 downloads
cuneAform 0.3.1
cuneAform is a Firefox extension designed to create a HTML Editor that anyone can use. more>>
cuneAform is a Firefox extension designed to create a HTML Editor that anyone can use.
<<less Download (0.085MB)
Added: 2007-05-07 License: MPL (Mozilla Public License) Price:
904 downloads
Want 0.14
Want is a Perl module created to implement the `want command. more>>
Want is a Perl module created to implement the `want command.
SYNOPSIS
use Want;
sub foo :lvalue {
if (want(qwLVALUE ASSIGN)) {
print "We have been assigned ", want(ASSIGN);
lnoreturn;
}
elsif (want(LIST)) {
rreturn (1, 2, 3);
}
elsif (want(BOOL)) {
rreturn 0;
}
elsif (want(qwSCALAR !REF)) {
rreturn 23;
}
elsif (want(HASH)) {
rreturn { foo => 17, bar => 23 };
}
return
}
This module generalises the mechanism of the wantarray function, allowing a function to determine in some detail how its return value is going to be immediately used.
...
EXAMPLES
use Carp croak;
use Want howmany;
sub numbers {
my $count = howmany();
croak("Cant make an infinite list") if !defined($count);
return (1..$count);
}
my ($one, $two, $three) = numbers();
use Want want;
sub pi () {
if (want(ARRAY)) {
return [3, 1, 4, 1, 5, 9];
}
elsif (want(LIST)) {
return (3, 1, 4, 1, 5, 9);
}
else {
return 3;
}
}
print pi->[2]; # prints 4
print ((pi)[3]); # prints 1
sub backstr :lvalue {
if (want(qwLVALUE ASSIGN)) {
my ($a) = want(ASSIGN);
$_[0] = reverse $a;
return undef;
}
elsif (want(RVALUE)) {
my $t = scalar reverse $_[0];
}
else {
carp("Not in ASSIGN context");
}
return
}
print "foo -> ", backstr("foo"), "n"; # foo -> oof
backstr(my $robin) = "nibor";
print "$robin is now $robinn"; # $robin is now robin
<<lessSYNOPSIS
use Want;
sub foo :lvalue {
if (want(qwLVALUE ASSIGN)) {
print "We have been assigned ", want(ASSIGN);
lnoreturn;
}
elsif (want(LIST)) {
rreturn (1, 2, 3);
}
elsif (want(BOOL)) {
rreturn 0;
}
elsif (want(qwSCALAR !REF)) {
rreturn 23;
}
elsif (want(HASH)) {
rreturn { foo => 17, bar => 23 };
}
return
}
This module generalises the mechanism of the wantarray function, allowing a function to determine in some detail how its return value is going to be immediately used.
...
EXAMPLES
use Carp croak;
use Want howmany;
sub numbers {
my $count = howmany();
croak("Cant make an infinite list") if !defined($count);
return (1..$count);
}
my ($one, $two, $three) = numbers();
use Want want;
sub pi () {
if (want(ARRAY)) {
return [3, 1, 4, 1, 5, 9];
}
elsif (want(LIST)) {
return (3, 1, 4, 1, 5, 9);
}
else {
return 3;
}
}
print pi->[2]; # prints 4
print ((pi)[3]); # prints 1
sub backstr :lvalue {
if (want(qwLVALUE ASSIGN)) {
my ($a) = want(ASSIGN);
$_[0] = reverse $a;
return undef;
}
elsif (want(RVALUE)) {
my $t = scalar reverse $_[0];
}
else {
carp("Not in ASSIGN context");
}
return
}
print "foo -> ", backstr("foo"), "n"; # foo -> oof
backstr(my $robin) = "nibor";
print "$robin is now $robinn"; # $robin is now robin
Download (0.017MB)
Added: 2007-05-05 License: Perl Artistic License Price:
902 downloads
File::Spec::Link 0.080
File::Spec::Link is a Perl extension for reading and resolving symbolic links. more>>
File::Spec::Link is a Perl extension for reading and resolving symbolic links.
SYNOPSIS
use File::Spec::Link;
my $file = File::Spec::Link->linked($link);
my $file = File::Spec::Link->resolve($link);
my $dirname = File::Spec::Link->chopfile($file);
my $newname = File::Spec::Link->relative_to_file($path, $link);
my $realname = File::Spec::Link->full_resolve($file);
my $realname = File::Spec::Link->resolve_path($file);
my $realname = File::Spec::Link->resolve_all($file);
File::Spec::Link is an extension to File::Spec, adding methods for resolving symbolic links; it was created to implement File::Copy::Link.
linked($link)
Returns the filename linked to by $link: by readlinking $link, and resolving that path relative to the directory of $link.
resolve($link)
Returns the non-link ultimately linked to by $link, by repeatedly calling linked. Returns undef if the link can not be resolved.
chopfile($file)
Returns the directory of $file, by splitting the path of $file and returning (the volumne and) directory parts.
relative_to_file($path, $file)
Returns the path of $path relative to the directory of file $file. If $path is absolute, just returns $path.
resolve_all($file)
Returns the filename of $file with all links in the path resolved, wihout using Cwd.
full_resolve($file)
Returns the filename of $file with all links in the path resolved.
This sub tries to use Cwd::abs_path via ->resolve_path.
resolve_path($file)
Returns the filename of $file with all links in the path resolved.
This sub uses Cwd::abs_path and is independent of the rest of File::Spec::Link.
<<lessSYNOPSIS
use File::Spec::Link;
my $file = File::Spec::Link->linked($link);
my $file = File::Spec::Link->resolve($link);
my $dirname = File::Spec::Link->chopfile($file);
my $newname = File::Spec::Link->relative_to_file($path, $link);
my $realname = File::Spec::Link->full_resolve($file);
my $realname = File::Spec::Link->resolve_path($file);
my $realname = File::Spec::Link->resolve_all($file);
File::Spec::Link is an extension to File::Spec, adding methods for resolving symbolic links; it was created to implement File::Copy::Link.
linked($link)
Returns the filename linked to by $link: by readlinking $link, and resolving that path relative to the directory of $link.
resolve($link)
Returns the non-link ultimately linked to by $link, by repeatedly calling linked. Returns undef if the link can not be resolved.
chopfile($file)
Returns the directory of $file, by splitting the path of $file and returning (the volumne and) directory parts.
relative_to_file($path, $file)
Returns the path of $path relative to the directory of file $file. If $path is absolute, just returns $path.
resolve_all($file)
Returns the filename of $file with all links in the path resolved, wihout using Cwd.
full_resolve($file)
Returns the filename of $file with all links in the path resolved.
This sub tries to use Cwd::abs_path via ->resolve_path.
resolve_path($file)
Returns the filename of $file with all links in the path resolved.
This sub uses Cwd::abs_path and is independent of the rest of File::Spec::Link.
Download (0.007MB)
Added: 2007-04-30 License: Perl Artistic License Price:
909 downloads
File::Copy::Link 0.080
File::Copy::Link is a Perl extension for replacing a link by a copy of the linked file. more>>
File::Copy::Link is a Perl extension for replacing a link by a copy of the linked file.
SYNOPSIS
use File::Copy::Link;
copylink file.lnk;
use File::Copy::Link qw(safecopylink);
safecopylink file.lnk;
copylink
reads the filename linked to by the argument and replaced the link with a copy of the file. It opens a filehandle to read from the link, deletes the link, and then copies the filehandle back to the link.
safecopylink
does the same as copylink but without the open-and-delete manouvre. Instead, it uses File::Spec::Link to find the target of the link and copies from there.
This module is mostly a wrapper round File::Spec::Link::linked and File::Copy::copy, the functionality is available in a command line script copylink.
<<lessSYNOPSIS
use File::Copy::Link;
copylink file.lnk;
use File::Copy::Link qw(safecopylink);
safecopylink file.lnk;
copylink
reads the filename linked to by the argument and replaced the link with a copy of the file. It opens a filehandle to read from the link, deletes the link, and then copies the filehandle back to the link.
safecopylink
does the same as copylink but without the open-and-delete manouvre. Instead, it uses File::Spec::Link to find the target of the link and copies from there.
This module is mostly a wrapper round File::Spec::Link::linked and File::Copy::copy, the functionality is available in a command line script copylink.
Download (0.007MB)
Added: 2007-04-26 License: Perl Artistic License Price:
915 downloads
CSS::SAC 0.06
CSS::SAC Perl module is a SAC CSS parser. more>>
CSS::SAC Perl module is a SAC CSS parser.
SYNOPSIS
use CSS::SAC qw();
use My::SACHandler ();
use My::SACErrors ();
my $doc_handler = My::SACHandler->new;
my $err_handler = My::SACErrors->new;
my $sac = CSS::SAC->new({
DocumentHandler => $doc_handler,
ErrorHandler => $err_handler,
});
# generate a stream of events
$sac->parse({ filename => foo.css });
SAC (Simple API for CSS) is an event-based API much like SAX for XML. If you are familiar with the latter, you should have little trouble getting used to SAC. More information on SAC can be found online at http://www.w3.org/TR/SAC.
CSS having more constructs than XML, core SAC is still more complex than core SAX. However, if you need to parse a CSS style sheet, SAC probably remains the easiest way to get it done.
Most of the spec is presently implemented. The following interfaces are not yet there: Locator, CSSException, CSSParseException, ParserFactory. They may or may not be implemented at a later date (the most likely candidates are the exception classes, for which I still have to find an appropriate model).
Some places differ slightly from what is in the spec. I have tried to keep those to a justified minimum and to flag them correctly.
<<lessSYNOPSIS
use CSS::SAC qw();
use My::SACHandler ();
use My::SACErrors ();
my $doc_handler = My::SACHandler->new;
my $err_handler = My::SACErrors->new;
my $sac = CSS::SAC->new({
DocumentHandler => $doc_handler,
ErrorHandler => $err_handler,
});
# generate a stream of events
$sac->parse({ filename => foo.css });
SAC (Simple API for CSS) is an event-based API much like SAX for XML. If you are familiar with the latter, you should have little trouble getting used to SAC. More information on SAC can be found online at http://www.w3.org/TR/SAC.
CSS having more constructs than XML, core SAC is still more complex than core SAX. However, if you need to parse a CSS style sheet, SAC probably remains the easiest way to get it done.
Most of the spec is presently implemented. The following interfaces are not yet there: Locator, CSSException, CSSParseException, ParserFactory. They may or may not be implemented at a later date (the most likely candidates are the exception classes, for which I still have to find an appropriate model).
Some places differ slightly from what is in the spec. I have tried to keep those to a justified minimum and to flag them correctly.
Download (0.037MB)
Added: 2007-04-02 License: Perl Artistic License Price:
935 downloads
mergelog 4.5
mergelog provides a fast tool to merge HTTP log files by date. more>>
mergelog provides a fast tool to merge HTTP log files by date.
mergelog is a small and fast C program, which merges HTTP log files by date in Common Log Format (Apache default log format) from Web servers, behind round-robin DNS.
It has been designed to easily process huge logs from highly stressed servers, and can manage gzipped files.
Enhancements:
- dont abort anymore on corrupted log lines
- set BUFFER_SIZE value to 32Ko
- fixed a major bug on a broken month initialization
- corrections on manpages
- fix in configure.in to abort if zlib is not present
- fixed a potential segmentation fault on malformed log lines
- autoconf compliant thanks to Igor Genibel
<<lessmergelog is a small and fast C program, which merges HTTP log files by date in Common Log Format (Apache default log format) from Web servers, behind round-robin DNS.
It has been designed to easily process huge logs from highly stressed servers, and can manage gzipped files.
Enhancements:
- dont abort anymore on corrupted log lines
- set BUFFER_SIZE value to 32Ko
- fixed a major bug on a broken month initialization
- corrections on manpages
- fix in configure.in to abort if zlib is not present
- fixed a potential segmentation fault on malformed log lines
- autoconf compliant thanks to Igor Genibel
Download (0.039MB)
Added: 2007-03-08 License: GPL (GNU General Public License) Price:
961 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 robin 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
