Free difference between software for linux

Text::Diff3::DiffHeckel is a two-way diff plug-in.

SYNOPSIS

use Text::Diff3;
my $f = Text::Diff3::Factory->new;
my $p = $f->create_diff;
my $mytext = $f->create_text([ map{chomp;$_} < F0 > ]);
my $original = $f->create_text([ map{chomp;$_} < F1 > ]);
my $diff2 = $p->diff( $origial, $mytext );
$diff2->each(sub{
my( $r ) = @_;
print $r->as_string, "n";
if ( $r->type ne d ) {
print -, $original->as_string_at( $_ ) for $r->rangeB;
}
if ( $r->type ne a ) {
print +, $mytext->as_string_at( $_ ) for $r->rangeA;
}
});

ABSTRACT

This is a package for Text::Diff3 to compute difference sets between two text buffers based on the P. Heckels algorithm. Anyone may change this to an another diff or a its wrapper module by a your custom Factory instance.

Text::Diff3 needs a support of computing difference sets between two text buffers (diff). As the diff(1) command, the required diff module creates a list of tipples recorded an information set of a change type (such as a, c, or d) and a range of line numbers between two text buffers.

Since there are several algorithms and their implementations for the diff computation, Text::Diff3 makes a plan independent on any specific diff routine. It calls a pluggable diff processor instance specified in a factory commonly used in Text::Diff3. Anyone may change diff plug-in according to text properties.

For users convenience, Text::Diff3 includes small diff based on the P. Heckels algorithm. On the other hands, many other systems use the popular Least Common Sequence (LCS) algorithm. The merits for each algorithm are case by case. In authors experience, two algorithms generate almost same results for small local changes in the text. In some cases, such as moving blocks of lines, it happened quite differences in results.Text::Diff3::DiffHeckel is a two-way diff plug-in.

Gerber Viewer in short gerbv is a viewer for Gerber files. Gerber files are generated from PCB CAD system and sent to PCB manufacturers as basis for the manufacturing process. The standard supported by gerbv is RS-274X.

The basic difference between RS-274D (the old standard) and RS-274X is basically the addition of apertures in RS-274X. It might be possible to make an RS-274X file out of an RS-274D file and an aperture list.

gerbv also supports drill files. The format supported are known under names as NC-drill or Excellon. The format is a bit undefined and different EDA-vendors implement it different. But basically you need to have the tools definition in the file, then the parser is quite tolerant. The different holes are shown as dots in the (scaled) correct size.

The different layers of the PCB are separated into different files. gerbv can load all files at the same time and display them "on top of each other". You can independently turn them on and off.

Data::Diff is a data structure comparison module.

SYNOPSIS

use Data::Diff qw(diff);

# simple procedural interface to raw difference output
$out = diff( $a, $b );

# OO usage
$diff = Data::Diff->new( $a, $b );

$new = $diff->apply();
$changes = $diff->diff_a();

Data::Diff computes the differences between two abirtray complex data structures.

METHODS

Creation

new Data::Diff( $a, $b, $options )

Creates and retruns a new Data::Diff object with the differences between $a and $b.

Access

apply( $options )

Returns the result of applying one side over the other.

raw()

Returns the internal data structure that describes the differences at all levels within.

Functions

Diff( $a, $b, $options )

Compares the two arguments $a and $b and returns the raw comparison between the two.

EXPORT

Nothing by default but you can choose to export the non-OO function Diff().

java-diff is a set of Java classes which implement the longest common subsequences algorithm.

java-diff compares the elements in two arrays, returning a list of Difference objects, each of which describes an addition, deletion, or change between the two arrays.

Lineox Enterprise Linux distribution is based on source RPM packages from which Red Hat Enterprise Linux is compiled. Lineox Enterprise Linux contains all programs included in various Red Hat Enterprise Linux variations (Advanced Server (AS), Entry/Mid Server (ES), and Workstation (WS)).
It also contains programs included in separately sold Red Hat Cluster Suite and Red Hat Developer Suite. Lineox has removed and replaced all files of Red Hat Enterprise Linux which have restrictive copyright by Red Hat, Inc. Lineox has also tried to remove all user-visible references to Red Hat in Lineox Enterprise Linux.
The most notable difference between Lineox Enterprise Linux and Red Hat Enterprise Linux is the support options provided by Red Hat, Inc. Lineox, Inc. does not provide any support for Lineox Enterprise Linux with the base product.
Lineox, Inc. however plans to provide binary package updates for Lineox Enterprise Linux as long as Red Hat, Inc. provides updates for Red Hat Enterprise Linux in source package format.
Lineox has an automated system running on a cluster which builds new binary rpm packages as soon as new source code is available. New rpm packages are usually available in less than 12 hours after source code release.
After that Lineox builds Always Current Lineox Enterprise Linux disks automatically, but because of the time it takes to transfer the disk images to our web server, they are available from 2 to 12 hours after we release new packages.
Isnt Always Current Lineox Enterprise Linux untested or unreliable if it is released so often? Not really. We dont rebuild the installation environment, we just replace the installable packages with new ones.
You can even use same boot floppies or other boot media created for Lineox Enterprise Linux 4.0 to boot Always Current series Lineox Enterprise Linux. So Always Current Lineox Enterprise Linux is as tested and reliable as a system installed from "base release" and updated later. The only difference really is the work and time saved and the higher security right from the start.
Enhancements:
- Always Current Lineox Enterprise Linux 4.096 with Update 4 available. In the version 4.096 the installation environment is rebuilt, so it offers better hardware support during the installation. See the release notes for full information. The x86_64 release requires either AMD Opteron or Athlon64 CPU based computer. Some new Intel Xeon and Pentium IV processors with EM64T (Extended Memory 64 Technology) will also be able to run this version.

Uncle Unc is an application that provides an integrated view of structured data sources. Using a very flexible and powerful representation model, many services can be represented in Uncle Unc.
Uncle Unc is a framework for network data-sharing, enabling remote administration and access to a range of services from a range of clients, using a simple text-based protocol that isnt tied to any platform, operating system or programming language.
Uncle Unc is a toolkit for agile development of interfaces to network services that are easy to maintain, and will grow as the service grows.
At the heart of Uncle Unc is a small generic specification of what a information-based network service might look like. This specification is very generic, and free of reference to any specific technologies or buzz-words.
It is based on the simple observation that much of the time we spend with computers is spent organising and categorising data, pushing data from one box to another, and invoking actions on that data. Most user interfaces attempt to represent this activity for a single type of data, such as a mailbox, a filesystem, a relational database, a network of computers or a music collection. Uncle Unc provides a framework that makes it easy to interact with any data source.
If you feel constrained by the user interfaces you are using (or developing!), or frustrated by having to use a poorly-designed user interface for a particular task, then Uncle Unc may turn out to be a good friend!
Uncle Unc is based on the simple observation that much of the time we spend with computers is spent organising and categorising data, pushing data from one box to another, and invoking actions on that data. Arguably, we ought to spend less time doing this sort of thing and get out into the fresh air more! At the very least, we should be able to do it efficiently and effectively. The more energy we expend on wrestling with the user interface in order to get these low-level jobs done, the less we will have to deal with the high-level problem-solving tasks that can make the difference between work and gainful productivity.
Lets call this low-level categorisation activity as stamp collecting, at the risk of offending philatelists. Most user interfaces attempt to represent stamp-collecting activities for a single type of data, such as a mailbox, a filesystem, a relational database, a network of computers or a music collection. Uncle Unc provides a framework that makes it easy to interact with any data source at this level.By doing it once, we can take the time and effort to do it well, so that it doesnt intrude on the users activities unduly.
Computing is a rapidly changing field, full of powerful new uses for computers such as digital multimedia, realistic graphics and artificial intelligence. And yet much of the time that we use computers, we are performing essentially the same stamp-collecting tasks that we did twenty years ago.
Even when dealing with the new high-powered uses of computers, this is the case. How much of a digital music player programs code is devoted to playing the music, compared to sorting through and organising album playtracks (and which does the user spend most of their time doing?). 3D graphics and neural network designer applications have a similar requirement to present their internal information in a useful way to the end-user.
There is currently little cohesion in the way that software developers address these tasks. Each application codes its own listings widgets. Some have sortable fields. Some have filters. Some can divide the results into pages. Most do some things quite well, some badly, and some not at all. Most will present the interface in a single medium - as a desktop application, or a HTML web interface, a java applet, a flash movie, or whatever. Most will run on a limited number of platforms, Operating Systems or browsers.
This situation restricts the exposure of the application behind the interface, by tying it to that interface. It also limits the exposure of a front-end to a single application. The proverbial wheel is frequently re-invented, and often under tight pressures of time and resources, with less than desirable results.
Uncle Unc is an attempt to develop a generic component framework that allows many different structured data-sorting tasks to be harnessed in a manageable way. A small central set of open interfaces serve as a broker between any client and any service, giving the owners of the network the maximum degree of flexibility. In the language of Desiogn Patterns, Uncle Unc implements a bridge pattern between list-like clients and list-like servers.
Main features:
- A common set of interfaces are provided in the java programming language, and the framework has been developed to make it easy to expose any java object as an Uncle Unc service, and to control what gets exposed and how.
- Network communication between clients and severs is done using XML, opening the door to non-java programs. Over time, we may develop more detailed frameworks for interoperability using PHP, Python, .NET or other popular programming languages.
- Clients and servers are decoupled. That is, a client that can understand one service can understand any service. A service that can talk to one client can talk to any client. This results in a very efficient path to network-enabling a service across a range of platforms, or allowing access to network resources from a new type of client.
- This increases the incentive for developers to provide new capabilities to the system. A widget set that provides a better view of a list of items does so for files, mail, log file entries, databases, newsgroups, etc. without any reworking. Similarly, a new backend service that delivers an Uncle Unc interface will enjoy exposure on all Uncle Unc client platforms (with plans afoot to cover web front-ends, smartphones, and scripting language access as well as the desktop clients).
- The content of the user interface layer is directly defined by the properties and methods of the back-end service. As the back-end service evolves, there is no need to recode the GUI (or other UI), simplky the skeleton used to support it. Even this can be automatically generated from the back-end systems objects. Agile development is supported and encouraged in this way.
- Defining the UI structure directly from the back-end has the further advantage of providing a good fit between the two. A hand-coded UI may omit certain capabilities of the back-end, because they are hard to express using an ad-hoc composition of low-level widgets such as textboxes, tick boxes and drop-down lists.
- The UI is built around an open-ended description of the structure of the service that one is interacting with, rather than expressing a set of fixed pathways of interaction. As such, it supports a flexible, problem-solving approach by the end-user, rather than a purely mechanistic one.

StringParser_BBCode class provides the possibility to parse strings with BB-Codes and convert them to e.g. HTML code.
BBCode is a kind of markup "language" with which one may structure and format text. It is similar to HTML but it utilizes square braces instead of angle brackets.
Another difference between BBCode and HTML is that when using BBCode invalid code is ignored whereas the validity of the code is important when using HTML.
Enhancements:
- Several bugfixes were made.
- Support was added for parsing [code=foo attr=bar].
- A callback function may be called again on close tag occurrence.
- A processing type "callback_replace?" was added which exhibits the opposite behavior of "usecontent?".