Skip to content

Commit

Permalink
Update nuget and assembly descriptions
Browse files Browse the repository at this point in the history
Don't publish Mac64 - it is only usable with a custom compiled mono at this point.
  • Loading branch information
cwensley committed Nov 14, 2014
1 parent c31d009 commit f9a88e2
Show file tree
Hide file tree
Showing 19 changed files with 91 additions and 85 deletions.
2 changes: 1 addition & 1 deletion Resources/Publish.targets
Original file line number Diff line number Diff line change
Expand Up @@ -151,7 +151,7 @@
<MSBuild Targets="PublishPackage" Properties="NupkgName=Eto.Platform.Gtk.$(AssemblyVersion).nupkg;TargetDir=$(TargetDir)" Projects="$(MSBuildProjectFile)"/>
<MSBuild Targets="PublishPackage" Properties="NupkgName=Eto.Platform.Gtk3.$(AssemblyVersion).nupkg;TargetDir=$(TargetDir)" Projects="$(MSBuildProjectFile)"/>
<MSBuild Targets="PublishPackage" Properties="NupkgName=Eto.Platform.Mac.$(AssemblyVersion).nupkg;TargetDir=$(TargetDir)" Projects="$(MSBuildProjectFile)"/>
<MSBuild Targets="PublishPackage" Properties="NupkgName=Eto.Platform.Mac64.$(AssemblyVersion).nupkg;TargetDir=$(TargetDir)" Projects="$(MSBuildProjectFile)"/>
<!--MSBuild Targets="PublishPackage" Properties="NupkgName=Eto.Platform.Mac64.$(AssemblyVersion).nupkg;TargetDir=$(TargetDir)" Projects="$(MSBuildProjectFile)"/-->
<MSBuild Targets="PublishPackage" Properties="NupkgName=Eto.Platform.Windows.$(AssemblyVersion).nupkg;TargetDir=$(TargetDir)" Projects="$(MSBuildProjectFile)"/>
<MSBuild Targets="PublishPackage" Properties="NupkgName=Eto.Platform.Wpf.$(AssemblyVersion).nupkg;TargetDir=$(TargetDir)" Projects="$(MSBuildProjectFile)"/>
<MSBuild Targets="PublishPackage" Properties="NupkgName=Eto.Platform.XamMac.$(AssemblyVersion).nupkg;TargetDir=$(TargetDir)" Projects="$(MSBuildProjectFile)"/>
Expand Down
8 changes: 5 additions & 3 deletions Resources/nuspec/Eto.Forms.Sample/Eto.Forms.Sample.nuspec
Original file line number Diff line number Diff line change
Expand Up @@ -11,11 +11,13 @@
<requireLicenseAcceptance>false</requireLicenseAcceptance>
<summary>Eto.Forms - Sample Cross Platform Application</summary>
<description>
This sample application provides a starting point for your Eto.Forms application.
This sample application provides a starting point for your Eto.Forms application.

Add this package to a blank console application, then delete the Program.cs of the existing application to use MyEtoApplication.Main() as your program startup.
Add this package to a blank console application, which will replace your Program.cs with the Eto.Forms startup code and include a MainForm.cs as a sample form to get you started.

You should also change the console application's output type to 'Windows Application' to suppress the console window from showing.
You will need to change the console application's output type to 'Windows Application' to suppress the console window from showing.

In Xamarin Studio, set the compile target to 'Executable with GUI' and uncheck 'Run on external console' in Run &gt; Build.
</description>
<copyright>Copyright 2014 by Curtis Wensley</copyright>
<tags>cross platform gui framework desktop winforms wpf mac osx gtk eto.forms sample</tags>
Expand Down
12 changes: 6 additions & 6 deletions Resources/nuspec/Eto.Platform.Direct2D.nuspec
Original file line number Diff line number Diff line change
Expand Up @@ -4,20 +4,20 @@
<id>Eto.Platform.Direct2D</id>
<version>$version$</version>
<title>$title$</title>
<authors>Picoe Software Solutions Inc.</authors>
<owners>Picoe Software Solutions Inc.</owners>
<authors>$author$</authors>
<owners>$author$</owners>
<licenseUrl>https://github.com/picoe/Eto/raw/master/LICENSE</licenseUrl>
<projectUrl>https://github.com/picoe/Eto</projectUrl>
<requireLicenseAcceptance>false</requireLicenseAcceptance>
<summary>$description$</summary>
<description>
This is the Direct2D platform for Eto.Forms UI Framework.
This is the Direct2D platform for Eto.Forms UI Framework.

Include this along with your Eto.Forms application to provide a WinForms interface with Direct2D drawing for your windows users.
Include this along with your Eto.Forms application to provide a WinForms interface with Direct2D drawing for your windows users.

The Direct2D platform allows for increased performance when custom drawing by using the GPU. This does not affect the behaviour or performance of regular controls, which will use the Windows Forms platform.
The Direct2D platform allows for increased performance when custom drawing by using the GPU. This does not affect the behaviour or performance of regular controls, which will use the Windows Forms platform.

You do not need to use any of the classes of this assembly (unless customizing the functionality of the platform), and should just use the UI controls from the Eto assembly.
You do not need to use any of the classes of this assembly (unless customizing the functionality of the platform), and should just use the UI controls from the Eto assembly.
</description>
<copyright>$copyright$</copyright>
<tags>cross platform gui ui framework desktop wpf eto.forms</tags>
Expand Down
8 changes: 4 additions & 4 deletions Resources/nuspec/Eto.Platform.Gtk.nuspec
Original file line number Diff line number Diff line change
Expand Up @@ -11,13 +11,13 @@
<requireLicenseAcceptance>false</requireLicenseAcceptance>
<summary>$description$</summary>
<description>
This is the GTK2 platform for Eto.Forms UI Framework.
This is the GTK2 platform for Eto.Forms UI Framework.

Include this along with your Eto.Forms application to provide a GTK interface, typically for Linux users.
Include this along with your Eto.Forms application to provide a GTK2 interface, typically for Linux users.

You do not need to use any of the classes of this assembly (unless customizing the GTK functionality of the platform), and should just use the UI controls from the Eto assembly.
You do not need to use any of the classes of this assembly (unless customizing the GTK functionality of the platform), and should just use the UI controls from the Eto assembly.

On Linux, mono framework 2.10 or higher and gtk-sharp2 are required.
On Linux, mono framework 2.10 or higher and gtk-sharp2 are required.
</description>
<copyright>$copyright$</copyright>
<tags>cross platform gui ui framework desktop gtk eto.forms</tags>
Expand Down
8 changes: 4 additions & 4 deletions Resources/nuspec/Eto.Platform.Gtk3.nuspec
Original file line number Diff line number Diff line change
Expand Up @@ -11,13 +11,13 @@
<requireLicenseAcceptance>false</requireLicenseAcceptance>
<summary>$description$</summary>
<description>
This is the GTK3 platform for Eto.Forms UI Framework.
This is the GTK3 platform for Eto.Forms UI Framework.

Include this along with your Eto.Forms application to provide a GTK interface, typically for Linux users.
Include this along with your Eto.Forms application to provide a GTK3 interface, typically for Linux users.

You do not need to use any of the classes of this assembly (unless customizing the GTK functionality of the platform), and should just use the UI controls from the Eto assembly.
You do not need to use any of the classes of this assembly (unless customizing the GTK functionality of the platform), and should just use the UI controls from the Eto assembly.

On Linux, mono framework 2.10 or higher and gtk-sharp2 are required.
On Linux, mono framework 2.10 or higher and gtk-sharp2 are required.
</description>
<copyright>$copyright$</copyright>
<tags>cross platform gui ui framework desktop gtk eto.forms</tags>
Expand Down
12 changes: 6 additions & 6 deletions Resources/nuspec/Eto.Platform.Mac.nuspec
Original file line number Diff line number Diff line change
Expand Up @@ -11,17 +11,17 @@
<requireLicenseAcceptance>false</requireLicenseAcceptance>
<summary>$description$</summary>
<description>
This is the MonoMac platform for Eto.Forms UI Framework.
This is the MonoMac platform for Eto.Forms UI Framework.

Include this along with your Eto.Forms application to provide an OS X interface for Mac users.
Include this along with your Eto.Forms application to provide an OS X interface for Mac users.

Eto.Platform.Mac uses the open source MonoMac, which allows you to create OS X Applications with no cost. However, it does require mono to be installed.
Eto.Platform.Mac uses the open source MonoMac, which allows you to create OS X Applications with no cost. However, it does require mono to be installed.

Using Eto.Platform.XamMac instead allows you to bundle mono inside your .app, however it requires purchasing Xamarin.Mac and using Xamarin Studio on OS X.
Using Eto.Platform.XamMac instead allows you to bundle mono inside your .app, however it requires purchasing Xamarin.Mac and using Xamarin Studio on OS X.

You can create your own .app bundle to run your app on OS X, without an OS X machine. This is included as the MyApp.app folder. Read MyApp.app\Contents\MonoBundle\README.txt for instructions on next steps.
You can create your own .app bundle to run your app on OS X, without using a Mac. Use the Eto.Platform.Mac.Template nuget package to build one for your app automatically.

You do not need to use any of the classes of this assembly (unless customizing the MonoMac functionality of the platform), and should just use the UI controls from the Eto assembly.
You do not need to use any of the classes of this assembly (unless customizing the MonoMac functionality of the platform), and should just use the UI controls from the Eto assembly.
</description>
<copyright>$copyright$</copyright>
<tags>cross platform gui ui framework desktop monomac osx mac eto.forms</tags>
Expand Down
14 changes: 7 additions & 7 deletions Resources/nuspec/Eto.Platform.Mac64.nuspec
Original file line number Diff line number Diff line change
Expand Up @@ -11,19 +11,19 @@
<requireLicenseAcceptance>false</requireLicenseAcceptance>
<summary>$description$</summary>
<description>
This is the MonoMac 64-bit platform for Eto.Forms UI Framework.
This is the MonoMac 64-bit platform for Eto.Forms UI Framework.

This is used only when running a 64-bit version of mono, which is typically useful for embedding scenarios as the default mono on OS X is only 32-bit currently.
This is used only when running a 64-bit version of mono, which is typically useful for embedding scenarios as the default mono on OS X is only 32-bit currently.

Eto.Platform.Mac64 uses a modified version of the open source MonoMac for 64-bit, which allows you to create OS X Applications at no cost. However, it does require 64-bit mono to be installed.
Eto.Platform.Mac64 uses a modified version of the open source MonoMac for 64-bit, which allows you to create OS X Applications at no cost. However, it does require 64-bit mono to be installed.

If you want to run using the standard mono install for OS X, use Eto.Platform.Mac.
If you want to run using the standard mono install for OS X, use Eto.Platform.Mac.

Using Eto.Platform.XamMac instead allows you to bundle mono inside your .app, however it requires purchasing Xamarin.Mac and using Xamarin Studio on OS X.
Using Eto.Platform.XamMac instead allows you to bundle mono inside your .app, however it requires purchasing Xamarin.Mac and using Xamarin Studio on OS X.

You can create your own .app bundle to run your app on OS X, without an OS X machine. This is included as the MyApp.app folder. Read MyApp.app\Contents\MonoBundle\README.txt for instructions on next steps.
You can create your own .app bundle to run your app on OS X, without an OS X machine. This is included as the MyApp.app folder. Read MyApp.app\Contents\MonoBundle\README.txt for instructions on next steps.

You do not need to use any of the classes of this assembly (unless customizing the MonoMac functionality of the platform), and should just use the UI controls from the Eto assembly.
You do not need to use any of the classes of this assembly (unless customizing the MonoMac functionality of the platform), and should just use the UI controls from the Eto assembly.
</description>
<copyright>$copyright$</copyright>
<tags>cross platform gui ui framework desktop monomac osx mac eto.forms</tags>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -11,12 +11,13 @@
<requireLicenseAcceptance>false</requireLicenseAcceptance>
<summary>Eto.Forms - Mac Application Template</summary>
<description>
This package provides an .app template for your Eto.Forms application when packaging for Mac.
This package provides an .app template for your Eto.Forms application when packaging for Mac.
When building, an .app bundle will be created for your app when you use this package.

You can create apps that run on OS X natively from windows using this package.
Note that Mono will need to be installed for your app to run.
You can create apps that run on OS X natively from windows using this package.
Note that Mono will need to be installed for your app to run.

Alternatively, you can package for a mac so it does not require Mono and can be distributed through the App Store using Xamarin Studio on OS X and Eto.Platform.XamMac.
Alternatively, you can package for a mac so it does not require Mono and can be distributed through the App Store using Xamarin Studio on OS X and Eto.Platform.XamMac.
</description>
<copyright>Copyright 2014 by Curtis Wensley</copyright>
<tags>cross platform gui ui framework desktop monomac osx mac eto.forms</tags>
Expand Down
6 changes: 3 additions & 3 deletions Resources/nuspec/Eto.Platform.WinRT.nuspec
Original file line number Diff line number Diff line change
Expand Up @@ -11,11 +11,11 @@
<requireLicenseAcceptance>false</requireLicenseAcceptance>
<summary>$description$</summary>
<description>
This is the Windows 8 platform for Eto.Forms UI Framework.
This is the Windows 8 platform for Eto.Forms UI Framework.

Include this along with your Eto.Forms application to provide a Windows 8 interface for your windows users.
Include this along with your Eto.Forms application to provide a Windows 8 interface for your windows users.

You do not need to use any of the classes of this assembly (unless customizing the functionality of the platform), and should just use the UI controls from the Eto assembly.
You do not need to use any of the classes of this assembly (unless customizing the functionality of the platform), and should just use the UI controls from the Eto assembly.
</description>
<copyright>$copyright$</copyright>
<tags>cross platform gui ui framework desktop wpf eto.forms</tags>
Expand Down
6 changes: 3 additions & 3 deletions Resources/nuspec/Eto.Platform.Windows.nuspec
Original file line number Diff line number Diff line change
Expand Up @@ -11,11 +11,11 @@
<requireLicenseAcceptance>false</requireLicenseAcceptance>
<summary>$description$</summary>
<description>
This is the Windows Forms platform for Eto.Forms UI Framework.
This is the Windows Forms platform for Eto.Forms UI Framework.

Include this along with your Eto.Forms application to provide a Windows Forms interface for your windows users.
Include this along with your Eto.Forms application to provide a Windows Forms interface for your windows users.

You do not need to use any of the classes of this assembly (unless customizing the Windows Forms functionality of the platform), and should just use the UI controls from the Eto assembly.
You do not need to use any of the classes of this assembly (unless customizing the Windows Forms functionality of the platform), and should just use the UI controls from the Eto assembly.
</description>
<copyright>$copyright$</copyright>
<tags>cross platform gui ui framework desktop wpf eto.forms</tags>
Expand Down
6 changes: 3 additions & 3 deletions Resources/nuspec/Eto.Platform.Wpf.nuspec
Original file line number Diff line number Diff line change
Expand Up @@ -11,11 +11,11 @@
<requireLicenseAcceptance>false</requireLicenseAcceptance>
<summary>$description$</summary>
<description>
This is the WPF platform for Eto.Forms UI Framework.
This is the WPF platform for Eto.Forms UI Framework.

Include this along with your Eto.Forms application to provide a WPF interface for your windows users. WPF is by default preferred over the Eto.Platform.Windows platform, so if both are included, WPF will be selected.
Include this along with your Eto.Forms application to provide a WPF interface for your windows users. WPF is by default preferred over the Eto.Platform.Windows platform, so if both are included, WPF will be selected.

You do not need to use any of the classes of this assembly (unless customizing the WPF functionality of the platform), and should just use the UI controls from the Eto assembly.
You do not need to use any of the classes of this assembly (unless customizing the WPF functionality of the platform), and should just use the UI controls from the Eto assembly.
</description>
<copyright>$copyright$</copyright>
<tags>cross platform gui ui framework desktop wpf eto.forms</tags>
Expand Down
10 changes: 5 additions & 5 deletions Resources/nuspec/Eto.Platform.XamMac.nuspec
Original file line number Diff line number Diff line change
Expand Up @@ -11,15 +11,15 @@
<requireLicenseAcceptance>false</requireLicenseAcceptance>
<summary>$description$</summary>
<description>
This is the Xamarin.Mac platform for Eto.Forms UI Framework.
This is the Xamarin.Mac platform for Eto.Forms UI Framework.

Include this along with your Eto.Forms application to provide an OS X interface for Mac users.
Include this along with your Eto.Forms application to provide an OS X interface for Mac users.

* Note: You should only use this package from an Xamarin.Mac project created with Xamarin Studio on OS X. Xamarin.Mac allows you to bundle mono inside your .app, however it requires purchasing Xamarin.Mac.
* Note: You should only use this package from an Xamarin.Mac project created with Xamarin Studio on OS X. Xamarin.Mac allows you to bundle mono inside your .app, however it requires purchasing Xamarin.Mac.

Using Eto.Platform.Mac instead uses the open source MonoMac, which allows you to create OS X Applications with no cost. However, it does require mono to be installed for the app to run.
Using Eto.Platform.Mac instead uses the open source MonoMac, which allows you to create OS X Applications with no cost. However, it does require mono to be installed for the app to run.

You do not need to use any of the classes of this assembly (unless customizing the Xamarin.Mac functionality of the platform), and should just use the UI controls from the Eto assembly.
You do not need to use any of the classes of this assembly (unless customizing the Xamarin.Mac functionality of the platform), and should just use the UI controls from the Eto assembly.
</description>
<copyright>$copyright$</copyright>
<tags>cross platform gui ui framework desktop osx xamarin.mac mac eto.forms</tags>
Expand Down
8 changes: 4 additions & 4 deletions Resources/nuspec/Eto.Platform.XamMac2.nuspec
Original file line number Diff line number Diff line change
Expand Up @@ -11,13 +11,13 @@
<requireLicenseAcceptance>false</requireLicenseAcceptance>
<summary>$description$</summary>
<description>
This is the Xamarin.Mac2 platform for Eto.Forms UI Framework.
This is the Xamarin.Mac2 (unified) platform for Eto.Forms UI Framework.

Include this along with your Eto.Forms application to provide an OS X interface for Mac users using the 64-bit compatible Xamarin.Mac.
Include this along with your Eto.Forms application to provide an OS X interface for Mac users using the 64-bit compatible Xamarin.Mac.

* Note: You should only use this package from an Xamarin.Mac project created with Xamarin Studio on OS X. Xamarin.Mac allows you to bundle mono inside your .app, however it requires purchasing Xamarin.Mac.
* Note: You should only use this package from an Xamarin.Mac project created with Xamarin Studio on OS X. Xamarin.Mac allows you to bundle mono inside your .app, however it requires purchasing Xamarin.Mac.

Using Eto.Platform.Mac instead uses the open source MonoMac, which allows you to create OS X Applications with no cost. However, it does require mono to be installed for the app to run.
Using Eto.Platform.Mac instead uses the open source MonoMac, which allows you to create OS X Applications with no cost. However, it does require mono to be installed for the app to run.

You do not need to use any of the classes of this assembly (unless customizing the Xamarin.Mac functionality of the platform), and should just use the UI controls from the Eto assembly.
</description>
Expand Down
6 changes: 3 additions & 3 deletions Resources/nuspec/Eto.Platform.iOS.nuspec
Original file line number Diff line number Diff line change
Expand Up @@ -11,11 +11,11 @@
<requireLicenseAcceptance>false</requireLicenseAcceptance>
<summary>$description$</summary>
<description>
This is the iOS mobile platform for Eto.Forms UI Framework.
This is the iOS mobile platform for Eto.Forms UI Framework.

Include this along with your Eto.Forms application to provide an iOS interface for iPhone/iPad/iPod touch users using Xamarin.iOS.
Include this along with your Eto.Forms application to provide an iOS interface for iPhone/iPad/iPod touch users using Xamarin.iOS.

You do not need to use any of the classes of this assembly (unless customizing the iOS functionality of the platform), and should just use the UI controls from the Eto assembly.
You do not need to use any of the classes of this assembly (unless customizing the iOS functionality of the platform), and should just use the UI controls from the Eto assembly.
</description>
<copyright>$copyright$</copyright>
<tags>cross platform gui ui framework desktop ios eto.forms</tags>
Expand Down
Loading

0 comments on commit f9a88e2

Please sign in to comment.