2009 keep on rolling

The daily work brought many new ideas to the project and the debugger had to fulfill a lot of different requirements. It was the year of fine tuning, the features where tested in many environments and use-cases. The debugger earned a fixed place in the development process of many projects and the software quality increased permanently.

Performance was a big point for that area, because every debugging output was append to the website source code and reached different browser or server limits sometimes. The debugger learned to respect his environment and reduced his output if necessary. Even the HTML, JavaScript and CSS elements were downsized to a reasonable scale.

More and more information's where removed from the default output and loaded when possible on demand from the server. This was a big advantage in compare to send every information to the user again and again, no matter if he really wants them.

The challenge to keep everything we need in one file for (really easy installations) required some new solutions to merge different file types together. Text based files where no big deal, but the use of images should be another great milestone inspired by the classic mime mails. They encode binary data with base64 and this allows us to store even image data as utf-8 compatible string. Finally a new animated icon was added with only 6kb written over 74 lines in the debuggers file to visualize background processes.

Configuration of the debugger was quite simple now. Once you activated the debug mode a configuration interface just through the existing function was established. A simple __debug('10%','config:maxMemory'); call told the debugger that he could use up to 10% of the available memory for his own data. This was very important to prevent memory limit exceeding, when the running PHP application needed a lot of memory.

xn.debug - free & easy - open sourceTo make the use of this tool even more comfortable, a documentation section was added with useful hints and tips to support the developer. The nifty trick was to extract the already existing source code documentation from the debugger file itself and bring it to the front client.

The debugger grows each day and the time feels ready to see the daylight. It is something like a proof of concept and this tool is ready to go into beta state. I hope it will help many people by their work and so I released it as an open source project in 2010.

The time has come, to overwork the whole idea and start work on version 2.0 in the hope that the open source community brings in their ideas, experiences and knowledge to build a next generation of debugging tools without the need of third party libraries.