Free flames software for linux

Fractal Flames are algorithmically generated images and animations. The software was originally written in 1992 and released as open source, aka free software. Since then it has developed a lot.

Flames has been incorporated into many graphics programs and ported to most operating systems. The shape of each image is specified by a long string of numbers - a genetic code of sorts.

You can create your own flames with the Apophysis interactive designer (for windows) or with the gimps flame plug-in (for linux and OSX). Or you can use the Electric Sheep distributed screen saver to join the collective evolution of animated fractal flames.

Flame Project is an Integrated Development Environment (IDE) for producing Flash and Animated SVG files, similar to Macromedia Captivate. It is licensed under the LGPL.

Imagine a free, easy to use GUI authoring environment that helps you create visually impressive and actually useful learning material. The short term goal for this project is to provide such an environment, and were well on the way to a first release for doing that.

Initially similar to Macromedia Captivate, but a big part is the support for Animated SVG. Flash has at least one serious design limitation (from my POV) making it nearly useless for comprehensive eLearning, and this appears to be addressed by the SVG spec.

The long term goal for this project is to provide both a complete authoring solution (like the Macromedia Flash IDE), and the components for server side communication, but thats a long way off. Lets finish the first bits first.

wmfire is a fiery dock app.
This is an update of the original wmfire dock applet. Like the wmufo program it uses the GDK library to improve its speed - using less than half the cpu of the original program.
It can monitor the average cpu load, or individual cpu load on SMP computers. Additionally it can monitor the memory, network load, a file or just be set to show a pretty flame. On entering the dock a burning spot replaces the cursor, and after two seconds symbols to represent the current monitor are "burnt" onscreen. The flame colour can also be changed.
Enhancements:
- Add sticky option and fix regression causing second window

pywmdockapps is the place to be if you are interested in WindowMaker, dockapps and Python. WindowMaker dockapps are graphical applications fitting in a 64x64 tile. they can work in WindowMaker or any other window manager which can handle WindowMaker style dockapps. pywmdockapps is a Python library enabling quick development of your own dockapps plus a small collection of usable examples.
The included examples are quite untested. they may work quite well, may not work at all, may set your computer in flames, even though this is not the most likely event among the three but you have been warned. the one on which most work has been performed is pywmhdmon, but this too is no guarantee for better functioning.
The example dockapps aim at simplicity and consistency. they are as similar as possible to each other and with no excessive graphics. Since they are written in Python, it shouldnt be too hard to change something you do not like about them. if you do modify things according to your needs and tastes or if you simply try things out, please share your opinions/changes with the community, by sending a comment, suggestion, or just drop a note to say that you have tried it.
Enhancements:
- This version introduces an object-oriented framework.
- It has an Application class usable enough for the most simple cases, or from which to derive your own class.
- A working example is provided that is based on the library.

Hardware Monitor is a multi-purpose, beautiful system-monitoring applet.
The Hardware Monitor applet is an applet for the GNOME panel which tries to be a beautiful all-around solution to system monitoring. It also strives to be user-friendly and generally nice and sensible, integrating pleasantly with the rest of your GNOME desktop.
Includes different viewers, including a flame effect, allows multiple devices to be monitored in the samme applet, uses smooth updating, polished graphs, clean HIG-compliant interface.
Main features:
- A graphical view where each monitor is represented by a (time, measurement) colored curve
- A bar-plot view with a horizontal bar per monitor
- A column view with a column (time, measurement) diagram for each monitor
- A textual view which simply lists the monitors and the currently measured values
- A flame view which produces spiffy flames, the sizes of which are determined by the values of the monitored device
And the applet supports monitoring the following hardware characteristics:
- CPU usage (all CPUs, or one at the time) - niced background processes such as SETI@home are automatically ignored
- Memory usage - cache and buffers are automatically ignored
- Swap usage
- Load average
- Disk usage (or disk space free)
- Network throughput (Ethernet, wireless, modem, serial link), either incoming or outgoing or both
- Temperatures from internal sensors (e.g. system board and CPU temperatures)
- Fan speeds from internal sensors

Bomberman for Java is an original 2D "5 player on one computer" (2 keyboard, 1 mouse, and 2 joystick players) Bomberman game.
Features include a level editor, dynamic key configuration, bomb kicker, bomb stopper, remote bombs, bomb stripper, revenge bombs, portals, rolling floor, flame mirrors, farting items, 10 diseases, adjustable items and disease probabilities, player names, an advanced scoring scheme, adjustable lifetime durations, etc.
Main features:
- fast: your player runs incredible fast
- slow: your player walks very slow
- reverse controls: you go right when you press left, ...
- invisibility: you are invisible, though not invinsible
- auto bomb putting: you put your bombs automatically
- immediate bomb explosion: your bombs explode within a second
- fart: like the item
- autoblock putting: you leave a trail of rocks behind yourself
- invisible bombs: your bombs are invisible, can be very handy
- bomb constipation: you cant lay bombs
- level editor, random level chooser, specific level chooser
- small and medium levels
- adjustable
- screen size, sound on or off, player names
- bonus lifetime, bomb explode time, amount of bonusses, remote lifetime
- fire lifetime, nr of blocks, block reappearance speed
- adjustable bonus and disease probabilities
- full dynamic control setup
- joystick support for two players
- mouse support for one player
- two players on one keyboard: four is possible, but your keyboard will not be able to handle all the pressed buttons.
- keeping track of the wins of every player, resetable via the options menu
- when a player dies, some items are created around his position.
- different background colors
- removed background music and sound effects, added other sound effects
- bomb stop item
- portals
- bomb stripper
- mirrors: reflects fire

Kandid is a system to evolve graphics. Graphics, in Kandid, is not drawn by hand. Instead new forms can be found using genetic algorithms.

To achieve this aim Kandid simulates evolution using sexual reproduction and populations. But there is no fitness function in side the program. Only the user decide which images are interesting.

To simulate evolution Kandid uses crossing over, mutation, populations and has a gene data base. Image calculation is based on Lisp like expressions, Iterated Function Systems (IFS), Linear Cellular Automata (LCA), Voroni diagrams, Lindenmayer Systems (L-systems), and layered textures renderd by Persistence of Vision.

Kandid can be used as an wrapper for image generation programs. These external programs must be able to read the parameters from an file and produce the resulting image to an other file. It is not necessary to edit the parameter files by hand nor starting the program manually.

From the users view there is no distinction between build in and the external calculations. At the moment Persistence of Vision ray tracer and Scott Draves Flame IFS renderer is supported.

While Kandid is platform independent these externals renderers are written in C/C++ and compiled for an special operation system.

You must install a version appropriate to your operating system. After the installation Kandid should be able to find the external program. On Linux programs are often placed in the folders /usr/local/bin/ or /usr/bin/.

This folders are automatically parsed by the operation system. On Windows you can place the exe file in the same folder where the kandid.bat file is located.

DSHub is a hubsoft for Direct Connect Network. DSHub project uses the ADC protocol currently in development by Jacek Sieka and DC DEV. ADC is the future of DC++ network.
How can I use DSHub ?
You can download DSHub from this site and just use it. DSHub is free and every user can take it for himself. You can also redistribute it and you can modify it ( substantially only) under the terms of GNU General Public License. Right click here to download . DSHub comes in zip archive.
DShub is now Open Source and source for current binaries is available here.
How do I install DSHub ?
DSHub is a software created in Java Language developed by Sun. For it to run you need JRE installed. [ That is, Java Runtime Environment]. JRE can be found on http://java.sun.com/ . DSHub requires the least JRE version 1.5.0.0 to run properly. After that just create a folder for your hub and paste the DSHub.jar file downloaded from this site in there.
How do I use DSHub ?
Either you read manual, or after you got your DSHub installed, you can run it from command line by using the command:
path_to_java_exe -jar path_to_DSHub.jar
Linux Example:
java -jar /home/user/myhub/dshub.jar
Whats New in Epsilon Stable Release:
- fixed bug with kick/ban message not showing properly;
- fixed again usercount hope its for good;
- fixed restarting from console;
- fixed rename issue selecting bad/used nick;
- fixed issue when putting max_chat_msg 0 nobody could change it from cmd line;
- ops_override_spam now override max_chat_msg too;
- corrected bug not showing when ureg not online user;
- DSHub is now OPEN-SOURCE under GPL !!! Please look into SRC and give me feedback !
- corrected massall command not working for more words;
- modyfied the random data from IGPA now its real random data;
- fixed bug when restarting, not showing new motd and help file ( thanks Catalin);
- fixed bug when restarting reading regs and bans, doubling them (thanks Catalin);
- fixed bug when restarting after a failure in starting server ( thanks Catalin);
- fixed bug when port was a out of range one and hub would crash;
- corrected message when disconnect on too many ops not showing (thanks ffrag);
- tryed to fix the ghost thingy on unnormal TCP closing sending a keepalive (thanks Ghost for helping);
- added a variable keep_alive_interval for seconds interval between keep alive messages;
- fixed bug when not checking nick lenght on rename ( thanks b_w_johan );
- fixed unbanning some string which is invalid CID;
- fixed issue with opchat nick cant rename to its nick now;
- now users cant use an IP for a nick;
- removed whocid and whoip commands, moved that to info example !info nick gives info about a nick, !info cid shows user with cid, !info ip shows info about users with given ip;
- big change: default password "defpass" removed, now, by default, regs have no pass, just CID check however is good to have one for even better security;
- tryed to fix ugly bug when double client connecting ( example: connecting at same time, double fav hub auto connect); syncronized method handleINF so that it cant be called @ same time;
- improved history, now retains IMSG broadcasts as well;
- created a command cmdhistory that pastes given commands since startup;
- added drop command , a kick with no reason and 0 ban time;
Kick Command:
- Kicking in DSHub is very simple now.
- Classic kick:
kicks just a user out in flames, with a kick_time temporary ban, default 5 minutes.
- Extended kick has way more advantages and can be used very efficiently with a large hub.
- Extended kick features:
- Kicking users that match a certain regular expression:
- Example: !kick [RO].* -- this command kicks all users that have their nick starting with [RO]
- Example: !kick .. --this command kicks all users with 2 letter nicks
- This type of kick accepts just any regular expression.
- Kicking users that have their fields checked:
- Example: !kick share, < , =, !
- And a list of possible fields : share, sl (slots), ni (nick length),su(supports, accepts only = or !, example: !kick su=tcp4),hn(normal hubs count),hr(registered hub count),ho(op hub count),aw(away, 1 means normal away, 2 means extended away),rg (1- registered, 0 otherwise, registered means not op),op ( 1 -op, 0 - otherwise , op means it has key).
- created a kick and ban function for easy call from commands;
- done almost all that kick stuff, for share slots and su, still need to do for rest;
- added a debug message, please ignore, or if you figure it out, report to me;
- modified share kick, to be in megabytes;
- completed kick with all mentioned above in the log;
- fixed bug on new kick, forgot to check if kick_ops is enabled;
- added same features to drop command as well;
- added extra fields to reg class so OLD regs DONT WORK anymore sorry so please REREG;
- modified reg command, now if user already added prints user info;
- added a getRegInfo method, also added extra fields on info and reg;
- added hideme command that toggles the hideme, also hideme is remembered in reg file;
- fixed bug when restarting and changing default port;
- fixed bug when opchat could have same nick as other users;
- fixed exploit when cmdhistory could see the !password;
- fixed bug with renaming into a CID or IP and not repsecting sizes;
Whats New in Zeta RC12 Development Release:
- Completely changed string parsing hope its better now.