Free download machine 0.2 software for linux

Download Machine provides a noninteractive, nongraphical, pure Java batch file downloader.
Download Machine is pure Java daemon that watches queue files for changes. If a new entry is available, DM will download it. Queue files are just URL lists. DM fully supports the HTTP, FSP, and FTP protocols.
Main features:
- Design goals
- Non graphical
- Non interactive
- Relieable downloads
- Queued downloads
- Portability (uses Java)
- Simple to use
- Resume interrupted downloads
- Transports
- Support for HTTP/1.1 protocol
- Support for HTTP/1.0 protocol
- Support for FTP protocol
- Support for FSP protocol
- Custom headers
- Fake user-agent header
- Custom referer header, configurable per URL
- Custom cookie header, configurable per URL
- Other features
- Can check in different directories if we already have downloaded file (configurable by wildcard)
- Can move downloaded file to special directory (configurable by wildcard)

Download Manager Tweak provides a modification of the Firefox download manager that changes its appearance.
The Download Manager Tweak extension streamlines the current Firefox download manager. The extension allows the Firefox download manager to be opened in a separate window, the sidebar, or a tab.
The extension also modifies the default appearance of the download manager to make it more concise and intuitive.
Main features:
- The download manager (DM) can now be opened in a separate window, the sidebar, or a tab.
- The toolbar can be positioned on the top or bottom of the DM window.
- The user can select which buttons should on the toolbar.
- The skin support has been fixed.
- Other minor options.
- New: Rudimentary download queue -- highly experimental
- German (de-DE) translation (thanks to Hendrik Gebhardt)
- Spanish (es-ES) translation (thanks to Carlos)
- Dutch (nl-NL) translation (thanks to Pascal De Vuyst)
- Russian (ru-RU) translation (thanks to Nik Skyfly)
- Chinese (zh-TW) translation (thanks to Kuo Wen-Hsing)
- French (fr-FR) translation (thanks to PhiNux and The_Sims)
- Polish (pl-PL) translation (thanks to cambridge)
- Swedish (sv-SV) translation (thanks to Carlos Murakami)
- Italian (it-IT) translation (thanks to Giuliano Masseroni)
- New: Japanese (ja-JP) translation (thanks to Premier)

Wayback Machine is an open source java implementation of the The Internet Archive Wayback Machine.
The current production version of the Wayback Machine is implemented in perl, and lacks in maintainability and extensibility. Also, the code is not open source. Primary motivation for the new version is to address these three issues, enabling public distribution of the application, and easy experimentation with new features and access technologies.
The current Java version of the Wayback Machine supports two access, or replay modes of operation: "Archival Url" mode and "Proxy" mode.
Archival URL mode provides a user experience very close to the current production Wayback Machine. All query and replay access requests can be expressed as URLs.
In Archival Url replay mode, HTML documents are delivered with additional Javascript embedded in the page. This Javascript alters the document within the browser, attempting to make links and embedded content refer back to the Wayback Machine by rewriting them as Archival URLs.
Proxy URL mode allows replaying of archived documents within a client browser by configuring the browser to proxy all HTTP requests through the Wayback Machine. This has the strong advantage that no Javascript page markup is required to coerce the client browser to request additional URLs and embedded content from the Wayback Machine -- content just works as-is. One major disadvantage of this mode is that there is no way to forward temporal information with each replay request. Because of this limitation, only the most recently archived version of any resource is accessible thru the Wayback Machine in proxy Url mode.
Another limitation of the Proxy URL mode is that it requires special configuration of the client web browser to access the Wayback Service. This browser configuration is not complex, but it means that content cannot be accessed as a global URL.
See the User Manual to learn more about access modes.
The current Java version is intended to operate as a standalone webapp, maintaining an index on the machine hosting the webapp. This index contains records of the resources within a set of ARC files, which are also assumed to be stored on the same machine hosting the webapp.
This software includes the capability to scan for ARC files in a specified location, and to automatically index and serve content in newly discovered ARC files as they appear. Directing the Wayback Machine to look for ARC files in the directory where an instance of the Heritrix web crawler is writing ARC output should provide the capability to browse content archived by Heritrix as it is crawled.
Future versions of this software may integrate more tightly with the Heritrix web crawler application.
Enhancements:
- A sorted CDX flat file ResourceIndex implementation was added, allowing for much larger data sets.
- Support for ArchivalUrl Date-Range requests was added.
- Character set detection was improved so pages are not mangled when server side modification occurs.
- Several new command-line tools were added for generating and updating each ResourceIndex type.
- Indexing and merging processing were separated into different threads.
- Bugfixes were made to allow integration with NutchWax full-text searching.

Download Slave provides a remote-controlled download slave.
The Download Slave is a very flexible script which is controlled via eMail and stores files requested for downloading on the servers harddisk or sends them via eMail to the user who asked for them. Users are identified by their eMail address and a personal password, so only authorized users can use the service.
Main features:
- users identified by their eMail address and a personal password
- a real multi user mode, so each user has his own home and can have his own CD-R burnt.
- corporate mode: all downloaded files are stored in one base directory
- every download is logged
- user gets a status mail about his download request
- slave is controlled via commands in the eMail message body
- download things onto the servers HDD... (also more than one URL per eMail request possible...)
- show already downloaded files (that are on the servers HDD)
- change own password
- download files onto the servers HDD and send them via eMail to you (split into parts of 1MB). The last one of such a multi part eMail has an attached script to rejoin the large file...
- online help
- an index file which holds who downloaded what and when and a short description given by the downloading user in his mail subject

Virtual Drum Machine is a simple drum machine.
It works for little endian/linux kind of machines. You may let it work on others machines, but you probably will get troubles with it.
You definitely need oss (or maybe alsa) for sound output, and a posix-like operating system. To let it work on a big endian machine should be painful.
You write a rhythm, then you compile it, then you are able to play it to your sound card or save it to a file.
The Virtual Drum Machine is made of
- the Rhythm Compiler,
- the runtime library.
The Virtual Drum Machine is in the public domain. Who needs a license? money makers? Protection against robbery? let me laugh... Read any text of law, you will see where the robbers reside.
A simple file would look like :
void main_rhythm(void)
{
tempo = 120;
- a
. b
. b
.
- a
.b
- a
.
. b
. b
- a c
. b
}
Install:
Do a "./configure" in the drums directory, then "make", then "make install", it should be alright. You can listen to some examples in the examples/ directory.
Who yo use it?
Write a rhythm. Compile it with "rc". Run the produced program. You are done.
See the examples/ directory to get the point.
When you run an example, try "-h" to get the available options.
It should be self-explanatory.
The rhythm compiler has several options. By running "rc --help", all should be clear.
Technical Details:
The compiler will parse the input file line by line.
If a line starts with "*" or "." (not counting leading white spaces), the whole line is seen as a rhythm line, and is transformed into C code. If not, it is passed as is to the C file.
Beware! You MUST NOT start any C code line by "*" or "."!
You can create as much functions as you want, write any C code you want. But remember that a line starting by "*" or "." is seen as a rhythm line and is translated by "rc" into C code.
You must provide a "void main_rhythm(void)" function, that will be called by the library. It is the starting point of your rhythm. It can be "void main_rhythm(int argc, char *argv[])" too, with common meaning for those parameters (non-C coders will have trouble with the Virtual Drum Machine).
You can change the tempo (ex. "tempo=100;") or the volume (ex "vol=0.4;") at any time. Each sample comes with its own volume and panning (ex. "a.vol = 0.1;" "a.pan=-0.8;"). Volumes range from 0 to what you want. 1 is for the normal volume. Panning ranges from -1 (left) to 1 (right). 0 is center. All values are double. You can use "volume" instead of "vol", and "panning" instead of "pan". There is no global panning, if you want all left, set all samples to left.
To run in stereo mode, dont forget "-s" when running the generated program. It is mono by default.
You absolutely need to compile and run the examples, and read them to get the point out of it!
The "rc.conf" file contains configuration informations. You specify the sample by "sample" followed by its name (the one you will use in your rhythm files), then the file that will be played. The name of the sample must start by a letter, followed by letters and/or numbers (it must be a valid C identifier, without "_" though). The configuration file contains the install directory, used by "rc" to compile your rhythms. Take a look at the one that is provided to see how to use it.
The sound files are simple wav files. They all should be of the same rate, which can be specified to the generated program, using the "-f" option (44100 is the default). (The library only handles very basic wav files, if yours dont work, you probably will have to modify the library for the program to handle it.)
When you add a sample, you must modify "rc.conf" for the changes to appear. The samples are hard-linked to the produced program, so if you change "sample a /some/dir/file1.wav" by "sample a /one/other/dir/file2.wav" in the configuration file, the previously generated programs will still use "/some/dir/file1.wav". You will have to compile them again to take the changes into account.
Enhancements:
- The code has been modified to let gcc 4 compile it.

PDF Download is an extension which allows you to choose what to do with a PDF file on a website.

Allows to choose if you want to view a PDF file inside the browser (as PDF or HTML), if you want to view it outside Firefox with your default or custom PDF reader, or if you want to download it!

Download Youtube video is a Konqueror service menu to download and encode youtube videos.
This is a hack of another service menu that stoped working (at least for me): http://www.kde-apps.org/content/show.php?content=37509
Main features:
- Download videos with the KDE file copy dialog instead of using KGet
- Automatically encode videos with mencoder, or just download
You can use ffmpeg too, just comment out the right lines in the python file, Im unable to encode some videos with ffmpeg, so mencoder is the default

Download Statusbar is a Firefox extension that allows you to manage downloads from the statusbar.
View and manage downloads from a tidy statusbar - without the download window getting in the way of your web browsing.
Main features:
- Auto-hides when not in use
- Single-click pause and resume
- Pause all, Resume all, Cancel all, and Remove all finished - available from the context menu of the bar itself
- Run a completed file with a double click on its finished box. Open containing folder, remove, and rename from the context menu
- In-line view of percent done, speed in KB/sec, KB downloaded so far, and remaining time, can be customized in the options.
- Updating tooltip provides a more detailed view of the current download, including source, destination, size of the download and the remaining time
- Option to automatically clear files after a specified number of seconds
- Copy source URL from the context menu
- Stop downloads and save them for the next browser session.
- Delete a file from your system from the context menu
- Localized strings for translation
- Download history can be viewed and configured to only keep the last # download items
- Option to start virus scanner when a download completes
- On browser close, option to continue downloads in download manager