From a7b4fc7be6dac8c4ff9ae7924eb499d7e2ac1453 Mon Sep 17 00:00:00 2001 From: marcinzelent Date: Tue, 10 Oct 2017 11:21:01 +0200 Subject: Removed packages, added Client project properly. --- packages/Xwt.0.2.40/LICENSE.txt | 21 --- packages/Xwt.0.2.40/README.markdown | 221 ----------------------- packages/Xwt.0.2.40/Xwt.0.2.40.nupkg | Bin 177505 -> 0 bytes packages/Xwt.0.2.40/lib/net40/Xwt.dll | Bin 414720 -> 0 bytes packages/Xwt.Gtk.0.2.40/LICENSE.txt | 21 --- packages/Xwt.Gtk.0.2.40/README.markdown | 221 ----------------------- packages/Xwt.Gtk.0.2.40/Xwt.Gtk.0.2.40.nupkg | Bin 138439 -> 0 bytes packages/Xwt.Gtk.0.2.40/build/Xwt.Gtk.dll.config | 22 --- packages/Xwt.Gtk.0.2.40/build/Xwt.Gtk.props | 10 - packages/Xwt.Gtk.0.2.40/lib/net40/Xwt.Gtk.dll | Bin 286720 -> 0 bytes 10 files changed, 516 deletions(-) delete mode 100644 packages/Xwt.0.2.40/LICENSE.txt delete mode 100644 packages/Xwt.0.2.40/README.markdown delete mode 100644 packages/Xwt.0.2.40/Xwt.0.2.40.nupkg delete mode 100644 packages/Xwt.0.2.40/lib/net40/Xwt.dll delete mode 100644 packages/Xwt.Gtk.0.2.40/LICENSE.txt delete mode 100644 packages/Xwt.Gtk.0.2.40/README.markdown delete mode 100644 packages/Xwt.Gtk.0.2.40/Xwt.Gtk.0.2.40.nupkg delete mode 100644 packages/Xwt.Gtk.0.2.40/build/Xwt.Gtk.dll.config delete mode 100644 packages/Xwt.Gtk.0.2.40/build/Xwt.Gtk.props delete mode 100644 packages/Xwt.Gtk.0.2.40/lib/net40/Xwt.Gtk.dll (limited to 'packages') diff --git a/packages/Xwt.0.2.40/LICENSE.txt b/packages/Xwt.0.2.40/LICENSE.txt deleted file mode 100644 index 170a488..0000000 --- a/packages/Xwt.0.2.40/LICENSE.txt +++ /dev/null @@ -1,21 +0,0 @@ -The MIT License (MIT) - -Copyright (c) 2014 Xamarin, Inc - -Permission is hereby granted, free of charge, to any person obtaining a copy -of this software and associated documentation files (the "Software"), to deal -in the Software without restriction, including without limitation the rights -to use, copy, modify, merge, publish, distribute, sublicense, and/or sell -copies of the Software, and to permit persons to whom the Software is -furnished to do so, subject to the following conditions: - -The above copyright notice and this permission notice shall be included in all -copies or substantial portions of the Software. - -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, -FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE -AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, -OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE -SOFTWARE. diff --git a/packages/Xwt.0.2.40/README.markdown b/packages/Xwt.0.2.40/README.markdown deleted file mode 100644 index 54de416..0000000 --- a/packages/Xwt.0.2.40/README.markdown +++ /dev/null @@ -1,221 +0,0 @@ -This document is an introduction to XWT, a cross-platform UI toolkit -for creating desktop applications. - -If you have any question about XWT or do you want to contribute -a discussion group for XWT is available here: - -http://groups.google.com/group/xwt-list - -Introduction -============ - -Xwt is a new .NET framework for creating desktop applications that run -on multiple platforms from the same codebase. Xwt works by exposing -one unified API across all environments that is mapped to a set of -native controls on each platform. - -This means that Xwt tends to focus on providing controls that will -work across all platforms. However, that doesn't mean that the -functionality available is a common denominator of all platforms. -If a specific feature or widget is not available in the -native framework of a platform, it will be emulated or implemented -as a set of native widgets. - -Xwt can be used as a standalone framework to power the entire application -or it can be embedded into an existing host. This allows developers -to develop their "shell" using native components (for example a Ribbon -on Windows, toolbars on Linux) and use Xwt for specific bits of the -application, like dialog boxes or cross platform surfaces. - -Xwt works by creating an engine at runtime that will map to the -underlying platform. These are the engines that are supported on -each platform: - -* Windows: WPF engine, Gtk engine (using Gtk#) -* MacOS X: Cocoa engine (using Xamarin.Mac) and Gtk engine (using Gtk#) -* Linux: Gtk engine (using Gtk#) - -This means for example that you can write code for Xwt on Windows that -can be hosted on an existing WPF application (like Visual Studio) or -an existing Gtk# application (like MonoDevelop). Or on Mac, you can -host Xwt on an existing Cocoa/Xamarin.Mac application or you can host it -in our own MonoDevelop IDE. - -Getting Started ---------------- - -Open the Xwt.sln with MonoDevelop (or VisualStudio on Windows) and -build the solution. You should end up with the libraries that you -can use in your project and a couple of sample applications. - -Using Xwt in your app ---------------------- - -Based on your platform and the backend that you want to use, you need -to pick the libraries that you want to use in your project. - -* Windows+WPF: Xwt.dll + Xwt.WPF.dll (requires WPF) -* Windows+Gtk: Xwt.dll + Xwt.Gtk.dll (requires Gtk#) -* Linux+Gtk: Xwt.dll + Xwt.Gtk.dll (requires Gtk#) -* Mac+Gtk: Xwt.dll + Xwt.Gtk.dll (requires Gtk#) -* Mac+Cocoa: Xwt.dll + Xwt.XamMac.dll (requires Xamarin.Mac.dll) - -Hello World ------------ - -To write your first application, create an empty .NET project in your -favorite language in MonoDevelop or Visual Studio and reference the -Xwt.dll library. This is the only library that you need to reference -at compile time. - -This is the simplest Xwt program you can write: - - using System; - using Xwt; - - class XwtDemo { - [STAThread] - static void Main () - { - Application.Initialize (ToolkitType.Gtk); - var mainWindow = new Window (){ - Title = "Xwt Demo Application", - Width = 500, - Height = 400 - }; - mainWindow.Show (); - Application.Run (); - mainWindow.Dispose (); - } - } - -You use the Application.Initialize() method to get the backend -initialized. In this example we are using the Gtk backend. If you -want to use another backend, just change the parameter provided -to the Initialize() method. Also make sure the appropiate backend -DLL is available in the application directory. - -Then we create an instance of the Window class, this class exposes two -interesting properties, MainMenu which can be used to set the Window's -main menu and "Content" which is of type "Widget" and allows you to -add some content to the window. - -Finally, the Application.Run method is called to get the UI events -processing going. - -Widget Class Hierarchy -====================== - -You will be using widgets to create the contents for your -application. Xwt.Widget is the abstract base class from which all -the other components are created. - -Some Widgets can contain other widgets, these are container widgets, -and in Xwt those are Canvas, Paned, HBox, VBox and Table. The first -two implement a box layout system, while the last one implements a -Table layout that allows widgets to be attached to different -anchor-points in a grid. - -The layout system uses an auto-sizing system similar to what is -availble in Gtk and HTML allowing the user interface to grow or shrink -based on the contents of the childrens on it. - -* XwtComponent - * Menu - * MenuItem - * Widget - * Box (Container) - * HBox (Container) - * VBox (Container) - * Button - * MenuButton - * Toggl