Free can be seen software for linux

Logical Desktop is a desktop environment. A "desktop environment" is a program that allows you to do many different things with your computer, but in a consistent way. Desktop environments can be seen as a "dogma" of how things should be done, and how they should look and feel.

Examples of desktop environments are KDE, Gnome, the Windows interface, etc.

In Logical Desktop, like in all desktop environments, you work by composing actions made of one verb and one or more objects (e.g. "Print" is the verb, and the objects are the printer, the files to print, and the program used for printing).

Logical Desktop is how you specify those things: 1) in any order 2) with automatic hiding of the things that dont make sense.

1. In any order: Logical Desktop enables you to specify your action with many possible styles of interaction (file-oriented, task-oriented, program-oriented, device-oriented). Logical Desktop can do that because it treats verbs and objects with complete symmetry and uniformity: you can select both verbs and objects, and in any order.

2. With automatic hiding: Logical Desktop is more intelligent than traditional systems because it hides the unnecessary things while you are composing the action. More precisely, Logical Desktop hides those verbs/files/devices/programs that make no sense with the current selection.
Combining this with the previous point (that you can select anything in any order), we obtain a very powerful mechanism: if you select a verb first, the objects that dont make sense with it are hidden; if you select an object first, the verbs that dont make sense with it are hidden.

Hugin is a panorama tools GUI.

Goal: an easy to use cross-platform GUI for Panorama Tools.

With hugin you can assemble a mosiac of photographs into a complete immersive panorama, stitch any series of overlapping pictures and much more.

Main Window

This window consists of a toolbar that provides quick access to important functions. It also contains the Images, Lens, Control Point, Optimizer and Panorama Tab, which will be explained below.

Images Tab

Images can either be added with the Add button, or via drag and drop. To change the orientation of one or more images, select them in the list on the left. The image will be show in the preview area, and its orientation (yaw, pitch and roll values) can be edited on the left.

It is possible to select multiple images at the same time. Changes in orientation will be applied to all selected images

Lens Tab

The lens tab looks a lot like the Images tab, except that the lens settings can be edited here. As in the Images Tab, multiselection can be used to change the parameters for multiple images.

Currently only one lens is supported. The idea is that the Lens describes the process that was used to create the image. The most important parameters are the Lens type and the HFOV (Horizontal Field of View). Hugin will read the EXIF information in jpg files created by digital cameras, so usually it is filled out correctly.

Photographers do not use a HFOV in degrees, but the focal length. The focal length can be entered and it will be converted to HFOV in degrees, like the panorama tool require it. The focal length entered is taken to be for 35 mm film cameras.

Usually images are more or less distorted. This can be seen especially if there are long straight lines close to the image border, which are usually not completely straight but bent a little. The a b and c parameters are used to remove that distortion. They are applied radially from the image center, which can be moved by changing the d and e parameters.

During image capture, it is possible that the parameters vary, that is are not the same for each image. This can have many reasons, one of the could be a scanner that cuts a way a few pixel more at one side than the other. Other parameters stay the same, like usually the a,b and c parameters (if the zoom and focus for the images is the same).

The inherit checkmark means that this parameter doesnt vary between the images that were captures with that lens setting. If a parameter is inheritied it is forced to be the same for all images. When inherited parameters are optimized they are kept the same for all images, whereas parameters that are not inherited can get values specific for a single picture.

Control Point Tab

Control Points are probably the most important thing when using panorama tools. The Tab consists of two image displays and tab bars to switch images to be editied. The bottom contains a list view where Points can be selected and some fields to edit a selected point. Points can also be selected by clicking or dragging on them in the images. It is possible to zoom out to show the full image.

Adding a control point works by clicking into one image to select a point and then into the other image. If auto add is not set, the points can be moved by clicking at some other place in the images. They are added to the list of control points by pressing the right mouse button. If you press the right mouse button when only one point is slected, the point selection will be aborted. auto add adds the control point as soon as both points have been specified.

Control point creation is influenced by the following checkboxes:

auto fine tune hugin helps you to find the second point by looking for it in a search region (shown by a rectange around the cursor). This might not always work, but usually is reliable, if the image distortions are not too big. Try and play with it.
auto add A control point is automatically added when both points are know. You wont have time to refine the selection before adding the point.
auto estimate Tries to estimate the position of the second point by estimating the translation between the two images. This is very crude and probably only works for single row panoramas created from rectilinear images.

All these flags can be combined. I typically use auto fine tune and auto estimate at the same time. Then hugin usually automatically selects the second point correctly. Well for single row panos that is...

The images are zoomed out, the first click zooms to a temporary 100% view to give you the chance to refine your selection. Note that only the second click will trigger the auto estimate.

The Fine Tune button can be used to find a better position for the point in the right image for already selected point. Contrary to auto fine tune it only looks in a very small area around the point. This function is especially useful if you moved both points by hand, but want to have fine tuned control points.

Press the middle mouse button to pan the image. If you press shift key while paning, both images will move.

This window supports some keyboard shortcuts:

a add a new point that has been selected in both images, and the auto add is switched off.
cursor keys scroll image under the mouse cursor
shift + cursor keys scroll both images at the same time
f fine tune currently selected control point pair. Same as the Fine Tune button
Del Remove currently selected control point.
0 Zoom out to full view.
1 100% view.
Mouse function
Function
control key + mouse movement Scroll image under cursor
shift key + mouse movement Scroll both images
left button Use left mouse button to select new points or drag existing points.
right mouse button Add control point, if auto add is switched off
middle mouse button Scroll image under cursor
shift + middle mouse button Scroll both images

Optimizer Tab

The optimizer moves the images into the right position, so that they can be assembled into a hopefully seamless panorama.

To select what the optimiser should try to estimate, use the Optimize combo box, then click the Optimize Button. If you select the "custom" setting, you can change

Pano Panel

Options concerning the output panorama can be set here.

The Noble Ape Simulation has been developed (as the Nervana Simulation) since 1996 and is a biological simulation software. The aim of the simulation is to create a detailed biological environment and a cognitive simulation.
The Simulation is intended as a palette for open source cross-platform development. It provides a stable means of simulating large-scale environments and cognitive processes on Windows, Mac and Linux.
The Simulation includes a detailed scripting language for user-implemented movement and cognitive-process development.
Enhancements:
- This release fixes a bug in displaying only the seen Noble Apes, and has code simplification towards OpenGL implementation.

conn-close gives us possibility to get rid of entries in ip_conntrack about ESTABLISHED TCP connections that goes through our server.

conn-close script uses hping2 to send spoofed RST packets which will fool conntrack and cause specified connections to be considered by conntrack as closed (now these connections will be in ip_conntrack in CLOSE state), even though RST packets will be more likely discarded by destination host.

Information about connections is read of course from /proc/net/ip_conntrack.

Idea was taken from script seen somewhere on the internet.

JavaDesktopEngines aim is to produce a piece of software that is at the same time:
Shared virtual machine
It allows to launch different java programs inside the same VM. The VM will always be alive, so no more startup overhead and less memory used.
It uses our JDSVM(Java Desktop Shared Virtual Machine), which in turn is based on Javagroups great Echidna Project
Xml Rpc local server
This way it is possible for programs, even written in languages different from java, to access "services" exposed by the engine.
Plugin host
It has been built with a pluggable architecture in mind, so that it is possible to develop new "services" for the engine.
Linux/Windows service (next release)
It is run as a service, so that its "services" will always be available for other programs.
For those of us who make heavy use of java tools its always been quite frustrating to have to open lots of resource eager VMs just to launch very useful but simple programs. Moreover, VM starting for simple utilities is a real waste of time.
Weve all appreciated the difference when launching a compilation from inside an IDE. In this case javac is launched as a process inside an already active VM, and the difference is evident.
JDE in the beginning was born to try to address these problems. Having an always active VM where it is possible to launch processes in, means faster process start and less resources used. A lot of time is saved by from not loading again and again the VM.
Theres nothing new in this. Some very good related projects are alive and kicking on the net, some of them focusing on a complete Java desktop enviroment, some on just a shared VM. JDE positions itself a bit differently, as it can be seen as a java engine exposing pluggable services (shared VM being just one of these).
There are several approaches to implementing a shared VM, all of them with pros and cons. Weve chosen to use the great code from the Echidna Project for now.
The entrypoint of JDE is an XML-RPC server accepting calls for services. Everything needed from JDE can be obtained by making a call to it.
The main service exposed by JDE is obviously the java process launching one. By making a call, it is possible to launch a java process insisde the VM. Having an XML-RPC server allows us to use any language with xmlrpc capabilities to launch java programs. The package includes a simple python script, that can be easily used as launcher (see our simple tutorial for details).
Included is also a "Manager", a simple swing application with active process listing and process launching capabilities.
Hopefully, this one will evolve as far as there will be more services in JDE to be the reference manager for the engine.
Included plugins:
1) Java process Launcher. The one this project was started for. You can launch java processes inside the living VM.
2) Scripting engine. Via a simple xmlrpc call you can launch a script on the engine and get back results. The nice thing, as usual, is that being xmlrpc based, you can use it as a service called by anything written in any language. Currently supported scripting language is BeanShell. More will be available soon via BSF.
3) Fast editor Based on jEdit Syntax Package 2.2.1, a simple, fast and useful editor with only some of the nice features jEdit has got us used to.
Enhancements:
- This release should be a bit more robust when killing processes that make use of System.exit(0) without "dispose()".
- An icon for the GUI manager has been added, as well as a bat file for Windows systems.

Maven is a software project management and comprehension tool. Based on the concept of a project object model (POM), Maven can manage a projects build, reporting and documentation from a central piece of information.
Main features:
Model based builds
- Maven is able to build any number of projects into predefined output types such as a JAR, WAR, or distribution based on metadata about the project, without any need to do any scripting in most cases.
Coherent site of project information
- Using the same metadata as for the build process, Maven is able to generate a web site or PDF including any documentation you care to add, and adds to that standard reports about the state of development of the project. Examples of this information can be seen at the bottom of the left-hand navigation of this site under the "Project Information" and "Project Reports" submenus.
Release management and distribution publication
- Without much additional configuration, Maven will integrate with your source control system such as CVS and manage the release of a project based on a certain tag. It can also publish this to a distribution location for use by other projects. Maven is able to publish individual outputs such as a JAR, an archive including other dependencies and documentation, or as a source distribution.
Dependency management
- Maven encourages the use of a central repository of JARs and other dependencies. Maven comes with a mechanism that your projects clients can use to download any JARs required for building your project from a central JAR repository much like Perls CPAN. This allows users of Maven to reuse JARs across projects and encourages communication between projects to ensure backward compatibility issues are dealt with. We are collaborating with the folks at Ibiblio who have graciously allowed the central repository to live on their servers.
Gump integration
- Integration with Gump. For those who are not familiar with Gump it is a tool used at Apache to help projects maintain backward compatibility with their clients. If you have a Maven project descriptor then you can easily participate in nightly Gump builds that will help your project stay abreast of the impact your changes actually have in Java developer community. We are working on our own massive build tool but integration with Gump comes at no cost to Maven users.

mod_relocate is an Apache module which allows you to create virtual documents that, when selected, transfer you offsite and log the transaction to your access log.

All GET arguments are passed along to the remote URL. Triggers can be set to run whenever a virtual document is selected.

So what is the purpose of all of this?
Ever seen a clickthrough.cgi? How about someone
redirecting you to a site right before they
send you to the final site? This is the
same thing only built into Apache. It
makes it nice and easy to log people leaving
your site.
This works as a virtual document.
Just add:
AddHandler relocate .relo
and you are set. From this point on you can
create virtual documents anywhere within
your site.

PCJBot is a jabber bot written in PCJ. It can do various things on a jabber multi-user chat (MUC) channel. PCJ means for POE::Component::Jabber, the bot uses this POE perl module to connect to a jabber server and a chat room.


Plugins include:
Bloglines
Cron
DNS lookups
Fortunes
Math
Spelling
Seen" nick
Spellcheck
URL repository
Weather lookup