|Re: New features in the XDebug 2.1 should be max. utilize by PDT [message #546329 is a reply to message #546308]
||Mon, 12 July 2010 13:33
Registered: July 2009
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)|
Content-Type: text/plain; charset=ISO-8859-1
On 12. 7. 2010 14:50, dave kelsey wrote:
> Hi sNop,
> PDT currently only utilitises what is available through the remote debu=
gging facilities of xdebug, but in theory PDT could send an eval request =
to invoke xdebug_get_headers() and somehow capture the output for display=
in the variable view, however
> you should be able to do that yourself through a watch expression.
> Give it a go and see what you think ?
I tried this and it works good, but I want to tell, that PDT should suppo=
rt e.g. this feature natively ( it could be implemented in PDT core ).
And there are few other features, which PDT could support and aren't impl=
emented now ( i don't understand java programming and i don't know how
debugging by XDebug works in PDT ), so i don't know which new features of=
XDebug 2.1 could be implemented in PDT.
This thread is all about, that you should decide and choose which new fea=
tures from XDebug 2.1 you could utilize in PDT.
So it was just my idea. ;) :)
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
Powered by FUDForum
. Page generated in 0.08402 seconds