Free electronic software for linux

ELOG is part of a family of applications known as weblogs. ELOG Electronic Web Logbook general purpose is :
1. to make it easy for people to put information online in a chronological fashion, in the form of short, time-stamped text messages ("entries") with optional HTML markup for presentation, and optional file attachments (images, archives, etc.)
2. to make it easy for other people to access this information through a Web interface, browse entries, search, download files, and optionally add, update, delete or comment on entries.
ELOG is a remarkable implementation of a weblog in at least two respects :
- its simplicity of use : you dont need to be a seasoned server operator and/or an experimented database administrator to run ELOG ; one executable file (under Unix or Windows), a simple configuration text file, and it works. No Web server or relational database required. It is also easy to translate the interface to the appropriate language for your users.
- its versatility : through its single configuration file, ELOG can be made to display an infinity of variants of the weblog concept. There are options for what to display, how to display it, what commands are available and to whom, access control, etc. Moreover, a single server can host several weblogs, and each weblog can be totally different from the rest.
Several logbooks can be served though a single ELOG server. Each logbook can use different attributes for its entries. The logbook can then be searched using these attributes. The right pane on the left image shows a search for all entries with attribute "Type" equal to "Configuration ", and the lower pane shows the search result. It is also possible to use full-text search in attributes and the entry body.
While logbook entries are usually displayed one entry per page, they can also be listed consecutively which makes it easy to produce a paper printout of a logbook.
Logbook pages can be edited or deleted. This feature can be turned off in the configuration file so that a logbook entries cannot be changed after being submitted.
An additional feature is the automatic generation of a notification email messages based on a certain type or category of a logbook entry.
Main features:
- Personal Logbooks. Personal notes can be written into ELOG and can then be retrieved from anywhere with a Web browser. This makes it handy for PC supporters who have to go around in companies or laboratories and dont want to carry their paper logbook with them. The same holds true for people traveling around a lot. The logbook database consists of plain ASCII files which can copied easily between different computers to have local access, for example on a notebook with no network connection.
- Shared Logbooks. Logbooks can be shared by several people, for reading and optionally for writing. This way workgroups can share and exchange information like in a (simplified) news group. This is supported by the Reply command in ELOG which creates "threads" of entries. Users can be notified by email when new entries are added to the logbook. Compared to that of a news server, the installation of ELOG is much simpler.
- Small Databases. Since arbitrary attributes can be defined for a logbook, it can be used as a small database with search facilities.
- Problem collections. A system can consist of two logbooks, in one of which users enter bugs or problems. If someone adds a problem, an email is automatically sent to the administrator, who can then copy the entry to the second logbook and add the solution to the problem. Users can then look up all fixed problems.
- Shift Logbooks. If the Allow delete and Allow edit flags are off, an entry cannot be modified once its been entered. This can be useful for shift logbooks for example in accelerator control rooms where each entry becomes a "document" with a time and author stamp. ELOG was originally developed as a shift logbook for the PiBeta and Muegamma particle experiments at PSI.
- File collections. Since files can be attached to ELOG entries, the system can be used to store and retrieve files. This can be used to store configuration files, which need to be accessible by several people over the web, or to store images. Since ELOG features an elaborate query facility, entries can be searched for by specifying several categories.
Enhancements:
- ELCode tags were improved with keyboard shortcuts, tables, and a date/time tag.
- Several small bugs were fixed.

Ryans Electronic Diary Sheet (aka RyansEDS) is a web-based Perl application which allows members of an organization (typically staff) to inform each other of their proposed whereabouts. The project is designed to be a simple shared calendaring application which does require complex (and often proprietary) client/server software.
Like its sister application Ryans In/Out Board it was written to fulfil a need at my employer Contact a Family. Staff needed a simple centralised way to let each other know when they would be out of the office rather than get into the complexities of sharing calendars.
The diary sheet works on a week by week basis and stores its data accordingly. A shell script (bacth file) is supplied which (when run as a scheduled event/cron job) will clear out data older that your chosen limit. Thus data storage is kept to a minimum. The diary sheet itself also has a feature will prevent users from going too far forward or backward.
Main features:
- Simple to use and administer
- Week to a screen view
- Users can be grouped into (colour coded) departments - current users department shown at top
- User aliases permit users to have friendly names on the diary sheet whilst logging in with more secure names 1
- No database required - uses simple text files for storage
- Tidies up after itself - deletes old storage files 2.
- No client application required - save for a web browser
- Easily configurable styles - all through the config file no HTML/CSS skills required.
- Allows additional comments/notes to be linked from the main diary sheet view
- Cross platform - runs on any browser and a range of server OSs.
- W3C compliant and fully accessible HTML output
- Suitable for small-medium installations (< 100 users)

OS-ELN is an Electronic Lab Notebook which you can freely download and use.
OS-ELN is deliberately simple; fully-fledged commercial ELNs are necessarily much more complex. As such, OS-ELN is a good teaching tool and a place for experimentation with ELN technology and concepts.
Users can sign up for an ELN, within which they can record their experiments, and you can attach files as part of an experiment. With knowledge of Zope, you can expand the system as you wish, for example to change the look & feel, to access relational databases, add other content to experiments, etc.
Version restrictions:
- You would be very unwise to use OS-ELN to document work that may lead to a patent claim (or defend against a patent infringement action) or for work that may be regulated (by, for example, the FDA). You should either buy a commerical ELN or use paper.

Electric VLSI Design System is a complete Electronic Design Automation (EDA) system that can handle many forms of circuit design, including:

* Custom IC layout
* Schematic Capture (digital and analog)
* Textual Languages such as VHDL and Verilog
* Programmable logic (FPGAs)
* ...and much more.

DContract project is a Java5 toolbox library for the management of digital contracts.
You can use this toolbox to put signatures on digital documents, and to verify signed documents. It also offers XML Advanced Electronic Signatures (XAdES) 1.3.2 support, up to XAdES-X-L.
Main features:
- Signing, co-signing and counter-signing of digital documents.
- Robust verification of digital signatures with the possibility to extend the verification framework with both document resolvers and key resolvers.
- The signature framework can be extended with self-defined signature aspects.
- XML Advanced Electronic Signatures (XAdES v1.3.2 2006-03) support: XAdES-BES, XAdES-EPES, XAdES-T, XAdES-C, XAdES-X, XAdES-X-L.
- Provides an easy-to-use abstraction level for creating legal signatures.
- Document repository to load/store XML DOM documents from/to various sources.
- Document schema validation with easy-to-use extendible schema catalog.
- Generation of RSA key pairs up to 2048 bit.
- Generation of self-signed X509 certificates, supporting the most common extensions.
- PKCS12 key repository management.
- Generic Smart Card support (e.g. eID cards).
- PEM exporting/importing of public keys, private keys, X509 certificates, and CSRs.
- X509 certificate OCSP support.
- TSP time-stamping support.
- OASIS Digital Signature Service (DSS) XML Timestamp support.
- Loading and storing of X509 certificates.
- MD5/SHA1 fingerprints.
Enhancements:
- This release includes a major refactoring of the XAdES signature aspects, resulting in performance improvements.
- Because of the refactoring it is now also possible to upgrade, for example, a XAdES-BES signature to XAdES-T, and it is also easier to query a verified signature for some XAdES attributes.
- The Web site also has a new section on the architecture of DContract and a code sample.
- Some interop tests were performed with IAIK XAdES, and the FAQ now offers a comparison between DContract and the IAIK XAdES library.

setpwc is a program that can set and list various settings of Philips (and compatibles) WebCams with the PWC chipset. If ioctls-commands fails, you have to upgrade to kernel 2.4.21 or more recent.
Main features:
- dump current settings
- set framerate
- store/restore settings in nonvolatile RAM
- restore factory settings
- set compression preference
- set automatic gain control
- set shutter speed
- red/blue-balance when white balance mode set to manual
- set automatic white balance mode speed and delay
- set led on- and off-time
- set electronic sharpness
- set backlight compensation
- set antiflicker mode
- set noise reduction mode
- set pan/tilt/zoom (Logitech QuickCam Orbit/Sphere)
Enhancements:
- Certain resolution and framerate combinations need to be set at the same time or else the PWC chipset refuses them.
- With some compilers, setpwc would end up in an infinite loop.
- The serial number of the webcam is now displayed.
- A man page was added.
- The -d option can now be anywhere in the command line.

LWP::UserAgent::iTMS_Client is a libwww-perl client for Apple iTunes music store.

SYNOPSIS

use LWP::UserAgent::iTMS_Client;

# search the Store
my $ua = LWP::UserAgent::iTMS_Client->new;

my $listings = $ua->search( song => apples );
foreach my $song (@{$listings}) { print $song->{songName} }

$listings = $ua->search(artist => Vangelis, song => long,
genre => Electronic);
foreach my $a (@{$results2}) {
foreach (sort keys %$a) { print "$_ => ", $a->{$_}, "n" }
}

# get my authorization keys
my $ua = new LWP::UserAgent::iTMS_Client(
account_type => apple,
user_id => name@email.org,
password => password,
);
$ua->retrieve_keys_from_iTMS;

This perl module implements a user agent which can interact with the Apple iTunes Music Store (iTMS). For example, this module could allow a perl program that would automatically get samples of new albums by a particular artist, or buy everything on a Top Ten list weekly.

LWP::UserAgent::iTMS_Client is a sub-class of LWP::UserAgent and implements the methods of UserAgent, but does so using Apples officially undocumented protocols. Because these protocols change with revisions to iTunes, the modules may occasionally lag Apples changes until this module, too, is updated.