Aktuelle Fotos

Neues WohnzimmerCIMG0340CIMG0339CIMG0338CIMG0337CIMG0336
  • user warning: Table 'drupal_herzi_eu.semaphore' doesn't exist query: SELECT expire, value FROM semaphore WHERE name = 'menu_rebuild' in /var/lib/www/shared/drupal-6.16/includes/lock.inc on line 154.
  • user warning: Table 'drupal_herzi_eu.semaphore' doesn't exist query: SELECT expire, value FROM semaphore WHERE name = 'menu_rebuild' in /var/lib/www/shared/drupal-6.16/includes/lock.inc on line 154.

Multilanguage Blog Articles with Drupal

So, let's see if this works out properly…

Das GTK+/GNOME-Entwicklerhandbuch

in

Matthias Warkus hat es endlich geschafft; die Neuauflage des hübschen orang

Monkey Bubble Website

I finally found the time on Monday and Tuesday to set up Drupal for the new Monkey Bubble website. After migrating most of the content, we added forwards from the old page to the new one (thanks, Jeff, for adding our news feed to Planet GNOME News).

Unfortunately, there's still one part lacking on the new website: it's using the default drupal theme. So if someone could pick up the old monkey-bubble theme and provide a version for Drupal 5.x, that would really rock.

In the mean time, really nice things are going on in Monkey Land. In January I merged the maemo-port of Monkey Bubble into upstream (thanks Jouni, for providing the port). These days are spent refactoring the audio engine to finally start working properly (that means: audio + sound effects - hick-coughs - memory leaks).

Chaosradio Express: GTK+ und GNOME

Tim Pritlove hat heute Nacht die Chaosradio-Folge hochgeladen, in der Tim Janik und ich zu GTK+, GNOME und

Linker warnings for deprecated functions

Lennart found the asm code in FreeBSD that makes GNU ld give a warning when using certain functions:

diff --git a/display.c b/display.c
index 24bba79..a0376f2 100644
--- a/display.c
+++ b/display.c
@@ -63,6 +63,10 @@ enum {

G_DEFINE_TYPE (Display, display, GTK_TYPE_WIDGET);

+_asm_(".section .gnu.warning.display_get_type");
+_asm_(".asciz \"sliff\"");

GNOME on CeBIT next week

The last preparations have been done for the GNOME presentation on CeBIT. There will be a GNOME booth in Hall 5 (F47/2) and a talk about security in GNOME on Saturday evening.

Important: I just got the exhibitor tickets and in contrast to the previous years we got 4, not 2. So there are still 2 exhibitor tickets if you like to visit CeBIT to support your desktop environment and development platform. Feel free to contact me. More information (German) can be found on the German wiki.

Right now, Mirco and I will staff the booth. We're going to have the event box, lots of posters, demo computers, and some devices based on GNOME technology. Feel free to join…

I hate perl, continued

or: prepare-ChangeLog.pl - now git-flavored

So, today I got fed up by our prepare-ChangeLog.pl to not support git at all. Fernando the Brave added support for Subversion 3.5 years ago, and now I decided to add support for git.

Chatting with Fernando and Olav we decided to move the script from web-devel-2 into the releng module and then I committed my changes on top. So, now the script is saved from Nirvana (which web-devel-2 will hopefully end up, soon) and is located next to Martyn's maintainer.py.

Using Webkit/GTK+ in Mac OS X

Webkit/GTK+ is a really nice thing already. It still has it's rough edges, but it already works really nicely.

Neulich im Internet…

in

Joomla! oder: die Quadratur der GPL, oder: warum ich seit geraumer Zeit keinen GPL-Code mehr schreibe. Mit der LGPL wäre das nicht passiert und LGPL-Code lässt sich beliebig von einer Anwendung in eine LGPL-Bibliothek migrieren, ohne dass man den Cruft von alten Contributors ausräumen muss…

Also nochmal: Leute, denkt nach bevor ihr euch eure Lizenz aussucht.

Approaching the nineth circle of hell

Dear Lazyweb,

today I had a problem debugging a GTK+ module (libatk-bridge.so). It threw a warning which looked like it was coming from my application:

** (criawips:26563): WARNING **: failure: no device event controller found.

By using grep I realized pretty quickly that the message didn't come from my application. The gdb was at least able to tell me where the meesage came from (after breaking on g_log):

(gdb) bt
#0 IA__g_log (log_domain=0x0, log_level=G_LOG_LEVEL_WARNING,

Syndicate content