author | Michael Krelin <hacker@klever.net> | 2005-04-01 22:23:54 (UTC) |
---|---|---|
committer | Michael Krelin <hacker@klever.net> | 2005-04-01 22:23:54 (UTC) |
commit | 8e7ab6661815e333ee9377c2655a03aee89372c2 (patch) (side-by-side diff) | |
tree | 9bd424c20665b85a46ba26e38a7504ed7ad7cf68 /htdocs/exceptions/runtime.chtml | |
parent | d379841850daab4693d596784b790b13e20e3a03 (diff) | |
download | sitecing-8e7ab6661815e333ee9377c2655a03aee89372c2.zip sitecing-8e7ab6661815e333ee9377c2655a03aee89372c2.tar.gz sitecing-8e7ab6661815e333ee9377c2655a03aee89372c2.tar.bz2 |
added a quick reference section
Diffstat (limited to 'htdocs/exceptions/runtime.chtml') (more/less context) (ignore whitespace changes)
-rw-r--r-- | htdocs/exceptions/runtime.chtml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/htdocs/exceptions/runtime.chtml b/htdocs/exceptions/runtime.chtml index 9a72afd..1fcd80f 100644 --- a/htdocs/exceptions/runtime.chtml +++ b/htdocs/exceptions/runtime.chtml @@ -1,49 +1,49 @@ % html(); return; /* vim:set ft=sitecing: */ %%derive layout = "/ancestry/layout.chtml"; <%constructor> b_strict = false; PN_PREV("/exceptions/compile","compile-time","compile-time errors"); - PN_NEXT("/sources","sources","source browser"); + PN_NEXT("/quickref/","quick reference","quick reference"); </%constructor> <%codemethod string title() %> return "runtime exceptions handling"; </%codemethod> <%method void content() %> <h1>site-C-ing runtime exception handling</h1> <p> The component may throw an exception while executing and the <em>site-C-ing</em> will gladly pass it to the handler component which will give the user appropriate output (unless it throws an exception itself, of course). Here you will see an example output provided by the handler bundled with the <em>site-C-ing</em>. </p> <p> Suppose you have <a href="/view/htdocs/exceptions/development/runtime.chtml" target="insert" title="the link opens in the frame below">a component</a>, which at some point throws an exception. Of course, <em>site-C-ing</em> will catch the exception and pass it to <a href="/view/htdocs/handlers/exception_dev" target="insert" title="the link opens in the frame below">the handler</a>, specified in <a href="/view/htdocs/exceptions/development/.scrc" target="insert" title="the link opens in the frame below">the configuration file</a>, which will produce some nice, human-readable <a href="/exceptions/development/runtime" target="insert" title="the link opens in the frame below">output</a>. Well, you may not wish to give out all this information in the production environment, so you just put in your <a href="/view/htdocs/exceptions/production/.scrc" target="insert" title="the link opens in the frame below">configuration file</a> some <a href="/view/htdocs/handlers/exception_prod" target="insert" title="the link opens in the frame below">different handler</a>, which just gives user <a href="/exceptions/production/runtime" target="insert" title="the link opens in the frame below">a friendly yet lame excuse</a>. </p> <div class="insert"> <iframe id="insert" name="insert" src="about:blank" width="95%" height="300"> <p>I wanted to put an <iframe> here, but your browser does not seem to support it. That is okay, it still will open links somehow.</p> </iframe> </div> </%method> |