diff --git a/archived/atksharp.md b/archived/atksharp.md index a0c06de95..73ab8b248 100644 --- a/archived/atksharp.md +++ b/archived/atksharp.md @@ -8,5 +8,5 @@ redirect_from: AtkSharp ======== -Go to the [MonoDoc API page](http://go-mono.org/docs/index.aspx?tlink=5@N%3aAtk) for reference. +Go to the [MonoDoc API page](http://docs.go-mono.com/index.aspx?tlink=5@N%3aAtk) for reference. diff --git a/archived/cryptography.md b/archived/cryptography.md index fc4297b5c..e8c656360 100644 --- a/archived/cryptography.md +++ b/archived/cryptography.md @@ -40,20 +40,20 @@ Namespace: **System.Security.Cryptography** **Status** -- All classes are present. Most of them have (minimal) documentation in [monodoc](http://www.go-mono.com/docs/index.aspx). +- All classes are present. Most of them have (minimal) documentation in [monodoc](http://docs.go-mono.com/index.aspx). - Most classes have their unit tests. Some tests like [SymmetricAlgorithmTest](http://anonsvn.mono-project.com/viewvc/trunk/mcs/class/corlib/Test/System.Security.Cryptography/SymmetricAlgorithmTest.cs?rev=9817&view=log) are generated by external tools. Namespace: **System.Security.Cryptography.X509Certificates** **Status** -- X.509 certificates are parsed using 100% managed code (using the [Mono.Security.ASN1](http://www.go-mono.com/docs/monodoc.ashx?link=T%3aMono.Security.ASN1) class). +- X.509 certificates are parsed using 100% managed code (using the [Mono.Security.ASN1](http://docs.go-mono.com/monodoc.ashx?link=T%3aMono.Security.ASN1) class). - Software Publisher Certificates (SPC) used by Authenticode(tm) to sign assemblies are supported and **minimally** validated. - Unit tests are generated from a set of existing certificates (about a dozen) each having different properties. Another set of certificates (more than 700) are used for a more complete test (but isn't part of the standard test suite for size and time consideration, i.e. a 7.5Mb C# source file). **Notes** -- The classes under [Mono.Security.X509.\*](http://www.go-mono.com/docs/monodoc.ashx?link=N%3aMono.Security.X509) (in Mono.Security.dll assembly) are a much better alternative - and will continue to evolve to support the security tools. +- The classes under [Mono.Security.X509.\*](http://docs.go-mono.com/monodoc.ashx?link=N%3aMono.Security.X509) (in Mono.Security.dll assembly) are a much better alternative - and will continue to evolve to support the security tools. Assembly: System ---------------- @@ -170,9 +170,9 @@ Namespace: **Mono.Security.Cryptography** **Status** -- A [RNGCryptoServiceProvider](http://www.go-mono.com/docs/monodoc.ashx?link=T%3aMono.Security.Cryptography.RNGCryptoServiceProvider) built on top of CryptoAPI. +- A [RNGCryptoServiceProvider](http://docs.go-mono.com/monodoc.ashx?link=T%3aMono.Security.Cryptography.RNGCryptoServiceProvider) built on top of CryptoAPI. - Wrapper classes for unmanaged versions of hash algorithms: MD2, MD4, MD5 and SHA1 are supported. **Note**: some algorithms shouldn't be used in new design because they aren't considered safe for some usage - this includes MD2, MD4, MD5 and SHA1. They are included to preserve interoperability with older applications (e.g. some old, but still valid, X.509 certificates use MD2, MD4 is required for NTLM authentication ...). -- Classes have minimal documentation available in [monodoc](http://www.go-mono.com/docs/index.aspx). +- Classes have minimal documentation available in [monodoc](http://docs.go-mono.com/index.aspx). **TODO** diff --git a/archived/gconftutorial.md b/archived/gconftutorial.md index 35cf63d68..dcd257e18 100644 --- a/archived/gconftutorial.md +++ b/archived/gconftutorial.md @@ -73,7 +73,7 @@ Most nontrivial applications will need to store user preferences. Traditionally, What are we going to do in this tutorial?: -- Create a [checkbox](http://www.go-mono.com/docs/monodoc.ashx?tlink=6@ecma%3a877%23CheckButton%2f) and an [editbox](http://www.go-mono.com/docs/monodoc.ashx?tlink=6@ecma%3a980%23Entry%2f) +- Create a [checkbox](http://docs.go-mono.com/monodoc.ashx?tlink=6@ecma%3a877%23CheckButton%2f) and an [editbox](http://docs.go-mono.com/monodoc.ashx?tlink=6@ecma%3a980%23Entry%2f) - Link them with [GConf](http://www.gnome.org/projects/gconf/) - Test live notification with [GConf-Editor](http://cvs.gnome.org/viewcvs/gconf-editor/) @@ -272,7 +272,7 @@ References ========== - [GConf Web Site](http://www.gnome.org/projects/gconf/) -- [GConf# Documentation](http://www.go-mono.com/docs/index.aspx?link=N:GConf) +- [GConf# Documentation](http://docs.go-mono.com/index.aspx?link=N:GConf) - [GNOME HIG](http://developer.gnome.org/projects/gup/hig/) diff --git a/archived/gtksharper.md b/archived/gtksharper.md index 5219fb03c..f0ead6a41 100644 --- a/archived/gtksharper.md +++ b/archived/gtksharper.md @@ -20,7 +20,7 @@ Gtk# is a Graphical User Interface Toolkit for mono and .Net. The project binds References ---------- -- [Online API Documentation](http://www.go-mono.com/docs/monodoc.ashx?tlink=root:/classlib-gnome) +- [Online API Documentation](http://docs.go-mono.com/monodoc.ashx?tlink=root:/classlib-gnome) - [What's New?](/GtkSharpNewInVersion2x) - [Release Plans](/GtkSharpPlan) - [Articles and Tutorials](/Articles) on Gtk#. diff --git a/archived/monomac_documentation_api_design.md b/archived/monomac_documentation_api_design.md index c25ff6871..3d8af8cab 100644 --- a/archived/monomac_documentation_api_design.md +++ b/archived/monomac_documentation_api_design.md @@ -126,7 +126,7 @@ MonoMac mirrors in C# the hierarchy of classes from Objective-C. For example, th Although this namespace provides bindings for the underlying Objective-C Foundation types, in a few cases we have mapped the underlying types to .NET types. For example: -1. Instead of dealing with [NSString](http://developer.apple.com/library/mac/documentation/Cocoa/Reference/Foundation/Classes/NSString_Class/Reference/NSString.html#//apple_ref/doc/uid/TP40003744) and [NSArray](http://developer.apple.com/library/mac/documentation/Cocoa/Reference/Foundation/Classes/NSArray_Class/NSArray.html#//apple_ref/doc/uid/TP40003620) the runtime instead exposes these as C# [string](http://www.go-mono.com/docs/index.aspx?link=T:System.String) and strongly typed [" array](http://www.go-mono.com/docs/index.aspx?link=T:System.Array)s throughout the API. +1. Instead of dealing with [NSString](http://developer.apple.com/library/mac/documentation/Cocoa/Reference/Foundation/Classes/NSString_Class/Reference/NSString.html#//apple_ref/doc/uid/TP40003744) and [NSArray](http://developer.apple.com/library/mac/documentation/Cocoa/Reference/Foundation/Classes/NSArray_Class/NSArray.html#//apple_ref/doc/uid/TP40003620) the runtime instead exposes these as C# [string](http://docs.go-mono.com/index.aspx?link=T:System.String) and strongly typed [" array](http://docs.go-mono.com/index.aspx?link=T:System.Array)s throughout the API. 2. Various helper APIs are exposed here to allow developers to bind third party Objective-C APIs, other OS X APIs or APIs that are not currently bound by MonoMac. For more details on binding APIs see the [MonoMac Binding Generator](/MonoMac/Documentation/Binding_New_Objective-C_Types) section. diff --git a/archived/monomacnew.md b/archived/monomacnew.md index 8bfedb43e..68691f21a 100644 --- a/archived/monomacnew.md +++ b/archived/monomacnew.md @@ -12,7 +12,7 @@ MonoMacNew Getting Started -[API Documentation](http://www.go-mono.com/docs/N:MonoMac) +[API Documentation](http://docs.go-mono.com/N:MonoMac) \
diff --git a/archived/monotouch_api.md b/archived/monotouch_api.md index ed609740a..df6f15c53 100644 --- a/archived/monotouch_api.md +++ b/archived/monotouch_api.md @@ -67,43 +67,43 @@ Major Namespaces MonoTouch.ObjCRuntime --------------------- -The [MonoTouch.ObjCRuntime](http://www.go-mono.com/docs/index.aspx?tlink=20@N:MonoTouch.ObjCRuntime) namespace allows developers to bridge the worlds between C# and Objective-C. This is a new binding designed specifically for the iPhone based on the experience from Cocoa# and Gtk#. +The [MonoTouch.ObjCRuntime](http://docs.go-mono.com/index.aspx?tlink=20@N:MonoTouch.ObjCRuntime) namespace allows developers to bridge the worlds between C# and Objective-C. This is a new binding designed specifically for the iPhone based on the experience from Cocoa# and Gtk#. MonoTouch.Foundation -------------------- -The [MonoTouch.Foundation](http://www.go-mono.com/docs/index.aspx?link=N:MonoTouch.Foundation) namespace provides the basic data types designed to interoperate with the Objective-C Foundation framework that is part of the iPhone and it is the base for object oriented programming in Objective-C. +The [MonoTouch.Foundation](http://docs.go-mono.com/index.aspx?link=N:MonoTouch.Foundation) namespace provides the basic data types designed to interoperate with the Objective-C Foundation framework that is part of the iPhone and it is the base for object oriented programming in Objective-C. -MonoTouch mirrors in C# the hierarchy of classes from Objective-C. For example, the Objective-C base class [NSObject](http://developer.apple.com/iphone/library/documentation/Cocoa/Reference/Foundation/Classes/NSObject_Class/Reference/Reference.html) is usable from C# via [MonoTouch.Foundation.NSObject](http://www.go-mono.com/docs/index.aspx?link=T:MonoTouch.Foundation.NSObject). +MonoTouch mirrors in C# the hierarchy of classes from Objective-C. For example, the Objective-C base class [NSObject](http://developer.apple.com/iphone/library/documentation/Cocoa/Reference/Foundation/Classes/NSObject_Class/Reference/Reference.html) is usable from C# via [MonoTouch.Foundation.NSObject](http://docs.go-mono.com/index.aspx?link=T:MonoTouch.Foundation.NSObject). Although this namespace provides bindings for the underlying Objective-C Foundation types, in a few cases we have mapped the underlying types to .NET types. For example: -- Instead of dealing with [NSString](http://developer.apple.com/iphone/library/documentation/Cocoa/Reference/Foundation/Classes/NSString_Class/Reference/NSString.html) and [NSArray](http://developer.apple.com/iphone/library/documentation/Cocoa/Reference/Foundation/Classes/NSArray_Class/Reference/Reference.html) the runtime instead exposes these as C# [string](http://www.go-mono.com/docs/index.aspx?link=T:System.String)s and strongly typed [array](http://www.go-mono.com/docs/index.aspx?link=T:System.Array)s throughout the API. +- Instead of dealing with [NSString](http://developer.apple.com/iphone/library/documentation/Cocoa/Reference/Foundation/Classes/NSString_Class/Reference/NSString.html) and [NSArray](http://developer.apple.com/iphone/library/documentation/Cocoa/Reference/Foundation/Classes/NSArray_Class/Reference/Reference.html) the runtime instead exposes these as C# [string](http://docs.go-mono.com/index.aspx?link=T:System.String)s and strongly typed [array](http://docs.go-mono.com/index.aspx?link=T:System.Array)s throughout the API. - Various helper APIs are exposed here to allow developers to bind third party Objective-C APIs, other iPhone APIs or APIs that are not currently bound by MonoTouch. For more details on binding APIs see the MonoTouch Binding Generator section. ### NSObject -The [NSObject](http://www.go-mono.com/docs/index.aspx?link=T:MonoTouch.Foundation.NSObject) type is the foundation for all the Objective-C bindings. +The [NSObject](http://docs.go-mono.com/index.aspx?link=T:MonoTouch.Foundation.NSObject) type is the foundation for all the Objective-C bindings. -While Mono will provide garbage collection for all of your objects, we made the `MonoTouch.Foundation.NSObject` implement the [http:/monodoc/T:System.IDisposable System.IDisposable] interface. If your type needs to perform deterministic finalization, override the [NSObject.Dispose(bool) method](http://www.go-mono.com/docs/index.aspx?link=M:MonoTouch.Foundation.NSObject.Dispose(System.Boolean)). +While Mono will provide garbage collection for all of your objects, we made the `MonoTouch.Foundation.NSObject` implement the [http:/monodoc/T:System.IDisposable System.IDisposable] interface. If your type needs to perform deterministic finalization, override the [NSObject.Dispose(bool) method](http://docs.go-mono.com/index.aspx?link=M:MonoTouch.Foundation.NSObject.Dispose(System.Boolean)). MonoTouch.UIKit --------------- -The [MonoTouch.UIKit](http://www.go-mono.com/docs/index.aspx?link=N:MonoTouch.UIKit) namespace contains a 1 to 1 mapping to all of the UI components that make up CocoaTouch in the form of C# classes. The API has been modified to follow the conventions used in the C# language. +The [MonoTouch.UIKit](http://docs.go-mono.com/index.aspx?link=N:MonoTouch.UIKit) namespace contains a 1 to 1 mapping to all of the UI components that make up CocoaTouch in the form of C# classes. The API has been modified to follow the conventions used in the C# language. C# delegates are provided for common operations. See the [delegates](#delegates) section for more information. OpenGLES -------- -For OpenGLES we distribute a [modified version](http://www.go-mono.com/docs/index.aspx?link=N:OpenTK) of the [OpenTK](http://www.opentk.com) API, an object-oriented binding to OpenGL that has been modified to use CoreGraphics data types and structures as well as only exposing the functionality that is available on the iPhone. +For OpenGLES we distribute a [modified version](http://docs.go-mono.com/index.aspx?link=N:OpenTK) of the [OpenTK](http://www.opentk.com) API, an object-oriented binding to OpenGL that has been modified to use CoreGraphics data types and structures as well as only exposing the functionality that is available on the iPhone. -OpenGLES 1.1 functionality is available through the [ES](http://www.go-mono.com/docs/index.aspx?link=T:OpenTK.Graphics.ES11.ES) type. +OpenGLES 1.1 functionality is available through the [ES](http://docs.go-mono.com/index.aspx?link=T:OpenTK.Graphics.ES11.ES) type. -OpenGLES 2.0 functionality is available through the [ES](http://www.go-mono.com/docs/index.aspx?link=T:OpenTK.Graphics.ES20.ES) type. +OpenGLES 2.0 functionality is available through the [ES](http://docs.go-mono.com/index.aspx?link=T:OpenTK.Graphics.ES20.ES) type. Binding Design ============== @@ -150,9 +150,9 @@ For example, consider the [UIWebView](http://developer.apple.com/iphone/library/ For many types, MonoTouch will automatically create an appropriate delegate which will forward the UIWebViewDelegate calls onto C# events. For UIWebView: -- The [webViewDidStartLoad](http://developer.apple.com/iphone/library/documentation/UIKit/Reference/UIWebViewDelegate_Protocol/Reference/Reference.html#//apple_ref/occ/intfm/UIWebViewDelegate/webViewDidStartLoad:) method is mapped to the [UIWebView.LoadStarted](http://www.go-mono.com/docs/index.aspx?link=E:MonoTouch.UIKit.UIWebView.LoadStarted) event. -- The [webViewDidFinishLoad](http://developer.apple.com/iphone/library/documentation/UIKit/Reference/UIWebViewDelegate_Protocol/Reference/Reference.html#//apple_ref/occ/intfm/UIWebViewDelegate/webViewDidFinishLoad:) method is mapped to the [UIWebView.LoadFinished](http://www.go-mono.com/docs/index.aspx?link=E:MonoTouch.UIKit.UIWebView.LoadFinished) event. -- The [webView:didFailLoadWithError](http://developer.apple.com/iphone/library/documentation/UIKit/Reference/UIWebViewDelegate_Protocol/Reference/Reference.html#//apple_ref/occ/intfm/UIWebViewDelegate/webView:didFailLoadWithError:) method is mapped to the [UIWebView.LoadError](http://www.go-mono.com/docs/index.aspx?link=E:MonoTouch.UIKit.UIWebView.LoadError) event. +- The [webViewDidStartLoad](http://developer.apple.com/iphone/library/documentation/UIKit/Reference/UIWebViewDelegate_Protocol/Reference/Reference.html#//apple_ref/occ/intfm/UIWebViewDelegate/webViewDidStartLoad:) method is mapped to the [UIWebView.LoadStarted](http://docs.go-mono.com/index.aspx?link=E:MonoTouch.UIKit.UIWebView.LoadStarted) event. +- The [webViewDidFinishLoad](http://developer.apple.com/iphone/library/documentation/UIKit/Reference/UIWebViewDelegate_Protocol/Reference/Reference.html#//apple_ref/occ/intfm/UIWebViewDelegate/webViewDidFinishLoad:) method is mapped to the [UIWebView.LoadFinished](http://docs.go-mono.com/index.aspx?link=E:MonoTouch.UIKit.UIWebView.LoadFinished) event. +- The [webView:didFailLoadWithError](http://developer.apple.com/iphone/library/documentation/UIKit/Reference/UIWebViewDelegate_Protocol/Reference/Reference.html#//apple_ref/occ/intfm/UIWebViewDelegate/webView:didFailLoadWithError:) method is mapped to the [UIWebView.LoadError](http://docs.go-mono.com/index.aspx?link=E:MonoTouch.UIKit.UIWebView.LoadError) event. For example, this simple program times the time it takes to load a web view: @@ -165,7 +165,7 @@ web.LoadFinished += (o, e) => endTime = DateTime.Now; ### Strongly typed via a Delegate property -If you would prefer not to use events, you can provide your own [UIWebViewDelegate](http://www.go-mono.com/docs/index.aspx?link=T:MonoTouch.UIKit.UIWebViewDelegate) subclass and assign it to the [UIWebView.Delegate](http://www.go-mono.com/docs/index.aspx?link=P:MonoTouch.UIKit.UIWebView.Delegate) property. Once UIWebView.Delegate has been assigned, the UIWebView event dispatch mechanism will no longer function, and the UIWebViewDelegate methods will be invoked when the corresponding events occur. +If you would prefer not to use events, you can provide your own [UIWebViewDelegate](http://docs.go-mono.com/index.aspx?link=T:MonoTouch.UIKit.UIWebViewDelegate) subclass and assign it to the [UIWebView.Delegate](http://docs.go-mono.com/index.aspx?link=P:MonoTouch.UIKit.UIWebView.Delegate) property. Once UIWebView.Delegate has been assigned, the UIWebView event dispatch mechanism will no longer function, and the UIWebViewDelegate methods will be invoked when the corresponding events occur. For example, this simple type records the time it takes to load a web view: @@ -194,15 +194,15 @@ The above is used in code like this: The above will create a UIWebViewer and it will instruct it to send messages to an instance of Notifier, a class that we created to respond to messages. -This pattern is also used to control behavior for certain controls, for example in the UIWebView case, the [UIWebView.ShouldStartLoad](http://www.go-mono.com/docs/index.aspx?link=P:MonoTouch.UIKit.UIWebView.ShouldStartLoad) property allows the UIWebView instance to control whether the UIWebView will load a page or not. +This pattern is also used to control behavior for certain controls, for example in the UIWebView case, the [UIWebView.ShouldStartLoad](http://docs.go-mono.com/index.aspx?link=P:MonoTouch.UIKit.UIWebView.ShouldStartLoad) property allows the UIWebView instance to control whether the UIWebView will load a page or not. -The pattern is also used to provide the data on demand for a few controls. For example the [UITableView](http://www.go-mono.com/docs/index.aspx?link=T:MonoTouch.UIKit.UITableView) control is a powerful table rendering control and both the look and the contents are driven by an instace of a [UITableViewDataSource](http://www.go-mono.com/docs/index.aspx?link=T:MonoTouch.UIKit.UITableViewDataSource). +The pattern is also used to provide the data on demand for a few controls. For example the [UITableView](http://docs.go-mono.com/index.aspx?link=T:MonoTouch.UIKit.UITableView) control is a powerful table rendering control and both the look and the contents are driven by an instace of a [UITableViewDataSource](http://docs.go-mono.com/index.aspx?link=T:MonoTouch.UIKit.UITableViewDataSource). ### Loosely typed via the WeakDelegate property In addition to the strongly typed property, there is also a weak typed delegate that allows the developer to bind things differently if desired. Everywhere where a strongly typed `Delegate` property is exposed in MonoTouch's binding a corresponding `WeakDelegate` property is also exposed. -When using the `WeakDelegate` you are responsible for properly decorating your class using the [Export](http://www.go-mono.com/docs/index.aspx?link=T:MonoTouch.Foundation.ExportAttribute) attribute to specify the selector. For example: +When using the `WeakDelegate` you are responsible for properly decorating your class using the [Export](http://docs.go-mono.com/index.aspx?link=T:MonoTouch.Foundation.ExportAttribute) attribute to specify the selector. For example: ``` csharp class Notifier : NSObject { diff --git a/archived/monotouch_manualselectorinvocation.md b/archived/monotouch_manualselectorinvocation.md index 62f38b3b2..553bbf0c5 100644 --- a/archived/monotouch_manualselectorinvocation.md +++ b/archived/monotouch_manualselectorinvocation.md @@ -45,13 +45,13 @@ Suppose you want to invoke the [-[NSString sizeWithFont:forWidth:lineBreakMode:] - (CGSize)sizeWithFont:(UIFont \*)font forWidth:(CGFloat)width lineBreakMode:(UILineBreakMode)lineBreakMode -The return type, GSize, is a [System.Drawing.SizeF](http://www.go-mono.com/docs/monodoc.ashx?link=T%3aSystem.Drawing.SizeF) in managed code (which is a value type). +The return type, GSize, is a [System.Drawing.SizeF](http://docs.go-mono.com/monodoc.ashx?link=T%3aSystem.Drawing.SizeF) in managed code (which is a value type). -The *font* parameter is a [UIFont](http://www.go-mono.com/docs/monodoc.ashx?link=T%3aMonoTouch.UIKit.UIFont) (and a type (indirectly) derived from [NSObject](http://www.go-mono.com/docs/monodoc.ashx?link=T%3aMonoTouch.Foundation.NSObject)), and is thus mapped to [System.IntPtr](http://www.go-mono.com/docs/monodoc.ashx?link=T:System.IntPtr). +The *font* parameter is a [UIFont](http://docs.go-mono.com/monodoc.ashx?link=T%3aMonoTouch.UIKit.UIFont) (and a type (indirectly) derived from [NSObject](http://docs.go-mono.com/monodoc.ashx?link=T%3aMonoTouch.Foundation.NSObject)), and is thus mapped to [System.IntPtr](http://docs.go-mono.com/monodoc.ashx?link=T:System.IntPtr). -The width parameter, a CGFloat, is mapped to [System.Single](http://www.go-mono.com/docs/monodoc.ashx?link=T%3aSystem.Single). +The width parameter, a CGFloat, is mapped to [System.Single](http://docs.go-mono.com/monodoc.ashx?link=T%3aSystem.Single). -The lineBreakMode parameter, a UILineBreakMode, has already been bound in MonoTouch as the [UILineBreakMode](http://www.go-mono.com/docs/monodoc.ashx?link=T%3aMonoTouch.UIKit.UILineBreakMode) enumeration. +The lineBreakMode parameter, a UILineBreakMode, has already been bound in MonoTouch as the [UILineBreakMode](http://docs.go-mono.com/monodoc.ashx?link=T%3aMonoTouch.UIKit.UILineBreakMode) enumeration. Put it all together, and we want an objc_msgSend declaration that matches: @@ -59,7 +59,7 @@ Put it all together, and we want an objc_msgSend declaration that matches: SizeF objc_msgSend(IntPtr target, IntPtr selector, IntPtr font, float width, UILineBreakMode mode); ``` -Checking the [MonoTouch.ObjCRuntime.Messaging](http://www.go-mono.com/docs/monodoc.ashx?link=T%3aMonoTouch.ObjCRuntime.Messaging%2f*) members, we don't see a match for this prototype. Consequently, we will need to declare it ourself: +Checking the [MonoTouch.ObjCRuntime.Messaging](http://docs.go-mono.com/monodoc.ashx?link=T%3aMonoTouch.ObjCRuntime.Messaging%2f*) members, we don't see a match for this prototype. Consequently, we will need to declare it ourself: ``` csharp [DllImport (MonoTouch.Constants.ObjectiveCLibrary)] @@ -97,15 +97,15 @@ Invoking a selector has three steps: ### Selector Targets -A selector target is either an object instance or an Objective-C class. If the target is an instance and came from a bound MonoTouch type, use the [MonoTouch.ObjCRuntime.INativeObject.Handle](http://www.go-mono.com/docs/monodoc.ashx?link=P%3aMonoTouch.ObjCRuntime.INativeObject.Handle) property. +A selector target is either an object instance or an Objective-C class. If the target is an instance and came from a bound MonoTouch type, use the [MonoTouch.ObjCRuntime.INativeObject.Handle](http://docs.go-mono.com/monodoc.ashx?link=P%3aMonoTouch.ObjCRuntime.INativeObject.Handle) property. -If the target is a class, use [MonoTouch.ObjCRuntime.Class](http://www.go-mono.com/docs/monodoc.ashx?link=T%3aMonoTouch.ObjCRuntime.Class) to get a reference to the class instance, then use the [Class.Handle](http://www.go-mono.com/docs/monodoc.ashx?link=P%3aMonoTouch.ObjCRuntime.Class.Handle) property. +If the target is a class, use [MonoTouch.ObjCRuntime.Class](http://docs.go-mono.com/monodoc.ashx?link=T%3aMonoTouch.ObjCRuntime.Class) to get a reference to the class instance, then use the [Class.Handle](http://docs.go-mono.com/monodoc.ashx?link=P%3aMonoTouch.ObjCRuntime.Class.Handle) property. ### Selector Names Selector names are listed within Apple's documentation. For example, the [http://developer.apple.com/iphone/library/documentation/UIKit/Reference/NSString_UIKit_Additions/Reference/Reference.html](http://developer.apple.com/iphone/library/documentation/UIKit/Reference/NSString_UIKit_Additions/Reference/Reference.html) UIKit NSString extension methods] include [sizeWithFont:](http://developer.apple.com/iphone/library/documentation/UIKit/Reference/NSString_UIKit_Additions/Reference/Reference.html#//apple_ref/occ/instm/NSString/sizeWithFont:) and [sizeWithFont:forWidth:lineBreakMode:](http://developer.apple.com/iphone/library/documentation/UIKit/Reference/NSString_UIKit_Additions/Reference/Reference.html#//apple_ref/occ/instm/NSString/sizeWithFont:forWidth:lineBreakMode:). The embedded and trailing colons are important, and are part of the selector name. -Once you have a selector name, you can create a [MonoTouch.ObjCRuntime.Selector](http://www.go-mono.com/docs/monodoc.ashx?link=T%3aMonoTouch.ObjCRuntime.Selector) instance for it. +Once you have a selector name, you can create a [MonoTouch.ObjCRuntime.Selector](http://docs.go-mono.com/monodoc.ashx?link=T%3aMonoTouch.ObjCRuntime.Selector) instance for it. ### Calling objc_msgSend() @@ -113,5 +113,5 @@ When invoking objc_msgSend(), you must pass the selector target (an instance or Objective-C types (e.g. NSString, NSDictionary, UIView, anything that has NSObject as an eventual base type) are passed as System.IntPtr. -A set of pre-made objc_msgSend() declarations can be found in [MonoTouch.ObjCRuntime.Messaging](http://www.go-mono.com/docs/monodoc.ashx?link=T%3aMonoTouch.ObjCRuntime.Messaging%2f*). +A set of pre-made objc_msgSend() declarations can be found in [MonoTouch.ObjCRuntime.Messaging](http://docs.go-mono.com/monodoc.ashx?link=T%3aMonoTouch.ObjCRuntime.Messaging%2f*). diff --git a/archived/monotouchlimitations.md b/archived/monotouchlimitations.md index b1b442f51..c1e49afe0 100644 --- a/archived/monotouchlimitations.md +++ b/archived/monotouchlimitations.md @@ -89,7 +89,7 @@ Using a value type as a Dictionary\ key is problematic, as the de This works for reference types (as the reflection+create a new type step is skipped), but for value types it crashes and burns rather quickly once you attempt to use it on the device. -**Workaround**: Manually implement the [IEqualityComparer\](http://www.go-mono.com/docs/index.aspx?link=T%3aSystem.Collections.Generic.IEqualityComparer%601) interface in a new type and provide an instance of that type to the [Dictionary\(IEqualityComparer\) constructor](http://www.go-mono.com/docs/monodoc.ashx?link=C%3aSystem.Collections.Generic.Dictionary%602(System.Collections.Generic.IEqualityComparer%7b%600%7d)). +**Workaround**: Manually implement the [IEqualityComparer\](http://docs.go-mono.com/index.aspx?link=T%3aSystem.Collections.Generic.IEqualityComparer%601) interface in a new type and provide an instance of that type to the [Dictionary\(IEqualityComparer\) constructor](http://docs.go-mono.com/monodoc.ashx?link=C%3aSystem.Collections.Generic.Dictionary%602(System.Collections.Generic.IEqualityComparer%7b%600%7d)). No Dynamic Code Generation ========================== diff --git a/archived/new_version_of_the_usepage.md b/archived/new_version_of_the_usepage.md index 9eea018e3..3325f2942 100644 --- a/archived/new_version_of_the_usepage.md +++ b/archived/new_version_of_the_usepage.md @@ -39,7 +39,7 @@ Mono can be used in variety of applications, however there are some pieces which - [C# Compiler](/CSharp_Compiler) and [Mono Runtime](/Mono:Runtime) - [Debugger](/Debugger), [Debugging Tutorial](/Guide:Debugger) and [Debugging](/Debugging) - [Profiling](/Profile) -- [API Documentation](http://www.go-mono.com/docs/) +- [API Documentation](http://docs.go-mono.com/) Create a cross-platform application ----------------------------------- diff --git a/archived/nothingtoseehere.md b/archived/nothingtoseehere.md index 1b8c2b844..4be723c62 100644 --- a/archived/nothingtoseehere.md +++ b/archived/nothingtoseehere.md @@ -44,7 +44,7 @@ Quick Links - [Screenshots](/Screenshots) - [Success Stories](/Companies_Using_Mono) - [Articles](/Articles) -- [API Docs](http://www.go-mono.com/docs/) +- [API Docs](http://docs.go-mono.com/) - [Plans](/Plans) - [Report Bugs](/Bugs) diff --git a/archived/oldpage.md b/archived/oldpage.md index ba5829891..52ba3bddf 100644 --- a/archived/oldpage.md +++ b/archived/oldpage.md @@ -17,7 +17,7 @@ Mono is a platform for running and developing modern applications, based on the Mono is an open source effort led by Novell and is the foundation for many new applications. [more...](/About_Mono) Users: [Downloads](/Downloads) | [Bug Reporting](/Bugs) | [Software](/Software) | [Support](/Support) - Developers: [Source Code](/SourceCodeRepository) | [Books](/Books) | [Languages](/Languages) | [Forge](/Novell_Forge) | [API Docs](http://www.go-mono.com/docs/) + Developers: [Source Code](/SourceCodeRepository) | [Books](/Books) | [Languages](/Languages) | [Forge](/Novell_Forge) | [API Docs](http://docs.go-mono.com/) Contributors: [Resources](/Resources) | [Development Plans](/Plans) | [Tasks](/Todo) | [Bug Tracking](/Bugs) Community: [Mailing Lists](/Mailing_Lists) | [IRC](/IRC) | [Related Sites](/Related_Mono_Sites) | [User Groups](/User_Groups) | [Blogs](http://www.go-mono.com/monologue/) FAQ: [General](/FAQ:_General) | [Technical](/FAQ:_Technical) | [Licensing](/FAQ:_Licensing) | [Asp.net](/FAQ:_ASP.NET) | [Security](/FAQ:_Security) diff --git a/archived/use.md b/archived/use.md index a9da700df..27b91b14d 100644 --- a/archived/use.md +++ b/archived/use.md @@ -13,7 +13,7 @@ Use Users:
  [Downloads](/Downloads) | [Bug Reporting](/Bugs) | [Software](/Software)
Developers:
-  [API Docs](http://www.go-mono.com/docs/) | [Languages](/Languages) | [Books](/Books) | [Roadmap](/Mono_Project_Roadmap) | [Plans](/Plans)
+  [API Docs](http://docs.go-mono.com/) | [Languages](/Languages) | [Books](/Books) | [Roadmap](/Mono_Project_Roadmap) | [Plans](/Plans)
Contributors:
  [Build Status](http://wrench.mono-project.com/builds) | [Source Code](/SourceCodeRepository)
Community:
@@ -26,7 +26,7 @@ Mono is positioned to be the leading platform for development of Gnome applicati - [Downloads](/Downloads) - [The Monkeyguide tutorial](/Monkeyguide) - [How-To pages](/Howto) -- [API Documentation](http://www.go-mono.com/docs/) +- [API Documentation](http://docs.go-mono.com/) - [Mailing Lists](/Mailing_Lists) to get help - [Bug reporting](/Bugs) to help us improve the software - Commercial [Support](/Support) diff --git a/community/contributing/index.md b/community/contributing/index.md index e30eaa878..ac9bbbd59 100644 --- a/community/contributing/index.md +++ b/community/contributing/index.md @@ -11,7 +11,7 @@ Track our various [Development Plans](/docs/about-mono/plans/) Users:
  [Downloads](/download/stable/) | [Bug Reporting](/community/bugs/) | [Software](/docs/about-mono/showcase/software/)
Developers:
-  [API Docs](http://www.go-mono.com/docs/) | [Languages](/docs/about-mono/languages/) | [Books](/archived/books) | [Roadmap](/docs/about-mono/roadmap/) | [Plans](/docs/about-mono/plans/)
+  [API Docs](http://docs.go-mono.com/) | [Languages](/docs/about-mono/languages/) | [Books](/archived/books) | [Roadmap](/docs/about-mono/roadmap/) | [Plans](/docs/about-mono/plans/)
Contributors:
  [Class Status](/archived/resources#api-completion-status-pages) | [Build Status](https://jenkins.mono-project.com/) | [Source Code](/community/contributing/source-code-repository/)
Community:
diff --git a/docs/about-mono/releases/0.28.0.md b/docs/about-mono/releases/0.28.0.md index 7e0c58b53..9bc4a1bfb 100644 --- a/docs/about-mono/releases/0.28.0.md +++ b/docs/about-mono/releases/0.28.0.md @@ -19,7 +19,7 @@ We have finished the SourceGear [contract](http://www.ximian.com/about_us/press_ As you can expect, this release features bug fixes everywhere: memory leaks plugged, performance problems solved, performance improvements and more. A special area of robustness is the client-side web services component: it is extremely robust now, as one of the SourceGear acceptance criteria was a 24-hour continuous test of their client library that did millions of web service operations. -We hope to bring the same level of robustness to the server side component in the next release, the www.go-mono.com site [documentation](http://www.go-mono.com/docs/index.html) is currently running with Mono and our ASP.NET implementation (that is why the site has gone down a few times: we were using it on our production system to use it under stress). +We hope to bring the same level of robustness to the server side component in the next release, the www.go-mono.com site [documentation](http://docs.go-mono.com/index.html) is currently running with Mono and our ASP.NET implementation (that is why the site has gone down a few times: we were using it on our production system to use it under stress). Each new release of Mono opens the door for more abusive tests, and this time is not an exception, we already have a few areas of performance and scalability that we want to address for the next release. diff --git a/docs/about-mono/releases/0.29.0.md b/docs/about-mono/releases/0.29.0.md index 9266f580b..f471091f3 100644 --- a/docs/about-mono/releases/0.29.0.md +++ b/docs/about-mono/releases/0.29.0.md @@ -189,7 +189,7 @@ The Web edition has better JavaScript navigation facilities for the tree explore You can use the Monodoc/web edition to host the documentation for your own class libraries. -You can see the web front-end for Monodoc live at [http://www.go-mono.com/docs/index.html](http://www.go-mono.com/docs/index.html) +You can see the web front-end for Monodoc live at [http://docs.go-mono.com/index.html](http://docs.go-mono.com/index.html) John Luke contributed various aesthetic changes to the web edition and various Gtk# types were documented by him. The new style is closer to the NDoc web interface. diff --git a/docs/about-mono/releases/0.30.0.md b/docs/about-mono/releases/0.30.0.md index 30caf454d..cfcde8169 100644 --- a/docs/about-mono/releases/0.30.0.md +++ b/docs/about-mono/releases/0.30.0.md @@ -153,9 +153,9 @@ The web service documentation page has been improved: now it can render sample r This feature has also been added to the wsdl tool, which means that you can print sample textual requests/responses for all web services, not just Monoweb services. ```bash -$ wsdl -sample:Register http://www.go-mono.com/docs/server.asmx?wsdl +$ wsdl -sample:Register http://docs.go-mono.com/server.asmx?wsdl Mono Web Services Description Language Utility -Fetching http://www.go-mono.com/docs/server.asmx?wsdl +Fetching http://docs.go-mono.com/server.asmx?wsdl Sample request message: POST /docs/server.asmx SOAPAction: http://tempuri.org/Register diff --git a/docs/about-mono/releases/1.9.0.md b/docs/about-mono/releases/1.9.0.md index 7a3b7b6c5..9b54dba6a 100644 --- a/docs/about-mono/releases/1.9.0.md +++ b/docs/about-mono/releases/1.9.0.md @@ -121,7 +121,7 @@ System.Core: A HashSet implementation is now available on System.Core and we hav Mono.Posix Improvements ----------------------- -[Stdlib.signal()](http://www.go-mono.com/docs/index.aspx?tlink=0@ecma%3a149%23Stdlib%2fM%2f53) has been deprecated, as its use was inherently usafe. `Stdlib.signal()`'s functionality has been replaced with a pair of members: [Jonathan Pryor] +[Stdlib.signal()](http://docs.go-mono.com/index.aspx?tlink=0@ecma%3a149%23Stdlib%2fM%2f53) has been deprecated, as its use was inherently usafe. `Stdlib.signal()`'s functionality has been replaced with a pair of members: [Jonathan Pryor] - `Mono.Unix.Native.Stdlib.SetSignalAction (Mono.Unix.Native.Signum, Mono.Unix.Native.SignalAction)` permits specifying whether to perform the default action (`SignalAction.Default`), ignore the signal (`SignalAction.Ignore`), or generate an error (`SignalAction.Error`) when the specified signal is generated. - The `Mono.Unix.UnixSignal` class permits instances to represents the signal itself, supporting polling to see if the signal has been generated via the `UnixSignal.IsSet` instance property, or blocking the current thread until the signal has been generated with `UnixSignal.WaitOne()`. diff --git a/docs/about-mono/releases/2.6.0.md b/docs/about-mono/releases/2.6.0.md index d98d42e58..20cdcdf44 100644 --- a/docs/about-mono/releases/2.6.0.md +++ b/docs/about-mono/releases/2.6.0.md @@ -96,7 +96,7 @@ var db = new DataContext("DbLinqProvider=Sqlite; " + "Data Source=Northwind.db3"); ``` -**DbLinqConnectionType** can be skipped if you provide your own [IDbConnection](http://www.go-mono.com/docs/index.aspx?link=T:System.Data.IDbConnection) instance, e.g. +**DbLinqConnectionType** can be skipped if you provide your own [IDbConnection](http://docs.go-mono.com/index.aspx?link=T:System.Data.IDbConnection) instance, e.g. ``` csharp var conn = new SqliteConnection ( @@ -271,7 +271,7 @@ Documentation Tools The monodoc GUI has had several crash fixes [#443699](https://bugzilla.novell.com/show_bug.cgi?id=443699), [#443508](https://bugzilla.novell.com/show_bug.cgi?id=443508). -The [mdoc(5)](http://www.go-mono.com/docs/index.aspx?link=man:mdoc(5)) format has been extended to support embedding arbitrary XML nodes via a **format** element. This can be used to embed e.g. HTML that isn't otherwise supported by the mdoc(5). It's based loosely in concept on Perl's *=begin* blocks. For example: +The [mdoc(5)](http://docs.go-mono.com/index.aspx?link=man:mdoc(5)) format has been extended to support embedding arbitrary XML nodes via a **format** element. This can be used to embed e.g. HTML that isn't otherwise supported by the mdoc(5). It's based loosely in concept on Perl's *=begin* blocks. For example: ``` xml diff --git a/docs/about-mono/releases/2.6.1.md b/docs/about-mono/releases/2.6.1.md index e323996d2..800c5e487 100644 --- a/docs/about-mono/releases/2.6.1.md +++ b/docs/about-mono/releases/2.6.1.md @@ -114,7 +114,7 @@ var db = new DataContext("DbLinqProvider=Sqlite; " + "Data Source=Northwind.db3"); ``` -**DbLinqConnectionType** can be skipped if you provide your own [IDbConnection](http://www.go-mono.com/docs/index.aspx?link=T:System.Data.IDbConnection) instance, e.g. +**DbLinqConnectionType** can be skipped if you provide your own [IDbConnection](http://docs.go-mono.com/index.aspx?link=T:System.Data.IDbConnection) instance, e.g. ``` csharp var conn = new SqliteConnection ( @@ -289,7 +289,7 @@ Documentation Tools The monodoc GUI has had several crash fixes [#443699](https://bugzilla.novell.com/show_bug.cgi?id=443699), [#443508](https://bugzilla.novell.com/show_bug.cgi?id=443508). -The [mdoc(5)](http://www.go-mono.com/docs/index.aspx?link=man:mdoc(5)) format has been extended to support embedding arbitrary XML nodes via a **format** element. This can be used to embed e.g. HTML that isn't otherwise supported by the mdoc(5). It's based loosely in concept on Perl's *=begin* blocks. For example: +The [mdoc(5)](http://docs.go-mono.com/index.aspx?link=man:mdoc(5)) format has been extended to support embedding arbitrary XML nodes via a **format** element. This can be used to embed e.g. HTML that isn't otherwise supported by the mdoc(5). It's based loosely in concept on Perl's *=begin* blocks. For example: ``` xml diff --git a/docs/about-mono/releases/2.6.3.md b/docs/about-mono/releases/2.6.3.md index def8bb344..b1cf5e700 100644 --- a/docs/about-mono/releases/2.6.3.md +++ b/docs/about-mono/releases/2.6.3.md @@ -242,7 +242,7 @@ var db = new DataContext("DbLinqProvider=Sqlite; " + "Data Source=Northwind.db3"); ``` -**DbLinqConnectionType** can be skipped if you provide your own [IDbConnection](http://www.go-mono.com/docs/index.aspx?link=T:System.Data.IDbConnection) instance, e.g. +**DbLinqConnectionType** can be skipped if you provide your own [IDbConnection](http://docs.go-mono.com/index.aspx?link=T:System.Data.IDbConnection) instance, e.g. ``` csharp var conn = new SqliteConnection ( @@ -417,7 +417,7 @@ Documentation Tools The monodoc GUI has had several crash fixes [#443699](https://bugzilla.novell.com/show_bug.cgi?id=443699), [#443508](https://bugzilla.novell.com/show_bug.cgi?id=443508). -The [mdoc(5)](http://www.go-mono.com/docs/index.aspx?link=man:mdoc(5)) format has been extended to support embedding arbitrary XML nodes via a **format** element. This can be used to embed e.g. HTML that isn't otherwise supported by the mdoc(5). It's based loosely in concept on Perl's *=begin* blocks. For example: +The [mdoc(5)](http://docs.go-mono.com/index.aspx?link=man:mdoc(5)) format has been extended to support embedding arbitrary XML nodes via a **format** element. This can be used to embed e.g. HTML that isn't otherwise supported by the mdoc(5). It's based loosely in concept on Perl's *=begin* blocks. For example: ``` xml diff --git a/docs/about-mono/releases/2.6.4.md b/docs/about-mono/releases/2.6.4.md index 206bfc9a3..e5bf87b63 100644 --- a/docs/about-mono/releases/2.6.4.md +++ b/docs/about-mono/releases/2.6.4.md @@ -280,7 +280,7 @@ var db = new DataContext("DbLinqProvider=Sqlite; " + "Data Source=Northwind.db3"); ``` -**DbLinqConnectionType** can be skipped if you provide your own [IDbConnection](http://www.go-mono.com/docs/index.aspx?link=T:System.Data.IDbConnection) instance, e.g. +**DbLinqConnectionType** can be skipped if you provide your own [IDbConnection](http://docs.go-mono.com/index.aspx?link=T:System.Data.IDbConnection) instance, e.g. ``` csharp var conn = new SqliteConnection ( @@ -455,7 +455,7 @@ Documentation Tools The monodoc GUI has had several crash fixes [#443699](https://bugzilla.novell.com/show_bug.cgi?id=443699), [#443508](https://bugzilla.novell.com/show_bug.cgi?id=443508). -The [mdoc(5)](http://www.go-mono.com/docs/index.aspx?link=man:mdoc(5)) format has been extended to support embedding arbitrary XML nodes via a **format** element. This can be used to embed e.g. HTML that isn't otherwise supported by the mdoc(5). It's based loosely in concept on Perl's *=begin* blocks. For example: +The [mdoc(5)](http://docs.go-mono.com/index.aspx?link=man:mdoc(5)) format has been extended to support embedding arbitrary XML nodes via a **format** element. This can be used to embed e.g. HTML that isn't otherwise supported by the mdoc(5). It's based loosely in concept on Perl's *=begin* blocks. For example: ``` xml diff --git a/docs/about-mono/releases/2.6.7.md b/docs/about-mono/releases/2.6.7.md index 83ca3d0a6..7feaf0d8d 100644 --- a/docs/about-mono/releases/2.6.7.md +++ b/docs/about-mono/releases/2.6.7.md @@ -417,7 +417,7 @@ var db = new DataContext("DbLinqProvider=Sqlite; " + "Data Source=Northwind.db3"); ``` -**DbLinqConnectionType** can be skipped if you provide your own [IDbConnection](http://www.go-mono.com/docs/index.aspx?link=T:System.Data.IDbConnection) instance, e.g. +**DbLinqConnectionType** can be skipped if you provide your own [IDbConnection](http://docs.go-mono.com/index.aspx?link=T:System.Data.IDbConnection) instance, e.g. ``` csharp var conn = new SqliteConnection ( @@ -592,7 +592,7 @@ Documentation Tools The monodoc GUI has had several crash fixes [#443699](https://bugzilla.novell.com/show_bug.cgi?id=443699), [#443508](https://bugzilla.novell.com/show_bug.cgi?id=443508). -The [mdoc(5)](http://www.go-mono.com/docs/index.aspx?link=man:mdoc(5)) format has been extended to support embedding arbitrary XML nodes via a **format** element. This can be used to embed e.g. HTML that isn't otherwise supported by the mdoc(5). It's based loosely in concept on Perl's *=begin* blocks. For example: +The [mdoc(5)](http://docs.go-mono.com/index.aspx?link=man:mdoc(5)) format has been extended to support embedding arbitrary XML nodes via a **format** element. This can be used to embed e.g. HTML that isn't otherwise supported by the mdoc(5). It's based loosely in concept on Perl's *=begin* blocks. For example: ``` xml diff --git a/docs/advanced/cas.md b/docs/advanced/cas.md index d652cf142..6a6bb1a21 100644 --- a/docs/advanced/cas.md +++ b/docs/advanced/cas.md @@ -39,17 +39,17 @@ Previously supported (released as of 1.1.10) features includes: - Cross-AppDomain support enabling appdomain based sandboxes (limited by #74411); - Unification (policies, permissions) between framework version numbers; - more security permissions present in `mscorlib.dll` (still unaudited); -- `Demand` for unmanaged code for P/Invoke including support for [SuppressUnmanagedCodeSecurity](http://www.go-mono.com/docs/monodoc.ashx?link=T%3aSystem.Security.SuppressUnmanagedCodeSecurityAttribute) attribute; +- `Demand` for unmanaged code for P/Invoke including support for [SuppressUnmanagedCodeSecurity](http://docs.go-mono.com/monodoc.ashx?link=T%3aSystem.Security.SuppressUnmanagedCodeSecurityAttribute) attribute; - `LinkDemand` (JIT time) and it's special cases: - internal calls (into the runtime); - P/Invoke to unmanaged libraries; and - - [AllowPartiallyTrustedCallers](http://www.go-mono.com/docs/monodoc.ashx?link=T%3aSystem.Security.AllowPartiallyTrustedCallersAttribute) attribute; + - [AllowPartiallyTrustedCallers](http://docs.go-mono.com/monodoc.ashx?link=T%3aSystem.Security.AllowPartiallyTrustedCallersAttribute) attribute; - `InheritanceDemand` (load time) for class inheritance, method overriding and interface implementations; - Support for the new 2.0 security actions. Note that the Mono runtime doesn't (yet) encode them properly. - `DemandChoice`; - `LinkDemandChoice`; and - `InheritanceDemandChoice`. -- Policy resolution - including `RequestMinimum`, `RequestOptional` and `RequestRefuse` [SecurityAction](http://www.go-mono.com/docs/monodoc.ashx?link=T%3aSystem.Security.Permissions.SecurityAction)s; +- Policy resolution - including `RequestMinimum`, `RequestOptional` and `RequestRefuse` [SecurityAction](http://docs.go-mono.com/monodoc.ashx?link=T%3aSystem.Security.Permissions.SecurityAction)s; - Declarative/Imperative demands; - Declarative stack modifiers (`Assert`, `Deny` and `PermitOnly`); @@ -136,7 +136,7 @@ Caspol is a tool to manage security policy files that affects the security manag All but the last one (AppDomain) keeps it's configuration in an XML file that can be configured using `caspol`. -The tool itself is a thin wrapper on top of the security classes in both [System.Security.Permissions](http://www.go-mono.com/docs/monodoc.ashx?link=N%3aSystem.Security.Permissions) and [System.Security.Policy](http://www.go-mono.com/docs/monodoc.ashx?link=N%3aSystem.Security.Policy) namespaces. +The tool itself is a thin wrapper on top of the security classes in both [System.Security.Permissions](http://docs.go-mono.com/monodoc.ashx?link=N%3aSystem.Security.Permissions) and [System.Security.Policy](http://docs.go-mono.com/monodoc.ashx?link=N%3aSystem.Security.Policy) namespaces. **Status** @@ -154,7 +154,7 @@ Permview is a tool that can extract the declarative security permission sets fro ### storeadm -Storeadm is a tool to manage isolated storage on a computer. It's handly for sysadmins to manage (and reclaim) disk space used for isolated storage. The tool is mainly built on top of the [System.IO.IsolatedStorage](http://www.go-mono.com/docs/monodoc.ashx?link=N%3aSystem.IO.IsolatedStorage) classes; +Storeadm is a tool to manage isolated storage on a computer. It's handly for sysadmins to manage (and reclaim) disk space used for isolated storage. The tool is mainly built on top of the [System.IO.IsolatedStorage](http://docs.go-mono.com/monodoc.ashx?link=N%3aSystem.IO.IsolatedStorage) classes; **Status** diff --git a/docs/advanced/runtime/index.md b/docs/advanced/runtime/index.md index da174f43c..5ca2f1186 100644 --- a/docs/advanced/runtime/index.md +++ b/docs/advanced/runtime/index.md @@ -23,7 +23,7 @@ The runtime offers the following services: - Backend engines: - Mono's own engine - [LLVM optimizing compiler backend engine](/docs/advanced/mono-llvm/) - - [First-class SIMD datatypes (Mono.Simd)](http://go-mono.com/docs/index.aspx?link=N%3aMono.Simd) + - [First-class SIMD datatypes (Mono.Simd)](http://docs.go-mono.com/index.aspx?link=N%3aMono.Simd) - Exception Handling - Software-triggered exceptions - Hardware-triggered exceptions like Floating point exceptions, null reference exceptions @@ -31,7 +31,7 @@ The runtime offers the following services: - File system IO - Networking IO - Access to operating system properties and features - - On Unix systems, [Mono.Posix APIs](http://go-mono.com/docs/index.aspx?link=N%3aMono.Posix) + - On Unix systems, [Mono.Posix APIs](http://docs.go-mono.com/index.aspx?link=N%3aMono.Posix) - Program isolation using Application Domains (AppDomain) - Thread management: - Threadpool for user code diff --git a/docs/faq/documentation.md b/docs/faq/documentation.md index 3847476a1..80c09b231 100644 --- a/docs/faq/documentation.md +++ b/docs/faq/documentation.md @@ -9,7 +9,7 @@ Getting Documentation ### Where can I find Mono documentation? -Mono documentation can either be viewed [on line](http://www.go-mono.com/docs/) or off line using the [GTK#](/docs/tools+libraries/tools/monodoc/#the-gtk-documentation-browser) or [console based](/docs/tools+libraries/tools/monodoc/#mod-command-line-documentation-viewer) documentation browsers. +Mono documentation can either be viewed [on line](http://docs.go-mono.com/) or off line using the [GTK#](/docs/tools+libraries/tools/monodoc/#the-gtk-documentation-browser) or [console based](/docs/tools+libraries/tools/monodoc/#mod-command-line-documentation-viewer) documentation browsers. ### Why do I read "Documentation for this section has not yet been entered." everywhere? diff --git a/docs/faq/security.md b/docs/faq/security.md index 4b428984a..628f07966 100644 --- a/docs/faq/security.md +++ b/docs/faq/security.md @@ -223,7 +223,7 @@ Security related compilation issues ### Compiling Mono's mscorlib.dll with CSC 7.x (Fx 1.x) -With the CLR 1.x a security permission object (implementing [IPermission](http://www.go-mono.com/docs/monodoc.ashx?link=T%3aSystem.Security.IPermission)) must be created, from its security attribute (inherited from [SecurityAttribute](http://www.go-mono.com/docs/monodoc.ashx?link=T%3aSystem.Security.Permissions.SecurityAttribute)), to generate the XML output that is embedded in the assembly. This means that the compiler cannot accept the use of *PermissionX* if *PermissionX* is defined in the assembly being compiled. This cause a problem for some assemblies, like `mscorlib.dll` which consume its own permission. +With the CLR 1.x a security permission object (implementing [IPermission](http://docs.go-mono.com/monodoc.ashx?link=T%3aSystem.Security.IPermission)) must be created, from its security attribute (inherited from [SecurityAttribute](http://docs.go-mono.com/monodoc.ashx?link=T%3aSystem.Security.Permissions.SecurityAttribute)), to generate the XML output that is embedded in the assembly. This means that the compiler cannot accept the use of *PermissionX* if *PermissionX* is defined in the assembly being compiled. This cause a problem for some assemblies, like `mscorlib.dll` which consume its own permission. In order to bootstrap such assemblies CSC 7.x looks for the environment variable `__SECURITY_BOOTSTRAP_DB` to create a security database. The information within (format unknown) enables CSC to compile them. @@ -238,7 +238,7 @@ From the [/mcs/class/corlib/Makefile](https://github.com/mono/mono/blob/master/m ### System.Security.SecurityException : Failure decoding embedded permission set object -This exception can occurs when using a path/file in a declarative [FileIOPermission](http://www.go-mono.com/docs/monodoc.ashx?link=T%3aSystem.Security.Permissions.FileIOPermissionAttribute) attribute (or any other security attribute accepting filenames). The Mono runtime supports UNIX-style filename when compiling (e.g. MCS) but the Microsoft runtime won't be able to decode them. The solution is to use imperative security when dealing with filenames. +This exception can occurs when using a path/file in a declarative [FileIOPermission](http://docs.go-mono.com/monodoc.ashx?link=T%3aSystem.Security.Permissions.FileIOPermissionAttribute) attribute (or any other security attribute accepting filenames). The Mono runtime supports UNIX-style filename when compiling (e.g. MCS) but the Microsoft runtime won't be able to decode them. The solution is to use imperative security when dealing with filenames. **Note**: You can see this problem if you compile corlib's unit tests under Linux then try to execute the tests under the MS runtime. diff --git a/docs/faq/technical.md b/docs/faq/technical.md index 73f038793..a26b2eae4 100644 --- a/docs/faq/technical.md +++ b/docs/faq/technical.md @@ -395,7 +395,7 @@ MonoDoc MonoDoc is a graphical documentation browser for the Mono documentation: class libraries, tutorials and manual pages. Currently, monodoc has a GUI front-end written in Gtk# and a Web front-end using ASP.NET -The contents of Monodoc today are visible on the web [here](http://www.go-mono.com/docs/) +The contents of Monodoc today are visible on the web [here](http://docs.go-mono.com/) More information about the Mono documentation can be found on the [Documentation](/docs/) page. diff --git a/docs/getting-started/index.md b/docs/getting-started/index.md index 2a9eff775..193a3e5c0 100644 --- a/docs/getting-started/index.md +++ b/docs/getting-started/index.md @@ -42,7 +42,7 @@ Working with Mono

Writing a Gtk# Application
Tutorial that shows how to write a Gtk# application using MonoDevelop and its visual Gtk# designer.

Porting Winforms Applications
Guide to porting a Winforms application to run on Mono.

Debugging Winforms Applications with VS
Guide to setting up the Winforms project in your application solution to enable debugging in Visual Studio.

-

API Reference
Mono Documentation Library

+

API Reference
Mono Documentation Library

Portability Guidelines
How to write your application to work on multiple platforms.

Deployment Guidelines
How to package and deploy your application to various platforms.

HowTo Guides
Short, specific guides for various topics.

diff --git a/docs/gui/gtksharp/beginners-guide.md b/docs/gui/gtksharp/beginners-guide.md index 5e5da5c60..4163d0a98 100644 --- a/docs/gui/gtksharp/beginners-guide.md +++ b/docs/gui/gtksharp/beginners-guide.md @@ -211,48 +211,48 @@ Now just compile like we did before and run it using \`mono HelloWorld.exe\` and Pretty easy, isn't it?" -The first thing that you might notice, if you have used System.Windows.Forms is that we didn't add any layout code for our label. For example we didn't say 'myLabel.Left = 100' or 'myLabel.Width = 200' or anything that to add the label to the form, and just simply said 'myWin.Add(...)'. This is because a 'Gtk.Window' is a widget that inherits from a '[Bin](http://www.go-mono.com/docs/index.aspx?link=T%3aGtk.Bin)', or single widget hosting '[Container](http://www.go-mono.com/docs/index.aspx?link=T%3aGtk.Container)'. +The first thing that you might notice, if you have used System.Windows.Forms is that we didn't add any layout code for our label. For example we didn't say 'myLabel.Left = 100' or 'myLabel.Width = 200' or anything that to add the label to the form, and just simply said 'myWin.Add(...)'. This is because a 'Gtk.Window' is a widget that inherits from a '[Bin](http://docs.go-mono.com/index.aspx?link=T%3aGtk.Bin)', or single widget hosting '[Container](http://docs.go-mono.com/index.aspx?link=T%3aGtk.Container)'. -The other part you may be interested in is what the "Application.Init()" and "Application.Run()" statements are for. If you have ever used System.Windows.Forms, its similar to "Application.Run()" in many ways. Normally, when the application gets done processing any code on its main thread the application will stop. Since "ShowAll()" doesn't block the code would continue on and shut down. The "Application.Init()" command tells the runtime to listen for any Gtk.Windows launched and when you run the run command it starts a the main loop on those windows. This keeps the application running until all the windows are closed. For more information check out the Monodoc information on the [Application](http://www.go-mono.com/docs/index.aspx?tlink=6@ecma%3a830%23Application%2f) object. +The other part you may be interested in is what the "Application.Init()" and "Application.Run()" statements are for. If you have ever used System.Windows.Forms, its similar to "Application.Run()" in many ways. Normally, when the application gets done processing any code on its main thread the application will stop. Since "ShowAll()" doesn't block the code would continue on and shut down. The "Application.Init()" command tells the runtime to listen for any Gtk.Windows launched and when you run the run command it starts a the main loop on those windows. This keeps the application running until all the windows are closed. For more information check out the Monodoc information on the [Application](http://docs.go-mono.com/index.aspx?tlink=6@ecma%3a830%23Application%2f) object. Step 5: Laying out the window ----------------------------- -Now you maybe asking yourself, "How do you then add more then one widget to a window if it can only contain one widget?". Well like before how we said that a Window was a widget with a single widget container, well we have other widgets that have the ability to contain multiple widgets at the same time. Some of those widgets will inherit from a '[Gtk.Box](http://www.go-mono.com/docs/index.aspx?link=T%3aGtk.Box)' container widget or from the container widget directly in some cases. A Bin container widget inherits form the container widget directly as well, just like all other widget containers, but a Bin can only contain one control. +Now you maybe asking yourself, "How do you then add more then one widget to a window if it can only contain one widget?". Well like before how we said that a Window was a widget with a single widget container, well we have other widgets that have the ability to contain multiple widgets at the same time. Some of those widgets will inherit from a '[Gtk.Box](http://docs.go-mono.com/index.aspx?link=T%3aGtk.Box)' container widget or from the container widget directly in some cases. A Bin container widget inherits form the container widget directly as well, just like all other widget containers, but a Bin can only contain one control. -In order to have multiple widgets on our Window (since its a Bin) we need to add one of these widgets that can contain multiple widgets. There are tons of controls that can do this but we will concern ourselves at this point with a few of the basic ones like '[HBox](http://www.go-mono.com/docs/index.aspx?link=T%3aGtk.HBox)', '[VBox](http://www.go-mono.com/docs/index.aspx?link=T%3aGtk.VBox)', and maybe a '[Table](http://www.go-mono.com/docs/index.aspx?link=T%3aGtk.Table)'. +In order to have multiple widgets on our Window (since its a Bin) we need to add one of these widgets that can contain multiple widgets. There are tons of controls that can do this but we will concern ourselves at this point with a few of the basic ones like '[HBox](http://docs.go-mono.com/index.aspx?link=T%3aGtk.HBox)', '[VBox](http://docs.go-mono.com/index.aspx?link=T%3aGtk.VBox)', and maybe a '[Table](http://docs.go-mono.com/index.aspx?link=T%3aGtk.Table)'. Step 6: Adding Events --------------------- -All the classes that derive from '[Widget](http://www.go-mono.com/docs/index.aspx?link=T%3aGtk.Widget)' provide the following events: - -- [ButtonPressEvent](http://www.go-mono.com/docs/monodoc.ashx?link=E%3aGtk.Widget.ButtonPressEvent) -- [ButtonReleaseEvent](http://www.go-mono.com/docs/monodoc.ashx?link=E%3aGtk.Widget.ButtonReleaseEvent) -- [ScrollEvent](http://www.go-mono.com/docs/monodoc.ashx?link=E%3aGtk.Widget.ScrollEvent) -- [MotionNotifyEvent](http://www.go-mono.com/docs/monodoc.ashx?link=E%3aGtk.Widget.MotionNotifyEvent) -- [DeleteEvent](http://www.go-mono.com/docs/monodoc.ashx?link=E%3aGtk.Widget.DeleteEvent) -- [DestroyEvent](http://www.go-mono.com/docs/monodoc.ashx?link=E%3aGtk.Widget.DestroyEvent) -- [ExposeEvent](http://www.go-mono.com/docs/monodoc.ashx?link=E%3aGtk.Widget.ExposeEvent) -- [KeyPressEvent](http://www.go-mono.com/docs/monodoc.ashx?link=E%3aGtk.Widget.KeyPressEvent) -- [KeyReleaseEvent](http://www.go-mono.com/docs/monodoc.ashx?link=E%3aGtk.Widget.KeyReleaseEvent) -- [EnterNotifyEvent](http://www.go-mono.com/docs/monodoc.ashx?link=E%3aGtk.Widget.EnterNotifyEvent) -- [LeaveNotifyEvent](http://www.go-mono.com/docs/monodoc.ashx?link=E%3aGtk.Widget.LeaveNotifyEvent) -- [ConfigureEvent](http://www.go-mono.com/docs/monodoc.ashx?link=E%3aGtk.Widget.ConfigureEvent) -- [FocusInEvent](http://www.go-mono.com/docs/monodoc.ashx?link=E%3aGtk.Widget.FocusInEvent) -- [FocusOutEvent](http://www.go-mono.com/docs/monodoc.ashx?link=E%3aGtk.Widget.FocusOutEvent) -- [MapEvent](http://www.go-mono.com/docs/monodoc.ashx?link=E%3aGtk.Widget.MapEvent) -- [UnmapEvent](http://www.go-mono.com/docs/monodoc.ashx?link=E%3aGtk.Widget.UnmapEvent) -- [PropertyNotifyEvent](http://www.go-mono.com/docs/monodoc.ashx?link=E%3aGtk.Widget.PropertyNotifyEvent) -- [SelectionClearEvent](http://www.go-mono.com/docs/monodoc.ashx?link=E%3aGtk.Widget.SelectionClearEvent) -- [SelectionRequestEvent](http://www.go-mono.com/docs/monodoc.ashx?link=E%3aGtk.Widget.SelectionRequestEvent) -- [SelectionNotifyEvent](http://www.go-mono.com/docs/monodoc.ashx?link=E%3aGtk.Widget.SelectionNotifyEvent) -- [ProximityInEvent](http://www.go-mono.com/docs/monodoc.ashx?link=E%3aGtk.Widget.ProximityInEvent) -- [ProximityOutEvent](http://www.go-mono.com/docs/monodoc.ashx?link=E%3aGtk.Widget.ProximityOutEvent) -- [VisibilityNotifyEvent](http://www.go-mono.com/docs/monodoc.ashx?link=E%3aGtk.Widget.VisibilityNotifyEvent) -- [ClientEvent](http://www.go-mono.com/docs/monodoc.ashx?link=E%3aGtk.Widget.ClientEvent) -- [NoExposeEvent](http://www.go-mono.com/docs/monodoc.ashx?link=E%3aGtk.Widget.NoExposeEvent) -- [WindowStateEvent](http://www.go-mono.com/docs/monodoc.ashx?link=E%3aGtk.Widget.WindowStateEvent) +All the classes that derive from '[Widget](http://docs.go-mono.com/index.aspx?link=T%3aGtk.Widget)' provide the following events: + +- [ButtonPressEvent](http://docs.go-mono.com/monodoc.ashx?link=E%3aGtk.Widget.ButtonPressEvent) +- [ButtonReleaseEvent](http://docs.go-mono.com/monodoc.ashx?link=E%3aGtk.Widget.ButtonReleaseEvent) +- [ScrollEvent](http://docs.go-mono.com/monodoc.ashx?link=E%3aGtk.Widget.ScrollEvent) +- [MotionNotifyEvent](http://docs.go-mono.com/monodoc.ashx?link=E%3aGtk.Widget.MotionNotifyEvent) +- [DeleteEvent](http://docs.go-mono.com/monodoc.ashx?link=E%3aGtk.Widget.DeleteEvent) +- [DestroyEvent](http://docs.go-mono.com/monodoc.ashx?link=E%3aGtk.Widget.DestroyEvent) +- [ExposeEvent](http://docs.go-mono.com/monodoc.ashx?link=E%3aGtk.Widget.ExposeEvent) +- [KeyPressEvent](http://docs.go-mono.com/monodoc.ashx?link=E%3aGtk.Widget.KeyPressEvent) +- [KeyReleaseEvent](http://docs.go-mono.com/monodoc.ashx?link=E%3aGtk.Widget.KeyReleaseEvent) +- [EnterNotifyEvent](http://docs.go-mono.com/monodoc.ashx?link=E%3aGtk.Widget.EnterNotifyEvent) +- [LeaveNotifyEvent](http://docs.go-mono.com/monodoc.ashx?link=E%3aGtk.Widget.LeaveNotifyEvent) +- [ConfigureEvent](http://docs.go-mono.com/monodoc.ashx?link=E%3aGtk.Widget.ConfigureEvent) +- [FocusInEvent](http://docs.go-mono.com/monodoc.ashx?link=E%3aGtk.Widget.FocusInEvent) +- [FocusOutEvent](http://docs.go-mono.com/monodoc.ashx?link=E%3aGtk.Widget.FocusOutEvent) +- [MapEvent](http://docs.go-mono.com/monodoc.ashx?link=E%3aGtk.Widget.MapEvent) +- [UnmapEvent](http://docs.go-mono.com/monodoc.ashx?link=E%3aGtk.Widget.UnmapEvent) +- [PropertyNotifyEvent](http://docs.go-mono.com/monodoc.ashx?link=E%3aGtk.Widget.PropertyNotifyEvent) +- [SelectionClearEvent](http://docs.go-mono.com/monodoc.ashx?link=E%3aGtk.Widget.SelectionClearEvent) +- [SelectionRequestEvent](http://docs.go-mono.com/monodoc.ashx?link=E%3aGtk.Widget.SelectionRequestEvent) +- [SelectionNotifyEvent](http://docs.go-mono.com/monodoc.ashx?link=E%3aGtk.Widget.SelectionNotifyEvent) +- [ProximityInEvent](http://docs.go-mono.com/monodoc.ashx?link=E%3aGtk.Widget.ProximityInEvent) +- [ProximityOutEvent](http://docs.go-mono.com/monodoc.ashx?link=E%3aGtk.Widget.ProximityOutEvent) +- [VisibilityNotifyEvent](http://docs.go-mono.com/monodoc.ashx?link=E%3aGtk.Widget.VisibilityNotifyEvent) +- [ClientEvent](http://docs.go-mono.com/monodoc.ashx?link=E%3aGtk.Widget.ClientEvent) +- [NoExposeEvent](http://docs.go-mono.com/monodoc.ashx?link=E%3aGtk.Widget.NoExposeEvent) +- [WindowStateEvent](http://docs.go-mono.com/monodoc.ashx?link=E%3aGtk.Widget.WindowStateEvent) Many of these events can be handled with a standard event handler. For example: diff --git a/docs/gui/gtksharp/index.md b/docs/gui/gtksharp/index.md index 5d47342cb..82ec37ee3 100644 --- a/docs/gui/gtksharp/index.md +++ b/docs/gui/gtksharp/index.md @@ -17,7 +17,7 @@ Gtk# is a Graphical User Interface Toolkit for mono and .Net. The project binds References ---------- -- [Online API Documentation](http://www.go-mono.com/docs/monodoc.ashx?link=root:/classlib-gnome) +- [Online API Documentation](http://docs.go-mono.com/monodoc.ashx?link=root:/classlib-gnome) - [What's New?](/docs/gui/gtksharp/new-in-version-2x/) - [Release Plans](/docs/gui/gtksharp/plan/) - [Articles and Tutorials on Gtk#](/docs/gui/gtksharp/tutorials/) diff --git a/docs/tools+libraries/libraries/Mono.Cairo/index.md b/docs/tools+libraries/libraries/Mono.Cairo/index.md index 1ec38c7e5..b351f074c 100644 --- a/docs/tools+libraries/libraries/Mono.Cairo/index.md +++ b/docs/tools+libraries/libraries/Mono.Cairo/index.md @@ -27,7 +27,7 @@ To use Cairo in Gdk/Gtk applications, a `Context` with a `Gdk.Drawable` target s - A second choice (recommended for older versions of Gtk) is to use a function provided in the [Mono.Cairo samples](https://github.com/mono/mono/tree/master/mcs/class/Mono.Cairo/Samples). This will work on all platforms and with older Gdk versions. The code in question resides in [sysdraw.cs](https://github.com/mono/mono/blob/master/mcs/class/Mono.Cairo/Samples/gtk/sysdraw.cs) and you can simply download & use this file in your project. -The best place to create and use the `Context` is the [ExposeEvent](http://www.go-mono.com/docs/monodoc.ashx?tlink=5@ecma%3a1351%23Widget%2fE%2f26) for the given widget. Usually you'll want to use the [Gtk.DrawingArea](http://www.go-mono.com/docs/monodoc.ashx?tlink=5@ecma%3a838%23DrawingArea%2f) for this task. An example implementation of the Expose event method: +The best place to create and use the `Context` is the [ExposeEvent](http://docs.go-mono.com/monodoc.ashx?tlink=5@ecma%3a1351%23Widget%2fE%2f26) for the given widget. Usually you'll want to use the [Gtk.DrawingArea](http://docs.go-mono.com/monodoc.ashx?tlink=5@ecma%3a838%23DrawingArea%2f) for this task. An example implementation of the Expose event method: ``` csharp void OnDrawingAreaExposed (object o, ExposeEventArgs args) @@ -46,7 +46,7 @@ Notice that `Surface` (the target the `Context` is actually drawing to), as well ### Drawing simple primitives -Cairo drawing model works very much like a plotting machine. An abstract pen moves around the `Surface` area drawing lines and curves. The basic functions to handle the "plotting" are: [MoveTo](http://www.go-mono.com/docs/monodoc.ashx?tlink=0@ecma%3a15%23Graphics%2fM%2f7), [LineTo](http://www.go-mono.com/docs/monodoc.ashx?tlink=0@ecma%3a15%23Graphics%2fM%2f8), [CurveTo](http://www.go-mono.com/docs/monodoc.ashx?tlink=0@ecma%3a15%23Graphics%2fM%2f9). These functions take [PointD](http://www.go-mono.com/docs/monodoc.ashx?tlink=0@ecma%3a26%23PointD%2f) objects as the arguments. `PointD` is a two-dimensional coordinate where `X` and `Y` are expressed as `double`. +Cairo drawing model works very much like a plotting machine. An abstract pen moves around the `Surface` area drawing lines and curves. The basic functions to handle the "plotting" are: [MoveTo](http://docs.go-mono.com/monodoc.ashx?tlink=0@ecma%3a15%23Graphics%2fM%2f7), [LineTo](http://docs.go-mono.com/monodoc.ashx?tlink=0@ecma%3a15%23Graphics%2fM%2f8), [CurveTo](http://docs.go-mono.com/monodoc.ashx?tlink=0@ecma%3a15%23Graphics%2fM%2f9). These functions take [PointD](http://docs.go-mono.com/monodoc.ashx?tlink=0@ecma%3a26%23PointD%2f) objects as the arguments. `PointD` is a two-dimensional coordinate where `X` and `Y` are expressed as `double`. - `Context.MoveTo (PointD coordinate)` will position the cursor/pen at the given coordinate - `Context.LineTo (PointD coordinate)` will make a straight line from the current pen position to the given coordinate. After calling this function the pen is located at the given coordinate. @@ -109,19 +109,19 @@ void OnDrawingAreaExposed (object o, ExposeEventArgs args) I used `FillPreserve` method instead of `Fill` because the latter destroys the current path. If you want to keep the path use `StrokePreserve` and `FillPreserve`. -Take a look at the [Graphics class members](http://www.go-mono.com/docs/monodoc.ashx?tlink=0@ecma%3a15%23Graphics%2f%2a) for other functions used to outline paths (ie. `ArcTo`, `Rectangle`). +Take a look at the [Graphics class members](http://docs.go-mono.com/monodoc.ashx?tlink=0@ecma%3a15%23Graphics%2f%2a) for other functions used to outline paths (ie. `ArcTo`, `Rectangle`). ### Saving and restoring the Cairo state As you have already noticed, most of the drawing parameters are controlled in a state-based manner. Various `Graphics` properties you can set include: -- [Color](http://www.go-mono.com/docs/monodoc.ashx?tlink=0@ecma%3a15%23Graphics%2fP%2f3) -- to set the stroke/fill color. Color values (Red, Green, Blue, Alpha) are expressed in a 0 - 1 range (as `double`). -- [LineWidth](http://www.go-mono.com/docs/monodoc.ashx?tlink=0@ecma%3a15%23Graphics%2fP%2f7) -- to control the width of the stroke line. -- [LineCap](http://www.go-mono.com/docs/monodoc.ashx?tlink=0@ecma%3a15%23Graphics%2fP%2f8) -- controls the line capping (round, square, etc.) +- [Color](http://docs.go-mono.com/monodoc.ashx?tlink=0@ecma%3a15%23Graphics%2fP%2f3) -- to set the stroke/fill color. Color values (Red, Green, Blue, Alpha) are expressed in a 0 - 1 range (as `double`). +- [LineWidth](http://docs.go-mono.com/monodoc.ashx?tlink=0@ecma%3a15%23Graphics%2fP%2f7) -- to control the width of the stroke line. +- [LineCap](http://docs.go-mono.com/monodoc.ashx?tlink=0@ecma%3a15%23Graphics%2fP%2f8) -- controls the line capping (round, square, etc.) This state-based approach is far more convenient than specifying all drawing parameters in a single function call (like it's done ie. in the low-level Gdk drawing methods). However, once you started creating your own custom drawing functions, you'll notice that it's hard to control all the state modifications spanned across multiple methods. In most cases you will not want to care about certain state modifiers assuming they're unset. -Cairo provides us with methods to control the state stack. The respective `Graphics` members are [Save](http://www.go-mono.com/docs/monodoc.ashx?tlink=0@ecma%3a15%23Graphics%2fM%2f2) and [Restore](http://www.go-mono.com/docs/monodoc.ashx?tlink=0@ecma%3a15%23Graphics%2fM%2f3). +Cairo provides us with methods to control the state stack. The respective `Graphics` members are [Save](http://docs.go-mono.com/monodoc.ashx?tlink=0@ecma%3a15%23Graphics%2fM%2f2) and [Restore](http://docs.go-mono.com/monodoc.ashx?tlink=0@ecma%3a15%23Graphics%2fM%2f3). `Context.Save` will copy the current state and push the copy on the top of the stack. `Context.Restore` will pop one state back from the stack. Clearly all the state-altering calls placed inside `Save`/`Restore` parenthesis are local. diff --git a/docs/tools+libraries/libraries/Mono.Cairo/tutorial.md b/docs/tools+libraries/libraries/Mono.Cairo/tutorial.md index 971b7039c..315af5661 100644 --- a/docs/tools+libraries/libraries/Mono.Cairo/tutorial.md +++ b/docs/tools+libraries/libraries/Mono.Cairo/tutorial.md @@ -142,7 +142,7 @@ In order to create an image you desire, you have to prepare the [context](http:/ ### Preparing and Selecting a Source -There are three main kinds of sources in cairo: colors, gradients, and images. Colors are the simplest; they use a uniform hue and opacity for the entire source. You can select these without any preparation by setting the [Color](http://www.go-mono.com/docs/monodoc.ashx?link=P%3aCairo.Context.Color) property. +There are three main kinds of sources in cairo: colors, gradients, and images. Colors are the simplest; they use a uniform hue and opacity for the entire source. You can select these without any preparation by setting the [Color](http://docs.go-mono.com/monodoc.ashx?link=P%3aCairo.Context.Color) property. [![Cairo_setsourcergba.png](/archived/images/c/cb/Cairo_setsourcergba.png)](/archived/images/c/cb/Cairo_setsourcergba.png) @@ -205,7 +205,7 @@ Cairo always has an active path. If you call [Stroke](#stroke) it will draw the What if you want to do multiple things with the same path? For instance to draw a red rectangle with a black border, you would want to fill the rectangle path with a red source, then stroke the same path with a black source. A rectangle path is easy to create multiple times, but a lot of paths are more complex. -Cairo supports easily reusing paths by having alternate versions of its operations. Both draw the same thing, but the alternate doesn't reset the path. For stroking, alongside [Stroke](http://www.go-mono.com/docs/monodoc.ashx?tlink=0@ecma%3a4%23Context%2fM%2f14) there is [Stroke Preserve](http://www.go-mono.com/docs/monodoc.ashx?tlink=0@ecma%3a4%23Context%2fM%2f28); for filling, [FillPreserve](http://www.go-mono.com/docs/monodoc.ashx?tlink=0@ecma%3a4%23Context%2fM%2f16) joins [Fill](http://www.go-mono.com/docs/index.aspx?tlink=0@ecma%3a4%23Context%2fM%2f15). Even setting the clip has a preserve variant. Apart from choosing when to preserve your path, there are only a couple common operations. +Cairo supports easily reusing paths by having alternate versions of its operations. Both draw the same thing, but the alternate doesn't reset the path. For stroking, alongside [Stroke](http://docs.go-mono.com/monodoc.ashx?tlink=0@ecma%3a4%23Context%2fM%2f14) there is [Stroke Preserve](http://docs.go-mono.com/monodoc.ashx?tlink=0@ecma%3a4%23Context%2fM%2f28); for filling, [FillPreserve](http://docs.go-mono.com/monodoc.ashx?tlink=0@ecma%3a4%23Context%2fM%2f16) joins [Fill](http://docs.go-mono.com/index.aspx?tlink=0@ecma%3a4%23Context%2fM%2f15). Even setting the clip has a preserve variant. Apart from choosing when to preserve your path, there are only a couple common operations. #### Moving @@ -252,7 +252,7 @@ Cairo can also close the path by drawing a straight line to the beginning of the #### Text -Finally text can be turned into a path with [TextPath](http://docs.go-mono.com/?link=M%3aCairo.Context.TextPath). Paths created from text are like any other path, supporting stroke or fill operations. This path is placed anchored to the current reference point, so [MoveTo](#moving) your desired location before turning text into a path. However there are performance concerns to doing this if you are working with a lot of text; when possible you should prefer using the verb [ShowText](#show-text--glyphs) over TextPath and [Fill](http://www.go-mono.com/docs/index.aspx?tlink=0@ecma%3a4%23Context%2fM%2f15). +Finally text can be turned into a path with [TextPath](http://docs.go-mono.com/?link=M%3aCairo.Context.TextPath). Paths created from text are like any other path, supporting stroke or fill operations. This path is placed anchored to the current reference point, so [MoveTo](#moving) your desired location before turning text into a path. However there are performance concerns to doing this if you are working with a lot of text; when possible you should prefer using the verb [ShowText](#show-text--glyphs) over TextPath and [Fill](http://docs.go-mono.com/index.aspx?tlink=0@ecma%3a4%23Context%2fM%2f15). Understanding Text ------------------ @@ -261,13 +261,13 @@ Understanding Text [View Source](http://mgsloan.nfshost.com/cairo_tut/textextents.cs) -To use text effectively you need to know where it will go. The methods [FontExtents](http://www.go-mono.com/docs/monodoc.ashx?link=P%3aCairo.Context.FontExtents) and [TextExtents](http://www.go-mono.com/docs/monodoc.ashx?link=M%3aCairo.Context.TextExtents(System.String)) get you this information. Since this diagram is hard to see so small, I suggest getting its [source](http://mgsloan.nfshost.com/cairo_tut/textextents.cs) and bump the size up to 600. It shows the relation between the reference point (red dot); suggested next reference point (blue dot); bounding box (dashed blue lines); bearing displacement (solid blue line); and height, ascent, baseline, and descent lines (dashed green). +To use text effectively you need to know where it will go. The methods [FontExtents](http://docs.go-mono.com/monodoc.ashx?link=P%3aCairo.Context.FontExtents) and [TextExtents](http://docs.go-mono.com/monodoc.ashx?link=M%3aCairo.Context.TextExtents(System.String)) get you this information. Since this diagram is hard to see so small, I suggest getting its [source](http://mgsloan.nfshost.com/cairo_tut/textextents.cs) and bump the size up to 600. It shows the relation between the reference point (red dot); suggested next reference point (blue dot); bounding box (dashed blue lines); bearing displacement (solid blue line); and height, ascent, baseline, and descent lines (dashed green). The reference point is always on the baseline. The descent line is below that, and reflects a rough bounding box for all characters in the font. However it is an artistic choice intended to indicate alignment rather than a true bounding box. The same is true for the ascent line above. Next above that is the height line, the artist-recommended spacing between subsequent baselines. All three of these are reported as distances from the baseline, and expected to be positive despite their differing directions. The bearing is the displacement from the reference point to the upper-left corner of the bounding box. It is often zero or a small positive value for x displacement, but can be negative x for characters like j as shown; it's almost always a negative value for y displacement. The width and height then describe the size of the bounding box. The advance takes you to the suggested reference point for the next letter. Note that bounding boxes for subsequent blocks of text can overlap if the bearing is negative, or the advance is smaller than the width would suggest. -In addition to placement, you also need to specify a face, style, and size. Set the face and style together with [SelectFontFace](http://docs.go-mono.com/?link=M%3aCairo.Context.SelectFontFace), and the size with [SetFontSize](http://docs.go-mono.com/?link=M%3aCairo.Context.SetFontSize). If you need even finer control, try modifying a [FontOptions struct](http://www.go-mono.com/docs/monodoc.ashx?link=T%3aCairo.FontOptions) with [FontOptions property](http://www.go-mono.com/docs/monodoc.ashx?tlink=0@ecma%3a4%23Context%2fP%2f19). +In addition to placement, you also need to specify a face, style, and size. Set the face and style together with [SelectFontFace](http://docs.go-mono.com/?link=M%3aCairo.Context.SelectFontFace), and the size with [SetFontSize](http://docs.go-mono.com/?link=M%3aCairo.Context.SetFontSize). If you need even finer control, try modifying a [FontOptions struct](http://docs.go-mono.com/monodoc.ashx?link=T%3aCairo.FontOptions) with [FontOptions property](http://docs.go-mono.com/monodoc.ashx?tlink=0@ecma%3a4%23Context%2fP%2f19). Working with Transforms ----------------------- diff --git a/docs/tools+libraries/tools/mdassembler.md b/docs/tools+libraries/tools/mdassembler.md index d02990e29..9abbad1cf 100644 --- a/docs/tools+libraries/tools/mdassembler.md +++ b/docs/tools+libraries/tools/mdassembler.md @@ -4,7 +4,7 @@ redirect_from: - /Assembler/ --- -The **assembler** is a tool to merge mdoc/monodocer output into three files. Since [mdoc](/docs/tools+libraries/tools/mdoc/) and [monodocer](/docs/tools+libraries/tools/monodocer/) produces tons of output files this is very unhandy to redistribute. Additionally, the documentation can not be shown in [monodoc](/docs/tools+libraries/tools/monodoc/) by just clicking it's icon you have to type *monodoc mydocs-folder* into your console. The **assembler** can be invoked by using [mdoc-assemble](http://www.go-mono.org/docs/index.aspx?link=man:mdoc-assemble(1)) or (for older Mono versions) with the **mdassembler** command. +The **assembler** is a tool to merge mdoc/monodocer output into three files. Since [mdoc](/docs/tools+libraries/tools/mdoc/) and [monodocer](/docs/tools+libraries/tools/monodocer/) produces tons of output files this is very unhandy to redistribute. Additionally, the documentation can not be shown in [monodoc](/docs/tools+libraries/tools/monodoc/) by just clicking it's icon you have to type *monodoc mydocs-folder* into your console. The **assembler** can be invoked by using [mdoc-assemble](http://docs.go-mono.com/index.aspx?link=man:mdoc-assemble(1)) or (for older Mono versions) with the **mdassembler** command. Usage ===== diff --git a/docs/tools+libraries/tools/mdoc.md b/docs/tools+libraries/tools/mdoc.md index 494eebdda..6a9f6f3d3 100644 --- a/docs/tools+libraries/tools/mdoc.md +++ b/docs/tools+libraries/tools/mdoc.md @@ -16,13 +16,13 @@ mdoc Commands The following are links to the mdoc man pages: -- [mdoc(1)](http://www.go-mono.org/docs/monodoc.ashx?link=man:mdoc(1)): Front-end to all other *mdoc* commands. *mdoc assemble* is equivalent to *mdoc-assemble*. -- [mdoc-assemble(1)](http://www.go-mono.org/docs/monodoc.ashx?link=man:mdoc-assemble(1)): Assembles a directory of [mdoc(5)](http://www.go-mono.org/docs/monodoc.ashx?link=man:mdoc(5))-formated XML documentation into a *.zip* file for display in [monodoc](/docs/tools+libraries/tools/monodoc/). +- [mdoc(1)](http://docs.go-mono.com/monodoc.ashx?link=man:mdoc(1)): Front-end to all other *mdoc* commands. *mdoc assemble* is equivalent to *mdoc-assemble*. +- [mdoc-assemble(1)](http://docs.go-mono.com/monodoc.ashx?link=man:mdoc-assemble(1)): Assembles a directory of [mdoc(5)](http://docs.go-mono.com/monodoc.ashx?link=man:mdoc(5))-formated XML documentation into a *.zip* file for display in [monodoc](/docs/tools+libraries/tools/monodoc/). - Equivalent to [Assembler](/docs/tools+libraries/tools/mdassembler/). -- [mdoc-export-html(1)](http://www.go-mono.org/docs/monodoc.ashx?link=man:mdoc-export-html(1)): Exports [mdoc(5)](http://www.go-mono.org/docs/monodoc.ashx?link=man:mdoc(5)) documentation into a set of static HTML files. +- [mdoc-export-html(1)](http://docs.go-mono.com/monodoc.ashx?link=man:mdoc-export-html(1)): Exports [mdoc(5)](http://docs.go-mono.com/monodoc.ashx?link=man:mdoc(5)) documentation into a set of static HTML files. - Equivalent to [monodocs2html](/docs/tools+libraries/tools/monodoc/generating-documentation/#generating-static-html-documentation) -- [mdoc-export-msxdoc(1)](http://www.go-mono.org/docs/monodoc.ashx?link=man:mdoc-export-msxdoc(1)): Exports [mdoc(5)](http://www.go-mono.org/docs/monodoc.ashx?link=man:mdoc(5)) documentation into a single Microsoft XML documentation file for use with Visual Studio and other documentation systems. -- [mdoc-update(1)](http://www.go-mono.org/docs/monodoc.ashx?link=man:mdoc-update(1)): Updates existing [mdoc(5)](http://www.go-mono.org/docs/monodoc.ashx?link=man:mdoc(5)) documentation to reflect changes within a set of assemblies. +- [mdoc-export-msxdoc(1)](http://docs.go-mono.com/monodoc.ashx?link=man:mdoc-export-msxdoc(1)): Exports [mdoc(5)](http://docs.go-mono.com/monodoc.ashx?link=man:mdoc(5)) documentation into a single Microsoft XML documentation file for use with Visual Studio and other documentation systems. +- [mdoc-update(1)](http://docs.go-mono.com/monodoc.ashx?link=man:mdoc-update(1)): Updates existing [mdoc(5)](http://docs.go-mono.com/monodoc.ashx?link=man:mdoc(5)) documentation to reflect changes within a set of assemblies. - Equivalent to [monodocer](/docs/tools+libraries/tools/monodocer/). -- [mdoc-validate(1)](http://www.go-mono.org/docs/monodoc.ashx?link=man:mdoc-validate(1)): Validates the [mdoc(5)](http://www.go-mono.org/docs/monodoc.ashx?link=man:mdoc(5)) XML against the *mdoc*(5) schema. +- [mdoc-validate(1)](http://docs.go-mono.com/monodoc.ashx?link=man:mdoc-validate(1)): Validates the [mdoc(5)](http://docs.go-mono.com/monodoc.ashx?link=man:mdoc(5)) XML against the *mdoc*(5) schema. - Equivalent to [mdvalidater](/docs/tools+libraries/tools/monodoc/generating-documentation/#validate-monodoc-xml-format). diff --git a/docs/tools+libraries/tools/monodoc/editing.md b/docs/tools+libraries/tools/monodoc/editing.md index 21f0e6fd6..d2658267c 100644 --- a/docs/tools+libraries/tools/monodoc/editing.md +++ b/docs/tools+libraries/tools/monodoc/editing.md @@ -7,7 +7,7 @@ redirect_from: Writing XML Documentation ========================= -See the [mdoc(5)](http://www.go-mono.org/docs/monodoc.ashx?link=man:mdoc(5)) man page for more details about monodoc XML file format and document markup. +See the [mdoc(5)](http://docs.go-mono.com/monodoc.ashx?link=man:mdoc(5)) man page for more details about monodoc XML file format and document markup. The following tags can be used inside the \ and \ sections of your documentation. diff --git a/docs/tools+libraries/tools/monodoc/generating-documentation.md b/docs/tools+libraries/tools/monodoc/generating-documentation.md index 8031c1ee6..b927902bc 100644 --- a/docs/tools+libraries/tools/monodoc/generating-documentation.md +++ b/docs/tools+libraries/tools/monodoc/generating-documentation.md @@ -90,7 +90,7 @@ will give us the following directory content: |- ImportantBClass.xml |- AnotherBClass.xml -As the documentation is an [XML format](http://www.go-mono.org/docs/monodoc.ashx?link=man:mdoc(5)), you can edit it directly, though it is easier to use the [Monodoc](/docs/tools+libraries/tools/monodoc/) browser. Just after creating the documentation with [monodocer](/docs/tools+libraries/tools/monodocer/), you can start navigating or [editing](#edit-and-write-documentation) it by typing: +As the documentation is an [XML format](http://docs.go-mono.com/monodoc.ashx?link=man:mdoc(5)), you can edit it directly, though it is easier to use the [Monodoc](/docs/tools+libraries/tools/monodoc/) browser. Just after creating the documentation with [monodocer](/docs/tools+libraries/tools/monodocer/), you can start navigating or [editing](#edit-and-write-documentation) it by typing: ``` bash monodoc --edit docfiles @@ -124,7 +124,7 @@ will insert a `` element for *every* type and member that This is useful when you need to distinguish which members were added in later versions of an assembly. -Both [monodocer](/docs/tools+libraries/tools/monodocer/) and [mdoc-update](/docs/tools+libraries/tools/mdoc/) insert the assembly versions that each member was found in, and the list of assembly versions is also displayed within [monodoc](/docs/tools+libraries/tools/monodoc/) and [http://www.go-mono.com/docs](http://www.go-mono.com/docs), for example the **Requirements** section at the [System.Environment documentation](http://www.go-mono.com/docs/monodoc.ashx?link=T:System.Environment). +Both [monodocer](/docs/tools+libraries/tools/monodocer/) and [mdoc-update](/docs/tools+libraries/tools/mdoc/) insert the assembly versions that each member was found in, and the list of assembly versions is also displayed within [monodoc](/docs/tools+libraries/tools/monodoc/) and [http://docs.go-mono.com/](http://docs.go-mono.com/), for example the **Requirements** section at the [System.Environment documentation](http://docs.go-mono.com/monodoc.ashx?link=T:System.Environment). Assemble the generated Documentation ------------------------------------ @@ -157,7 +157,7 @@ The above two commands will create the files *lib.tree* and *lib.zip*. Now, we c The *provider* attribute tells the browser which kind of documentation is within the *lib.zip* file. When editing library documentation it should always be *ecma*. The *provider* attribute MUST match the format provided to [mdassembler](/docs/tools+libraries/tools/mdassembler/) or [mdoc-assemble](/docs/tools+libraries/tools/mdoc/). -Other documentation formats are supported as well; see [mdoc-assemble(1)](http://www.go-mono.com/docs/monodoc.ashx?link=man:mdoc-assemble(1)) for details. +Other documentation formats are supported as well; see [mdoc-assemble(1)](http://docs.go-mono.com/monodoc.ashx?link=man:mdoc-assemble(1)) for details. The *basefile* attribute tells the browser where to find that documentation; it is the base name of your .zip and .tree files. diff --git a/docs/tools+libraries/tools/monodoc/index.md b/docs/tools+libraries/tools/monodoc/index.md index d695c0eb9..9597d8d63 100644 --- a/docs/tools+libraries/tools/monodoc/index.md +++ b/docs/tools+libraries/tools/monodoc/index.md @@ -37,7 +37,7 @@ Of course, more documentation sources can be added from installed libraries or f Online Documentation -------------------- -You can view the complete documentation library online (only API documentation) at [http://www.go-mono.com/docs/](http://www.go-mono.com/docs/). +You can view the complete documentation library online (only API documentation) at [http://docs.go-mono.com/](http://docs.go-mono.com/). Mod (Command-Line Documentation Viewer) ---------------------------------------