The official site for PHP-GTK is obviously a natural must for anything related to PHP-GTK 2.
However, its resource pages links indiscriminately to fresh and useful material, and to obsolete intro-level information for the now-defunct PHP-GTK 1.
Here is my selection of current useful resources for PHP-GTK 2, for the developer who already read the advertorials, installed the environment and ran the intro tutorials, and now wants to actually create with the extension.
As many other developers of e-commerce sites using Drupal, I've had to solve the problem of integrating the "front-office" store maintained in the ecommerce module with the back-office data like the actual invoicing matching legal requirements, tax documents, product ordering from suppliers, and so on, and I've had to choose a toolkit for this.
Until recently I had been using Delphi with XML-RPC to upload content and remotely monitor my sites, but I was looking for a cross-platform solution, and one that would preferably have sources available. Using Kylix for other projects and it *does* work, even with SOAP and remote data stores, but the level of support and lack of upgrades from Borland regarding it left me rather skeptical about using it for new projects. And this was not even taking into account the fact the XML-RPC for Delphi and Kylix is a poorly supported Open Source project. So what ?
UPDATED for eC4 in new post
The Drupal ecommerce module suite is a rapidly evolving and quite massive part of Drupal, and newcoming developers may be overwhelmed by the sheer number of modules included in the suite. This UML dependency diagram chart should help understand how the modules fit together.
Having non-HTML-skilled contributors input content on a Drupal site seems to often lead to invalid HTML tag soup being input. And even with seasoned coders, a HTML input error happens sometimes, which can be a problem until someone fixes the post.
So I figured I'd force valid HTML from user input, and here is the proof-of-concept valid_node module: it will force any node to be saved as a XHTML fragment.
Some months ago, I noticed Arnab's blog note about the importance of the sequence table, albeit in a multisite context.
This table also needs special care when copying a drupal site: logically enough, its rows contain the name of the prefixed tables for which a sequence is maintained. For instance, this means that, if you defined the source site as using, say, oldsite_ as a prefix, the name field on the row for the next nid will look like: oldsite_node_nid.
Since the designer is still on holiday, I created a fake logo for the upcoming OSInet 5.0 site, due this winter, and tried to give it a Web 2.0 look.
Did it work ? Any suggestions to increase the connotations ?
Hmmmm....
UPDATE 2006-08-28: for Audean.
For quite a long time I'd been wishing this blog had an original theme. Not that I dislike Marvin, but I felt it was time to create my own theme, especially after doing work on adding settings to drupal themes.
Since today was bank holiday for the Assumption day, I decided I'd use it to create a theme after one of my pet peeves: white space on web pages.
For some months now, I've been noticing that the Audean wiki, which I use as a live documentation site for various aspects of my sites, appeared comparatively rarely in Google search results, although it was referenced in various places and Google cache info (cache:-prefixed queries) showed the site was indexed.
Now, the Audean Wiki is based on Splitbrain's Dokuwiki very convenient Open Source wiki, which often appears in relation with Drupal for documentation purposes, and it appears there are three problems with a default Dokuwiki installation, which prevent effective search engine optimization:
Here's how to overturn these hurdles.