- Single-widget examples for PHP-GTK2
- Code hints
- Code snippets
- PHP-GTK 2 code snippets
- Building a GtkMenubar
- CommandWidget - a terminal like widget for php-gtk
- Desktop Gadget - a small widget moving around your screen
- Dial widget - a graphical widget to display an analog value.
- Easily empty GtkContainer/GtkWindow
- Editable cells within GtkTreeView
- Extending GtkDrawingArea with OO methods
- Extending GtkFileSelection : the FileSelectionDialog class
- Extending GtkMenu class for Popup menu dialog
- Extending GtkToolbar to quickly build toolbars
- Fast starting with Glade 2
- GtkClock : a clockwork GtkLabel
- Inspecting class methods
- Managing Multiple Windows
- Merry Christmas with php-gtk and object oriented software (tutorial).
- PhpGtkDirectoryTree: displaying a directory tree
- Playing with GtkStyle
- ScrollingLabel - a funny label widget with scrolling capabilities
- Timer class : simplifying gtk::timeout_add
- TreeViewPhpModel class - an easy way to build visual tree with GtkTreeView widget
- Using GtkSourceview to build a php editor with syntax highlighting
- Extending GtkDrawingArea to draw animated graphs
- PHP-GTK 1 code snippets
- PHP-GTK 2 code snippets

Here is an example using
Comments
Decision needed
I'm a bit annoyed by this post : one the one hand, the example is interesting when one goes on the remote site to see it. On the other, since it is hosted outside and has no local content, I feel it might not warrant being included as a node on the site, but might more logically fit in the "Community" section of the aggregator, if Marc provides a RSS feed on his site.
Yet another solution could be to create a specific category for externally hosted articles, like so many "press-review"-type PHP sites do. This would obviously increase the content volume immediately, but on the other hand make content less dense and useful, less of a "community" site and more of yet another pumped up aggregator.
What do Marc and other community members think of such a situation ?
I do not personally care, he
I do not personally care, he supplied an index which will archive the article for local database searches, I probably would have done something similar. The only bad thing is if the link 404's eventually - in that case the full article with a link to the original would be preferable.
I agree with Bob
I agree with Bob on this, It does not really bother me and that the only problem I see is the 404 that may happen in the future it might have been nice for the full article or even a trimed down version with a link back would be a good idea.
404 reached :(
A few years later, it appears that you, Frédéric, were right.
Of course, I disagree with Bob and Leon about that: in my humble opinion, an acceptable choice would have been a hosting at freshmeat's or at sourceforge's, or even google.
Just my two cents,
Pierre.