Free software development software for linux

Open Office Software Development Kit is an add-on for OpenOffice suite.
It provides the necessary tools and documentation for programming the OpenOffice.org APIs and creating own extensions (UNO components) for OpenOffice.org.
The highlight of the SDK is the 900-page Developers Guide. This comprehensive guide provides a detailed description of the OpenOffice.org API concepts, the OpenOffice.org UNO component model and how to use the API in the context of the different application areas. At the close of each chapter, there is at least one example that demonstrates how to use a specific API.
Developers who are new to OpenOffice.org will also find the OpenOffice.org developer page useful.
Main features:
- 900-page Developers Guide (HTML + PDF version)
- XML file format specification
- IDL reference with cross references to the Developers Guide and vice versa
- C/C++ and Java UNO reference documentation
- development and deployment tools
- code samples for Java, C++, OpenOffice.org Basic and OLE
- easy-to-use build environment for the included samples

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!

CDK4AVR stands for Cross Development Kit for Atmels AVR RISC processor serie and should support your development with a comprehensive Assembler and C development environment for even this processor familie under Linux. It will present only free of fee tools, so you can use it without risks. Further you will find some useful OS projects and related sample code all arround AVRs inside of the example packages.
CDK4AVR collects all programms and development tools in one directory (/opt/cdk4avr) and will try to present an easy to admin installation.
My intention for CDK4AVR is / was to provide a full featurd tool chain distribution of all the free accessible resources, because the most stuff is scattered to the wide of the whole Internet and only compileable by wizards or professions.
Installation:
Each package will be provided as RPM only. It is not necessary to install all packages,but you have to install the base package cdk-avr-base every time you want to use another package. Here is an example for a typical GNU development environment:
[user@host]$ rpm -hiv cdk-avr-base-0.3-20031111.i386.rpm
[user@host]$ rpm -hiv cdk-avr-binutils-2.14-20030906.i386.rpm
[user@host]$ rpm -hiv cdk-avr-gcc-3.3.2-20031021.i386.rpm
[user@host]$ rpm -hiv cdk-avr-gcc-c++-3.3.2-20031021.i386.rpm
[user@host]$ rpm -hiv cdk-avr-gcc-colorgcc-3.3.2-20031021.i386.rpm
[user@host]$ rpm -hiv cdk-avr-libc-1.0.2-20040229.noarch.rpm
[user@host]$ rpm -hiv cdk-avr-gdb-6.0-20031019.i386.rpm
[user@host]$ rpm -hiv cdk-avr-simulavr-0.1.2.20040304cvs-20040304.i386.rpm
[user@host]$ rpm -hiv cdk-avr-avarice-2.2-20040229.i386.rpm
[user@host]$ rpm -hiv cdk-avr-uisp-20040207cvs-20040304.i386.rpm
[user@host]$ rpm -hiv cdk-avr-avrdude-4.3.0-20040229.i386.rpm
Base package -- is needed every time you will use any CDK4AVR package.
NOTE: Users of base packages with version 0.2 and prior have to update to latest version. There was a damaged (t)csh startup script. As a result of an buggy %preun script in previous packages you have to update in two cycles:
[user@host]$ rpm -hUv cdk-nios-base-0.3-20031111.i386.rpm
[user@host]$ rpm -hUv --force cdk-nios-base-0.3-20031111.i386.rpm
Enhancements:
- There are minor feature enhancements in AVR-Ada 0.4.1.
- As a result, the packeges for binutils and gcc/gnat were rebuilt.
- There are new packages for the AVR-Ada run time system and related examples.

Curses Development Kit is a library of widgets for curses development.
Installation:
To build the library cd into the Cdk distribution directory and follow the following steps:
1) Run configure. This will create a Makefile with a default install directory root of /usr/local. If you want to change the default install directory use the --prefix command line argument on configure. For example, if you want to install under /export/local instead, run the command: ./configure --prefix="/export/local"
2) Type make. This will make the library, the example binaries and the demonstration binaries.
3) Type make install. This will install the CDK distribution. Look at step 1 if you want to install other than /usr/local.
Enhancements:
- Adds functions to simplify changes of the list for alphalist and fselect widgets.
- Modifies handling of the delete key to make it delete the current character (unlike backspace).
- Several other minor fixes and improvements.

Chemistry Development Kit classes are Java utitility classes for ChemoInformatics and Computational chemistry, written in Java. They are developed constantly developed parallel to other projects that make use of them.
They are a complete re-write of the CompChem classes that were the basis of JChemPaint, a Java Editor for 2D chemical structures, and of JMDraw, a Java package for the graphical layout of 2D chemical structures.
The CDK project was started in September 2000 to replace the CompChem libraries used by JChemPaint, Jmol and SENECA. It no longer is in its initial stage, but is slowly getting a solid state.
The people involved in setting up the project are Christoph Steinbeck then at the Chemoinformatics Group at the Max Planck Institute of Chemical Ecology in Jena, as well as Egon Willighagen from the University of Nijmegen, The Netherlands, who is also involved with JChemPaint and many other Java Chemoinformatics programs, and Dan Gezelter from Notre Dame University, South Bend, USA, the initiator of Jmol, a 3D viewer and analyzer for molecules .
Now, the rewrite of these CompChem/CDK library classes do somehow effect all of our projects. All of our code relies to some extend on the so-called CompChem classes for computational chemistry.
Christoph Steinbeck started this chemistry library when he started programming SENECA, a system for Computer Assisted Structure Elucidation. It turned out that some of the code had design flaws that prevented others, like the authors of (Jmol) to use it.
Enhancements:
- This release consists of mostly some bugfixes, but also solves a few Java 1.4.2 compile problems and adds more functionality to the SMARTS parser.

GNU MIX Development Kit offers an emulation of MIX and MIXAL. The current version of MDK includes the following applications:
- mixasm A MIXAL compiler, which translates your source files into binary ones, executable by the MIX virtual machine.
- mixvm A MIX virtual machine which is able to run and debug compiled MIXAL programs, using a command line interface with readlines line editting capabilities.
- gmixvm A MIX virtual machine with a GTK+ GUI which allows you running and debugging your MIXAL programs through a nice graphical interface (see screenshots).
- mixguile A Guile interpreter with an embedded MIX virtual machine, manipulable through a library of Scheme functions.
- mixal-mode.el An Emacs major mode for MIXAL source files editing, providing syntax highlighting, documentation lookup and invocation of mixvm within Emacs.
- mixvm.el An elisp program which allows you to run mixvm within an Emacs GUD window, simultaneously viewing your MIXAL source file in another buffer.
Using the GNU MDK tools, youll be able to:
- write, compile and execute MIXAL programs,
- set breakpoints and run your programs step by step,
- set conditional breakpoints (register change, memory change, etc.),
- collect execution timing statistics,
- trace executed instructions,
- inspect and modify the MIX registers, flags and memory contents at any step,
- simulate MIX input-output devices using the standard output and your file system.
In addition, the MIX virtual machine simulators include an embedded Guile interpreter and, therefore, their functionality can be extended using Scheme.
Enhancements:
- The Gmixvm interface has been improved with respect to the external programs dialog and about box.
- Compilation warnings in PPC and 64-bit platforms were fixed.
- Minor bugs were fixed.

NCurses Development Kit for C++ provides a set of widgets for text user interface like menubars, popup menus, various dialog boxes, and controls (push buttons, check buttons etc.). Using this library you can easy create a powefull console program with compicated interface. А powerfull event engine allows you to create a various dynamic widgets.

There are two big branches of this library avaliable - main (head) and the ALT:

Main - original NDK++ library. This library is an extention of libncurses++ library. Event system is working like MFC.

ALT - full rewrite and redesign of the previous code. It not a superset of libncurses++ library, it uses only ncurses and panel libraries. It also uses a new event engine.

Rapid Application Development Library 2.8.3 is yet another excellent utility you should not miss. It is actually a C language library developed to abstract details of interprocess communications and common linux/unix system facilities so that application developers can concentrate on application solutions. It encourages developers (whether expert or novice) to use a proven paradigm of event-driven, asynchronous design. By abstracting interprocess messaging, events, timers, and any I/O device that can be represented as a file descriptor, radlib simplifies the implementation of multi-purpose processes, as well as multi-process applications.

Radlib greatly improves typical process performance through the use of shared memory buffers to avoid costly "malloc" and "free" library calls. These buffers are used for interprocess messages. radlib utilizes shared memory constructs to provide global message queue management and global "Queue Groups" for increased interprocess communications flexibility. All shared resources are semaphore protected to avoid issues with concurrent access.

In short, radlib is a sincere attempt to provide real-time OS capability on a non-real-time OS. It has been successfully deployed on linux, MacOSX and FreeBSD but there is no reason it would not build and run on any flavor of unix supporting System V IPC.

Specifically, radlib provides fast system buffers, a simple config file utility, events, doubly-linked lists, process logging through syslog, message queues, semaphores, shared memory utilities, timers, stacks, state machine utilities, a process framework, a process management utility to start/stop groups of processes, optional MySQL or PostgreSQL database API, a straightforward TCP/streams socket API, a UDP/datagram unicast/multicast/broadcast API, CRC and SHA utility APIs, and other assorted system utilities.

An example application template is provided in the distribution (see the "Example Application Template" link in the left column of this page). The template example serves two purposes: it demonstrates, through source code inspection, how a well constructed radlib process is implemented and it provides an example build environment with the capability for someone new to radlib to build and execute an example application "right out of the box".

Proprietary forms of radlib have been used in several mission-critical commercial applications with excellent results. It is light yet very powerful and efficient in real time. radlib is BSD-licensed (free to use in binary or source forms) and distributed as source to be built on the target platform. Build instructions are included in the distribution. See the file "COPYING" in the distribution for details concerning open source software and the BSD license.