priority one
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 233
Supervisor 3.01a
Supervisor is a client/server system that allows its users to control a number of processes on UNIX-like operating systems. more>>
Supervisor is a client/server system that allows its users to control a number of processes on UNIX-like operating systems. It was inspired by the following:
- It is often inconvenient to need to write "rc.d" scripts for every single process instance. rc.d scripts are a great lowest-common-denominator form of process initialization/autostart/management, but they can be painful to write and maintain. Additionally, rc.d scripts cannot automatically restart a crashed process and many programs do not restart themselves properly on a crash. Supervisord starts processes as its subprocesses, and can be configured to automatically restart them on a crash. It can also automatically be configured to start processes on its own invocation.
- Its often difficult to get accurate up/down status on processes on UNIX. Pidfiles often lie. Supervisord starts processes as subprocesses, so it always knows the true up/down status of its children and can be queried conveniently for this data.
- Users who need to control process state often need only to do that. They dont want or need full-blown shell access to the machine on which the processes are running. Supervisorctl allows a very limited form of access to the machine, essentially allowing users to see process status and control supervisord-controlled subprocesses by emitting "stop", "start", and "restart" commands from a simple shell or web UI.
- Users often need to control processes on many machines. Supervisor provides a simple, secure, and uniform mechanism for interactively and automatically controlling processes on groups of machines.
- Processes which listen on "low" TCP ports often need to be started and restarted as the root user (a UNIX misfeature). Its usually the case that its perfectly fine to allow "normal" people to stop or restart such a process, but providing them with shell access is often impractical, and providing them with root access or sudo access is often impossible. Its also (rightly) difficult to explain to them why this problem exists. If supervisord is started as root, it is possible to allow "normal" users to control such processes without needing to explain the intricacies of the problem to them.
- Processes often need to be started and stopped in groups, sometimes even in a "priority order". Its often difficult to explain to people how to do this. Supervisor allows you to assign priorities to processes, and allows user to emit commands via the supervisorctl client like "start all", and "restart all", which starts them in the preassigned priority order. Additionally, processes can be grouped into "process groups" and a set of logically related processes can be stopped and started as a unit.
<<less- It is often inconvenient to need to write "rc.d" scripts for every single process instance. rc.d scripts are a great lowest-common-denominator form of process initialization/autostart/management, but they can be painful to write and maintain. Additionally, rc.d scripts cannot automatically restart a crashed process and many programs do not restart themselves properly on a crash. Supervisord starts processes as its subprocesses, and can be configured to automatically restart them on a crash. It can also automatically be configured to start processes on its own invocation.
- Its often difficult to get accurate up/down status on processes on UNIX. Pidfiles often lie. Supervisord starts processes as subprocesses, so it always knows the true up/down status of its children and can be queried conveniently for this data.
- Users who need to control process state often need only to do that. They dont want or need full-blown shell access to the machine on which the processes are running. Supervisorctl allows a very limited form of access to the machine, essentially allowing users to see process status and control supervisord-controlled subprocesses by emitting "stop", "start", and "restart" commands from a simple shell or web UI.
- Users often need to control processes on many machines. Supervisor provides a simple, secure, and uniform mechanism for interactively and automatically controlling processes on groups of machines.
- Processes which listen on "low" TCP ports often need to be started and restarted as the root user (a UNIX misfeature). Its usually the case that its perfectly fine to allow "normal" people to stop or restart such a process, but providing them with shell access is often impractical, and providing them with root access or sudo access is often impossible. Its also (rightly) difficult to explain to them why this problem exists. If supervisord is started as root, it is possible to allow "normal" users to control such processes without needing to explain the intricacies of the problem to them.
- Processes often need to be started and stopped in groups, sometimes even in a "priority order". Its often difficult to explain to people how to do this. Supervisor allows you to assign priorities to processes, and allows user to emit commands via the supervisorctl client like "start all", and "restart all", which starts them in the preassigned priority order. Additionally, processes can be grouped into "process groups" and a set of logically related processes can be stopped and started as a unit.
Download (0.13MB)
Added: 2007-08-23 License: ZPL (Zope Public License) Price:
497 downloads
cpulimit 1.1
cpulimit is a simple program that attempts to limit the cpu usage of a process (expressed in percentage, not in cpu time). more>>
cpulimit is a simple program that attempts to limit the cpu usage of a process (expressed in percentage, not in cpu time). This is useful to control batch jobs, when you dont want they eat too much cpu.
cpulimit project does not act on the nice value or other scheduling priority stuff, but on the real cpu usage. Also, it is able to adapt itself to the overall system load, dynamically and quickly.
<<lesscpulimit project does not act on the nice value or other scheduling priority stuff, but on the real cpu usage. Also, it is able to adapt itself to the overall system load, dynamically and quickly.
Download (0.005MB)
Added: 2007-01-09 License: GPL (GNU General Public License) Price:
1023 downloads
Aurora Project 0.3
The Aurora Project aims to be a simple yet effective and intuitive Desktop Environment. more>>
The Aurora Project is an attempt to create a new generation of Linux distributions. It will try to break free from old patterns and establish Linux as a serious world player.
Currently, Aurora Project consists of the Aurora Desktop Environment which, unlike most other Linux-based desktop environments, dont attempts to accomplish everything but to remove the focus from system configuration and desktop customizing by creating an easy-to-use out-of-the-box intuitive and beutiful desktop experience.
The UI is (for now) somewhat Microsoft Windows-inspired. I am satisfied with the general layout of the panel and start menu, currently I am busy designing the core functionality of the desktop with the panel as my number one priority. Also there is the session manager, the desktop manager and the shared library.
The Aurora Project currently consists of two major components - the panel and the shared library.
Main features:
- Windows-like user interface with a start menu.
- Freedesktop-compliant application menu (compatible with GNOME and KDE).
- Frequently used applications are easy to access.
<<lessCurrently, Aurora Project consists of the Aurora Desktop Environment which, unlike most other Linux-based desktop environments, dont attempts to accomplish everything but to remove the focus from system configuration and desktop customizing by creating an easy-to-use out-of-the-box intuitive and beutiful desktop experience.
The UI is (for now) somewhat Microsoft Windows-inspired. I am satisfied with the general layout of the panel and start menu, currently I am busy designing the core functionality of the desktop with the panel as my number one priority. Also there is the session manager, the desktop manager and the shared library.
The Aurora Project currently consists of two major components - the panel and the shared library.
Main features:
- Windows-like user interface with a start menu.
- Freedesktop-compliant application menu (compatible with GNOME and KDE).
- Frequently used applications are easy to access.
Download (2.5MB)
Added: 2005-08-31 License: GPL (GNU General Public License) Price:
1514 downloads
issPolicy 1.01
The issPolicy utility allows ISS RealSecure Network Sensor and policy files to be converted into a single HTML file. more>>
issPolicy is a free open-source utility for converting an ISS RealSecure Network Sensor and ISS Proventia Inline Appliance Policy to a static HTML file.
Written in Perl, issPolicy allows for granular parsing of ISS RSNS and ISS Proventia policies (also refer to the "support" section), and supports a wide variety of features (see "features" section) allowing the HTML generation to be customized based on different policy parameters.
Main features:
- issPolicy automatically detects whether the policy is a ISS RealSecure Network Sensor or ISS Proventia Inline Appliance policy and generates a static HTML file based on the policy type and its features.
- issPolicy extracts the following information from the ISS RealSecure Network Sensor Policy:
- Signatures Policy (Signature Name, Signature Description, Signature Status, Signature Priority, Configured Responses, Logging Type)
- IP Filters Policy (Filter Name, Filter Description, Filter Status, Protocol, Source Address, Source Port, Destination Address, Destination Port)
- Event Filters Policy (Filter Name, Filter Description, Filter Status, Filtered Event, Source Address, Source Port, Destination Address, Destination Port)
- issPolicy extracts the following information from the ISS Proventia Inline Appliance Policy:
- Signatures Policy (Signature Name, Signature Description, Signature Status, Signature Priority, Configured Responses, Logging Type, Drop Options, DynamicBlock Options)
- IP Filters Policy (Filter Name, Filter Description, Filter Status, Protocol, Source Address, Source Port, Destination Address, Destination Port)
- Event Filters Policy (Filter Name, Filter Description, Filter Status, Filtered Event, Source Address, Source Port, Destination Address, Destination Port)
- issPolicy contains various useful options allowing for a tailored HTML Policy file to be generated, based on one or more of the following criteria:
- Signature Policy Criteria:
- Whether signature is enabled or disabled
- Based on signature priority (High, Medium, or Low)
- Whether drop is enabled [only on ISS Proventia Inline Appliance Policies]
- Based on drop options (ConnectionWithReset, Connection, or Packet) [only on ISS Proventia Inline Appliance Policies]
- Whether dynamicblock is enabled [only on ISS Proventia Inline Appliance Policies]
- Based on dynamicblock options (IsolateTrojan, BlockWorm, BlockIntruder) [only on ISS Proventia Inline Appliance Policies]
- IP Filter Policy Criteria:
- Whether IP filter is enabled or disabled
- Event Filter Policy Criteria:
- Whether Event Filter is enabled or disabled
- issPolicy uses an "API" structured format, pushing the entire policy to hash arrays, allowing the possibility for other output methods to be developed (CSV, XML, etc...)
<<lessWritten in Perl, issPolicy allows for granular parsing of ISS RSNS and ISS Proventia policies (also refer to the "support" section), and supports a wide variety of features (see "features" section) allowing the HTML generation to be customized based on different policy parameters.
Main features:
- issPolicy automatically detects whether the policy is a ISS RealSecure Network Sensor or ISS Proventia Inline Appliance policy and generates a static HTML file based on the policy type and its features.
- issPolicy extracts the following information from the ISS RealSecure Network Sensor Policy:
- Signatures Policy (Signature Name, Signature Description, Signature Status, Signature Priority, Configured Responses, Logging Type)
- IP Filters Policy (Filter Name, Filter Description, Filter Status, Protocol, Source Address, Source Port, Destination Address, Destination Port)
- Event Filters Policy (Filter Name, Filter Description, Filter Status, Filtered Event, Source Address, Source Port, Destination Address, Destination Port)
- issPolicy extracts the following information from the ISS Proventia Inline Appliance Policy:
- Signatures Policy (Signature Name, Signature Description, Signature Status, Signature Priority, Configured Responses, Logging Type, Drop Options, DynamicBlock Options)
- IP Filters Policy (Filter Name, Filter Description, Filter Status, Protocol, Source Address, Source Port, Destination Address, Destination Port)
- Event Filters Policy (Filter Name, Filter Description, Filter Status, Filtered Event, Source Address, Source Port, Destination Address, Destination Port)
- issPolicy contains various useful options allowing for a tailored HTML Policy file to be generated, based on one or more of the following criteria:
- Signature Policy Criteria:
- Whether signature is enabled or disabled
- Based on signature priority (High, Medium, or Low)
- Whether drop is enabled [only on ISS Proventia Inline Appliance Policies]
- Based on drop options (ConnectionWithReset, Connection, or Packet) [only on ISS Proventia Inline Appliance Policies]
- Whether dynamicblock is enabled [only on ISS Proventia Inline Appliance Policies]
- Based on dynamicblock options (IsolateTrojan, BlockWorm, BlockIntruder) [only on ISS Proventia Inline Appliance Policies]
- IP Filter Policy Criteria:
- Whether IP filter is enabled or disabled
- Event Filter Policy Criteria:
- Whether Event Filter is enabled or disabled
- issPolicy uses an "API" structured format, pushing the entire policy to hash arrays, allowing the possibility for other output methods to be developed (CSV, XML, etc...)
Download (0.016MB)
Added: 2005-07-04 License: GPL (GNU General Public License) Price:
1573 downloads
Audiality 0.1.1
Audiality is a scalable and portable audio engine for music and sound effects. more>>
Audiality is a scalable and portable audio engine for music and sound effects. It is intended to play equally well in studios and inside games, in order to serve as a flexible tool for content creation, and for use in the final product.
Audiality uses MIDI files in combination with scripting and modular synthesis, to minimize file sizes and maximise flexibility. It is very portable, and supports both integer and floating point processing modes.
Scalability has been a major priority from the start. The current version will run on very low end Pentium systems, but can also produce high quality audio on more powerful hardware.
The main goal for the future is to extend the scalability of Audiality well into the range of serious home and professional studio use. The idea is to provide total control, a wide range of features, tools for fast and effective creation of original sounds, and excellent audio quality.
<<lessAudiality uses MIDI files in combination with scripting and modular synthesis, to minimize file sizes and maximise flexibility. It is very portable, and supports both integer and floating point processing modes.
Scalability has been a major priority from the start. The current version will run on very low end Pentium systems, but can also produce high quality audio on more powerful hardware.
The main goal for the future is to extend the scalability of Audiality well into the range of serious home and professional studio use. The idea is to provide total control, a wide range of features, tools for fast and effective creation of original sounds, and excellent audio quality.
Download (0.80MB)
Added: 2006-08-03 License: LGPL (GNU Lesser General Public License) Price:
1178 downloads
PKAudio 0.3
PKAudio library is a high performance audio/signal processing library. more>>
PKAudio library is a high performance signal/audio processing library that allows stream objects to be created and mixed without interrupting the main stream of audio.
The core library runs in pkaudiod, an executable that runs with realtime or high priority, and a single client can communicate with it via a tcp socket.
A python client is provided, and can be used to write clients in other languages if necessary. The API is small and the protocol is simple.
Installation:
There are two parts to pkaudio: the pkaudiod daemon executable and the python module to communicate with it. The daemon is written in C++ and is configured and compiled like and other make program. To install everything, all you have to do is use the install.py python script like any other extension module. Here are the simplest install instructions:
cd < source dir >
python install.py [-h]
Usage:
If Jack support is compiled into pkaudio, make sure you start the jack daemon before running pkaudiod. If you dont, there will be no audio output. You can start the jack server with at least something like this (-r 44100 is required):
jackd -d alsa -r 44100
The pkaudiod executable is installed in your path and can be executed explicitly from the command line, or implicitly with the python module:
pkaudiod --realtime
The "--realtime" option tells pkaudiod to run with realtime priority, or the highest priority possible if realtime shceduling is not available in the kernel. Most systems will only allow processes to be scheduled with realtime priority if they are executed by the superuser "root". If you want to run the daemon with realtime priority as a normal user, you have to set the owner of the file to root, and the suid bit to on, like this (this is automatically done in the install.py script):
su
chown root `which pkaudiod`
chmod +s `which pkaudiod`
The daemon will tell you if it is running with realtime priority, or if it is running with increased priority.
Using the Python Module:
A good way to learn how to use the python module is to look at test_unittest.py. But, the following code will start the pkaudiod daemon as a child process and play a wav file:
import time
import pkaudio
pkaudio.connect(startserver=1)
sid = pkaudio.createModule(Sample,
/home/ajole/wav/loops/Document 1.wav)
sample = pkaudio.getModuleInfo(sid)
mixer = pkaudio.getMainMixer(0)
pkaudio.getModuleInfo(mixer)
pkaudio.connectToMixer(mixer, sample[outs][0])
pkaudio.setProperty(sid, playing, pkaudio.TRUE)
pkaudio.setProperty(sid, looping, pkaudio.TRUE)
time.sleep(100)
Fortunately, all of this can be accomplished with the higher-level PKAudio module:
import time
import PKAudio
PKAudio.start_server()
d = PKAudio.Driver()
s = PKAudio.Sample("/home/me/my.wav")
m = d.getMixer(0)
m.connect(s.outputPort())
s.play()
while not s.atEnd():
time.sleep(1)
<<lessThe core library runs in pkaudiod, an executable that runs with realtime or high priority, and a single client can communicate with it via a tcp socket.
A python client is provided, and can be used to write clients in other languages if necessary. The API is small and the protocol is simple.
Installation:
There are two parts to pkaudio: the pkaudiod daemon executable and the python module to communicate with it. The daemon is written in C++ and is configured and compiled like and other make program. To install everything, all you have to do is use the install.py python script like any other extension module. Here are the simplest install instructions:
cd < source dir >
python install.py [-h]
Usage:
If Jack support is compiled into pkaudio, make sure you start the jack daemon before running pkaudiod. If you dont, there will be no audio output. You can start the jack server with at least something like this (-r 44100 is required):
jackd -d alsa -r 44100
The pkaudiod executable is installed in your path and can be executed explicitly from the command line, or implicitly with the python module:
pkaudiod --realtime
The "--realtime" option tells pkaudiod to run with realtime priority, or the highest priority possible if realtime shceduling is not available in the kernel. Most systems will only allow processes to be scheduled with realtime priority if they are executed by the superuser "root". If you want to run the daemon with realtime priority as a normal user, you have to set the owner of the file to root, and the suid bit to on, like this (this is automatically done in the install.py script):
su
chown root `which pkaudiod`
chmod +s `which pkaudiod`
The daemon will tell you if it is running with realtime priority, or if it is running with increased priority.
Using the Python Module:
A good way to learn how to use the python module is to look at test_unittest.py. But, the following code will start the pkaudiod daemon as a child process and play a wav file:
import time
import pkaudio
pkaudio.connect(startserver=1)
sid = pkaudio.createModule(Sample,
/home/ajole/wav/loops/Document 1.wav)
sample = pkaudio.getModuleInfo(sid)
mixer = pkaudio.getMainMixer(0)
pkaudio.getModuleInfo(mixer)
pkaudio.connectToMixer(mixer, sample[outs][0])
pkaudio.setProperty(sid, playing, pkaudio.TRUE)
pkaudio.setProperty(sid, looping, pkaudio.TRUE)
time.sleep(100)
Fortunately, all of this can be accomplished with the higher-level PKAudio module:
import time
import PKAudio
PKAudio.start_server()
d = PKAudio.Driver()
s = PKAudio.Sample("/home/me/my.wav")
m = d.getMixer(0)
m.connect(s.outputPort())
s.play()
while not s.atEnd():
time.sleep(1)
Download (0.66MB)
Added: 2006-02-15 License: GPL (GNU General Public License) Price:
1349 downloads
frottle 0.2.1
Frottle (Freenet throttle) is a project to control traffic on wireless networks. more>>
Frottle (Freenet throttle) is a project to control traffic on wireless networks. Such control eliminates the common hidden-node effect even on large scale wireless networks. Frottle is currently only available for Linux wireless gateways using iptables firewalls, with plans to develop a windows client in the future.
Frottle is made to schedule the traffic of each client, using a master node to co-ordinate actions. This eliminates collisions, and prevents clients with stronger signals from receiving bandwidth bias.
Frottle has been developed and tested on the large community wireless network of WaFreeNet. We have found running frottle has given us a significant improvment in the network usability. Testing results will be documented here as time permits.
Frottle currently operates as a userspace application, receiveing outbound packets via the iptables QUEUE functionality. Access to the network is controlled by the frottle master, sending each client a control packet (token) which contains information about how much data can be sent at this time.
Each client receives its token and sends any required data, one at a time. This eliminates collisions, and with a reasonable signal packetloss is virtually zero. Also, since each client gets a limited slice of the bandwidth, everyone can get fair access regardless of their signal strength. Whilst this mechanism does result in increased latency, overall network performance and utilisation can significantly increase.
Main features:
- Traffic queues built in to frottle assign different, dynamic priorities to different traffic. Most traffic has a default priority. Traffic to/from specified ports (and ICMP packets) are made high priority. Traffic for connections that have done more than 2 MB of data and have a rate of more than 5 KB/s are made low priority. When a client is polled, high priority traffic is sent first, then default, then low until the poll quota is used.
-
- Realtime info on each clients performance is available from the master in a html file and optionally at each client in a similar html file. (The names and locations of these files is set in /etc/frottle.conf.)
<<lessFrottle is made to schedule the traffic of each client, using a master node to co-ordinate actions. This eliminates collisions, and prevents clients with stronger signals from receiving bandwidth bias.
Frottle has been developed and tested on the large community wireless network of WaFreeNet. We have found running frottle has given us a significant improvment in the network usability. Testing results will be documented here as time permits.
Frottle currently operates as a userspace application, receiveing outbound packets via the iptables QUEUE functionality. Access to the network is controlled by the frottle master, sending each client a control packet (token) which contains information about how much data can be sent at this time.
Each client receives its token and sends any required data, one at a time. This eliminates collisions, and with a reasonable signal packetloss is virtually zero. Also, since each client gets a limited slice of the bandwidth, everyone can get fair access regardless of their signal strength. Whilst this mechanism does result in increased latency, overall network performance and utilisation can significantly increase.
Main features:
- Traffic queues built in to frottle assign different, dynamic priorities to different traffic. Most traffic has a default priority. Traffic to/from specified ports (and ICMP packets) are made high priority. Traffic for connections that have done more than 2 MB of data and have a rate of more than 5 KB/s are made low priority. When a client is polled, high priority traffic is sent first, then default, then low until the poll quota is used.
-
- Realtime info on each clients performance is available from the master in a html file and optionally at each client in a similar html file. (The names and locations of these files is set in /etc/frottle.conf.)
Download (0.030MB)
Added: 2006-06-27 License: GPL (GNU General Public License) Price:
1216 downloads
Hardware Monitor applet 1.4
The Hardware Monitor applet is a small program for the Gnome panel. more>>
Hardware Monitor applet is a small program for the Gnome panel which tries to be a beautiful all-round solution to hardware monitoring.
It also tries to be user-friendly and generally nice and sensible, integrating pleasantly with the rest of your Gnome desktop.
Main features:
- A graphical view where each monitor is represented by a (time, measurement) colored curve
- A bar-plot view with a horizontal bar per monitor
- A column view with a column (time, measurement) diagram for each monitor
- A textual view which simply lists the monitors and the currently measured values
- A flame view which produces spiffy flames, the sizes of which are determined by the values of the monitored device
And the applet supports monitoring the following hardware characteristics:
- CPU usage (all CPUs, or one at the time) - niced background processes such as SETI@home are automatically ignored
- Memory usage - cache and buffers are automatically ignored
- Swap usage
- Load average
- Disk usage (or disk space free)
- Network throughput (Ethernet, wireless, modem, serial link), either incoming or outgoing or both
- Temperatures from internal sensors (e.g. system board and CPU temperatures)
- Fan speeds from internal sensors
- To avoid eating CPU time when it is scarce, the applet lowers its priority.
<<lessIt also tries to be user-friendly and generally nice and sensible, integrating pleasantly with the rest of your Gnome desktop.
Main features:
- A graphical view where each monitor is represented by a (time, measurement) colored curve
- A bar-plot view with a horizontal bar per monitor
- A column view with a column (time, measurement) diagram for each monitor
- A textual view which simply lists the monitors and the currently measured values
- A flame view which produces spiffy flames, the sizes of which are determined by the values of the monitored device
And the applet supports monitoring the following hardware characteristics:
- CPU usage (all CPUs, or one at the time) - niced background processes such as SETI@home are automatically ignored
- Memory usage - cache and buffers are automatically ignored
- Swap usage
- Load average
- Disk usage (or disk space free)
- Network throughput (Ethernet, wireless, modem, serial link), either incoming or outgoing or both
- Temperatures from internal sensors (e.g. system board and CPU temperatures)
- Fan speeds from internal sensors
- To avoid eating CPU time when it is scarce, the applet lowers its priority.
Download (0.30MB)
Added: 2007-01-17 License: GPL (GNU General Public License) Price:
601 downloads
Palm::Progect::Converter::CSV 2.0.4
Palm::Progect::Converter::CSV is a Perl module to convert between Progect databases and CSV files. more>>
Palm::Progect::Converter::CSV is a Perl module to convert between Progect databases and CSV files.
SYNOPSIS
my $converter = Palm::Progect::Converter->new(
format => CSV,
# ... other args ...
);
$converter->load_records();
# ... do stuff with records
$converter->save_records();
This converts between CSV files and Palm::Progect records and preferences.
The CSV format allows for basic import/export with spreadsheet programs. The CSV file does not look like a tree structure; instead, there is a level column, which indicates the indent level for the current row.
The columns in the format are:
level
The indent level of the record.
description
priority
The priority of the record from 1 to 5, or 0 for no priority.
isAction
isProgress
isNumeric
isInfo
Any record can have one (and only one) of the above types.
If you are going to change the type of a record, remember to set all the other types to false:
isAction isProgress isNumeric isInfo
0 0 0 1
completed
Completed has different values depending upon the type of record. For action items, it is either 1 or 0, for complete or not complete.
For Progress items, it is a number between 1 and 100, indicating a percentage.
For Numeric items it is a number between 1 and 100 indicating the the integer percentage of the numericActual value divided by the numericLimit value.
numericActual
The numerator of a numeric record. If the numeric value of a record is 4/5, then the numericActual value is 4.
numericLimit
The denominator of a numeric record. If the numeric value of a record is 4/5, then the numericLimit value is 5.
DateDue
This is a date in the format specified on the command line with the --csv-date-format option
category
opened
description
note
<<lessSYNOPSIS
my $converter = Palm::Progect::Converter->new(
format => CSV,
# ... other args ...
);
$converter->load_records();
# ... do stuff with records
$converter->save_records();
This converts between CSV files and Palm::Progect records and preferences.
The CSV format allows for basic import/export with spreadsheet programs. The CSV file does not look like a tree structure; instead, there is a level column, which indicates the indent level for the current row.
The columns in the format are:
level
The indent level of the record.
description
priority
The priority of the record from 1 to 5, or 0 for no priority.
isAction
isProgress
isNumeric
isInfo
Any record can have one (and only one) of the above types.
If you are going to change the type of a record, remember to set all the other types to false:
isAction isProgress isNumeric isInfo
0 0 0 1
completed
Completed has different values depending upon the type of record. For action items, it is either 1 or 0, for complete or not complete.
For Progress items, it is a number between 1 and 100, indicating a percentage.
For Numeric items it is a number between 1 and 100 indicating the the integer percentage of the numericActual value divided by the numericLimit value.
numericActual
The numerator of a numeric record. If the numeric value of a record is 4/5, then the numericActual value is 4.
numericLimit
The denominator of a numeric record. If the numeric value of a record is 4/5, then the numericLimit value is 5.
DateDue
This is a date in the format specified on the command line with the --csv-date-format option
category
opened
description
note
Download (0.040MB)
Added: 2006-08-23 License: Perl Artistic License Price:
1157 downloads
Titration 1.3.2
Titration is a multi-user, multi-project tracking system. more>>
Titration is a multi-user, multi-project tracking system. Titration is simple and is designed to work with other project management and time-tracking projects.
It is designed to show the present work load, priority, and state of (closed/ongoing/queued/active) projects.
This is not a micro-management package, a project management tool, or time-tracking software. It is an extension of tools that do these things.
Enhancements:
- You can now drag and drop the priorities into the desired location.
- The project name in the drop down lists is now sorted by name desc.
- On the "Overview" tab, the user logging in will now have that users project details loaded.
- The overview menu now supports the exporting of data in XML and HTML formats.
<<lessIt is designed to show the present work load, priority, and state of (closed/ongoing/queued/active) projects.
This is not a micro-management package, a project management tool, or time-tracking software. It is an extension of tools that do these things.
Enhancements:
- You can now drag and drop the priorities into the desired location.
- The project name in the drop down lists is now sorted by name desc.
- On the "Overview" tab, the user logging in will now have that users project details loaded.
- The overview menu now supports the exporting of data in XML and HTML formats.
Download (0.094MB)
Added: 2006-01-31 License: GPL (GNU General Public License) Price:
1363 downloads
Printbill 4.2.0
Printbill is a sophistocated Unix print billing and/or accounting system with associated administration utilities. more>>
Printbill is a sophistocated Unix print billing and/or accounting system with associated administration utilities. It primarily supports LPRng but now has limited CUPS support as well.
A simple print filter and accompanying daemon perform pre-printing billing, post-printing billing, print-accounting and print job quote generation. In addition, various utilities for administrators and users are provided - including programs to check your print quota and usage patterns, a web interface for both users and administrators and a command-line quote generator.
Charge rates may be specified on per-page, per-percent-coverage or both, and any number of printers/print queues can be provided (with different charge rates and printer parameters). Monochrome and CMYK colour printers are supported (with separate charge rates for both colour and black ink).
For all filters, processing can happen out-of-order, and you may prioritise jobs on the basis of size (jobs larger than a threshold can get lower priority or higher priority as desired) and jobs are billed in parallel / overlapping - jobs which finish billing first get printed first.
This is not necessarily the same as the order of arrival. Detailed stats are collected on a per-printer basis for job size, CPU time for each job, page count and ink/toner coverage, so you can analyse the usage patterns for your printers and predict when a cartridge will need to be replaced. It supports an optional user-supplied anything-to-postscript filter, so you can get properly billed for plain text, DVI files, image files, and so forth as well as PostScript.
Databases and configuration files may be stored on a centralised web server. This allows read-only access so that Unix (and conceivably Windows) clients could easily check quota, calculate quotes etc. remotely.
For fun, an additional filter is provided which allows users to deduct fixed amounts from their accounts (we use it to let students buy drinks and food from an unsecured laboratory fridge).
Enhancements:
- Finished support for per-user per-printer stats, tested that it works.
<<lessA simple print filter and accompanying daemon perform pre-printing billing, post-printing billing, print-accounting and print job quote generation. In addition, various utilities for administrators and users are provided - including programs to check your print quota and usage patterns, a web interface for both users and administrators and a command-line quote generator.
Charge rates may be specified on per-page, per-percent-coverage or both, and any number of printers/print queues can be provided (with different charge rates and printer parameters). Monochrome and CMYK colour printers are supported (with separate charge rates for both colour and black ink).
For all filters, processing can happen out-of-order, and you may prioritise jobs on the basis of size (jobs larger than a threshold can get lower priority or higher priority as desired) and jobs are billed in parallel / overlapping - jobs which finish billing first get printed first.
This is not necessarily the same as the order of arrival. Detailed stats are collected on a per-printer basis for job size, CPU time for each job, page count and ink/toner coverage, so you can analyse the usage patterns for your printers and predict when a cartridge will need to be replaced. It supports an optional user-supplied anything-to-postscript filter, so you can get properly billed for plain text, DVI files, image files, and so forth as well as PostScript.
Databases and configuration files may be stored on a centralised web server. This allows read-only access so that Unix (and conceivably Windows) clients could easily check quota, calculate quotes etc. remotely.
For fun, an additional filter is provided which allows users to deduct fixed amounts from their accounts (we use it to let students buy drinks and food from an unsecured laboratory fridge).
Enhancements:
- Finished support for per-user per-printer stats, tested that it works.
Download (0.11MB)
Added: 2005-11-21 License: GPL (GNU General Public License) Price:
1436 downloads
Imendio Planner 0.14.2
Planner is a project managment tool for the Gnome desktop, for planning, scheduling and tracking projects. more>>
Planner is a project managment tool for the Gnome desktop, for planning, scheduling and tracking projects.
Main features:
- Definition of tasks and subtasks, resources and resource groups
- Dependencies between tasks
- Display of the critical path
- Calendars with working/non-working time
- Gantt chart and resource usage overview
- HTML export of project plans
- Translated to nearly 20 languages, e.g. French, Spanish and Swedish
Enhancements:
- fix bug #353232 - patch to raise majic priority, fixing nautilus behavior when clicking on a planner file
- fix bug #368186 - patch to paint guide lines behind project start date rather than on top - contributed by Arthur Petitpierre
- added -Wno-return-type for compile with database enabled
- patch related to bug #353213 - added #ifdefs to allow compile with libgda 1 or 2, up to libgda-1.9.102
- Added Arabic - contributed by Djihed Afifi
- fix for bug 358415 crash in gantt view, contributed by Arthur Petitpierre and mdpoole trolius org.
<<lessMain features:
- Definition of tasks and subtasks, resources and resource groups
- Dependencies between tasks
- Display of the critical path
- Calendars with working/non-working time
- Gantt chart and resource usage overview
- HTML export of project plans
- Translated to nearly 20 languages, e.g. French, Spanish and Swedish
Enhancements:
- fix bug #353232 - patch to raise majic priority, fixing nautilus behavior when clicking on a planner file
- fix bug #368186 - patch to paint guide lines behind project start date rather than on top - contributed by Arthur Petitpierre
- added -Wno-return-type for compile with database enabled
- patch related to bug #353213 - added #ifdefs to allow compile with libgda 1 or 2, up to libgda-1.9.102
- Added Arabic - contributed by Djihed Afifi
- fix for bug 358415 crash in gantt view, contributed by Arthur Petitpierre and mdpoole trolius org.
Download (2.9MB)
Added: 2006-11-29 License: GPL (GNU General Public License) Price:
621 downloads
Palm::Progect::Converter::Text 2.0.4
Palm::Progect::Converter::Text is a Perl module to convert between Progect databases and Text files. more>>
Palm::Progect::Converter::Text is a Perl module to convert between Progect databases and Text files.
SYNOPSIS
my $converter = Palm::Progect::Converter->new(
format => Text,
# ... other args ...
);
$converter->load_records();
# ... do stuff with records
$converter->save_records();
This converts between Text files and Palm::Progect records and preferences.
The Text format used for import/export looks something like this:
[x] Level 1 Todo item
[10%] Child (progress)
. Child of Child (informational)
[80%] (31/12/2001) Progress item
[ ] Unticked action item
Here is a summary of the various types of records:
[ ] action type
[x] completed action type
< > action type with todo link
completed action type with todo link
[80%] progress type
[4/5] numeric type
. info type
[ ] [5] action type with priority
[ ] (15/7/2001) action type with date
[80%] [5] (15/7/2001) {category} progress type with priority and date and category
[80%] [5] (15/7/2001) {category} progress type with priority and date and category >
<<lessSYNOPSIS
my $converter = Palm::Progect::Converter->new(
format => Text,
# ... other args ...
);
$converter->load_records();
# ... do stuff with records
$converter->save_records();
This converts between Text files and Palm::Progect records and preferences.
The Text format used for import/export looks something like this:
[x] Level 1 Todo item
[10%] Child (progress)
. Child of Child (informational)
[80%] (31/12/2001) Progress item
[ ] Unticked action item
Here is a summary of the various types of records:
[ ] action type
[x] completed action type
< > action type with todo link
completed action type with todo link
[80%] progress type
[4/5] numeric type
. info type
[ ] [5] action type with priority
[ ] (15/7/2001) action type with date
[80%] [5] (15/7/2001) {category} progress type with priority and date and category
[80%] [5] (15/7/2001) {category} progress type with priority and date and category >
Download (0.040MB)
Added: 2006-08-23 License: Perl Artistic License Price:
1160 downloads
zOGI r581
zOGI is the ZideStore OpenGroupware Interface. more>>
zOGI project is the ZideStore OpenGroupware Interface.
zOGIs mission is to provide a clean and consistent XML-RPC API to the full suite of OpenGroupwares collaberation services.
Main features:
The initial focus is to support tasks and projects.
- These are the weakest sections of the older official XML-RPC.
- Surpasses functionality and performance of the older XML-RPC API.
- TODO Support BLOB retrieval (via URL?)
- TODO Support storing BLOBS (?)
The secondary focus is to support calendaring / scheduling functions,
- Conflicts are reported
- Access hints provided to client
- Permissions can be modified
- Participants can be modified
- Notes can be created, edited, and deleted
- TODO Still needs support for accept/decline
- TODO Still needs some proposal mechanism (very low priority)
The tertiary focus is to support contact management.
- As of r408 addresses and phone numbers can be put to the server.
- As of r411 contacts and enterprises can be created, edited, and deleted.
- As of r419 contacts and enterprise assignments are stored.
- TODO Assignment of contacts and enterprises to projects
The primary consumer of zOGI support is the Consonance groupware client.
<<lesszOGIs mission is to provide a clean and consistent XML-RPC API to the full suite of OpenGroupwares collaberation services.
Main features:
The initial focus is to support tasks and projects.
- These are the weakest sections of the older official XML-RPC.
- Surpasses functionality and performance of the older XML-RPC API.
- TODO Support BLOB retrieval (via URL?)
- TODO Support storing BLOBS (?)
The secondary focus is to support calendaring / scheduling functions,
- Conflicts are reported
- Access hints provided to client
- Permissions can be modified
- Participants can be modified
- Notes can be created, edited, and deleted
- TODO Still needs support for accept/decline
- TODO Still needs some proposal mechanism (very low priority)
The tertiary focus is to support contact management.
- As of r408 addresses and phone numbers can be put to the server.
- As of r411 contacts and enterprises can be created, edited, and deleted.
- As of r419 contacts and enterprise assignments are stored.
- TODO Assignment of contacts and enterprises to projects
The primary consumer of zOGI support is the Consonance groupware client.
Download (0.17MB)
Added: 2007-08-16 License: LGPL (GNU Lesser General Public License) Price:
799 downloads
vtkContainers 0.3
vtkContainers is a container library for VTK. more>>
vtkContainers is a container library for VTK providing list, deque, and vector sequence types; set, map, and hash map associative types; as well as stack, queue, and priority queue adaptor types.
All container implementions, except hash map, are wrappers around an internal C++ STL type. Similar to a vtkCollection, all containers register objects on insertion, unregister them on removal, are wrappable into other languages, and are covered by a unit testing suite. vtkContainers also provides many unique capabilities, higher performance, and support for object level locking.
Though the standard vtkCollection is an excellent general purpose container type that serves the internal needs of VTK very well, specialized containers are often needed for application-level support.
vtkContainers originated as the implementation of a simple stack class for use with parsers or transaction systems and a simple map class for accessing C++ objects by name. The current library grew from the desire to complete the concept by providing all applicable STL container types and their iterators.
<<lessAll container implementions, except hash map, are wrappers around an internal C++ STL type. Similar to a vtkCollection, all containers register objects on insertion, unregister them on removal, are wrappable into other languages, and are covered by a unit testing suite. vtkContainers also provides many unique capabilities, higher performance, and support for object level locking.
Though the standard vtkCollection is an excellent general purpose container type that serves the internal needs of VTK very well, specialized containers are often needed for application-level support.
vtkContainers originated as the implementation of a simple stack class for use with parsers or transaction systems and a simple map class for accessing C++ objects by name. The current library grew from the desire to complete the concept by providing all applicable STL container types and their iterators.
Download (0.25MB)
Added: 2005-07-15 License: GPL (GNU General Public License) Price:
1562 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 priority one 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
