mirror of
				https://github.com/Ryujinx/GtkSharp.git
				synced 2025-11-04 13:04:53 +00:00 
			
		
		
		
	* HACKING : New rulez. * NOTES: Killed. We have a mailing list now for this kind of stuff. * glib/makefile : New, to build the new glib-sharp.dll target. * glib/Object.cs : (GetObject): Commented out. Design problems here. IntPtr's can't be used in the manner this code attempts to use them. (Data prop): Commented out. Apparently keyed properties are not supported. (Object prop): Renamed RawObject, and made it protected. (Events): Fixed to cause list to be initialized if null and then return the list. * glib/ObjectManager.cs : commented out entirely. Not sure what this code is trying to accomplish and it doesn't compile. * glib/Value.cs : New attempt at implementing GValues. Doesn't work yet. * gtk/Button.cs : Updated to use RawObject. (Clicked event): s/EmitDeleteEvent/EmitClickedEvent. (Button(String)): s/gtk_label_new_with_lable/gtk_button_new_with_label. * gtk/Label.cs : Fixed some yank and paste errors where 2 value params were getting passed to all the set_* property methods. * gtk/Window.cs : Fixed hanging GTK namespace ref. * sample/HelloWorld.cs : Fixed hanging GTK namespace ref. svn path=/trunk/gtk-sharp/; revision=884
		
			
				
	
	
		
			20 lines
		
	
	
		
			909 B
		
	
	
	
		
			Plaintext
		
	
	
		
			Executable file
		
	
	
	
	
			
		
		
	
	
			20 lines
		
	
	
		
			909 B
		
	
	
	
		
			Plaintext
		
	
	
		
			Executable file
		
	
	
	
	
Please please please hack on gtk-sharp.
 | 
						|
 | 
						|
Okay, now for the details.
 | 
						|
 | 
						|
Prior to checking anything into CVS, please send a patch to the mailing list
 | 
						|
(gtk-sharp-list@ximian.com) for approval.  Any patches should be submitted in
 | 
						|
diff -u format.  Also, it is assumed that the submitter has verified that the
 | 
						|
patch does not break the build, and hopefully that it doesn't break runtime.
 | 
						|
 | 
						|
Second, patches without Documentation comments will be seriously frowned upon,
 | 
						|
if not outright rejected.  All classes, methods, properties, events, etc...
 | 
						|
that are non-private should be documented with XML comment tags.  At a minimum,
 | 
						|
the summary and remarks tags, plus returns and params, if applicable.
 | 
						|
 | 
						|
Third, Make a ChangeLog entry.  Get credit for your hard work, and let me know
 | 
						|
who I need to get cranky with at a glance, instead of having to do cvs history
 | 
						|
reports.  :-)
 | 
						|
 | 
						|
Fourth, please please please hack on gtk-sharp.  
 |