From 707d2c72642b633d5ba8aa0373a272e972971535 Mon Sep 17 00:00:00 2001
From: tof <>
Date: Fri, 22 Feb 2008 17:22:17 +0000
Subject: Added TFirebugLogRoute

---
 demos/quickstart/protected/pages/Advanced/Logging.page           | 5 +++--
 demos/quickstart/protected/pages/GettingStarted/NewFeatures.page | 1 +
 2 files changed, 4 insertions(+), 2 deletions(-)

(limited to 'demos/quickstart')

diff --git a/demos/quickstart/protected/pages/Advanced/Logging.page b/demos/quickstart/protected/pages/Advanced/Logging.page
index 650de616..7f14c004 100644
--- a/demos/quickstart/protected/pages/Advanced/Logging.page
+++ b/demos/quickstart/protected/pages/Advanced/Logging.page
@@ -20,12 +20,13 @@ The difference between <tt>Prado::log()</tt> and <tt>Prado::trace()</tt> is  tha
 
 <h2 id="6103">Message Routing</h2>
 <p id="780618" class="block-content">
-Messages logged using the above two functions are kept in memory. To make use of the messages, developers need to route them to specific destinations, such as files, emails, or browser windows. The message routing is managed by <tt>System.Util.TLogRouter</tt> module. When plugged into an application, it can route the messages to different destination in parallel. Currently, PRADO provides three types of routes:
+Messages logged using the above two functions are kept in memory. To make use of the messages, developers need to route them to specific destinations, such as files, emails, or browser windows. The message routing is managed by <tt>System.Util.TLogRouter</tt> module. When plugged into an application, it can route the messages to different destination in parallel. Currently, PRADO provides four types of routes:
 </p>
 <ul id="u1" class="block-content">
   <li><tt>TFileLogRoute</tt> - filtered messages are stored in a specified log file. By default, this file is named <tt>prado.log</tt> under the runtime directory of the application. File rotation is provided.</li>
   <li><tt>TEmailLogRoute</tt> - filtered messages are sent to pre-specified email addresses.</li>
-  <li><tt>TBrowserLogRoute</tt> - filtered messages are appended to the end of the current page output.</li>
+  <li><tt>TBrowserLogRoute</tt> - filtered messages are appended to the end of the current page output.</li>
+  <li><tt>TFirebugLogRoute</tt> - filtered messages are sent to the <a href="http:/www.getfirebug.com">Firebug</a> console</li>
 </ul>
 <p id="780619" class="block-content">
 To enable message routing, plug in and configure the <tt>TLogRouter</tt> module in application configuration,
diff --git a/demos/quickstart/protected/pages/GettingStarted/NewFeatures.page b/demos/quickstart/protected/pages/GettingStarted/NewFeatures.page
index 3d9bc155..66e3111d 100644
--- a/demos/quickstart/protected/pages/GettingStarted/NewFeatures.page
+++ b/demos/quickstart/protected/pages/GettingStarted/NewFeatures.page
@@ -9,6 +9,7 @@ This page summarizes the main new features that are introduced in each PRADO rel
 <h2>Version 3.1.2</h2>
 <ul>
 <li>Added a new active control <a href="?page=ActiveControls.ActivePager">TActivePager</a> that allows to paginate a databound control with an ajax callback.</li>
+<li>Added TFirebugLogRoute to send logs to the Firebug console</li>
 </ul>
 
 <h2>Version 3.1.1</h2>
-- 
cgit v1.2.3