yasmin side effects
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 1293
![[Amos-Effect] 2007-06-10_01](http://linux.wareseeker.com/images_icon/detail_no-screenshot.gif){kind=icon}
[Amos-Effect] 2007-06-10_01
[Amos-Effect] parses and visualizes mobile phone connection data provided by O2 in the form of downloadable CSV files. more>>
[Amos-Effect] parses and visualizes mobile phone connection data provided by O2 in the form of downloadable CSV files. The project calculates mobile phone charges on a global and monthly basis.
[Amos-Effect] also determines average charges derived from the pre-calculated sums. [Amos-Effect] visualizes these stats by textual and by graphical means (using perls libgd module).
<<less[Amos-Effect] also determines average charges derived from the pre-calculated sums. [Amos-Effect] visualizes these stats by textual and by graphical means (using perls libgd module).
Download (0.006MB)
Added: 2007-06-13 License: GPL (GNU General Public License) Price:
868 downloads
DVD Slideshow 7.1
dvd-slideshow makes a DVD slideshow video with menus from a text file listin... more>> dvd-slideshow makes a DVD slideshow video with menus from a text file listing of pictures, effects, and audio tracks. You can add some nice effects like fades, crops, scrolls, or Ken Burns effects. It will hopefully become a command-line clone of imovie<<less
Download (4.0MB)
Added: 2009-04-23 License: Freeware Price:
190 downloads
Trip on the Funny Boat 1.4
Trip on the Funny Boat is a side scrolling shooter game starring a steamboat on the sea. more>>
Trip on the Funny Boat is a side scrolling shooter game starring a steamboat on the sea.
Trip on the Funny Boat is side scrolling arcade shooter game on a steamboat equipped with a cannon and the ability to jump. The player will need to take advantage of waves to defeat the enemies and dodge hazards.
This game was made for the second PyWeek competition during the week from 25.3.2006 to 2.4.2006.
<<lessTrip on the Funny Boat is side scrolling arcade shooter game on a steamboat equipped with a cannon and the ability to jump. The player will need to take advantage of waves to defeat the enemies and dodge hazards.
This game was made for the second PyWeek competition during the week from 25.3.2006 to 2.4.2006.
Download (3.8MB)
Added: 2007-03-14 License: MIT/X Consortium License Price:
959 downloads
Sidebar on Right 0.3
Sidebar on Right is an extension which moves the sidebar to the right side of the browser. more>>
Sidebar on Right is an extension which moves the sidebar to the right side of the browser.
<<less Download (0.003MB)
Added: 2007-04-18 License: MPL (Mozilla Public License) Price:
923 downloads
dbxbandmin 0.1
dbxbandmin collects traffic via ipchains/iptables/ipfwadm-rules and writes the data into an Interbase database. more>>
dbxbandmin collects traffic via ipchains/iptables/ipfwadm-rules and writes the data into an Interbase database. It uses Perls DBI-driver and can be extended with support for various database versions.
- You need a kernel with firewall-support
- you need ipfwadm or ipchains or iptables
- you need the InterBase-Client
- you need Perl 5.xx, pE. 5.5
- you need IBPerl0.8x
- you need DBI-Modul for Perl
- you need DBD::InterBase
(try "perl -Mcpan -e shell;" and type "install DBD::Interbase")
If you do not know what parts you needed, try install.sh for reports
First you must install a "Listening" firewall-policy. The tool tng-acc-bandminstart will do this. Follow the instructions of TNG-installation. The options-overview can you get by typing
"./tng-acc-bandmin --help", if you want a german-explanation, try "./tng-acc-bandmin --language=german --help". To remove firewall-policy use tng-acc-bandminstop.
If you have questions after reading all damn documentation, please dont hesitate to ask me for tng-acc-bandmin or marco for TNG in general.
Enhancements:
- tng-acc-bandmin.rc, tng-acc-bandmin: - added POD-documentation about all - checking if "kennung" exists - tng-acc-bandmin supports now a quiet simple and human-readable configfile - fixed misspelled words - moved short switch for "ReadDevices" from "-c" to "-r" - added switch to use a special config file (default one in current dir is "./.tng-acc-bandmin.rc"), please check documentation for side-effects - virtualization of "DBI"-driver, that means the DBI-Call is complete configurable by configfile or -switches - added an example for a configfile
<<less- You need a kernel with firewall-support
- you need ipfwadm or ipchains or iptables
- you need the InterBase-Client
- you need Perl 5.xx, pE. 5.5
- you need IBPerl0.8x
- you need DBI-Modul for Perl
- you need DBD::InterBase
(try "perl -Mcpan -e shell;" and type "install DBD::Interbase")
If you do not know what parts you needed, try install.sh for reports
First you must install a "Listening" firewall-policy. The tool tng-acc-bandminstart will do this. Follow the instructions of TNG-installation. The options-overview can you get by typing
"./tng-acc-bandmin --help", if you want a german-explanation, try "./tng-acc-bandmin --language=german --help". To remove firewall-policy use tng-acc-bandminstop.
If you have questions after reading all damn documentation, please dont hesitate to ask me for tng-acc-bandmin or marco for TNG in general.
Enhancements:
- tng-acc-bandmin.rc, tng-acc-bandmin: - added POD-documentation about all - checking if "kennung" exists - tng-acc-bandmin supports now a quiet simple and human-readable configfile - fixed misspelled words - moved short switch for "ReadDevices" from "-c" to "-r" - added switch to use a special config file (default one in current dir is "./.tng-acc-bandmin.rc"), please check documentation for side-effects - virtualization of "DBI"-driver, that means the DBI-Call is complete configurable by configfile or -switches - added an example for a configfile
Download (0.019MB)
Added: 2006-07-06 License: GPL (GNU General Public License) Price:
1205 downloads
Audio::FindChunks 0.03
Audio::FindChunks can breaks audio files into sound/silence parts. more>>
Audio::FindChunks can breaks audio files into sound/silence parts.
SYNOPSIS
use Audio::FindChunks;
# Duplicate input to output, caching RMS values to a file (as a side effect)
Audio::FindChunks->new(rms_filename => x.rms, filter => 1)->get(rms_data);
# Output human-readable info, using RMS cache file xxx.rms if present:
Audio::FindChunks->new(cache_rms => 1, filename => xxx.mp3,
stem_strip_extension => 1)->output_blocks();
# Remove start/end silence (if longer than 0.2sec):
Audio::FindChunks->new(cache_rms => 1, filename => xxx.mp3,
min_actual_silence_sec => 1e100)->split_file();
# Split a multiple-sides tape recording
Audio::FindChunks->new(filename => xxx.mp3, min_actual_silence_sec => 11
)->split_file({verbose => 1});
Audio sequence is broken into parts which contain only noise ("gaps"), and parts with usable signal ("tracks").
The following configuration settings (and defaults) are supported:
# For getting PCM flow (and if averaging data is read from cache)
frequency => 44100, # If raw_pcm or override_header_info only
bytes_per_sample => 4, # likewise
channels => 2, # likewise
sizedata => MY_INF, # likewise (how many bytes of PCM to read)
out_fh => *STDOUT, # mirror WAV/PCM to this FH if filter
# Process non-WAV data:
preprocess => {mp3 => [[qw(lame --silent --decode)], [], [-]]}, # Second contains extra args to read stdin
# RMS cache (used if valid_rms)
rms_extension => .rms, # Appended to the filestem
# Averaging to RMS info
sec_per_chunk => 0.1, # The window for taking mean square
# thresholds picking from the list of sorted 3-medians of RMS data
threshold_in_sorted_min_rel => 0, # relative position of threashold_min
threshold_in_sorted_min_sec => 1, # shifted by this amount in the list
threshold_factor_min => 1, # the list elt is multiplied by this
threshold_in_sorted_max_rel => 0.5, # likewise
threshold_in_sorted_max_sec => 0, # likewise
threshold_factor_max => 1, # likewise
threshold_ratio => 0.15, # relative position between min/max
# Chunkification: smoothification
above_thres_window => 11, # in units of chunks
above_thres_window_rel => 0.25, # fractions of chunks above threshold
# in a window to make chunk signal
# Splitting into runs of signal/noise
max_tracks => 9999, # fail if more signal/noise runs
min_signal_sec => 5, # such runs of signal are forced
min_silence_sec => 2, # likewise
ignore_signal_sec => 1, # short runs of signal are ignored
min_silence_chunks_merge (see below) # and long resulting runs of silence
# are forced
# Calculate average signal in an interval "deeply inside" silence runs
local_level_ignore_pre_sec => 0.3, # offset the start of this interval
local_level_ignore_pre_rel => 0.02, # additional relative offset
local_level_ignore_post_sec => 0.3, # likewise for end of the interval
local_level_ignore_post_rel => 0.02, # likewise
# Enlargement of signal runs: attach consequent chunks with signal this much
# above this average over the neighbour silence run
local_threshold_factor => 1.05,
# Final enlargement of runs of signal
extend_track_end_sec => 0.5, # Unconditional enlargement
extend_track_begin_sec => 0.3, # likewise
min_boundary_silence_sec => 0.2, # Ignore short silence at start/end
Note that above_thres_window is the only value specified directly in units of chunks; the other *_sec may be optionally specified in units of chunks by setting the corresponding *_chunks value. Note also that this window should better be decreased if minimal allowed silence length parameters are decreased.
These values are mirrored from other values if not explicitly specified:
min_actual_silence_sec<<less
SYNOPSIS
use Audio::FindChunks;
# Duplicate input to output, caching RMS values to a file (as a side effect)
Audio::FindChunks->new(rms_filename => x.rms, filter => 1)->get(rms_data);
# Output human-readable info, using RMS cache file xxx.rms if present:
Audio::FindChunks->new(cache_rms => 1, filename => xxx.mp3,
stem_strip_extension => 1)->output_blocks();
# Remove start/end silence (if longer than 0.2sec):
Audio::FindChunks->new(cache_rms => 1, filename => xxx.mp3,
min_actual_silence_sec => 1e100)->split_file();
# Split a multiple-sides tape recording
Audio::FindChunks->new(filename => xxx.mp3, min_actual_silence_sec => 11
)->split_file({verbose => 1});
Audio sequence is broken into parts which contain only noise ("gaps"), and parts with usable signal ("tracks").
The following configuration settings (and defaults) are supported:
# For getting PCM flow (and if averaging data is read from cache)
frequency => 44100, # If raw_pcm or override_header_info only
bytes_per_sample => 4, # likewise
channels => 2, # likewise
sizedata => MY_INF, # likewise (how many bytes of PCM to read)
out_fh => *STDOUT, # mirror WAV/PCM to this FH if filter
# Process non-WAV data:
preprocess => {mp3 => [[qw(lame --silent --decode)], [], [-]]}, # Second contains extra args to read stdin
# RMS cache (used if valid_rms)
rms_extension => .rms, # Appended to the filestem
# Averaging to RMS info
sec_per_chunk => 0.1, # The window for taking mean square
# thresholds picking from the list of sorted 3-medians of RMS data
threshold_in_sorted_min_rel => 0, # relative position of threashold_min
threshold_in_sorted_min_sec => 1, # shifted by this amount in the list
threshold_factor_min => 1, # the list elt is multiplied by this
threshold_in_sorted_max_rel => 0.5, # likewise
threshold_in_sorted_max_sec => 0, # likewise
threshold_factor_max => 1, # likewise
threshold_ratio => 0.15, # relative position between min/max
# Chunkification: smoothification
above_thres_window => 11, # in units of chunks
above_thres_window_rel => 0.25, # fractions of chunks above threshold
# in a window to make chunk signal
# Splitting into runs of signal/noise
max_tracks => 9999, # fail if more signal/noise runs
min_signal_sec => 5, # such runs of signal are forced
min_silence_sec => 2, # likewise
ignore_signal_sec => 1, # short runs of signal are ignored
min_silence_chunks_merge (see below) # and long resulting runs of silence
# are forced
# Calculate average signal in an interval "deeply inside" silence runs
local_level_ignore_pre_sec => 0.3, # offset the start of this interval
local_level_ignore_pre_rel => 0.02, # additional relative offset
local_level_ignore_post_sec => 0.3, # likewise for end of the interval
local_level_ignore_post_rel => 0.02, # likewise
# Enlargement of signal runs: attach consequent chunks with signal this much
# above this average over the neighbour silence run
local_threshold_factor => 1.05,
# Final enlargement of runs of signal
extend_track_end_sec => 0.5, # Unconditional enlargement
extend_track_begin_sec => 0.3, # likewise
min_boundary_silence_sec => 0.2, # Ignore short silence at start/end
Note that above_thres_window is the only value specified directly in units of chunks; the other *_sec may be optionally specified in units of chunks by setting the corresponding *_chunks value. Note also that this window should better be decreased if minimal allowed silence length parameters are decreased.
These values are mirrored from other values if not explicitly specified:
min_actual_silence_sec<<less
Download (0.024MB)
Added: 2006-06-19 License: Perl Artistic License Price:
1222 downloads
Indus 0.8
Indus is a collection of program analyzers and transformations implemented for customizing and adapting Java programs. more>>
Indus is an effort to provide a collection of program analyses and transformations implemented in Java to customize and adapt Java programs. Indus is intended to serve as an umbrella for:
* static analyses such as points-to analysis, escape analysis, and dependence analyses,
* transformations such as program slicing and program specialization via partial evaluation, and
* any software module that delivers the analyses/transformations into a particular application such as Bandera or platform such as Eclipse.
At present, there are 3 modules that are part of Indus. More modules are expected to be added over the course of time. We provide an overview of the intent of each module that are available at present.
Indus is a module that houses the implementation pertaining to algorithms and data structures common to analyses and transformations that are part of or are planned to be part of Indus. This module contains interface definition common to most analyses and transformations to provide a framework in which various implementations of analyses/transformations can be combined to form systems with ease. Hence, this module is updated when a new sort of analysis/transformation is implemented as a module in Indus. However, a new implementation of an analysis/transformation will not affect this module as it will implement an existing interface.
StaticAnalyses module is intended to be the collection of static analyses such as object-flow analysis, escape analysis, and dependence analyses. The analyses in this module use common interfaces and implementations from Indus and may define/provide new interfaces/implementations specific to new analyses. Existing analyses are mentioned below.
* Object-flow Analysis (OFA) is a points-to analysis for Java. Each allocation site in the analyzed system is treated as an abstract object and its flow through the system is tracked to infer the possible types an receiver at a call-site to enable the construction of a precise call-graph. The precision of the analysis can be varied in terms of flow-sensitiveness for method local variables and object-sensitiveness for instance fields.
* Escape Analysis is an extended implementation of the escape analysis proposed by Ruf for the purpose of pruning interference and ready dependence edges. The extensions are in the form of seamless addition of value equivalence to the analysis to improve the detection of conflicting field reads/writes occurring in different threads beyond just using type equality of the primaries of the access expressions. The analysis also uses object-flow information orthogonally to further improve precision.
* Dependence Analyses is a collection of dependence analyses: entry-based control, exit-based control, identifier-based data, reference-based data, interference, ready, synchronization, and divergence, required by analyses/transformations such program slicing and partial evaluation. Interference and Ready dependence analyses depend on the previous escape analysis while reference-based data and synchronization dependence analyses depend on object-flow information and the calculated call-graph information. Some analyses have varying levels of precision which can be varied via a well defined interface.
* Side-Effect Analysis provides method-level side-effect information. The user can query if any of the arguments/parameters to a call-site/method will be affected either directly (immediate members) or indirectly (recursively reachable members). Similarly, the user can provide a data access path rooted at arguments/parameters to a call-site/method and query if end point of the data access path is affected by the call/method.
* Monitor Anlaysis is a simple analysis that provides monitor/lock graph information for the given system.
* Safe Lock Analysis is an analysis that conservatively discovers if a lock (monitors) will not be held indefinitely. This information is used in conjunction with temporal dependences steming for Object.wait() and Object.notify()/ Object.notifyAll() as it is done in ready dependence.
* Atomicity Analysis provides information about atomicity in the given system. Current implementation relies on escape analysis to predict if a statement can be executed atomically. This information is used to detect atomic region of codes. This information is useful in applications such as model checking to reduce the the size of the state space, hence, improve performance.
Some analyses may be large enough to constitute module on their own and such analyses will be hosted as different modules in Indus rather than being consumed by this module.
Java Program Slicer module contains the core implementation of Java program slicer along with adapters that deliver the slicer in other applications such as Bandera and Eclipse. The implementation is architected as a library rather than as an application to facilitate the reuse of its subparts. The core is independent of the application; Each applications requirement of the slice can be satisfied by coding up implementations of post-processing interfaces and hooking in these implementations to form a customized slicer.
This module relies heavily on the information provided by dependence analyses and also the call-graph provided by OFA via well-defined interfaces that enables external implementations to be used for slicing.
This implementation of slicer is delivered to Eclipse with an intuitive UI via Kaveri plugin.
Features:o
Backward and Forward slice generation. Complete slices (union of backward and forward
slices starting from the same slice criteria) can be generated.
* Support to residualize (appropriate) slices into executable class files.
* Support for context-sensitive slicing via context rich slice criteria specification.
* Support to restrict the slice to a particular part of the system by scope specifications.
* Support to serialize slice criteria, slicer configurations, and slices.
All modules in Indus project work on Jimple, an intermediate representation of Java, provided by Soot toolkit from Sable group in McGill University. Each module in the project will be exposed as one or more Eclipse plugins if the provided information is useful to the user and amenable for user consumption via a graphical user interface.
Software Engineering Philosophy
Each module in this project will provide just the required functionality via well-defined interfaces that can be implemented to assemble a customized system with suitable extensions that fulfill specific requirement. As the interface is clearly separated from the implementation, any external implementation that provides the required interface can be seamlessly used with modules from this project.
Background
The implementation of most of the analyses was driven by the requirements of Java program slicer required by Bandera. However, as the program slicer could be used outside Bandera and the analyses could be used to enable other transformations such as program specialization via partial evaluation, we moved the analyses and transformations into a new project called Indus.
<<less* static analyses such as points-to analysis, escape analysis, and dependence analyses,
* transformations such as program slicing and program specialization via partial evaluation, and
* any software module that delivers the analyses/transformations into a particular application such as Bandera or platform such as Eclipse.
At present, there are 3 modules that are part of Indus. More modules are expected to be added over the course of time. We provide an overview of the intent of each module that are available at present.
Indus is a module that houses the implementation pertaining to algorithms and data structures common to analyses and transformations that are part of or are planned to be part of Indus. This module contains interface definition common to most analyses and transformations to provide a framework in which various implementations of analyses/transformations can be combined to form systems with ease. Hence, this module is updated when a new sort of analysis/transformation is implemented as a module in Indus. However, a new implementation of an analysis/transformation will not affect this module as it will implement an existing interface.
StaticAnalyses module is intended to be the collection of static analyses such as object-flow analysis, escape analysis, and dependence analyses. The analyses in this module use common interfaces and implementations from Indus and may define/provide new interfaces/implementations specific to new analyses. Existing analyses are mentioned below.
* Object-flow Analysis (OFA) is a points-to analysis for Java. Each allocation site in the analyzed system is treated as an abstract object and its flow through the system is tracked to infer the possible types an receiver at a call-site to enable the construction of a precise call-graph. The precision of the analysis can be varied in terms of flow-sensitiveness for method local variables and object-sensitiveness for instance fields.
* Escape Analysis is an extended implementation of the escape analysis proposed by Ruf for the purpose of pruning interference and ready dependence edges. The extensions are in the form of seamless addition of value equivalence to the analysis to improve the detection of conflicting field reads/writes occurring in different threads beyond just using type equality of the primaries of the access expressions. The analysis also uses object-flow information orthogonally to further improve precision.
* Dependence Analyses is a collection of dependence analyses: entry-based control, exit-based control, identifier-based data, reference-based data, interference, ready, synchronization, and divergence, required by analyses/transformations such program slicing and partial evaluation. Interference and Ready dependence analyses depend on the previous escape analysis while reference-based data and synchronization dependence analyses depend on object-flow information and the calculated call-graph information. Some analyses have varying levels of precision which can be varied via a well defined interface.
* Side-Effect Analysis provides method-level side-effect information. The user can query if any of the arguments/parameters to a call-site/method will be affected either directly (immediate members) or indirectly (recursively reachable members). Similarly, the user can provide a data access path rooted at arguments/parameters to a call-site/method and query if end point of the data access path is affected by the call/method.
* Monitor Anlaysis is a simple analysis that provides monitor/lock graph information for the given system.
* Safe Lock Analysis is an analysis that conservatively discovers if a lock (monitors) will not be held indefinitely. This information is used in conjunction with temporal dependences steming for Object.wait() and Object.notify()/ Object.notifyAll() as it is done in ready dependence.
* Atomicity Analysis provides information about atomicity in the given system. Current implementation relies on escape analysis to predict if a statement can be executed atomically. This information is used to detect atomic region of codes. This information is useful in applications such as model checking to reduce the the size of the state space, hence, improve performance.
Some analyses may be large enough to constitute module on their own and such analyses will be hosted as different modules in Indus rather than being consumed by this module.
Java Program Slicer module contains the core implementation of Java program slicer along with adapters that deliver the slicer in other applications such as Bandera and Eclipse. The implementation is architected as a library rather than as an application to facilitate the reuse of its subparts. The core is independent of the application; Each applications requirement of the slice can be satisfied by coding up implementations of post-processing interfaces and hooking in these implementations to form a customized slicer.
This module relies heavily on the information provided by dependence analyses and also the call-graph provided by OFA via well-defined interfaces that enables external implementations to be used for slicing.
This implementation of slicer is delivered to Eclipse with an intuitive UI via Kaveri plugin.
Features:o
Backward and Forward slice generation. Complete slices (union of backward and forward
slices starting from the same slice criteria) can be generated.
* Support to residualize (appropriate) slices into executable class files.
* Support for context-sensitive slicing via context rich slice criteria specification.
* Support to restrict the slice to a particular part of the system by scope specifications.
* Support to serialize slice criteria, slicer configurations, and slices.
All modules in Indus project work on Jimple, an intermediate representation of Java, provided by Soot toolkit from Sable group in McGill University. Each module in the project will be exposed as one or more Eclipse plugins if the provided information is useful to the user and amenable for user consumption via a graphical user interface.
Software Engineering Philosophy
Each module in this project will provide just the required functionality via well-defined interfaces that can be implemented to assemble a customized system with suitable extensions that fulfill specific requirement. As the interface is clearly separated from the implementation, any external implementation that provides the required interface can be seamlessly used with modules from this project.
Background
The implementation of most of the analyses was driven by the requirements of Java program slicer required by Bandera. However, as the program slicer could be used outside Bandera and the analyses could be used to enable other transformations such as program specialization via partial evaluation, we moved the analyses and transformations into a new project called Indus.
Download (0.24MB)
Added: 2006-04-26 License: Other/Proprietary License Price:
1277 downloads
System Configuration Collector 1.7.38
System Configuration Collector (SCC) is yet another configuration collector. more>>
System Configuration Collector in short SCC, collects configuration data of systems in snapshots. The structure of the snapshot allows SCC to compare a snapshot with the previous one and detect changes in the configuration.
Upon detecting changes, scc adds the differences to a logbook. The snapshot and the logbook are converted to HTML for local inspection. Optionally, the SCC-files can be send to a system running the SCC server software. On the server, summaries of the SCC-data are generated and search/compare operations on the snapshots and logbooks are available via a web-interface.
The logbook is a starting point in case a system "suddenly" does not work correctly and the administrator is wondering what he/she has changed in the last weeks or months. As most of us know by experience, configuration changes can have accidental side-effects on (other) systems.
By examining the entries in the logbooks and considering the consequences, the cause of an actual problem might be found more easily than by just trying to remember the changes that were performed.
The snapshots can be used to compare the configuration of two systems. Imagine systems, that are supposed to be identical, but behave differently. Comparing parts of the snapshots of the two systems can indicate the cause of the difference in behavior.
Enhancements:
- The DIV tags in the HTML was corrected.
- Directory data/transfer was created to avoid errors in scc-pull. cpu-speed for SunOS was added.
- The machinfo variable is now initialized.
- The determination of local filesystems on Linux was corrected.
- Squid classification was corrected.
<<lessUpon detecting changes, scc adds the differences to a logbook. The snapshot and the logbook are converted to HTML for local inspection. Optionally, the SCC-files can be send to a system running the SCC server software. On the server, summaries of the SCC-data are generated and search/compare operations on the snapshots and logbooks are available via a web-interface.
The logbook is a starting point in case a system "suddenly" does not work correctly and the administrator is wondering what he/she has changed in the last weeks or months. As most of us know by experience, configuration changes can have accidental side-effects on (other) systems.
By examining the entries in the logbooks and considering the consequences, the cause of an actual problem might be found more easily than by just trying to remember the changes that were performed.
The snapshots can be used to compare the configuration of two systems. Imagine systems, that are supposed to be identical, but behave differently. Comparing parts of the snapshots of the two systems can indicate the cause of the difference in behavior.
Enhancements:
- The DIV tags in the HTML was corrected.
- Directory data/transfer was created to avoid errors in scc-pull. cpu-speed for SunOS was added.
- The machinfo variable is now initialized.
- The determination of local filesystems on Linux was corrected.
- Squid classification was corrected.
Download (MB)
Added: 2007-07-13 License: GPL (GNU General Public License) Price:
836 downloads
imgSeekWeb 0.0.1
imgSeekWeb is a content base image search engine for your web-server. more>>
imgSeekWeb is a content base image search engine for your web-server.
imgSeekWeb is based on imgSeek project. The final goal is a distributed server side content-based image search engine.
<<lessimgSeekWeb is based on imgSeek project. The final goal is a distributed server side content-based image search engine.
Download (0.046MB)
Added: 2006-05-05 License: GPL (GNU General Public License) Price:
1269 downloads
GM Invert 0-1-12
GM Invert is a collection of GIMP effects that lets you toggle any one of the effects than it gives back the original image. more>>
GM Invert is a collection of GIMP effects that lets you toggle any one of the effects than it gives back the original image. Cycle through all three effects in any order, and you arrive back to the original image.
The latest version adds the Solarize effect and the cool Vivid V-invert effect.
<<lessThe latest version adds the Solarize effect and the cool Vivid V-invert effect.
Download (0.028MB)
Added: 2006-09-15 License: GPL (GNU General Public License) Price:
1136 downloads
Photo resize 0.1
Photo resize is a service menu for KDE that changes the selected pictures to a chosen size. more>>
Photo resize is a service menu for KDE that changes the selected pictures to the chosen size (550x550px, 500x500px, 450x450px,200x200px,150x150px).
The geometry will be hold. The script will size the pictures to their longer side.
Attention: The pictures will be overwritten!!
<<lessThe geometry will be hold. The script will size the pictures to their longer side.
Attention: The pictures will be overwritten!!
Download (MB)
Added: 2007-07-10 License: GPL (GNU General Public License) Price:
843 downloads
Simple Backup 1.0
Simple Backup is a shell script to create basic backups using tar, grep, sed, and bash. more>>
Simple Backup is a shell script to create basic backups using tar, grep, sed, and bash.
Simple Backup works by using a file that contains the folders to be backed up and a file that contains expressions to exclude certain folders/files.
Usage: backup.sh < backuplist > < excludelist >
Free to use at your own risk. The author cant be held responsible for any side effects
of using this software. Use at your own risk.
<<lessSimple Backup works by using a file that contains the folders to be backed up and a file that contains expressions to exclude certain folders/files.
Usage: backup.sh < backuplist > < excludelist >
Free to use at your own risk. The author cant be held responsible for any side effects
of using this software. Use at your own risk.
Download (0.003MB)
Added: 2006-07-26 License: Freeware Price:
1186 downloads
Archimedes 0.52.0
Archimedes is an Open CAD for architects. more>>
Archimedes is an Open CAD for architects.
Archimedes is a Computer Aided Design (CAD) program developed side by side with architecture offices in order to fulfill all their needs.
This way, we hope to develop software better suited for architects than the currently widely used AutoCAD.
<<lessArchimedes is a Computer Aided Design (CAD) program developed side by side with architecture offices in order to fulfill all their needs.
This way, we hope to develop software better suited for architects than the currently widely used AutoCAD.
Download (6.3MB)
Added: 2007-05-29 License: GPL (GNU General Public License) Price:
886 downloads
eXtensible Server Side Markup Language 1.0
eXtensible Server Side Markup Language is an XML-based language to streamline development of Web applications, etc. more>>
eXtensible Server Side Markup Language is based on XML and Struts technologies, and allows for an easy and streamlined creation of various technical and business rules with further implementation as Web services and interfaces.
It features the ability to define XML structures and ties such to actual Java code, conditional and flow processing logic, variable definition by value and reference, and logging both at class and custom component level.
<<lessIt features the ability to define XML structures and ties such to actual Java code, conditional and flow processing logic, variable definition by value and reference, and logging both at class and custom component level.
Download (0.018MB)
Added: 2005-04-03 License: Freely Distributable Price:
1672 downloads
CSS Sync 0.2
CSS Sync is a Firefox extension which automatically Sync the CSS from your server. more>>
CSS Sync is a Firefox extension which automatically Sync the CSS from your server.
Automatically Sync the CSS from your server! This extension automatically syncs the style sheets that you edit on the server side to the client and applies them continuously.
For a web developer this will save lot of time. In development stage you just need to continuously edit the style sheet on server and see the effect on client side(browser) instantaneously.
<<lessAutomatically Sync the CSS from your server! This extension automatically syncs the style sheets that you edit on the server side to the client and applies them continuously.
For a web developer this will save lot of time. In development stage you just need to continuously edit the style sheet on server and see the effect on client side(browser) instantaneously.
Download (0.005MB)
Added: 2007-04-10 License: MPL (Mozilla Public License) Price:
935 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 yasmin side effects 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
