Jump to content

Mono (software): Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
m Minor grammar error, and replacement of best practice written as a language requirement (namespaces do not have to be prefixed by the organization).
Removed history based on Reuters interview that was later debunked by Eben Moglen himself (http://www.linux-watch.com/news/NS6837365670.html)
Line 96: Line 96:
}}
}}
</ref> this agreement extends to Mono but only for Novell developers and users. It was criticized by the [[Open source]] community because it violates the principles of giving equal rights to all users of a particular program (see [[Novell#Patent Agreement with Microsoft|Patent Agreement with Microsoft]]).
</ref> this agreement extends to Mono but only for Novell developers and users. It was criticized by the [[Open source]] community because it violates the principles of giving equal rights to all users of a particular program (see [[Novell#Patent Agreement with Microsoft|Patent Agreement with Microsoft]]).

In [[February 2007]], the [[Free Software Foundation]] announced that it is reviewing Novell's right to sell Linux versions, and even may ban Novell from selling Linux, because of this agreement [http://today.reuters.com/misc/PrinterFriendlyPopup.aspx?type=technologyNews&storyID=2007-02-02T230933Z_01_N02280856_RTRUKOC_0_US-NOVELL-LINUX.xml] <ref>see quote from [[Eben Moglen]], the Foundation's general counsel : ''"The community of people wants to do anything they can to interfere with this deal and all deals like it. They have every reason to be deeply concerned that this is the beginning of a significant patent aggression by Microsoft"''.</ref>


===Defensive patent strategy===
===Defensive patent strategy===

Revision as of 02:47, 20 February 2007

Mono
Developer(s)Novell
Stable release
1.2.3 / February 7, 2007
Repository
Operating systemCross-platform
TypePlatform
LicenseGPL, LGPL and MIT, or dual license
Websitewww.mono-project.com

Mono is a project led by Novell (formerly by Ximian) to create an ECMA standard compliant .NET compatible set of tools, including among others a C# compiler and a Common Language Runtime. Mono can be run on Linux, FreeBSD, UNIX, Mac OS X, Solaris and Windows operating systems.

Microsoft has a version of .NET available for FreeBSD, Windows and Mac OS X called the Shared Source CLI (Rotor). Microsoft's shared source license may be insufficient for the needs of the community (it explicitly forbids commercial use). The Mono project has many of the same goals as the Portable.NET project.

The Mono runtime contains a just-in-time compilation (JIT) engine for a number of processors: x86, SPARC, PowerPC, ARM, S390 (in 32-bit and 64-bit mode), and x86-64, IA64 and SPARC for 64-bit modes. The runtime will perform a just-in-time compilation to the machine's native code which is cached as the application runs. It is also possible to precache the native image before execution. For other supported systems not listed, an interpreter performs each byte code one by one without compiling the image to native code. In almost every condition the JIT method will outperform the interpreted method.

History

Miguel de Icaza became interested in .NET technology as soon as the .NET documents came out in December 2000. After looking at the byte code interpreter, he realized that there were no specifications for the metadata. In February 2001 de Icaza asked for the missing information on the metadata file format in the .NET mailing lists and at the same time started to work on a C# compiler written in C#, as an exercise in C#. In April 2001 ECMA published the missing file format, and at GUADEC (April 6 – April 8, 2001) de Icaza demonstrated the features of his compiler (which by then was able to parse itself).

Internally at Ximian there was much discussion about building tools to increase productivity: making it possible to create more applications in less time and therefore reduce time and cost of development. After a feasibility study, which clearly stated that it was possible to build the technology, Ximian reassigned staff from other projects and created the Mono team. Lacking the manpower to build a full .NET replacement on their own, they formed the Mono open source project, which was announced on July 19 2001 at the O'Reilly conference.

Almost three years later, on June 30, 2004 Mono 1.0 was released.

The logo of Mono features a monkey, mono being the Spanish word for monkey.

Current status and roadmap

Mono current version is 1.2.3 (as of February 2007). This version provides the core API of the .NET Framework 2.0, but its implementation of this API is still incomplete [1].

Complete support for the .NET Framework 2.0, including the .NET 2.0 version of Windows.Forms, is planned for Mono 2.2, by the end of 2007 [2].

Implementation of .NET Framework 3.0 is under development under an experimental Mono subproject called Olive, but the availability of a Mono framework supporting .NET 3.0, is still not planned yet [3].

Mono components

Mono consists of three groups of components: 1) core components; 2) Mono/Linux/GNOME development stack; and 3) the Microsoft compatibility stack.

The core components include the C# compiler, the virtual machine, and the base class libraries. These components are based on the Ecma-334 and Ecma-335 standards, allowing Mono to provide a standards compliant, free and open source CLI virtual machine.

The Mono/Linux/GNOME development stack provide tools for application development while leveraging existing GNOME and Free and Open Source libraries. These include: Gtk# for GUI development, Mozilla libraries for working with the Gecko rendering engine, Unix integration libraries, database connectivity libraries, a security stack, and the XML schema language RelaxNG. Gtk# allows Mono applications to integrate into the Gnome desktop as native applications. The database libraries provide connectivity to MySQL, SQLite, PostgreSQL, Firebird, Open Database Connectivity (ODBC), Microsoft SQL Server (MSSQL), Oracle, the object-relational database db4o, and many others. The Mono project tracks developing database components at its website.

The Microsoft compatibility stack provides a pathway for porting Windows .NET applications to Linux. This group of components include ADO.NET, ASP.NET, and Windows.Forms, among others. As these components are not covered by ECMA standards, some of them remain subject to patent fears and concerns.

Framework architecture

Class library

The class library provides a comprehensive set of facilities for application development. They are primarily written in C#, but thanks to the Common Language Specification they can be used by any .NET language. The class library is structured into namespaces, and deployed in shared libraries known as assemblies. When we speak of the .NET framework, we are primarily referring to this class library.

Namespaces and assemblies

Namespaces are a mechanism for logically grouping similar classes into a hierarchical structure. This prevents naming conflicts. The structure is implemented using dot-separated words, where the most common top-level namespace is System, such as System.IO and System.Net (a complete list can be found in Mono Documentation). There are other top-level namespaces as well, such as Accessibility and Windows. A user can define a namespace by placing elements inside a namespace block.

Assemblies are the physical packaging of the class libraries. These are .dll files, just as (but not to be confused with) Win32 shared libraries. Examples of assemblies are mscorlib.dll, System.dll, System.Data.dll and Accessibility.dll. Namespaces are often distributed among several assemblies and one assembly can be composed of several files.

Common Language Infrastructure and Common Language Specification

The Common Language Infrastructure (CLI), or more commonly known as the Common Language Runtime, is implemented by the Mono executable. The runtime is used to execute compiled .NET applications. The common language infrastructure is defined by the ECMA standard ECMA-335. To run an application, you must invoke the runtime with the relevant parameters.

The Common Language Specification (CLS) is specified in chapter 6 of ECMA-335 and defines the interface to the CLI, such as conventions like the underlying types for Enum. The Mono compiler generates an image that conforms to the CLS. This is the Common Intermediate Language. The Mono runtime takes this image and runs it. The ECMA standard formally defines a library that conforms to the CLS as a framework.

Managed and unmanaged code

Within a native .NET/Mono application, all code is managed; that is, it is governed by the CLI's style of memory management and thread safety. Other .NET or Mono applications can use legacy code, which is referred to as unmanaged, by using the System.Runtime.InteropServices libraries to create C# bindings. Many libraries which ship with Mono use this feature of the CLI, such as Gtk#.

Related projects

There exist lots of projects related to Mono that extend Mono and allows developers to use Mono in their development environment. These projects include:

  • Cocoa#, wrappers around the native Mac OS X toolkit (Cocoa).
  • Gecko#, bindings for embedding the layout engine used in Mozilla (Gecko).
  • Gtk#, C# wrappers around the underlying GTK+ and GNOME libraries, written in C.
  • Tao, a collection of graphics and gaming bindings

MonoDevelop: the Mono IDE

Main article: MonoDevelop

MonoDevelop is a free GNOME integrated development environment primarily designed for C# and other .NET languages such as Nemerle, Boo, and Java (via IKVM.NET). MonoDevelop was originally a port of SharpDevelop to Gtk#, but it has since evolved to meet the needs of Mono developers. The IDE includes class management, built-in help, code completion, Stetic (a GUI designer), project support, and an integrated debugger.

The MonoDoc browser provides access to API documentation and code samples. The documentation browser uses wiki-style content management, allowing developers to edit and improve the documentation.

License

Mono is dual licensed by Novell, similar to other products such as Qt and the Mozilla Application Suite. Mono's C# compiler and tools are released under the GNU General Public License (GPL), the runtime libraries under the GNU Lesser General Public License (LGPL) and the class libraries under the MIT License. These are all free software and open-source licenses and hence Mono is free and open-source software. Developers contributing source code to Mono must sign a copyright assignment allowing Novell to relicense the code under other licensing terms. This preserves Novell's ability under the dual license to commercially license Mono.[4]

Mono and Microsoft's patents

Mono's implementation of those components of the .NET stack not submitted to the ECMA for standardization has been the source of patent violation concerns for much of the life of the project. In particular, discussion has taken place about whether Microsoft could destroy the Mono project through patent suits. The problematic parts are not the core technologies submitted to the ECMA or the Unix/Gnome-specific parts. The patent concerns primarily relate to technologies developed by Microsoft on top of the .NET Framework, such as ASP.NET, ADO.NET and Windows Forms, i.e. parts composing Mono's Windows compatibility stack. These technologies are today not fully implemented in Mono and not required for developing Mono-applications. Not providing a patented capability would weaken the interoperability, but it would still provide the free software / open source software community with good development tools, which is the primary reason for developing Mono.

However, on November 2 2006, Microsoft and Novell announced a joint agreement whereby Microsoft agreed to not sue Novell or its customers for patent infringement.[5]

According to a statement on the blog of Mono project leader Miguel de Icaza,[6] this agreement extends to Mono but only for Novell developers and users. It was criticized by the Open source community because it violates the principles of giving equal rights to all users of a particular program (see Patent Agreement with Microsoft).

Defensive patent strategy

Corporations with a vested interest in free and open source software developed a means to protect FOSS projects from the threats of patent suits by pooling patents into the Open Invention Network (OIN). The OIN is a company that acquires patents and offers them royalty free "to any company, institution or individual that agrees not to assert its patents against the Linux operating system or certain Linux-related applications".[7]

The OIN has the Commerce One patents that cover web services, which potentially threaten anyone who uses web services. The OIN's founders intend for these patents to encourage others to join, and to discourage legal threats against Linux and Linux-related applications. Along with several other projects, Mono is listed as a covered project.

IBM, Novell, Philips, Red Hat, and Sony founded the OIN November 10 2005.

Software developed with Mono

File:F-Spot screenshot.png
F-Spot photo management program
Muine music player

The following are programs that use the Mono API and C#.

Distributions shipping Mono

See also

References

  1. ^ http://www.mono-project.com/Mono_Project_Roadmap#Mono_1.2
  2. ^ http://www.mono-project.com/Mono_Project_Roadmap#Mono_2.2
  3. ^ http://www.mono-project.com/Mono_Project_Roadmap#Mono_and_.NET_3.0
  4. ^ For more information about the licensing, see Mono FAQ: Licensing
  5. ^ "Microsoft and Novell Announce Broad Collaboration on Windows and SUSE Linux Interoperability and Support" (Press release). Novell. 2006-11-02. Retrieved 2006-11-02. {{cite press release}}: Check date values in: |date= (help)
  6. ^ "Statement on the blog of Mono project leader Miguel de Icaza regarding patent protection for Mono". 2006-11-04. Retrieved 2006-11-06. {{cite web}}: Check date values in: |date= (help)
  7. ^ "Open Invention Network formed to promote Linux and spur innovation globally through access to key patents". Open Invention Network. November 10, 2005. {{cite web}}: Check date values in: |year= (help); Unknown parameter |accessmonthday= ignored (help); Unknown parameter |accessyear= ignored (|access-date= suggested) (help)

External links

International


Retrieved from "https://en.wikipedia.org/w/index.php?title=Mono_(software)&oldid=109461146"