Free environment software for linux

SVK::Help::Environment is a list of svks environment variables.

A number of system environment variables influence how svk runs. Below is a complete list of variables you can use to alter svks behavior.

All Platforms

$SVKROOT

Unless you tell it otherwise, svk stores your configuration and repository in $HOME/.svk. If you set SVKROOT to a path on disk, svk will look there instead of in $HOME/.svk.

$SVN_EDITOR / $EDITOR

Sometimes, svk needs to pop up a text editor. svk first tries to launch the editor specified in $SVN_EDITOR and falls back to $EDITOR if thats not defined.

$SVKDIFF

If youd prefer to use an external "diff" tool instead of svks builtin diff library, set this variable to your tools name or path.

$SVKMERGE

svk lets you resolve conflicts, interactively, with a text editor or use an external diff tool. Out of the box, svk comes with support for the following merge tools:

AraxisMerge
Emacs
FileMerge
GtkDiff
Guiffy
GVim
KDiff3
Meld
P4WinMerge
TkDiff
TortoiseMerge
Vim
XXDiff

If you want svk to spawn a specific merge tool, set this variable to the tools name.

$SVKRESOLVE

If you set this variable, svks interactive resolver will always perform the command its set to. For more details about the commands available in svks interactive resolver, type perldoc SVK::Resolve.

$SVKPAGER

When svk needs to pipe long output through a pager, it uses $SVKPAGER to send the output to your display. If this variable is not set or set to something thats not executable, the output will not be paged. svk ignores your $PAGER setting, so you must explicitly set $SVKPAGER if you want paging.

$SVKPGP

svk supports signing and verifying changesets using the Gnu Privacy Guard. By default, svk tries to run the first program called gpg in your path. To tell svk to use a specific gpg executable, set this variable to the executables name or path.

$SVNFSTYPE

By default, svk creates its local repository as a fsfs repository when running on Subversion 1.1 and newer. On Subversion 1.0, SVK defaults to bdb. To explicitly specify a repository type, set this variable to fsfs or bdb.

$SVKNOSVM

To be able to talk to a remote Subversion server, svk needs the SVN::Mirror perl package installed. If you have SVN::Mirror installed, but want svk to operate as if you didnt, set $SVKNOSVM to a true value.

POE (Perl Object Environment) parcels out execution time among one or more tasks, called sessions. Sessions multitask through cooperation (at least until Perls threads become mainstream). That is, each session returns execution to POE as quickly as possible so it can parcel out time to the next.
POE includes a high-level component architecture. Components are modular, reusable pieces of programs. They perform common, often tedious tasks so programmers can work on more interesting things.
Several POE components have been written to handle client, server, and peer networking tasks. Because of them, POE has become a convenient and quick way to write multitasking network applications.
Anyone can write and publish POE components. The CPAN contains a [steadily growing list] of them. The POE Components List includes ones that havent been uploaded to the CPAN yet.
POE provides medium- and low-level concurrency functions. Components use them to perform their tasks. The functions are also available to programmers who prefer to avoid the overhead of components at the expense of writing more code. Components and custom sessions coexist because they all use the same basic functions.
POE supports graphical toolkits such as Tk and Gtk. It is the only Perl programming framework that does this. It also supports Curses, HTTP, and other user interfaces. POE programs can present multiple user interfaces at once.
Enhancements:
- A number of stability and performance fixes were done, including making the tests less prone to race conditions, improving the installation process, eliminating known resource leaks, and reducing CPU use when combined with Tk.

Equinox Desktop Environment (shortly EDE) is small desktop environment, builted to be simple and fast.
Comparing to other desktop environments, EDE is much faster and smaller in memory space (EDEs window manager use less memory than xterm).
The word "equinox" comes from the Latin for "equal night". The equinoxes in March and September are the two occasions each year when the day and the night are of equal duration.
For measuring the length of a day, sunrise is the moment when the sun is half-above the horizon and sunset is the moment when the sun is half-under the horizon. Using this definition, the length of the day (and the night) is precisely 12 hours at an equinox.
Main features:
- desktop with icons and wallpaper;
- Xft font anti-aliasing;
- taskbar with configurable menu, cpu status, easy keyboard switching;
- theming;
- localization;
Graphical front-end for:
- xscreensaver configuration;
- software installation (.rpm, .deb, .tgz);
- time and time-zone configuration;
- fast file and directory serch utility;

AntiRight Desktop Environment is a lightweight and scripted desktop environment that uses the Motif toolkit. Development is carried out with a minimalistic philosophy in mind.

The software consists of a text editor, a desktop panel, a sticky note utility, system management panels, a file manager, a calculator interface, a color/background selector, a command launcher, a simple help system, an email and Web browser launcher, a theme selector, a preferences utility, a series of system monitors including a graphical load meter, and a CD player.

The desktop panel consists of launcher icons, a launcher panel button, a screen lock button, a virtual desktop switcher, an alarm utility, a command launcher, a clock, a user counter, a load meter, and a mail checker.

Techisa Desktop Environment is a lightweight alternative desktop environment developed using Qt.
The projects goal is to provide users with a comfortable environment using as few resources as possible. Only a Brazillian Portuguese translation is currently available.
Enhancements:
- Better support for KDE desktop files.
- Improved recognition of KDM/GDM sessions.
- New icon search paths.
- Enhancements to the TDE menu.
- Better handling of links and properties.
- TDESU shows correct error codes.
- Thumbnails.
- A tree view in the file browser. tdeopen accepts new parameters: [file name] directly executes a file or associated application, and -f [source] [destination] shows a popup allowing user to copy, move, or link.

Software Engineering Environment (SEE) is frame for manufacturing information. It is implemented in sevlet and xml, and is used by the web-browser.
Software Engineering Environment (SEE) attempts to provide the information manufacturing platform for software development.
SEE is a free project, that is the author will provide all of its source code at the same time.
It runs in any servlet environment (The author merely verified in the Win and Linux environment), not using any special technique and needs no auxiliary program.
All of its data are saved in XML files, and need not database. (The future release will support the option of saving data, so that the user can select some free database, such as mysql, or commercial database to improve SEE speed.)
This means that the user can run SEE without any money. (Tomcat is a free servlet environment.)
User uses all SEE functions with the web-browser. So information sharing is very convenient.
SEE supports Simplified Chinese, Traditional Chinese, and English now.( It will support any language if someone will translate.) User can switch to interfaces in different language at any time when SEE is running. And user can add language translations which will work at once.
The main body of SEE is a frame for information manufacturing. All information included in it can be costumed dynamically and all changes will get into effect immediately. This means that the user can modify or add her/his own information structure as will at any time.
SEE provides various predefined selections for information attributes, which correspond various predefined information manufacturing patterns. The user can focus on the information description when costuming information definition, and the system will implement the functions automatically. This is the core of SEE. Most functions of SEE are in this model.
The default information definition of SEE is the result that the author understands what is the Software Engineering.
Although the target of SEE is helping for software development, actually, user can use it to design any type information, such as book registering, personnel lists, and financial reports etc.
The speed of SEE is not bad. Reading and writing 20000 records needs no more than 1 second. At present, the sorting speed is 9 seconds for 5000 records. (The testing platform is 1.8G CPU and 256M memory)
Enhancements:
- The data interface to prepare supporting databases.
- The databases are not supported in this release.
- A new interface style "Beautiful Flowers".
- These flowers are photoed in parks in this year by the author.
- The author likes the honeybee who holds a flower in its mouth very much. It is the first cartoon figure by the author. It will appear when you save wrong data. :)
- The function of "Personal Message".
- User can only query the messages sent by and sent to herself/himself. And user can only remove the messages sent to herself/himself.
- After a user read a message sent to her/him, SEE will mark it as "have_read" automatically.
- The number of new arrived messages will be shown in the interface.
- The data privileges management
- When user "Remove All" or "Modify All", the "base conditions" will be checked at first. That is user can only do what she/he can do.
- The Password fields values can not be visited, except when the user, who owns the "Import" privilege to current data, exports the data.
- All the data structures of ACL tables are changed! Their keywords become the "Title". This will permit user define better ACL.
- And the "condition" in the ACL tables are implemented completely. Now any "SEE conditions" is valid.
- Snapshot for image file
- When list the data, a snapshot will be shown for the image files type, which may end with jpg/jpeg/gif/png.
- Data sorting concerned with langauges.
- Thus when sorting data in Chinese, the result is Chinese result.
- General users can not visit the "User" table! Then they can not fill in many data!
- This is a fatal bug! This means all former releases can not be used actually!
- Now all ACL tables are redesigned.
- When a new user is added without password, SEE will add some password itself! Then this new user can never login!
- This is another fatal bug!
- In the last English release, which is 0.06, the ACL data are in Chinese!
- So the English users can not use SEE at all~~
- This is still a fatal bug!
- The "Risk Items" in the table "Deviation Handling" is wrong defined.
- This will cause an error information when user clicks the "Select" button.
- The values of Password fields can be visited when query or export.
- Although the values are meaningless encoded codes, they are still security thread.
- When some quota marks in the key values, pages will report errors and the function buttons, such as Modify and Remove, can not act!
- This is because quota is also an element of web page.
- When the interface language changes, the language in audit records changes too!
- This is not permitted. Language of all data is determined when SEE is installed and can not change with interface!

Modularized Information Environment (MIE) is a Web-based information management tool designed to meet the needs of small or medium sized organizations.

Modularized Information Environment implements user authentication, storage of settings in a database, multi-lingual support and a presentation layer API that always generates well-formed XML.

Transparent Parallel I/O Environment is a software environment (written in C++) that facilitates the implementation of external memory algorithms.
The goal of theoretical work in the area of external memory algorithms (also called I/O algorithms or out-of-core algorithms) has been to develop algorithms that minimize the Input/Output communication (or just I/O) performed when solving problems on very large data sets.
The area was effectively started in the late eighties by Aggarwal and Vitter and subsequently I/O algorithms have been developed for several problem domains. See below for recent surveys of theoretical results in the area of I/O-efficient algorithms.
Main features:
- Abstract away the I/O details through a simple high-level interface.
- Implement I/O-efficient paradigms to show their practical viability.
- Be flexible, allowing a wide variety of algorithms to be implemented within the system.
- Be portable across a variety of hardware platforms.
- Be extensible, so that new features can be easily added later.
The TPIE library consists of a kernel and a set of I/O-efficient algorithms and data structures implemented on top of the kernel. Most of the functionality is provided as templated classes and functions in C++. In addition, small programs are provided for testing and illustrating the usage of the application interface.