Free whole new software for linux

wyoFiler shows all directories and files of a base directory in one tree window. Directories and files can be selected and manipulated across the whole hierarchy, from the base directory all the way down to the lowest level.

Selected items may be in different directories on different levels. The base directory itself may be switched to any other convenient directory.

All file manipulations are done in the background, so multiple commands are possible simultaneously.

The filer can display multiple base directories in tabbed notebook pages or separate top level windows.

GoldSeeker provides a small formatted data extraction application.
It was built to extract formatted data from HTML files, but can be used with all kind of files.
Its behaviour is defined by a rule-based configuration file. It can process files on the local server, or directly get web pages via http://.
GoldSeeker is still in development, its neither whole nor stable; nevertheless it can already be used for simple extractions.
Use
Edit GSParser.php and set your mysql connection parameters (if you dont want to use database export just comment out the "dbConnect();" line). Check that the include paths are correct, and run sample.php.
GS parameters:
include(GSparser.php);
$gs = new GSParser(config file path, data source path, data source type);
$gs->parse();
?>
Data source type: singleFile for... well, a single file; listOfFiles for an array of filenames; directory for a whole directory. Source path : file path or array of file paths.
Enhancements:
- Corrected some linkVariableValues bugs
- Optional (non-mandatory) variables support
- Added a set of unit tests to avoid further regressions (they also serve as a set of samples)

file*HANDLER project is primarily a Perl script which coordinates some free media conversion packages (cited later) with a PostgreSQL back end accessing server to index and serve binary and text files direct from the database. A simple CGI file with embedded AJAX makes calls to this server which is also constantly looking for other alive f*H servers on the Internet.
Since the server caches media into the SQL database on demand, as the network grows, the network improves.
Its gridded directory sharing/browsing/searching with streaming audio/video as well as flat text/doc/pdf/image display for everyone. Its written with a few hooks for tags that would be included in your actual front page so that the UI is discard-able -- anyone can quickly rewrite a whole new [GT]UI without having to worry about the syntax of the newest version of dojo.licio.r or whatever.
If you wanted to ignore the JS/HTML/CSS hooks then you can easily use the system to make direct requests that just return lists formatted as HTML table-bodies. In other words, the markup IS the markup.
As such, Ive whipped up a Dojo 0.2 Widget that coordinates the serving backend with a UI so anyone can embed f*H functionality anywhere, or easily customize a provided default page.
A file*HANDLER server is really a few constituent parts Ive tied up for you (top down):
- A local web page providing the UI(served by an HTTP server of your choice) that is generated by a cgi script with embedded AJAX.
- A secondary portion of the same CGI script, acting as middle-ware, which communicates, via AJAX, with the local front page to reconcile asynchronous JavaScript requests with the file*HANDLER sub-network back-end.
- An always-on network server written in PERL that serves to the front and end communicates laterally with everyone elses file*HANDLER back-end PERL server additionally, it manages indexing of content directories you choose to serve.
- A PostgreSQL database that is accessed only via internal PERL routines called from your front page.
So for example, a remote user comes to your site. First, not only can they browse and search your files, but they can also browse and search the files of anyone else hosting a file*HANDLER server that your local server knows about. (file*HANDLER identifies other servers on the network automatically). The user can now read/view/listen/watch by stream any content they find from whomevers server. Theres no download, so theres so actual sharing, just direct streaming to the users browser.

WebGrab is a tool that acts as a CGI proxy. It simulates a Web browser and grabs data from external programs, and can exchange individual words or whole blocks.

The project can be run standalone or in conjunction with phpCMS.

wsdebug is a debugger for the more or less famous whitespace programming language, coming along with a rather fast interpreter (wsi).

Most programming languages like C or Perl do not care for white space characters (like tab, space or newline/linefeed). The whitespace programming language works just the other way round, dont care for any character but those white space ones.

On the whole its just another geeky language like Brainfuck and others, however more adicting.

If youve written a whole lot of instructions youll probably reach the point, where you get lost. Then just put your script into wsdebug and step through your bunch of whitespace instructions and watch how each command manipulates the stack (or heap).

dtoGe project is a java source generation tool that can ease the development of multi-tier systems by offering a reliable solution to obtain the data transfer objects out of the domain model objects without hand-writting additional code.

Using a simple set of javadoc tags, dtoGen™ provides the possibility to define the whole set of data transfer objects used by your system.

LinuxMCE is a free, open source add-on to Ubuntu including a 10 UI, complete whole-house media solution with pvr + distributed media, and the most advanced smarthome solution available. The project is stable, easy to use, and requires no knowledge of Linux and only basic computer skills.
Enhancements:
- LinuxMCE Version 1.1 for Kubuntu Feisty represents a significant change over 1.0. The code in LinuxMCE 1.0 was already quite stable, however, many users reported installation issues, too many scripts inherited from Pluto that took over the conf files, a kludgey integration with Ubuntu, and incomplete integration with MythTV. All these are addressed in the new 1.1.

Whole Platform project is a technology for engineering the production of software.
We think that programming is an activity concerning the development of domain languages; so, we provide a platform for developing new languages, manipulating them using domain notations and transforming them to executable code.
Using the Whole Platform, the problem domain experts can work together with the programming experts for the development of software products.
The Whole Platform includes a modeling framework, a generative system, a family of languages, and domain editors integrated with the Eclipse platform.
The languages boundled with the Platform include popular languages such as Java and XML together with some new domain languages used for modeling the structure, the behavior, the persistence and the notations of a language.
Main features:
Architecture
- Extensible. The architecture provides an API for language extension. You can add/remove languages, notations, persistences and operations.
- Java frameworks and domain languages. All the expressive power of the Whole Platform is available as standard Java frameworks. Part of this expressive power is also available through a family of domain languages.
- Generative. The Whole modeling languages generate code on top of the Java frameworks. Together with the extensive use of wellknown Design Patterns in frameworks, the code generated feels hand written.
Metaprogramming
- Native support. Each Whole language can be used at template level and, if it has an executable semantics, it can be also used at base or host level.
- Staging support for visitors. Staging support is available for behavior defined using the visitors traversal framework.
- Mixing template languages. A single artifacts generator can use multiple template languages.
Persistence
- Stream based persistence. The Persistence syntax of a model is pluggable. Both stream based and model based persistence methods (kits) are supported. The streaming API looks like the building events produced by the Director participant of the Builder Design Pattern.
- Java code and XML default serializers. The standard persistence kits are based on a streaming API and are available in two flavor: Java and XML. The Java code, when executed, fires a stream of building events.
- Stream based behavior. Model behavior can be defined directly on top of the streaming API without prior building of the model.
- Multiple languages support. Programs written using multiple languages are supported even on a single source file.
- Versioning support. Facilities for versioning metamodels and migrate/import existing models are provided.
Editing
- GEF based editors for Eclipse. Model based visual editors for Eclipse can be added to a Whole language even using separate plugins.
- Rich graphical user interfaces. Multiple kinds of notations are supported including grammar layouts for text oriented languages, math layout for mathematical expressions, tree and graph layouts for diagram oriented languages.
- Multiple notations for a language. For each language multiple notations can be defined and deployed in a modular way. The notation can be changed while editing.
- Mixing notations. Multiple notations can be mixed even on a single editor view. This feature is especially useful for metaprogramming using concrete syntaxes for template languages.