Comments for GGGeek http://gggeek.altervista.org il mago di eZ Tue, 10 Nov 2009 10:48:35 +0100 http://wordpress.org/?v=2.8.4 hourly 1 Comment on Slides of my talks at phpday: eZ Publish and eZ Components by bathroom taps http://gggeek.altervista.org/2008/05/29/slides-of-my-talks-at-phpday-ez-publish-and-ez-components/comment-page-1/#comment-11624 bathroom taps Tue, 10 Nov 2009 10:48:35 +0000 http://gggeek.altervista.org/2008/05/29/slides-of-my-talks-at-phpday-ez-publish-and-ez-components/#comment-11624 My brother has been using one of these for some time now and he thinks it is brilliant.. I’ve never really seen much point in them myself, but each to there own eh lol My brother has been using one of these for some time now and he thinks it is brilliant.. I’ve never really seen much point in them myself, but each to there own eh lol

]]> Comment on The blog is dead, long live the tweet! by Ste http://gggeek.altervista.org/2009/10/15/the-blog-is-dead-long-live-the-tweet/comment-page-1/#comment-11623 Ste Tue, 10 Nov 2009 08:20:18 +0000 http://gggeek.altervista.org/?p=50#comment-11623 One reader still exists, but the frequency which I read is even lower than the one which you write :-). A plenty of new stuff every time:-). Hope to see you soon! One reader still exists, but the frequency which I read is even lower than the one which you write :-) . A plenty of new stuff every time:-).
Hope to see you soon!

]]> Comment on Setting up a DocBook Toolchain for documenting PHP code The Right Way (TM) by gggeek http://gggeek.altervista.org/2007/07/05/setting-up-a-docbook-toolchain-for-documenting-php-code-the-right-way-tm/comment-page-1/#comment-11316 gggeek Sat, 12 Sep 2009 22:07:03 +0000 http://gggeek.altervista.org/2007/07/05/setting-up-a-docbook-toolchain-for-documenting-php-code-the-right-way-tm/#comment-11316 Sorry, I never tried this, but it sounds a good idea. You could probably use an xslt (or even plain php) script to inject the source code into the xml at the phase of producing the final output - not optimal because you loose visibility of the code while editing the docs though... Sorry, I never tried this, but it sounds a good idea.
You could probably use an xslt (or even plain php) script to inject the source code into the xml at the phase of producing the final output – not optimal because you loose visibility of the code while editing the docs though…

]]> Comment on An xmlrpc connector for Mantis by gggeek http://gggeek.altervista.org/2008/10/30/an-xmlrpc-connector-for-mantis/comment-page-1/#comment-11315 gggeek Sat, 12 Sep 2009 22:03:40 +0000 http://gggeek.altervista.org/2008/10/30/an-xmlrpc-connector-for-mantis/#comment-11315 Nopes - no new releases. In fact zero bugs or feature request showed up - there seems to be very little interest in this, at least until now ;) Nopes – no new releases.
In fact zero bugs or feature request showed up – there seems to be very little interest in this, at least until now ;)

]]> Comment on An xmlrpc connector for Mantis by Laurent http://gggeek.altervista.org/2008/10/30/an-xmlrpc-connector-for-mantis/comment-page-1/#comment-11311 Laurent Fri, 11 Sep 2009 13:05:38 +0000 http://gggeek.altervista.org/2008/10/30/an-xmlrpc-connector-for-mantis/#comment-11311 Ciao, Have you updated your code since last year ? We're going to have a look as we need to plug mantis to other web services (like basecamp or zoho project, a CRM, ...) and I would prefer to look at the last release. Grazzie mille, Laurent Ciao,
Have you updated your code since last year ?
We’re going to have a look as we need to plug mantis to other web services (like basecamp or zoho project, a CRM, …) and I would prefer to look at the last release.

Grazzie mille,

Laurent

]]> Comment on Setting up a DocBook Toolchain for documenting PHP code The Right Way (TM) by Johan http://gggeek.altervista.org/2007/07/05/setting-up-a-docbook-toolchain-for-documenting-php-code-the-right-way-tm/comment-page-1/#comment-8860 Johan Wed, 15 Apr 2009 15:59:57 +0000 http://gggeek.altervista.org/2007/07/05/setting-up-a-docbook-toolchain-for-documenting-php-code-the-right-way-tm/#comment-8860 Thanks for the tips! I'm just doing the same myself since I want to find a new way to document a fairly large PHP library using XMLMind among other things. One thing I haven't yet found a good way to do is to include external small PHP examples (highlighted) in the source XML document (in programlistings tag) without copy the source text into the document. I have tried using tags (automatic generated) and then use &link; within the programlisting tag but for some reason it doesn't quite work. The reason is that I like to have the source fully separate from the manual to make sure it can be run as part of a test suit. Does anyone know the best way of doing this? /Johan Thanks for the tips! I’m just doing the same myself since I want to find a new way to document a fairly large PHP library using XMLMind among other things.

One thing I haven’t yet found a good way to do is to include external small PHP examples (highlighted) in the source XML document (in programlistings tag) without copy the source text into the document. I have tried using tags (automatic generated) and then use &link; within the programlisting tag but for some reason it doesn’t quite work.

The reason is that I like to have the source fully separate from the manual to make sure it can be run as part of a test suit.

Does anyone know the best way of doing this?

/Johan

]]> Comment on The completely unofficial Xdebug.ini by gggeek http://gggeek.altervista.org/2007/11/26/the-completely-unofficial-xdebugini/comment-page-1/#comment-8391 gggeek Fri, 03 Apr 2009 11:32:52 +0000 http://gggeek.altervista.org/2007/11/26/the-completely-unofficial-xdebugini/#comment-8391 @james: no idea, sorry Did you recently set up the xdebug.ini I provided whereas you had none before? Or did you change something else? What is your platform (os/webserver/php/xdebug)? A common cause of trouble with php.ini is editing one version of the file while actually using another one @james: no idea, sorry

Did you recently set up the xdebug.ini I provided whereas you had none before? Or did you change something else?
What is your platform (os/webserver/php/xdebug)?

A common cause of trouble with php.ini is editing one version of the file while actually using another one

]]> Comment on The completely unofficial Xdebug.ini by James Printer http://gggeek.altervista.org/2007/11/26/the-completely-unofficial-xdebugini/comment-page-1/#comment-8387 James Printer Fri, 03 Apr 2009 10:52:24 +0000 http://gggeek.altervista.org/2007/11/26/the-completely-unofficial-xdebugini/#comment-8387 My xdebug used to create a unique file each time, but now just uses the same filename, and whatever I set xdebug.profiler_output_name to it doesn't seem to make a difference. Any ideas? My xdebug used to create a unique file each time, but now just uses the same filename, and whatever I set xdebug.profiler_output_name to it doesn’t seem to make a difference. Any ideas?

]]> Comment on How NOT to take advantage of a recent full-disk backup… by Kristof http://gggeek.altervista.org/2009/02/27/how-not-to-take-advantage-of-a-recent-full-disk-backup/comment-page-1/#comment-7858 Kristof Mon, 02 Mar 2009 18:06:55 +0000 http://gggeek.altervista.org/2009/02/27/how-not-to-take-advantage-of-a-recent-full-disk-backup/#comment-7858 My condolences... May the disk and your data rest in peace ;) My condolences… May the disk and your data rest in peace ;)

]]> Comment on An xmlrpc connector for Mantis by duude http://gggeek.altervista.org/2008/10/30/an-xmlrpc-connector-for-mantis/comment-page-1/#comment-7388 duude Tue, 09 Dec 2008 14:31:43 +0000 http://gggeek.altervista.org/2008/10/30/an-xmlrpc-connector-for-mantis/#comment-7388 duude!!! nice one :D duude!!! nice one :D

]]>