Amino Introduction
		Amino is first and foremost an application framework based on the MVC pattern made famous by the SmallTalk community. What this means is that the application objects tend to fall into 1 of 3 groups: Model, View, or Controller. There are some other types involved, but they are decorations to the normal MVC pattern.
			The initial goal for Amino is to serve as the foundation for a modeling and simulation application - specifically for supporting modeling of multi-body systems (mechanical engineering.) However the Amino framework has been designed to support virually any type of simulation, in any domain. This is a large challenge, but not as much as actually implementing  meaningful applications in other domains -due to time.
				A major design consideration for the Amino API was allowing the flexibility of making Amino a distributed application.Of course the need for an application to be distributed is usually over-rated, and the performance hits for distributed simulations tend to make the distribution un-reasonable. However, collaboration is the strongest argument for pursuing distributed technologies within this framework. Therefore the API was created (and the distribution directory structure) in such a way as to maximize flexibility in using distributed technology packages, and keep the maintenance and design challenges to a minimum. As of 2003, the Amino system can be run in local mode, or using CORBA (OpenORB). The mode is set at build-time in order to maximize the performance benefit of running locally, without the need for any distributed-technology libraries.
					Since this is a volunteer open source project, development is slow. You're welcome to begin contributing no matter your skill level. If the documentation doesn't already exist on this web-site, it'll be created for you to as, upon request. All you need to do is ask, and be patient. This is meant to be a project for learning and exploration.