Free lucas rocha software for linux

Just Journal is a blogging application. You can use it to create one or more blogs on a Web site.
Just Journal allows registered users to comment on other blogs, list friends, consume and provide RSS feeds, and post public, friends only, or private journal entries. Just Journal has been tested using MySQL 5.x and Tomcat 5.5.
Enhancements:
- This release features weblogs.com pinging (preliminary), avatars, RSS feeds, and various other features.
- The code is not production ready, but might be useful to others working on Java based blog software.
- This version makes use of MySQL 5 stored procedures.

C-Dogs SDL is a port of the old DOS arcade game C-Dogs to modern operating systems utilising the SDL Media Libraries. In theory C-Dogs SDL should be able to run on Windows, MacOS X, BeOS and the other systems supported by SDL.

Genererally, the more UNIX like a system is, the greater the chance of C-Dogs working (MacOS X and BeOS people, I mean you guys).

C-Dogs SDL was ported to SDL by Jeremy Chin and Lucas Martin-King, using Gentoo Linux as their development environment.

C-Dogs is an arcade shoot-em-up which lets players work alone and co-operativly during missions, and against each other in the "dogfight" deathmatch mode. The DOS version of C-Dogs came with several built in missions and dogfight maps, this version is no exception.

The author of the DOS version of C-Dogs was Ronny Wester. See the "official" homepage for more details. We would like to thank him for releasing the C-Dogs sources to the public.

libPaje is a library developed in GNUstep environment and is released under the GNU Lesser General Public License.

The library intends to provide a better way to generate trace files for Paje Visualization Tool.

libPaje library can be used to create conversion tools from other format to Paje trace file format.

Paje is an interactive and scalable trace-based visualization tool which can be used for a large variety of visualizations including:

performance monitoring of parallel applications
monitoring the execution of processors in a large scale PC cluster
representing the behavior of distributed applications
cluster monitoring and management

Users of Paje can tailor the visualization to their needs, without having to know any insight nor to modify any component of Paje. This can be done by defining the type hierarchy of objects to be visualized as well as how these objects should be visualized. This feature allows the use of Paje for a wide variety of visualizations such as the use of resources by applications in a large-size cluster or the behavior of distributed Java applications.

The Paje trace format include three different kind of informations:

definition of the formats of the event
definition of the type hierarchy of the objects to be visualized
set of recorded events complying with the format definition and according to the type hierarchy previously defined.

Although the Paje trace file format is very easily to understand, there are no library or program to generate files in this format directly. Normally, it is necessary a conversion from a set of information to the format readable to Paje. To make this conversion process more abstract in terms of the definition of a Paje trace file, we create this libPaje.

The libPaje library intends to cover the three different kind of information in a Paje trace file.

It manages the first kind, the definition of the formats of the event, with PajeHeaderCenter class. This class automatically generates code for the events, manages extended events and prints the header according to the format.

The second kind of information in a Paje trace file is the type hierarchy. The PajeHierarchy class tries to simplify the type hierarchy definition by receiving a file in the Property List format with some reserved words and prints the type hierarchy defined there in Paje trace file format.

This class also manages the aliases for objects created in Paje trace file. Aliases can be used to downsize the trace files for Paje.

The third kind of information of a Paje trace file is the events that build the visualization in Paje. To cover this third part we created a set of classes which are subclasses of PajeEvent class. Each of them receives information and properly prints itself according to the header specified with PajeHeaderCenter.

The already defined subclasses of PajeEvent can be extended adding new fields with extra information in the events. This extra information can be visualized in Paje with the Inspection Tool.

Root-Portal is a GNOME program that monitors files, processes etc and displays changes either directly to the desktop or in a transparent border-less window. This is useful for monitoring system logs and for providing feedback on system activities.

Root Portal is a way to do stuff on your desktop in the background. We find it useful as a monitor of system log files such as /var/log/messages and /var/log/xferlog and /var/log/httpd/access_log etc etc.

You can have as many spots, or portals of text on the screen as you want in varying size and varying font and colour and practically any other property you care to think of. They can have the added advantage of being transcient so that you can still see your background picture underneith the text.

As well as this, using the roottext module, you can run programs such as xsnow and the snow flakes will not disappear because of the text, they will pass through it. Using the module such as gnometext allows you to shade the background and put alternate images as backgrounds for your portals.

You may also shade these custom backgrounds, the only disadvantage to this system is that programs such as xsnow cannot mix their graphics with this and disappear behind them. The only other difference between the two is that the root text can handle non-fixed sized fonts with a breeze.

Because the gnome module is using zvt, it currently does no like non-fixed sized fonts too much at all. We are hoping the author of zvt will change this in later releases of his library. As well as the file tailing facility to monitor log files, there is also a loading monitor, to show you when a new process has been created and when a process has been destroyed.
Basically this is a pretty anti-paranoia program for people who sit at their desktops and wonder who is doing what to them from the outside, what is running what on their system, and why their harddisk is suddenly ticking over for no reason *aha, crond is doing something weird*

Support Incident Tracker (or SiT!) is a Web-based application for tracking technical support calls or emails.
Support Incident Tracker project can manage contacts, sites, technical support contracts, and support incidents in one place. You can send and receive email directly from SiT!, attaching files and recording every communication in the incident log.
SiT! is aware of Service Level Agreements, and incidents are flagged if they stray outside of them.
Support Incident Tracker grew out of an application developed by Salford Software since 2000 called Webtrack and is used in-house by Support Engineers to easily track support incidents.
Enhancements:
- Fixed service levels for reopened incidents, service level target opened is now added making the next action initial response
- Fixed regression where mark for closure was ignored and the incident was closed immediately
- Lists number of incidents of each priority a user has on the user listings page.
- Show more accurately who last updated the call on list incidents pages
- Added multiple global signatures, one is choosen at random when email is sent.
- Fixed bug where disabled user accounts would still display as having relevant skills
- Fixed issue where URLs would not be shortened if they contained a % (percent) or $ (dollar) symbol
- Fixed issues with URLs that contain colons
- Incidents page informs you more accuratly who updated the call
- Specified MySQL Engine type to be MyISAM on all table creations
- Call opening notes are shown in tool tip after new incidents logged rather than reassign
- BB Code. Basic set of BB codes supported in incident updates
- Prevent summary and solution from being uncheck from close incident page since these are mandatory
- Fixed bug with not sending closing email
- send_template_email now store emails in the incident log
- Holiday calendar is now functional
- New holiday planner shows when all users are in/out
- Users can now be placed in groups, view users shows just your own group by default
- Users with edit user permission can set users holiday entitlement
- Able to change external escalation details on bulk
- View users now has links to Waiting queues and holiday calendars
- New interface for adding vendors
- Ability to request email notification when a call is reassigned to a user
- Users without valid email address are now prompted on the main page to edit their profile
- Ability for administrators to disable users by editing a profile and setting status to Disabled Account.
- Force username to be unique when adding new users
- Do incident switchover when changing status via edit profie
- New report, average incident duration. Shows the time taken to close incidents over the months.
- When session expires and user logs in again the user is now redirected the the previously accessed page rather than the main page.
- Improved accuracy of SLA calculation
- Added ability to edit/delete software records
- When an inicdent is closed pending-reassignments are remove as necessary
- When an incident is closed any related incidents are notified of the closure.
- Added icons to priority selection dropdown for browsers that support it
- Improved sorting of some tables, you can now click again on the column header to sort in the opposite direction ascending/descending
- Holding queue locks now timeout after $CONFIG[record_lock_delay]
- Ability to delete multiple held emails in one go
- Ability to add resellers
- Escalation can now be configured via a database table, though there is no GUI for this yet
- External escalation partners can be configured via config file
- Edit incident now lets you select an escalation path (assuming paths are configured in the escalationpaths database table)
- Ability to add/edit/view tasks
- Ability to add notes to tasks
- Note owners can now delete their own notes
- Basic incoming email handler now included with SiT, as inboundemail.php
- New report incidents by software shows which software has the most incidents logged
- Tidied more HTML
- Fixed next action field, this is now stored and displayed again
- Interface to configure external escalation partners
- Made holiday booking easier
- Added ability to check which users have been granted each permission

Concurrent Hierarchical State Machine (CHSM) is a language system for specifying concurrent, hierarchical, finite state machines (an implementation of "statecharts") to model and control reactive systems.
CHSM uses its own statechart specification langauge annotated with either C++ or Java code fragments in the tradition of yacc grammars with C code fragments. The generated code is fully object oriented allowing multiple state machines to exist concurrently. The CHSM run-time library is small, efficient, and thread-safe.
CHSM has been used successfullly in production environments such as CERN, Philips, and Qualcomm. There is an independent review from users at CERN.
Enhancements:
- The "dominance" rule has been extended from parent/child transitions to sibling transitions.
- This allows "if-else" transitions to be done more efficiently.

BigAl is a free and platform independent software. The project is written entirely in Java. With BigAl you can calculate really BIG numbers with an accuracy your desktop calculator is still dreaming of. The only restriction is the power of your computer! Not only basic calculations are supported, but also special functions like factorial, fibonacci, lucas-sequence, periods, fraction reducing, sum of the digits, binomial coefficient calculation, factorize function, bit oriented functions and many more.

In February 2001, I wanted to know the result of the factorial of one million. BigAl was born and both many CPU cycles and months later I knew the exact result. Since the beginning, BigAl was able to handle numbers stored in files. Meanwhile a lot of functions has been added and a few of them got a much better performance. BigAl uses the Java classes called BigInteger and BigDecimal.