Posts tagged 'pugdebug'

pugdebug 1.0.0.

published on July 01, 2015.

After 3 months since announcing that I’m working on pugdebug, and some 5 months since I actually started working on it, it is finally time to let version 1.0.0 out in the wild.

It’s been a busy 3 months: 82 pull requests got merged, 67 issues resolved, more than 350 commits pushed. A lot of changes, fixes and improvements found their way into this first version.

First of all, a big thanks goes out to Ivan Habunek and Srdjan Vranac for helping. They asked for and added new features, tested on Windows and OSX systems, helped fleshing out ideas.

One of the biggest news is that there are binaries built for Linux and Windows operating systems, using pyinstaller. These binaries include everything pugdebug needs to work so there is no need to install anything. Just download the binary for your system and run it. That’s it. It makes me incredibly happy that it’s possible to have it this simple to run and use pugdebug.

pugdebug

The user interface has improved a great deal. It is using dockable widgets for different pieces of the UI, making the layout of the application configurable by just dragging the widgets around. It’s not all great though, there’s still room for improvement, but it will be better over time.

pugdebug allows to debug multiple requests one after the other which helps debugging in a more “complicated” scenario where there are, for example, multiple AJAX calls triggered in succession. By starting to listen to incomming connections, pugdebug will listen to all incoming connections and, based on the IDE key setting, decide should the connection be queued for debugging, or ignored.

It is also now possible to create projects inside pugdebug, as a way to help switching between different PHP projects where debugging is needed. Simply name the project, set it’s settings and that’s it. pugdebug stores all the configuration files in it’s own directory, so nothing will be added to your PHP projects.

I’m especially happy and proud that pugdebug got included on Xdebug’s website on the list of remote debugging clients. Thanks to Derick Rethans!

For more information on how to use pugdebug, take a look at the read me file or the wiki and let me know if you have any issues with it!

Introducing pugdebug

published on April 01, 2015.

In my spare time in the past few months I was working on a tool that would help
me in my every day job as a PHP programmer. As you may, or may not, know, I’m
using vim as my editor/almost IDE, but one thing that is missing from it is the
ability to debug PHP files remotely. Yes, there are a bunch of plugins out
there that add debugging to vim, but none of them felt usable for me.

And based on my google searches, there are no standalone remote debuggers for
PHP, that work on Linux.

In February this year I started to work on a desktop application that would help
me address this issue.

pugdebug

pugdebug  is a PyQt desktop application meant to be used as a remote debugger for PHP,
that communicates with xdebug.

It is meant to be a debugger and only a debugger. There are a plenty of (good) IDEs
that include remote debugging and I’m not going to start writing another one
(although I did start one, once).

The application is still pretty simple, ugly as hell, but it works. Sort of.
There are still a few kinks left to sort out and I’m doing my best to
write them all down.

It’s dependencies are Python 3.4, Qt 5.4, SIP 4.6 and PyQt 5.4. The
read me file
should have a bit more details on how to start using it. I know it’s a bit messy
to set everything up, but I am working on building executables for different
Linux distros. That stuff is hard!

It is lincesed under the GNU GPL v3 license, because PyQt.

Using pugdebug

Start the application, click the start button and then it waits for incomming
connections. Load a PHP page to start a
HTTP debug session,
and pugdebug should break on the first line of your code.

Stepping around the code is possible with the step into, step out and step over
commands. At each step, pugdebug will get the current variables state from xdebug
and display them.

Double clicking on lines in the code viewer will set breakpoints on those lines.
Do note though that there needs to be a debugging session active to be able to
set a breakpoint. This will change in the (near) future.

And that’s about it. While I know it doesn’t look like much, this was, and still
is, a nice learning experience for me and the best part of it is that I was using
pugdebug earlier this week to debug a PHP application I’m working on.

Robert Basic

Robert Basic

Software developer making web applications better.

Let's work together!

I would like to help you make your web application better.

Robert Basic © 2008 — 2020
Get the feed