1
urbanspacema
Xoops debug improvement

I found this system very useful for debugging and analyze code php. You can enter as an additional method of debugging in XOOPS?

http://particletree.com/features/php-quick-profiler
http://www.ultrasonica.it
http://www.noisecollective.net

2
Mamba
Re: Xoops debug improvement
  • 2009/4/27 17:39

  • Mamba

  • Moderator

  • Posts: 11366

  • Since: 2004/4/23


It looks very interesting! Thank you for sharing with us!!!

There is a cool demo from a guy who made some changes to PQP using AJAX:

http://demos.stuartloxton.com/pqp/
Support XOOPS => DONATE
Use 2.5.10 | Docs | Modules | Bugs

3
trabis
Re: Xoops debug improvement
  • 2009/4/27 21:51

  • trabis

  • Core Developer

  • Posts: 2269

  • Since: 2006/9/1 1


I'll make a hack for this!

4
frankblack
Re: Xoops debug improvement
  • 2009/4/29 14:49

  • frankblack

  • Just can't stay away

  • Posts: 830

  • Since: 2005/6/13


@trabis: Maybe you should rethink the design before making a hack?

Drawback of the PQP or the XOOPS debugger is the fact, that the debug information appears where it should NOT appear: at the end of the body (or even after the body) or in a popup. Sometimes the debug information messes with the other html code. A more elegant solution I found a long time ago at the makers of tinymce. For an older version of tinymce they made a devkit plugin which writes all debug information into an iframe located at the top of the page. A small button drops down a window with the debug info.

Resized Image

This kind of mechanism I would like to see in the next XOOPS debugger.

If you want to see the code: devkit

5
trabis
Re: Xoops debug improvement
  • 2009/4/29 17:36

  • trabis

  • Core Developer

  • Posts: 2269

  • Since: 2006/9/1 1


Thanks frankblack, I'll have a look into it. Pqp way is a little annoying because it is placed over the content and you have no way, for example, to see the 'old' debug info, or the footer of the theme. Also, when the box is full height, you cannot click on mainmenu links, they are visible but not reachable. What I like in pqp way (although I have already made some changes in the code) is the chronology. You can know when XOOPS boot begins, when blocks are loaded, when module is being executed, etc. You can isolate now for instance, what queries are made for each block. This is very useful and can give you a more wide picture on how XOOPS works.

6
frankblack
Re: Xoops debug improvement
  • 2009/4/29 19:11

  • frankblack

  • Just can't stay away

  • Posts: 830

  • Since: 2005/6/13


I see, so then good luck! I hope the devkit will help a bit.

7
urbanspacema
Re: Xoops debug improvement

hello, me and a friend are working on some modules that use jQuery / ajax in administration and user side. Debugging of XOOPS blocking ajax and interferes with the operation. should find a solution. I for the moment disable debugging.
http://www.ultrasonica.it
http://www.noisecollective.net

Login

Who's Online

236 user(s) are online (146 user(s) are browsing Support Forums)


Members: 0


Guests: 236


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Apr 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits