Free clay modeling tools software for linux

QML (Quantity Modeling Language) is a "thing"-based language for scientific and mathematical data modeling.
Each "thing" is a quantity which may be associated with either a structure or physical phenomena.
Quantities, in turn, may hold other Quantities or values (numbers or strings). Higher-level data models, which associate or define meanings to various quantities (such as velocity or position), can be built from QML quantities.
The higher-level data model (XML) schema that inherits from QML may be understood, and its instance documents may be parsed into QML documents and objects by the QMLReader.
Enhancements:
- This release adds partial Xerces2 DOM support, and works with Java 1.4 and Java 1.5 (no JAXP DocumentBuilder/Factory support currently).
- The test procedure is a little less chatty.
- Support has been added for testing either/both Crimson/Xerces DOM support.
- (Note: Crimson support only works with Java 1.4, as Java 1.5 interfaces have DOM lvl 2 and 3, which crimson doesnt support).
- This release adds compilerargs, and better build support for different configurations to build.xml.

Config::Model::WarpedThing is a base class for warped classes.

SYNOPSIS

use base qw/Config::Model::WarpedThing/ ;

This class must be inherited by all classes that can be warped by Config::Model::Value. This class provides a set of methods that are expected by a warp master from a warped class.

Currently this class is inherited by Config::Model::Value, Config::Model::AnyId and Config::Model::WarpedNode.

WarpThing does not provide a constructor.

Open Blue Lab is an enterprise resource planning system.
Whatever your goal is, the objective of this tool is to provide you the ready-to use stuff to create, update, search and view data you need for your application.
Moreover, this stuff is provided with the latest UI goodies like AJAX support that will ensure you the best feeling you never had in browsing.
Like OpenBlueLab.org project is portal aware, that means you have aggregation and personalization too.
That way, you can focus on your added value : the business logic and requirements your customer needs.
Main features:
- to collaborate and communicate better
- to manage your personal time
- to schedule your appointments
- to define and track personal and group project
- to manage your content (asset, document, ...)
- to manage your customer relationship
- to make coffee (not yet, next release maybe
We want to develop a product, free, that fits exactly your needs, so read this web site and take time to indicate us your requirements. They will appear on our todo list, maybe in a long time, but they will. Then, you may incitate people to contribute in your direction by sponsoring somebody to achieve it.
This product is completely free. You can even package it and sell it. If you wonder what is our business model, you can ask to the forum.
Built on java technology, you may download the GUI installer, double-click and use it (with all your entreprise) through your preferred browser, whatever your environment is.
Built on XML and REST technology, you may integrate (in synchronous or asynchronous mode) it very easily in your environment too.
OMF (OpenBlueLab Modeling Famework) created by and for OpenBlueLab permit to configure easily the portal. Actually, we must use ArgoUML or the plugin ArgoEclipse with the IDE Eclipse. The goal is to create a specialized editor to create the diagrams needed by OpenBlueLab to configure the portal.
The main steps are :
- Transformation files generated by ArgoUML (XMI format) to the ECORE format.
- Transformation files from ECORE format to XMI format (or PIVOT format) to configure the portal.
- Creation of the editor.
Enhancements:
- This version integrates the transformation to UML2, and adds a dialog on comments in the class diagram.

Config::Model provides a framework to help in validating the semantic content of configuration data. The project can also be used to provide a semantic check of options of a complex program like mplayer or transcode.
For most complex software, configuration upgrade is a difficult task for most people. By using Config::Model, a software can provide a smooth upgrade path for their users.
How does this work ?
Using this project, a typical configuration validation tool will be made of 3 parts :
The user interface
The validation engine which is in charge of validating all the configuration information provided by the user.
The storage facility that store the configuration information
Dont we already have some configuration validation tools ?
Youre probably thinking of tools like webmin. Yes, these tools exist and work fine, but they have their set of drawbacks.
Usually, the validation of configuration data is done with a script which performs semantic validation and often ends up being quite complex (e.g. 2500 lines for Debians xserver-xorg.config script which handles xorg.conf file).
In most cases, the configuration model is expressed in instructions (whatever programming language is used) and interspersed with a lot of processing to handle the actual configuration data.
Whats the advantage of this project ?
The Config::Model projects provide a way to get a validation engine where the configuration model is completely separated from the actual processing instruction.
The configuration model is expressed in a declarative form (i.e. a Perl data structure) which is always easier to maintain than a lot of code.
The declaration specifies:
the structure of the configuration data (which can be queried by generic user interfaces)
the properties of each element (boundaries, check, integer or string, enum like type ...)
the default values of parameters (if any)
mandatory parameters
the targeted audience (intermediate, advance, master)
on-line help (for ach parameter or value of parameter)
the level of expertise of each parameter (to hide expert parameters from newbie eyes)
So, in the end:
maintenance and evolution of the configuration content is easier
user will see a *common* interface for *all* programs using this project.
user will not see advanced parameters
upgrade of configuration data is easier and sanity check is performed
audit of configuration is possible to check what was modified by the user compated to default values
What about the user interface ?
Config::Model will also come with a Curses::UI interface that queries the users model and generate the relevant user screens.
What about data storage ?
Since the syntax of configuration files vary wildly form one program to another, most people who want to use this framework will have to provide a dedicated parser/writer.
Nevertheless, this project can also provide a writer/parser for most common format: like ini style file, or provide an interface to the Elektra or debconf projects. This point is open for discussion.
It is entirely possible for a single configuration model to use several parsers and writers so one model will ensure the consistency of several configuration files together.
Enhancements:
- The Xorg model was updated to Config::model version 0.609.
- Some bugs were fixed.

Biomolecule Toolkit project is an Open Source library for the structural modeling of biological macromolecules. The toolkit provides a C++ interface for common tasks in computational structural biology, to facilitate the development of molecular modeling, design, and analysis tools.
Enhancements:
Documentation updates
- Addition of an extensive discussion of the leastsquares_superposition and RMSD-calculation methods, including a description of the mathematical theory behind their operation.
- Fully documented the rotation/translation methods
- Addition of a documented example program ("gyration_radius.cpp")
Bug fixes
- Fixed copy construction bug in PDBAtomDecorator that caused compilation errors in rare situations.
- Fixed a bug in PDBFileParser that caused a compilation error in the PDBSystem copy constructor.
- Fixed a const-conversion bug in GroupedElementIterator which prevented proper interoperation of const and non-const iterator types.
- Fixed a crash-producing bug in stream output for the TypeID class.
- Fixed a math error in RMSD and superposition methods that would corrupt molecule coordinates.
- Fixed a bug that caused all default-constructed PDBAtom objects to be treated as HETATMs.
Feature additions
- Added operator[] to AtomicStructure and PolymerStructure-derived classes.
- Added protected increment() and decrement() operators to TypeID class.
- PDBFileParser can now handle PDB files with ill-formed residue numbering (i.e. Files where residue numbers are repeated in successive chains).

Misfit Model 3D is an OpenGL-based 3D model editor that works with triangle-based models. Misfit Model 3D supports multi-level undo, skeletal animations, simple texturing, scripting, command-line batch processing, and a plugin system for adding new model and image filters.
Complete online help is included. It is designed to be easy to use and easy to extend with plugins and scripts.
Misfit Model 3D was written and tested on Linux (2.4 and 2.6 kernels) and has been compiled and tested on most major Linux distributions.
It is not endian-safe so it is unlikely to run on non-x86 hardware platforms--this will probably not change soon unless I get requests for a version thats usable on big-endian archs.
Enhancements:
- The menus have been re-organized. There is a new command to make normals face outward. The texture coordinate window now has a rotate tool. Material support for COB has been improved. Many animation bugs have been fixed. A "File | Export" command has been added to indicate which formats have less reliable write support.

XML Tree Object Model Parser is an easy to use XML parser designed to provide an easy and simple to use library for parsing XML configuration files. It is split into two components.

The first one is the Parser itself, which uses J2SE 1.4 XML Parsing API, and the second one is what I call XML Tree Object Model, which is a XMLTree containing all of the XML Nodes or Elements in that tree.

The basic idea behind XTOM is to parse the XML file into an XMLTree and then navigate the elements of that tree by refering to them by the path, such as one/two/three.

The idead behind the navigation system came from Jakartas Digester. XTOM just simplifies it to increase the developement of XML based applications.

KPovModeler is a modeling and composition program for creating POV-Ray scenes in KDE.
For most of the modelers, POV-Ray is nothing but a rendering engine and they bring a lot of limitations to the innate possibilities of POV-Ray scripted language. This is not the case for KPovModeler which allows you to use all the features of POV-Ray through the translation of POV-Ray language into a graphical tree.
Almost all options of POV-Rays script language can be used within KPovModeler. "Almost" because variables, loop instructions, macros and some operators cant directly be, unfortunately.
On the other hand, KPovModeler allows you to include a part of a script with the "Raw POV-Ray" tool; such a raw code will only be taken into account by POV-Ray during the rendering stage.
Main features:
- Management of the scene through a graphical tree.
- Object modification with control points in a graphical view or direct manipulation of object attributes in a dialog
- Nonblocking scene rendering with OpenGL as wire frame views
- Freely configurable view layout with dock widgets
- Copy/paste and drag/drop of (a subset of) povray(!) code into and out of the object tree
- Undo and redo
- Scene rendering and texture preview with povray inside the program
- Support for almost all povray objects
- Support for all textures
- Prototypes (declarations) and references
- All projection modes of the camera
For modeling an object, it is not required to know POV-Rays script language. On the other hand, for creating textures refering to POV-Rays documentation will be difficult to avoid.
But to ease the work, it is possible to simply cut-and-paste a script from POV-Ray into KPovModeler. KPovModeler will then, if the script only makes use of known primitives, convert the pasted text and include it into the current scene.
In other words, if you dont know how to create an object or an effect with KPovModeler, you could always copy its example from POV-Rays documentation and experiment with it within KPovModeler.