Free marie 0.5.0 software for linux

MARIE project is a robotic development and integration environment focused on software reusability and exploitation of already available APIs and middlewares frequently used in robotics.
The main purpose of MARIE is to create a rapid-prototyping approach to software development in robotics.
MARIE proposes a development environment, which copes directly with inter-application communications, creating transparency for communications between them and their localization.
Each application interacts with MARIE communication system, instead of the typical application-to-application relation. It proposes a development environment, which helps and supports distributed system creation. We can see it as a toolbox appropriate for creation of robotics system, plus development guidelines and some APIs to support what is specific in applications.
MARIE uses the mediator design pattern for distributed system in order to cope with different applications not sharing the same communication protocol. This mediator design pattern creates a centralized control unit (the mediator) which interacts with each colleague (the applications) independently.
It coordinates global interactions between colleagues in order to realize the desired system. The five principal consequences from this design are: limiting subclassing, decoupling colleagues, simplifying object protocols, abstracting how objects cooperate and centralizing control.
Application Adapters are responsible for sending service requests and communications from the centralized control unit to the applications, and vice versa, using an application proxy. Each application to be integrated must have its own Application Adapter that encapsulates communication mechanism, the services it provides and the specific configurations it needs.
Communication Adapters are responsible for translating information between different communication protocols and mechanisms.
Communication Managers are responsible of creating and managing communication links between Application Adapters that need to be connected together.
Application Managers manage and control the entire system by coordinating system states, achieving coherence and stability, and configuring and controlling of all components available in the system.
Ports & Communication Strategies are responsible of interconnections between MARIEs components. Each components have one or more Ports that are used as tap points where communication links can be established. Each Port can have its own strategy, called Communication Strategy(CS), on how it handles incoming and outgoing data. Typically, CS implements or is based on a known protocol, such as TCP, UDP or IPC, but it can be any other strategies as well (shared memory, files, direct function calls, ...). Decoupling Communication Strategy from Port functionnalities opens the possibility to choose which protocol is used for each Port without having to modify code related to Ports/components functionnalities.
Enhancements:
- Lots of changes were made in this release.
- A build system based on Scons is used.
- Component creation was simplified.
- User-defined plugins were added for CFB, CS, and Data Factory (SerDes).
- Project file description is used instead of start scripts.
- Socket port number is now automatically managed.
- A new console and GUI Application Manager were added.
- A toolbox for RobotFlow was added.
- Unit tests were introduced.
- New documentation was written.
- A new wiki-based Web site used.
- Code bugs and issues were corrected.

Garden is a dependency injection for PHP5.

Inspired by Spring Framework, it uses XML application context with syntax as similar as possible to Spring context definitions.

Kickstarter

Create example.xml file like this (dont forget to put garden-beans.dtd next to it!):

< ?xml version="1.0" encoding="UTF-8"? >
< !DOCTYPE beans PUBLIC "-//GARDEN//DTD BEAN//EN" "garden-beans.dtd" >
< beans default-lazy-init="true" >

< bean id="dog" class="Dog" file="ext/Dog.php" >
< property name="collar" >
< ref local="dogCollar"/ >
< /property >
< /bean >

< bean id="dogCollar" class="Collar" file="ext/Dog/Collar.php" >
< property name="spiked" value="true"/ >
< /bean >

< /beans >

etx/Dog.php contains:
class Dog
{
private $collar;
public function setCollar($collar)
{
$this->collar = $collar;
}
public function getCollar()
{
return $this->collar;
}
}

etx/Dog/Collar.php contains:
class Collar
{
private $spiked;
public function setSpiked($spiked)
{
$this->spiked = $spiked;
}
public function getSpiked()
{
return $this->spiked;
}
}

Deme is a Web tool to host asynchronous meetings including discussions, document comments and collaborations, straw polls, and decision- making for small to medium groups of people.
It also provides features useful for groups including file storage, member lists, and the like. It is intended to create an environment to allow participation and help strengthen organizations critical to civil society.
Deme is free software, licensed under the AGPL, for asynchronous interactions that include discussions, document collaboration, polls and decision making among small to medium sized groups of people. Our intent in creating Deme is to support the type of deliberation critical to the functioning of smaller, informal organizations in civil society. Read the Deme white paper (pdf format) for more detail on the priciples behind Deme.
Enhancements:
- Full email integration and interface tweaking along with standard bugfixes.

Mailody is a Qt/KDE based mail client which only supports the IMAP protocol. It supports tabbed email reading. This is the first release. I want to have feedback about all the problems. To which mailservers can Mailody not talk for example. Are there any crucial bugs which renders the software unusable for you.
By the way, that is something different as experimental. Mailody should not trash your mail or do other nasty things. I understand mail is important to you. I use Mailody on a daily bases and I would not do that if its buggy.
Enhancements:
- rewrite of large parts of the imap part.
- fetch mailboxlist removed, sync is improved.
- new attachment list in the composer.
- added a re-edit, makes resend possible.
- added a save as draft to the composer.
- added a possibility to add a automatically generated html part to each message.
- fixed bug in selecting the correct profile for forwarding messages.
- stopped stripping the signature when forwarding a message.
- fixed quick search when switching folders.
- Speed improvement for opening folders.
- Fixed drawing error on first messages.
- Added go-to-next-unread.
- Added the possibility to save a message to disk.
- Added fixed font mode for the composer.
- Fixed rare bug in quoted printible messages.
- Improved signature handling.
- Extended the command line parameters & dcop.
- Added a basic phising check.
- Fix some encoding issues in subject and name.
- Most important: ** A MANUAL ** by Richard Johnson.

animmaker creates an unindexed raw AVI from a list or stream of uncompressed Targa files (the ones generated by POV-Ray are accepted perfectly).
After having a raw AVI file generated by animmaker, you can encode it to DivX with MPlayer, like this:
mencoder foo.avi -o foo2.avi -divx4opts br=800:q=5:key=25
Or if you prefer libavcodec instead of divx4linux and two-pass encoding (enhances the quality/size ratio), you can do it like this:
mencoder foo.avi -o foo2.avi -ovc lavc -lavcopts vcodec=mpeg4:vbitrate=800:vhq:vpass=1
mencoder foo.avi -o foo2.avi -ovc lavc -lavcopts vcodec=mpeg4:vbitrate=800:vhq:vpass=2
Refer to the mencoder documentation to see how you can add audio, use different codecs, tune the compression parameters etc. Note that not all codecs support two pass encoding, which is completely optional anyway.
Version restrictions:
- All input tga files must be the same resolution.
- Only uncompressed bgr24/bgr16/bgr15 tga files are accepted.
- The resulting avi will not contain index.
- Resulting avi may not be bigger than 2 GB.
- Only raw audio is accepted, and the soundtrack can only have 1 or 2 channels and can only be 8-bit or 16-bit.
Enhancements:
- This release adds support for huge files (64-bit offsets), and the AVI OpenDML vprp section in the riffdump program.
- Some code cleanup was also done.

Elidune project is a library management software.
Built as a client/server application, using the XML-RPC protocol, it has been developed to be easy to use, yet powerful and able to be easily extended.
It supports cataloguing, customisable search, user management, and document circulation.
Enhancements:
- Makefile.am (SUBDIRS): Add m4.
- (ACLOCAL_AMFLAGS): New variable.
- (EXTRA_DIST): Add config.rpath.
- configure.in (AC_OUTPUT): Add m4/Makefile.

wGui is a platform independent dialog management library based on SDL (Simple Direct-Media Layer) and Freetype 2.
wGuis purpose is to fill the small niche of a GUI library for SDL. There are actually three well known alternatives: LibUta, ParaGUI and aedGui. wGui was spawned from the work of another project (as was LibUta), which I may someday actually get back to.
This was designed to have as few dependencies as possible, and currently only relies upon SDL and Freetype. There is also no platform dependent code, which means it should work properly on any platform that has SDL and Freetype.
wGui was also designed to take advantage of C++, the Standard Library, and the latest Object Oriented techniques. Unfortunately both SDL and Freetype are regular C projects, so not everything is strict C++.
Enhancements:
- The big change in this release was to support Unicode.
- Support for building in Microsoft Visual Studio 2005 has also been added.

Jimm is a native ICQ clone for Java 2 Platform Micro Edition (J2ME), Mobile Information Device Profile (MIDP) 1.0 and 2.0 . It supports the new v8 protocol, former protocols are not supported.
Jimm is the most lightweight ICQ clone available, so please do not expect the same features your favourite desktop client has.
Main features:
- Request and read the server side contact list
- Send plain messages (type 1 and 2)
- Receive plain messages (type 1, 2 and 4, and offline messages)
- Send URL messages (type 4)
- Send and receive status messages (away, n/a, etc.)
- Receive URL messages (type 1, 2 and 4, and offline messages)
- Send file transfer messages and send files (type 2 and direct connection)
- Set your status (away, n/a, etc.)
- Receive status updates (user is away, n/a, etc.)
- Request information about other users
- Remove users from the server side contact list
- Add users to the server side contact list
- Rename users on the server side contact list
- Search for users
- Answer authorization requests
- Multilingual user interface