Tracy: the standalone version of Nette Debugger

David Grudl wrote:

And now it is called Tracy.

Currently, Tracy has the same API as Nette\Diagnostics (only namespace was changed). But I think this is chance to take a step in the development and find much better API. Any ideas?

Wouldn't it be better then if Nette was using Tracy rather than Nette\Diagnostics as there would be no duplicities when updating either source (Nette master/Tracy master)? In my opinion both should be identical. Or not?

Nette itself should require/suggest Tracy in composer.json and remove Nette\Diagnostics.

@**Filip Procházka**: But I think that if replace Nette\Diagnostic with Tracy (over composer) will be in 2.1 … you can skip alliases

@**Filip Procházka**: That sounds like a good idea ;)

And add one more shortcut:

function bdump($var)
{
	Tracy\Debugger::barDump(func_get_args());
}

To the API change topic… I would appreciate these changes.

1. Convert static classes to singletons. For Dumper and Debugger at least. In my code is often Debugger::log($e), in better cases $this->logger->log($e) where:

class ErrorLogger {
	public function log(...) {
		Tracy\Debugger::log(...);
	}
}

2. Provide mechanism to object dumping. E.g. Dumper::forObject('Milo\Class', function($dumper) {...}).
3. Provide mechanism to easiest Dumper or Debugger configuration. This is my often usage:

Tracy\Debugger::enable(...);
Tracy\Debugger::$strictMode = TRUE;
Tracy\Debugger::$maxDepth = 1e5;
// and configure Dumper::COLLAPSE_COUNT is very hard

// Fluent may be helpful
Tracy\Debugger::configure()->enable(TRUE)->email(...)->getDumper()->maxDepth(10);

4. Somehow remember which object/class members should stay collapsed or expanded. Or mark them as non-dumpable. It is very useful for big structures where is a little bit annoying still clicking after every dump. I have no concrete idea how to do it. Perhaps over JavaScript and cookie

this.collapsed['Milo\Class::member'] = TRUE;

5. Provide interface to logging on non-stdout. Useful during XML-RPC debugging where FireBug does not exists. I have a SqliteDebugger where I fill dumps and by AJAX dumping them into browser. Somehow easy redirect whole BlueScreen/dumps html would be great.
6. Possibility to continue after Warning/Notice in strictMode, just like PHP itself.

These are things which I find useful to have. I'm sure that some of issues can be solved in other way I proposed, it is just idea.