Code handbook

Here's THE place to share some piece of code or a tutorial with the community of php-gtk.

The docs are currently arranged in three sections, for increasing degrees of proficiency with PHP-GTK:

The Single-widget examples for PHP-GTK 2 section contains short introductory examples demonstrating one scenario each for a given widget or widget combination, like how to use a GtkFileSelection dialog.

The Code hints section contains useful examples on how to manipulate certain combination of widgets and/or calls to achieve a given result, like a way to activate a menu bar with the ALT key.

The Code snippets section contains complete examples of reusable code demonstrating techniques, typically along with extensions to the basic PHP-GTK classes, like a class to add icon buttons to application menus and the code to use it

Code snippets

Code hints

Handbook updates: RSS feed

Regarding the copyrights

Can I use all those pieces of code in any of my apps ?

Only a lawyer is entitled to answer this type of questions. What we can give you here is an information : refer to the license under which the code you intend to use is distributed. And try to locate a lawyer versed in Open Source licensing questions ; not many of them are yet.

Can others do what they want with the code I post in this site ?

It depends on the license under which your code has been distributed. If you want to distribute your code, so don't forget to put a license reference with your code, as in certain countries (such as France) you simply can't use code without a license, which is why the GPL-compatible CeCILL license has been crafted.

After 01 november 2006

Handbooks, hints and code fragments

The registration procedure on this site is designed so that all content added after 01 november 2006 is licensed to the owners of this site by the contributors under the Creative Commons "BY-SA 2.0 FR" defined at the about page of this site, and is relicensed for general use under identical terms.

RSS content

Check the about page of this site, the essential point being that the community site only acts as a form of "cache" in these situations, and everything depend on the original (upstream) source.