X-Git-Url: http://wien.tomnetworks.com/gitweb/?a=blobdiff_plain;f=web%2Frationale;h=d63cf225a59b302fb5ce278dc0459f66e8ef468a;hb=2a3c48c55e0619d7cb3fa51184539fb5e0caf2a3;hp=8d81ae0625ec98977c7c35357d5a36cb27d4f239;hpb=3d6ecf40664c0e72e250e1628289279c2859b98a;p=mono.git diff --git a/web/rationale b/web/rationale index 8d81ae0625e..d63cf225a59 100644 --- a/web/rationale +++ b/web/rationale @@ -1,44 +1,47 @@ -The Mono Project +* The Mono Project -* Background. +** Background. The GNOME project goal was to bring missing technologies to Unix and make it competitive in the current market place for desktop applications. We also realized early on that language independence was important, and that is why GNOME APIs were coded using a standard that allowed the APIs to be easily - wrapped for other languages. Our APIs are available on most + wrapped for other languages. Our APIs are available to most programming languages on Unix (Perl, Python, Scheme, C++, Objective-C, Ada). Later on we decided to use better methods for encapsulating our APIs, and we started to use CORBA to define interfaces to - components we complemented it with policy and a set of - standard GNOME interfaces for easily creating reusable and + components. We complemented it with policy and a set of + standard GNOME interfaces for easily creating reusable, language independent components, controls and compound documents. This technology is known as Bonobo, and - easy to use interfaces to Bonobo exist for C, Perl, Python, + href="http://developer.ximian.com/tech/bonobo.html">Bonobo. + Interfaces to Bonobo exist for C, Perl, Python, and Java. CORBA is good when you define coarse interfaces, and most Bonobo interfaces are coarse. The only problem is that Bonobo/CORBA interfaces are not good for small interfaces. - For example implementing an XML parser component and use it to - parse, create and walk an XML document would be inneficient - compared to a C API. + For example, an XML parsing Bonobo/CORBA component would be + inefficient compared to a C API. -* Microsoft's .NET +** Another explanation + + I recently explained our motivations to Dave Winer, and he posted + it here + +** Microsoft's .NET The Microsoft .NET initiative is confusing because it is a company wide effort that ranges from development tools to end - user applications. - - Depending who you ask, you will probably get a different - answer on what .NET is, as .NET is a branding formative that + user applications. .NET is a branding formative that has been applied to: + + + Mono is an implementation of the .NET development platform. -* The Common Language Infrastructure platform. +** The Common Language Infrastructure platform. Microsoft has created a new development platform. The highlights of this new development platform are: + The Common Language Infrastructure platform is similar to the goals we had in GNOME of giving language independence to @@ -100,17 +106,17 @@ The Mono Project for program development that gives Microsoft a room to grow for the coming years. -* ECMA standards. +** ECMA standards. - Microsoft together with HP and Intel have submitted the + Microsoft has submitted the specifications of C#, the runtime, the metadata and the other various bits of the .NET development platform to the - ECMA for standarization. + ECMA for standarization. You can get a copy of the specifications submitted to ECMA from: http://www.dotnetexperts.com/ecma -* Mono: an Open Source Common Language Infrastructure implementation. +** Mono: an Open Source Common Language Infrastructure implementation. Ximian has begun work on Mono, a project that aims to bring the Common Language Infrastructure platform to free systems. @@ -126,10 +132,11 @@ The Mono Project .NET development platform because it is a great platform to build on. -* What makes up Mono? +** What makes up Mono? There are various pieces that will make up Mono: + -* Why use GNOME components? +** Why use GNOME components? GNOME is an umbrella project that consists of infrastructural components (GUI toolkit, XML libraries, CORBA implementation,