Free in brazil software for linux

Rhino in Spring is a project that intends to integrate Mozilla Rhino JavaScript interpreter, the interpreter for the best (in our opinion) dynamic language on the Java platform with Spring Framework, the also best (again, in our opinion) enterprise framework on the Java platform.
Rhino in Springs aim is to provide a system that amalgamates the rapid development benefits and flexibility of a dynamic language with the strength, scalability and versatility of the Java platform and the Spring framework.
At the moment, the project delivers a controller component for Spring MVC that allows complex control flows spanning several webpages in web applications to be expressed as a single structured algorithm in JavaScript, putting the rich set of control flow structures and function reusability of a full-blown language at your fingertips. It transparently maps the users requests to the correct points of execution in your JavaScript code, even as the user freely navigates your website using the browsers back button or even "File-New Window" functionality!
A flexible set of state persistence options (including one where all state management is shifted to the browser, for maximum server scalability) is included.
Enhancements:
- Added support for relative pathnames in include(), with backward compatible lookup of absolute pathnames
- Fixed bug when an implicitly created ScriptStorage wasnt properly initialized

run in xterm is an servcie menu which adds "run in xterm" & "run in xterm as root" to action menu on binary files, scripts etc.

It has 2 languages: english and polish.

Installation:

copy/save this file in
~/.kde/share/apps/konqueror/servicemenus

Filler in Java project is a graphical game where you occupy coloured hexes by changing colours.
Its strengths are better computer players, internationalisability, and cross-platform deployability.
Installing
In the top directory (same directory as this file), run make. That will build a jar file for you. You then need to be super-user (root), and run make install. If you cant be super-user, just do java -jar filler.jar instead.
The executable program is called filler, and will be installed in /usr/local/bin. Since release 1.01, filler will use your shell variable LANG to set the language that it runs in.
Enhancements:
- Added inc to other directory. This is the code header you include to say that the code is released under GPL.
- Removed resources_de.properties, resources_fr.properties, as I wrote them and they were pretty bad.
- Added sortByRandom() to PlayerWrappers.
- Added build.xml to other. This is for use with ant.
- Cleaned up some access privileges on some fields, cleaned up some bad identifiers.
- Added Kris Verbeecks RemotePlayer.

Dry Brush Plug-In is a plug-in like a tool in Gimp.

It mainly tries to express a feeling of a drawing materials with strength that is brought by pressure sensor of a tablet.

Valgrind is an award-winning suite of tools for debugging and profiling Linux programs. With the tools that come with Valgrind, you can automatically detect many memory management and threading bugs, avoiding hours of frustrating bug-hunting, making your programs more stable. You can also perform detailed profiling, to speed up and reduce memory use of your programs.
Valgrind distribution currently includes three tools: a memory error detectors, a cache (time) profiler and a heap (space) profiler.
Valgrind is Open Source / Free Software, and is freely available under the GNU General Public License.
Main features:
- Valgrind will save you hours of debugging time. With Valgrind tools you can automatically detect many memory management and threading bugs. This gives you confidence that your programs are free of many common bugs, some of which would take hours to find manually, or never be found at all. You can find and eliminate bugs before they become a problem.
- Valgrind can help you speed up your programs. With Valgrind tools you can also perform very detailed profiling to help speed up your programs.
- Valgrind is free. Free-as-in-speech: you can download it, read the source code, make modifications, and pass them on, all within the limits of the GNU GPL. And free-as-in-beer: we arent charging for it.
- Valgrind runs on x86/Linux, AMD64/Linux and PPC32/Linux, several of the most popular platforms in use. Valgrind works with all the major Linux distributions, including Red Hat, SuSE, Debian, Gentoo, Slackware, Mandrake, etc.
- Valgrind is easy to use. Valgrind uses dynamic binary translation, so you dont need to modify, recompile or relink your applications. Just prefix your command line with valgrind and everything works.
- Valgrind is not a toy. Valgrind is first and foremost a debugging and profiling system for large, complex programs. We have had feedback from users working on projects with up to 25 million lines of code. It has been used on projects of all sizes, from single-user personal projects, to projects with hundreds of programmers.
- Valgrind is suitable for any type of software. Valgrind has been used on almost every kind of software imaginable: desktop applications, libraries, databases, games, web browsers, network servers, distributed control systems, virtual reality frameworks, transaction servers, compilers, interpreters, virtual machines, telecom applications, embedded software, medical imaging, scientific programming, signal processing, video/audio programs, NASA Mars lander vision and rover navigation systems, business intelligence software, financial/banking software, operating system daemons, etc, etc. See a list of projects using Valgrind.
- Valgrind is widely used. Valgrind has been used by thousands of programmers across the world. We have received feedback from users in over 25 countries, including: Belgium, Czech Republic, Denmark, Finland, France, Germany, Greece, Hungary, Italy, The Netherlands, Norway, Poland, Portugal, Russia, Sweden, Switzerland, UK, Argentina, Brazil, Canada, USA, Australia, India, Japan, New Zealand, Singapore, South Africa and Israel.
- Valgrind works with programs written in any language. Because Valgrind works directly with program binaries, it works with programs written in any programming language, be they compiled, just-in-time compiled, or interpreted. The Valgrind tools are largely aimed at programs written in C and C++, because programs written in these languages tend to have the most bugs! But it can, for example, be used to debug and profile systems written in a mixture of languages. Valgrind has been used on programs written partly or entirely in C, C++, Java, Perl, Python, assembly code, Fortran, Ada, and many others.
- Valgrind debugs and profiles your entire program. Unlike tools that require a recompilation step, Valgrind gives you total debugging and profiling coverage of every instruction executed by your program, even within system libraries. You can even use Valgrind on programs for which you dont have the source code.
- Valgrind can be used with other tools. Valgrind can start GDB and attach it to your program at the point(s) where errors are detected, so that you can poke around and figure out what was going on at the time.
- Valgrind is extensible. Valgrind consists of the Valgrind core, which provides a synthetic software CPU, and Valgrind tools, which plug into the core, and instrument and analyse the running program. Anyone can write powerful new tools that add arbitrary instrumentation to programs. This is much easier than writing such tools from scratch. This makes Valgrind ideal for experimenting with new kinds of debuggers, profilers, and similar tools.
- Valgrind is actively maintained. The Valgrind developers are constantly working to fix bugs, improve Valgrind, and ensure it works as new Linux distributions and libraries come out. There are also mailing lists you can subscribe to, and contact if youre having problems.
- So whats the catch? The main one is that programs run significantly more slowly under Valgrind. Depending on which tool you use, the slowdown factor can range from 5--100. This slowdown is similar to that of similar debugging and profiling tools. But since you dont have to use Valgrind all the time, this usually isnt too much of a problem. The hours youll save debugging will more than make up for it.
Enhancements:
- 3.2.3 is almost identical to 3.2.2, but fixes a regression that unfortunately crept into 3.2.2. The regression causes an assertion failure in Valgrind when running certain obscure SSE code fragments on x86-linux and amd64-linux. Please do not use (or package) 3.2.2; instead use 3.2.3.

Sidebar in a Can is a simple and powerful tool for webmasters to take a large amount of static content (intimidating to new users) and turn it into a quite manageable amount of dynamic content. The result showcases your sites material.

Sidebar in a Can is built on Snippets technology.

Sidebar in a Can is designed to be run as a straightforward web application, with much administrative activity performed on-web. Rather than trying to explain how to use it, I simply encourage you to explore.

Security

The present release of Sidebar in a Can has not been closely scrutinized for security, and should be treated as such by security-conscious administrators. If you examine the code and discover a vulnerability that could compromise the server, please contact the author at jshayward@pobox.com. The script is intended to have light security and not to compromise a server, but it is not intended to store credit card numbers or other sensitive information.

The default installation sets < the private sidebar data directory > and contents to mode 777. Administrators are encouraged to set directory and contents to mode 700, owned by the effective user ID that Snippets will be running under.

Open Directory in VLC is just a modified version of the Open in Kaffeine service menu.

I use it to open DVD/VIDEO_TS folders. VLC plays them with menus in tact.