Features/GTK3/Porting: Difference between revisions
No edit summary |
No edit summary |
||
| Line 85: | Line 85: | ||
Ok, let's do these changes now for your activity. Make sure you are in your master branch using the 'git branch' command (the master branch should have a '*' before it). Make your changes, commit them ('git commit -a') and push them to the remote repository ('git push origin master'). | Ok, let's do these changes now for your activity. Make sure you are in your master branch using the 'git branch' command (the master branch should have a '*' before it). Make your changes, commit them ('git commit -a') and push them to the remote repository ('git push origin master'). | ||
===Tools=== | |||
There are tools to help you do the porting. There is a script in the pygobject repository for porting called [http://git.gnome.org/browse/pygobject/tree/pygi-convert.sh pygi-convert.sh], more info about the script can be found in [http://live.gnome.org/PyGObject/IntrospectionPorting the PyGObject Introspection Porting guide]. | |||
If you are having trouble finding how a particular GTK class/method/constant has been named in PyGI, run [http://dev.laptop.org/~dsd/20110806/pygi-enumerate.py pygi-enumerate.py] and grep the output. (this app lists all identified methods and constants). | |||
==Make a release== | ==Make a release== | ||
| Line 91: | Line 96: | ||
== | ==Info for merging== | ||
To document: | To document: | ||
* Gtk.Alignment() no longer has default parameters - specify all 4 | * Gtk.Alignment() no longer has default parameters - specify all 4 | ||