summaryrefslogtreecommitdiff
path: root/framework/Util/TLogger.php
AgeCommit message (Collapse)Author
2016-03-23belated happy new yearFabio Bas
2015-12-07Move urls from pradosoft.com to github's project page; drop unmaintained ↵Fabio Bas
quickstart tutorial translations
2015-11-07Prepare for release: update (c) year to 2015, version to 3.3Fabio Bas
2014-01-06Removed all @version $Id comments: they were managed by svn and are useless ↵Fabio Bas
with git
2014-01-06Happy 2014!Fabio Bas
2013-04-24Update to 3.2.1Ciro Mattia Gonano
2013-01-19bumped year to 2013, integrated recent changes from branch/3.2ctrlaltca
2012-07-12standardize the use of unix eol; use svn properties to enforce native eolctrlaltca
2012-07-12happy new yearctrlaltca
2011-12-21TLogger: fixed filterByControl method; added timestamp parameter; added ↵ctrlaltca@gmail.com
deleteLogs() method; refs #237
2011-06-20updated year information on all framework sources where possible (Copyright ↵ctrlaltca@gmail.com
© 2005-2008 PradoSoft => Copyright © 2005-2011 PradoSoft)
2010-04-14changed the gmdate to just date. TLogger now captures the memory footprint ↵javalizard
and controls. TLogRouter now can specify logs that require the header with the IHeaderRoute interface. so the TFirePhpLogRoute can work. TLogRoutes can be disabled and all of the routes can be gotten. Each TLogRoute also can have a control filter, user role filter (so, for instance, if you wanted a browser log route on a production site but only for developers), a meta id is also stored for linking to other data in the system, the user id if a user is logged in, active (so routes can be turned off but not deleted), and an error should something go bad with a log route it shouldn't take down the page. Updated the docs on the category filter having to be an array instead of a string. This includes some functions for serializing the Log Router classes as xml. Also the browser route does a quartile analysis on the times and memory footprint of each log item (independently), and highlights the log lines that are memory hogs or time hogs. We can use this as a basis for a set of analysis classes? This includes some interesting functions which does array of array key index to value sorting. For instance getting all rows from a database table. eg. $arr array(array('key'=>'value1', ...), array('key'=>...), array(...)). vsort($arr, 'key'). We may want to move some of this stuff around
2008-10-21removed all trailing ?>qiang.xue
2008-07-30updated copyrightknut
2006-09-08merge from 3.0 branch till 1397.xue
2006-04-03Modified storage type of timestamp.xue
2006-03-31Reorganized folders under framework. This may break existing applications.xue