
The wxGubed Client

About
These are Linux instructions for setting up the wxGubed client for use with
Gubed PHP Debugger. For win32, see the 'Mingw compilation' file.

Get the sources
http://sourceforge.net/projects/gubed/download
You'll need to get one of the complete archives to get the wxGubed source, ie
either GubedVERSION.tar.bz2 or GubedVERSION.tar.gz. (The GubedServer
packages contain only the Gubed php files and the proxy)


Compilation
Unpack the sources, for example: 
$ tar -xjvf Gubed0.1.4.tar.bz2
$ cd Gubed0.1.4/Clients/wxGubed/
$ ./autogen.sh
$ ./configure
$ make

You do not need to install it to try it out, so either do:
$ make install
$ gbdwxGubed
to install it then start it, or
$ src/gbdwxGubed
to try it without installing.


Settings
The first thing you need to do with your fresh Gubed is to change the settings
to suit your needs.
The settings are reached by the Program->Settings menu, Ctrl + O for short.

You'll find three tabs in the settings dialog: Connection, Debug behaviour and GUI.

Connection Settings:
Specify wether to use the proxy or not (it's recommended to get it to work with-
out proxy to start with, since the setup is easier)
If you use the proxy, specify what address (hostname or ip) it's running on and
what port its listening to.

If you chose not to use proxy, chose which port wxGubed should listen to.

Debug Behaviour Settings:
Here you can chose what types of errors Gubed should halt on. Recommended
settings are E_WARNING and all E_USER_-settings. If you also chose E_NOTICE
Gubed will, amongst other things, halt on every undefined variable used, which 
is usually not wanted.

GUI Settings:
Change the GUI settings to your preference.



Debugging

Once everything is set up and configured (and you've also set up the server parts),
you can start debugging. 

When wxGubed is started it will automatically start listening for incoming
debug-connections or connect to the proxy. If you've changed the network
settings or if wxGubed for some reason could bind or connect to the proxy, you
can manually start listening/do a proxy connection attempt by chosing 'Connect'
in the 'Program' menu.

Once wxGubed is ready for connections, open a browser and point it to your
Gubed directory on the webserver. (That directory is a part of the distribution
archive, see 'serversetup.txt' for more info)
You will then see the Gubed welcome page and from there, you can click
the link to enter the Gubed testbench to test your setup, or to 'StartSession.php' 
('specify script to debug') to start debugging your own scripts.

When a debugging session is started, you should see the sourcecode and other
info in the wxGubed window/log display. 

