Debugging PHP Code with Quanta Plus

faq
flatforty
contribute
subscribe
configure
search
rdf

main

Debugging PHP Code with Quanta Plus

Posted by Andras Mantia on Sunday 24/Apr/2005, @02:39
from the learn-to-debug-php dept.
Ewald Kicker has written a detailed tutorial about debugging a PHP script inside Quanta Plus using the Gubed debugger. The document is aimed at beginners and describes step-by-step how to set up and use the debugger for your web projects.

There is an older Gubed tutorial written by Werner Joss, now slightly out of date, but was the first detailed document about using Gubed inside Quanta Plus.

Both tutorials show how anyone can contribute to a Free Software project even if you are not a C++ developer. If you do not have time even for writing documentation or tutorials, you can still use Quanta's donation page to assure and support the future of Quanta Plus and Kommander.

< | >

Related Links

·   Articles on Developer
·   Also by Andras Mantia
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Neat
by Derek Kite on Sunday 24/Apr/2005, @16:50

Did the rather simple installation and setup, lo and behold, it works!

With large scripts you may want to increase the server timeout.

Very cool, and just in time to track down a bug in my code.

Thanks to everyone.

Derek

[ Reply To This | View ]

Sweet :-)
by Macavity on Monday 25/Apr/2005, @04:01

Man the Gubed homepage looks sweet with all those KDE whistles and bells :-)

~Macavity

[ Reply To This | View ]

Good Gubed docs
by Richard Dale on Monday 25/Apr/2005, @05:13

I've been reading about how the Gubed debugger works on the site. The docs are very good, with clear diagrams about how it all fits together with the web request.

We we discussing ruby/Rails support in the recent Dot KDE story about Quanta, but I didn't really know what was involved. I can think about what would be needed now to do the same thing in ruby. Maybe the same wire protocol over the socket connection could be used for a ruby debugger, I'm not sure - that wasn't in the docs.

[ Reply To This | View ]

Re: Good Gubed docs
by Eric Laffoon on Monday 25/Apr/2005, @13:27

Hi Richard,
in fact our idea was that any scripting debugger should be pluggable. Of course there can always be surprises but we would love to expand our capabilities. In addition to this there is the document type package which manages tag auto completion and structure. If you have an itch to do this just let us know how we can help.

[ Reply To This | View ]

no packages == no go
by JelleB on Friday 29/Apr/2005, @08:53

This is the umptieth tutorial aimed at beginners that suggests installing software from source. When will the world realise that installing from source is very bad from a maintainace point of view? Do you want all those users to reinstall -à la windows- every year or so? installing from source does not provide easy upgrades, dependency maintainance and removal. You will have to do it all manually yourself.
That itch is the reason package management was developed. Just ask kpackage, synaptic, apt or yum to install the software you want, and you are done. No hassle trying to hunt down the correct libraries or breaking other applications.
Now what if a program has not been packaged for your distro yet? Well... maybe you are wanting too much. In the case of this program: it is at version 0.2 or something: not really stable software if you can judge from the version number. So it is no wonder really it has not been packaged yet. Their homepage does not even mention packages! So unless you want to be a developer of said package, are prepared to clean up the mess it makes, steer clear of it.

Just my grumpy 2 cents worth.
(and no, not installiong this stuff, although I use Quanta and php regularly)

[ Reply To This | View ]

Re: no packages == no go
by Tom on Saturday 30/Apr/2005, @01:44

What are you talking about?

If you would have tried it you would see that you don't need to compile anything. All you need to do is to download the archive, extract it and copy a directory to the right place. There are no dependencies because you don't download a program - it's just a bunch of PHP scripts in a directory that need to be placed in you web root.

"it is at version 0.2 or something: not really stable software if you can judge from the version number"

The low version number does not mean that it's not stable. If you want to give your opinion about something please at least give it a try!

[ Reply To This | View ]

Re: no packages == no go
by JelleB on Saturday 30/Apr/2005, @11:48

well maybe this one is not chanting the ./configure && make && make install mantra. But it is software, right? Would you say that the are some sorts of software that does not need to be installed with a package manager?

Personally I think not. As they admid themselves, it is a security risk to put this sofware in a publically accesible webroot. So you need to have an intelligent install script that put is somewhere usable but safe, and changes some seting in the webserver to make it safe.

As for the version number: it clearly signals "not yet ready" to me.

[ Reply To This | View ]

Re: no packages == no go
by Tom on Sunday 01/May/2005, @14:58

"not yet ready" != "not stable"

Normally you don't debug scripts on your production server. It will never be complety safe to do this, no matter if you install it by hand or with "packet management" but don't you think it is more safe to do this by hand where you have to think about what you are doing?

Normally you debug on your local developement machine while developing...

[ Reply To This | View ]

Re: no packages == no go
by Evan "JabberWokky" E. on Wednesday 04/May/2005, @07:27

This is for developers to use as a tool to edit and debug PHP code. Written in PHP. Provided as PHP code.

Is giving *developers* a tool that is only useful for active editing of code and is provided in the same format as their projects now undesirable?

[ Reply To This | View ]

PHP_Debug
by Loic Vernet on Monday 25/Jul/2005, @02:08

Hello, i have made a library to debug php code. You can check it here http://www.php-debug.com See you. Coil :)

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"I just wanted to be certain that the code was unmaintainable." -- Charles Samuels
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.