diff options
author | Miguel de Icaza <miguel@gnome.org> | 2001-06-21 07:42:57 +0400 |
---|---|---|
committer | Miguel de Icaza <miguel@gnome.org> | 2001-06-21 07:42:57 +0400 |
commit | aceaacc0abe56540c7f93bcf8d5050d087573a23 (patch) | |
tree | 1d5737f11ae47119392691cbd670318d029b9d5b /web/class-library | |
parent | 854d04f65c36d9004efd5496cffa5506b14b38bd (diff) |
Further flushage
svn path=/trunk/mono/; revision=19
Diffstat (limited to 'web/class-library')
-rw-r--r-- | web/class-library | 42 |
1 files changed, 24 insertions, 18 deletions
diff --git a/web/class-library b/web/class-library index 4cea4b24a9d..58302f32898 100644 --- a/web/class-library +++ b/web/class-library @@ -3,8 +3,8 @@ The Class Library should be compatible with Microsoft's .NET implementation. - Ideally as much code as possible should be written using C#, - in some cases we might either need to interface with code + Ideally as much code as possible should be written using C#. + In some cases we might either need to interface with code written in C for large chunks of functionality (libart and Gtk+ for example) or we would need to interface to the system libraries (libc on Unix for networking functions for @@ -20,21 +20,21 @@ ** Class Library and Win32 dependencies. There are a few spots where the Win32 foundation is exposed to - the class library (the HDC and HWND properties in the GDI+), - it seems from casual inspection that these can be safely + the class library (the HDC and HWND properties in the GDI+). + It seems from casual inspection that these can be safely mapped to Gdk's GC and GdkWindow pointers without breaking anything. - The only drawback is that, we will not support PInvoke - invocations of Win32 code. This could be possible in the - future by reusing pieces of Wine, and probably using Wine as - our toolkit, but we think this is not as important as most - people will always be isolated from the Win32 system. + The only drawback is that support for PInvoke of Win32 code + wont be available. If this is necessary it could be possible + in the future by reusing pieces of Wine, and probably using + Wine as our toolkit, but we think that this is not as + important as we will wrap GNOME elements in the meantime. *** Initial GDI+ and WinForms implementation The initial implementation will use Gtk+ as the underlying toolkit, but implementations for other windowing systems - should be possible (specially thinking about PDA devices + should be possible (particularly thinking about PDA devices here). Since Gtk+ 2.0 has been ported to other windowing systems @@ -57,11 +57,17 @@ ** Licensing The class library will be licensed under the terms of the GNU - GPL, with the special provision that linking to this library - does not cause your application to be covered by the GNU GPL. - - This is a stop gap measure, I am using this until we can - figure out why not use the laxer GNU LGPL license. We do - request that contributors allow us to relicense the code under - a GNU LGPL like license in the future for inclussion in the - code base at any point in the future. + LGPL. + + We suggest that you assign the copyright of your work to the + GNOME Foundation or the Free Software Foundation to simplify + defending the code in case it is used inappropiately. + +** Contributing + + We welcome contributions to the the Class Library, you can + check the status page. Our status page describes which APIs + are being worked on and the contact information for the + contributor. + + |