<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: PHP frontend for Xdebug profiling?</title>
	<atom:link href="http://www.sitepoint.com/blogs/2006/04/20/php-frontend-for-xdebug-profiling/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2006/04/20/php-frontend-for-xdebug-profiling/</link>
	<description>News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com.</description>
	<lastBuildDate>Mon, 23 Nov 2009 01:39:24 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mike Smullin</title>
		<link>http://www.sitepoint.com/blogs/2006/04/20/php-frontend-for-xdebug-profiling/comment-page-1/#comment-531606</link>
		<dc:creator>Mike Smullin</dc:creator>
		<pubDate>Sat, 01 Dec 2007 21:44:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1513#comment-531606</guid>
		<description>I&#039;d love to see a KCachegrind or WinCachegrind plugin for Eclipse PDT. Combined with XDebug, that would allow me to debug and profile my PHP code all within the same IDE.</description>
		<content:encoded><![CDATA[<p>I&#8217;d love to see a KCachegrind or WinCachegrind plugin for Eclipse PDT. Combined with XDebug, that would allow me to debug and profile my PHP code all within the same IDE.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: SitePoint Blogs &#187; wxDebug</title>
		<link>http://www.sitepoint.com/blogs/2006/04/20/php-frontend-for-xdebug-profiling/comment-page-1/#comment-23261</link>
		<dc:creator>SitePoint Blogs &#187; wxDebug</dc:creator>
		<pubDate>Mon, 15 May 2006 20:43:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1513#comment-23261</guid>
		<description>[...] In possession of wxPython in Action and with an itch to scratch, hacked together wxDebug (thanks to Python hosting)&#8212;a front end for viewing Xdebug profiling output, the UI design being inspired by (but by no means as good as) WinCacheGrind. A screenshot&#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] In possession of wxPython in Action and with an itch to scratch, hacked together wxDebug (thanks to Python hosting)&#8212;a front end for viewing Xdebug profiling output, the UI design being inspired by (but by no means as good as) WinCacheGrind. A screenshot&#8230; [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: mariuszn3</title>
		<link>http://www.sitepoint.com/blogs/2006/04/20/php-frontend-for-xdebug-profiling/comment-page-1/#comment-18873</link>
		<dc:creator>mariuszn3</dc:creator>
		<pubDate>Sat, 22 Apr 2006 10:46:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1513#comment-18873</guid>
		<description>I&#039;ve made myself php frontend but for Xdebug tracing. This gives times of execution but of course not the way the kcachegrind does. It&#039;s just nice readable output of xdebug xt trace file - more usefull for debugging than profiling. It&#039;s XHTML strict with some ajax functionality (to hide/show parts of trace)
I&#039;m planing to publish it on my site but first I want to clear out some design/functionality issues that I&#039;ve noticed in current version. If there&#039;s interests in that, drop me a note maybe it will motivate me to push it forward :)</description>
		<content:encoded><![CDATA[<p>I&#8217;ve made myself php frontend but for Xdebug tracing. This gives times of execution but of course not the way the kcachegrind does. It&#8217;s just nice readable output of xdebug xt trace file &#8211; more usefull for debugging than profiling. It&#8217;s XHTML strict with some ajax functionality (to hide/show parts of trace)<br />
I&#8217;m planing to publish it on my site but first I want to clear out some design/functionality issues that I&#8217;ve noticed in current version. If there&#8217;s interests in that, drop me a note maybe it will motivate me to push it forward :)</p>]]></content:encoded>
	</item>
	<item>
		<title>By: jayboots</title>
		<link>http://www.sitepoint.com/blogs/2006/04/20/php-frontend-for-xdebug-profiling/comment-page-1/#comment-18838</link>
		<dc:creator>jayboots</dc:creator>
		<pubDate>Fri, 21 Apr 2006 17:21:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1513#comment-18838</guid>
		<description>Thanks for the answer.

&lt;blockquote&gt;Think HTML (or XML / XSLT?) will make a better display in the end, plus it’s easier to customize.&lt;/blockquote&gt;

If you said XUL I might be tempted to agree :)</description>
		<content:encoded><![CDATA[<p>Thanks for the answer.</p>
<blockquote><p>Think HTML (or XML / XSLT?) will make a better display in the end, plus it’s easier to customize.</p></blockquote>
<p>If you said XUL I might be tempted to agree :)</p>]]></content:encoded>
	</item>
	<item>
		<title>By: lmpmbernardo</title>
		<link>http://www.sitepoint.com/blogs/2006/04/20/php-frontend-for-xdebug-profiling/comment-page-1/#comment-18833</link>
		<dc:creator>lmpmbernardo</dc:creator>
		<pubDate>Fri, 21 Apr 2006 15:22:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1513#comment-18833</guid>
		<description>I wrote a 10 line php script that does the same as the ct_annotate perl script. It&#039;s not the same as having a kcachegrind view but I find it almost as useful.</description>
		<content:encoded><![CDATA[<p>I wrote a 10 line php script that does the same as the ct_annotate perl script. It&#8217;s not the same as having a kcachegrind view but I find it almost as useful.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Bob</title>
		<link>http://www.sitepoint.com/blogs/2006/04/20/php-frontend-for-xdebug-profiling/comment-page-1/#comment-18795</link>
		<dc:creator>Bob</dc:creator>
		<pubDate>Fri, 21 Apr 2006 08:24:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1513#comment-18795</guid>
		<description>I&#039;m on OSX as well, and was recently surprised to find no solution for &quot;grinding&quot; cachegrind files natively.  Even if the output was text on the command line - similar to the output of APD&#039;s pprofp - I&#039;d be in heaven.  Graphs are for sucks anyways ;)

Please Harry - go forth and conquer.</description>
		<content:encoded><![CDATA[<p>I&#8217;m on OSX as well, and was recently surprised to find no solution for &#8220;grinding&#8221; cachegrind files natively.  Even if the output was text on the command line &#8211; similar to the output of APD&#8217;s pprofp &#8211; I&#8217;d be in heaven.  Graphs are for sucks anyways ;)</p>
<p>Please Harry &#8211; go forth and conquer.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: svanpoeck</title>
		<link>http://www.sitepoint.com/blogs/2006/04/20/php-frontend-for-xdebug-profiling/comment-page-1/#comment-18794</link>
		<dc:creator>svanpoeck</dc:creator>
		<pubDate>Fri, 21 Apr 2006 08:19:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1513#comment-18794</guid>
		<description>Just looking for a quick answer --seems like a lot of experts are loose here ;) -- does WinCacheGrind have any features Zend Studio Profiler has not ?

Just curious...</description>
		<content:encoded><![CDATA[<p>Just looking for a quick answer &#8211;seems like a lot of experts are loose here ;) &#8212; does WinCacheGrind have any features Zend Studio Profiler has not ?</p>
<p>Just curious&#8230;</p>]]></content:encoded>
	</item>
	<item>
		<title>By: koto</title>
		<link>http://www.sitepoint.com/blogs/2006/04/20/php-frontend-for-xdebug-profiling/comment-page-1/#comment-18792</link>
		<dc:creator>koto</dc:creator>
		<pubDate>Fri, 21 Apr 2006 07:54:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1513#comment-18792</guid>
		<description>&lt;blockquote&gt;
- Occasionally Wincachegrind “explodes” for no apparent reason. Not that I know my way around Delphi but without the source, it’s not promising.
&lt;/blockquote&gt;

Just for the record - the new release of &lt;a href=&quot;http://sourceforge.net/project/showfiles.php?group_id=135562&quot; rel=&quot;nofollow&quot;&gt;
wincachegrind 1.0.0.12&lt;/a&gt; has source files included.</description>
		<content:encoded><![CDATA[<blockquote><p>
- Occasionally Wincachegrind “explodes” for no apparent reason. Not that I know my way around Delphi but without the source, it’s not promising.
</p></blockquote>
<p>Just for the record &#8211; the new release of <a href="http://sourceforge.net/project/showfiles.php?group_id=135562" rel="nofollow"><br />
wincachegrind 1.0.0.12</a> has source files included.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: HarryF</title>
		<link>http://www.sitepoint.com/blogs/2006/04/20/php-frontend-for-xdebug-profiling/comment-page-1/#comment-18791</link>
		<dc:creator>HarryF</dc:creator>
		<pubDate>Fri, 21 Apr 2006 06:54:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1513#comment-18791</guid>
		<description>&lt;blockquote&gt;
Why bother? kcachegrind and wincachegrind both do a good job and are very fast. I&#039;m interested to know what brings you to wonder about a webified version. Are there particular features that are missing that you are interested in?
&lt;/blockquote&gt;

There isn&#039;t really a good reason but a there are a bunch of bad reasons which, put together, start to make a good reason like;

- It&#039;s a different tool on different platforms (and sounds like tough luck of the OS X people). Personally my desktop is about 50/50 Windows / Ubuntu these days (plus it&#039;s nice to keep Ubuntu K-free) so I&#039;d like to use the same thing on both

- Occasionally Wincachegrind &quot;explodes&quot; for no apparent reason. Not that I know my way around Delphi but without the source, it&#039;s not promising.

- Think HTML (or XML / XSLT?) will make a better display in the end, plus it&#039;s easier to customize

&lt;blockquote&gt;
You&#039;re just looking for an excuse to write it ;-P
&lt;/blockquote&gt;

...and there&#039;s that ;)</description>
		<content:encoded><![CDATA[<blockquote><p>
Why bother? kcachegrind and wincachegrind both do a good job and are very fast. I&#8217;m interested to know what brings you to wonder about a webified version. Are there particular features that are missing that you are interested in?
</p></blockquote>
<p>There isn&#8217;t really a good reason but a there are a bunch of bad reasons which, put together, start to make a good reason like;</p>
<p>- It&#8217;s a different tool on different platforms (and sounds like tough luck of the OS X people). Personally my desktop is about 50/50 Windows / Ubuntu these days (plus it&#8217;s nice to keep Ubuntu K-free) so I&#8217;d like to use the same thing on both</p>
<p>- Occasionally Wincachegrind &#8220;explodes&#8221; for no apparent reason. Not that I know my way around Delphi but without the source, it&#8217;s not promising.</p>
<p>- Think HTML (or XML / XSLT?) will make a better display in the end, plus it&#8217;s easier to customize</p>
<blockquote><p>
You&#8217;re just looking for an excuse to write it ;-P
</p></blockquote>
<p>&#8230;and there&#8217;s that ;)</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Eric.Coleman</title>
		<link>http://www.sitepoint.com/blogs/2006/04/20/php-frontend-for-xdebug-profiling/comment-page-1/#comment-18772</link>
		<dc:creator>Eric.Coleman</dc:creator>
		<pubDate>Fri, 21 Apr 2006 00:30:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1513#comment-18772</guid>
		<description>Pain in the ass to get either of those working on OS X, unless im missing the point ;)

Then again, I can just fire up parallels and use wincachegrind.</description>
		<content:encoded><![CDATA[<p>Pain in the ass to get either of those working on OS X, unless im missing the point ;)</p>
<p>Then again, I can just fire up parallels and use wincachegrind.</p>]]></content:encoded>
	</item>
</channel>
</rss>
