| -rw-r--r-- | htdocs/ancestry/layout.chtml | 4 | ||||
| -rw-r--r-- | htdocs/exceptions/compile.chtml | 3 | ||||
| -rw-r--r-- | htdocs/exceptions/index.chtml | 3 | ||||
| -rw-r--r-- | htdocs/exceptions/preprocess.chtml | 3 | ||||
| -rw-r--r-- | htdocs/exceptions/runtime.chtml | 3 | ||||
| -rw-r--r-- | htdocs/index.chtml | 4 | ||||
| -rw-r--r-- | htdocs/quickref/index.chtml | 3 | ||||
| -rw-r--r-- | htdocs/quickref/metasyntax.chtml | 3 | ||||
| -rw-r--r-- | htdocs/simple.chtml | 3 | ||||
| -rw-r--r-- | htdocs/sources.chtml | 3 | ||||
| -rw-r--r-- | htdocs/view.chtml | 3 |
11 files changed, 22 insertions, 13 deletions
diff --git a/htdocs/ancestry/layout.chtml b/htdocs/ancestry/layout.chtml index 4551d04..64d1cd2 100644 --- a/htdocs/ancestry/layout.chtml +++ b/htdocs/ancestry/layout.chtml @@ -1,34 +1,34 @@ -% html(); return; /* vim:set ft=sitecing: */ -%%derive page = "/ancestry/page.chtml"; +%%derive page = "/ancestry/page.chtml"; /* vim:set ft=sitecing: */ +%%pragma main=page <%decl> #define PN_PREV(h,d,t) urlPrev=h; descPrev=d; titlePrev=t; #define PN_NEXT(h,d,t) urlNext=h; descNext=d; titleNext=t; </%decl> %%impl #include <sitecing/util.h> %%impl #include "acconfig.h" %%var bool b_svn = false; %%var std::string urlPrev; %%var std::string descPrev; %%var std::string titlePrev; %%var std::string urlNext; %%var std::string descNext; %%var std::string titleNext; <%constructor> if(strstr(PACKAGE_STRING,"svn")) b_svn = true; </%constructor> <%method void prevnext() %> % if(urlPrev.empty() && urlNext.empty()) return; % if(descPrev.empty() && descNext.empty()) return; <div class="prevnext"> % if(!(urlPrev.empty() || descPrev.empty())) { <a class="prevnext-prev" href="<% urlPrev %>" title="<% sitecing::html_escape(titlePrev.empty()?descPrev:titlePrev) %>">◄ <% sitecing::html_escape(descPrev) %></a> % } % if(!(urlNext.empty() || descNext.empty())) { <a class="prevnext-next" href="<% urlNext %>" title="<% sitecing::html_escape(titleNext.empty()?descNext:titleNext) %>"><% sitecing::html_escape(descNext) %> ►</a> % } </div> </%method> <%method void body() %> <div id="content"> <%code> diff --git a/htdocs/exceptions/compile.chtml b/htdocs/exceptions/compile.chtml index 68dd034..94bd2e1 100644 --- a/htdocs/exceptions/compile.chtml +++ b/htdocs/exceptions/compile.chtml @@ -1,34 +1,35 @@ -% html(); return; /* vim:set ft=sitecing: */ +% /* vim:set ft=sitecing: */ %%derive layout = "/ancestry/layout.chtml"; +%%pragma main=page <%constructor> b_strict = false; PN_PREV("/exceptions/preprocess","preprocess","preprocessing errors"); PN_NEXT("/exceptions/runtime","runtime","runtime exceptions"); </%constructor> <%codemethod string title() %> return "compile-time exceptions handling"; </%codemethod> <%method void content() %> <h1>site-C-ing compile-time exception handling</h1> <p> Similar to <a href="/exceptions/preprocess">preprocessing exceptions</a> there is a wide range of errors you may put into your code which will pass through preprocessor and will be caught later at the compile-time. </p> <p> Once you complete writing your <a href="/view/htdocs/exceptions/development/compile.chtml" target="insert" title="the link opens in the frame below">erroneous code</a> and <em>site-C-ing</em> is done preprocessing it, it will feed the preprocessed code into c++ compiler which will refuse to compile the code like this. This is where <a href="/view/htdocs/handlers/exception_dev" target="insert" title="the link opens in the frame below">the exception 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>, takes over the process and gives you <a href="/exceptions/development/compile" target="insert" title="the link opens in the frame below">the report</a>. Like with any handler, you may wish to set some <a href="/view/htdocs/handlers/exception_prod" target="insert" title="the link opens in the frame below">different handler</a> in your <a href="/view/htdocs/exceptions/production/.scrc" target="insert" title="the link opens in the frame below">production configuration</a>, which just gives diff --git a/htdocs/exceptions/index.chtml b/htdocs/exceptions/index.chtml index 6bb2a3c..c700e42 100644 --- a/htdocs/exceptions/index.chtml +++ b/htdocs/exceptions/index.chtml @@ -1,34 +1,35 @@ -% html(); return; /* vim:set ft=sitecing: */ +% /* vim:set ft=sitecing: */ %%derive layout = "/ancestry/layout.chtml"; +%%pragma main=page <%constructor> PN_PREV("/simple","simple page","building a really simple page"); PN_NEXT("/exceptions/preprocess","preprocess","preprocessing errors"); </%constructor> <%codemethod string title() %> return "exceptions handling"; </%codemethod> <%method void content() %> <h1>site-C-ing exception handling</h1> <p> The purpose of this section is to give an overview of the <em>site-C-ing</em> exception handling mechanism. Before the web visitor can see the page each site-C-ing component goes through a few stages, namely, preprocessing, compiling and execution. Having three stages to go through also means three stages one can fail to go through and three exciting opportunities to handle different errors. </p> <p> First each component is preprocessed so that you can feed the valid c++ code to the compiler. Here is where the preprocessor can choke at your broken source code. Once preprocessor failes to parse your code it will throw an exception which <em>site-C-ing</em> will catch and pass to <a href="/sources/htdocs/handlers/exception_dev" title="development mode exception handler source">the exception handler component</a>. Want to <a href="/exceptions/preprocess">read more</a> about preprocessor exception handling? </p> <p> After the preprocessing stage is over we have a great opportunity to catch the compile-time errors. After <em>site-C-ing</em> fails to compile the component it throws another exception and passes it to the same handler which may show you some information on what's gone wrong with your source code from diff --git a/htdocs/exceptions/preprocess.chtml b/htdocs/exceptions/preprocess.chtml index 88b8741..e42b102 100644 --- a/htdocs/exceptions/preprocess.chtml +++ b/htdocs/exceptions/preprocess.chtml @@ -1,34 +1,35 @@ -% html(); return; /* vim:set ft=sitecing: */ +% /* vim:set ft=sitecing: */ %%derive layout = "/ancestry/layout.chtml"; +%%pragma main=page <%constructor> b_strict = false; PN_PREV("/exceptions","exceptions","exception handling overview"); PN_NEXT("/exceptions/compile","compile-time","compile-time errors"); </%constructor> <%codemethod string title() %> return "preprocessor exceptions handling"; </%codemethod> <%method void content() %> <h1>site-C-ing preprocessor exception handling</h1> <p> It was one of those days when you just can't type right and can't think of what you're typing. It is not unusual that, under such circumstances, you end up with a code like <a href="/view/htdocs/exceptions/development/preprocess.chtml" target="insert" title="the link opens in the frame below">this</a> -- by the time you were about to close your <code><%code></code> block you were thinking about some constructor in some component elsewhere in the universe. </p> <p> <em>site-C-ing</em> parser will see the inconsistency and throw an exception which will be caught and passed 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/preprocess" 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 diff --git a/htdocs/exceptions/runtime.chtml b/htdocs/exceptions/runtime.chtml index 1fcd80f..989e89f 100644 --- a/htdocs/exceptions/runtime.chtml +++ b/htdocs/exceptions/runtime.chtml @@ -1,34 +1,35 @@ -% html(); return; /* vim:set ft=sitecing: */ +% /* vim:set ft=sitecing: */ %%derive layout = "/ancestry/layout.chtml"; +%%pragma main=page <%constructor> b_strict = false; PN_PREV("/exceptions/compile","compile-time","compile-time errors"); 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 diff --git a/htdocs/index.chtml b/htdocs/index.chtml index 20d34c2..76d6d7e 100644 --- a/htdocs/index.chtml +++ b/htdocs/index.chtml @@ -1,34 +1,34 @@ -% html(); return; /* vim:set ft=sitecing: */ -%%derive layout = "/ancestry/layout.chtml"; +%%derive layout = "/ancestry/layout.chtml"; /* vim:set ft=sitecing: */ +%%pragma main=page <%constructor> PN_NEXT("/simple","simple page","building a really simple page"); </%constructor> <%codemethod string title() %> return "introduction"; </%codemethod> <%method void content() %> <h1>introduction to site-C-ing</h1> <p> This is a sample site, which is supposed to demonstrate <em>site-C-ing</em> features. Since the <em>site-C-ing</em> is still at the early stages of development or rather proof of concept, this site is also far from being complete. I am planning to add more pages as the time permits, though. </p> <p> Once you download and install <a href="http://kin.klever.net/sitecing/">site-C-ing</a> you may wish to try this sample site for yourself. The source is available from <a href="http://kin.klever.net/sitecing/sources">the site-C-ing download page</a>. After you download the source code, you should configure it using the ever so popular <code>configure</code> script. It is likely that you will want to pass the <code>--with-vhostname</code> option to configure to name the apache virtual host. </p> <p> The configure script will generate the apache vhost configuration for you, which you can <code>Include</code> in the main apache configuration file. </p> <p class="note"> Note, that the configuration is tailored for apache 2.x. It is no problem to get it working with apache 1.3.x, although I haven't tried and so I am not sure if it will run out of the box (your patches are <a diff --git a/htdocs/quickref/index.chtml b/htdocs/quickref/index.chtml index d139190..5119723 100644 --- a/htdocs/quickref/index.chtml +++ b/htdocs/quickref/index.chtml @@ -1,17 +1,18 @@ -% html(); return; /* vim:set ft=sitecing: */ +% /* vim:set ft=sitecing: */ %%derive layout = "/ancestry/layout.chtml"; +%%pragma main=page <%constructor> PN_PREV("/exceptions/runtime","runtime","runtime exceptions"); PN_NEXT("/quickref/metasyntax","syntax","meta syntax"); </%constructor> <%codemethod string title() %> return "quick reference"; </%codemethod> <%method void content() %> <h1>site-C-ing quick reference</h1> <p> I am hoping to put together some quick reference documentation here. For now, I am adding the <a href="/quickref/metasyntax">component meta-syntax quick reference</a>. </p> </%method> diff --git a/htdocs/quickref/metasyntax.chtml b/htdocs/quickref/metasyntax.chtml index 4efc37c..67186f9 100644 --- a/htdocs/quickref/metasyntax.chtml +++ b/htdocs/quickref/metasyntax.chtml @@ -1,34 +1,35 @@ -% html(); return; /* vim:set ft=sitecing: */ +% /* vim:set ft=sitecing: */ %%derive layout = "/ancestry/layout.chtml"; +%%pragma main=page <%constructor> PN_PREV("/quickref/","quick reference","quick reference"); PN_NEXT("/sources","sources","source browser"); </%constructor> <%codemethod string title() %> return "meta syntax quick reference"; </%codemethod> <%method void content() %> <h1>site-C-ing meta syntax quick reference</h1> <h2>Table of Contents</h2> <ul class="quickref toc"> <li><a href="#qr__line">% ...</a></li> <li><a href="#qr__inline"><% ... %></a></li> <li><a href="#qr__code"><%code></a></li> <li><a href="#qr__codemethod"><%codemethod ... ></a></li> <li><a href="#qr__constructor"><%constructor></a></li> <li><a href="#qr__decl"><%decl></a></li> <li><a href="#qr___decl">%%decl</a></li> <li><a href="#qr___derive">%%derive</a></li> <li><a href="#qr__destructor"><%destructor></a></li> <li><a href="#qr__impl"><%impl></a></li> <li><a href="#qr___impl">%%impl</a></li> <li><a href="#qr__method"><%method ... ></a></li> <li><a href="#qr__output"><%output></a></li> <li><a href="#qr___pragma">%%pragma</a></li> <li><a href="#qr___var">%%var</a></li> </ul> <dl class="metasyntax quickref"> diff --git a/htdocs/simple.chtml b/htdocs/simple.chtml index 845b840..d538b01 100644 --- a/htdocs/simple.chtml +++ b/htdocs/simple.chtml @@ -1,33 +1,34 @@ -% html(); return; /* vim:set ft=sitecing: */ +% /* vim:set ft=sitecing: */ %%derive layout = "/ancestry/layout.chtml"; +%%pragma main=page <%constructor> b_strict = false; PN_PREV("/","overview","introduction to site-C-ing"); PN_NEXT("/exceptions","exceptions","exception handling overview"); </%constructor> <%codemethod string title() %> return "simple page"; </%codemethod> <%method void content() %> <h1>building a really simple page</h1> <p> Building a really simple page is really simple. I will not go into much detail here. The example provided should speak for itself. </p> <p> The component being written doesn't do much but show you the calendar for the current month. First, take a look at <a href="/view/htdocs/examples/calendar.chtml" title="the link opens in the frame below" target="insert">the code</a> and, after you examined it, feel free to check out <a href="/examples/calendar" title="the link opens in the frame below" target="insert">the output</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> diff --git a/htdocs/sources.chtml b/htdocs/sources.chtml index 8c0c701..268b0e0 100644 --- a/htdocs/sources.chtml +++ b/htdocs/sources.chtml @@ -1,35 +1,36 @@ -% html(); return; /* vim:set ft=sitecing: */ +% /* vim:set ft=sitecing: */ %%derive layout = "/ancestry/layout.chtml"; %%derive sources = "/ancestry/sources.chtml"; +%%pragma main=page <%impl> #include <sitecing/sitecing_util.h> </%impl> <%constructor> b_strict = false; PN_PREV("/quickref/metasyntax","syntax","meta syntax"); </%constructor> <%codemethod string title() %> return "runtime exceptions handling"; </%codemethod> <%method void content() %> <h1>browse this site sources</h1> <ul class="sourcebrowser"> % for(int n=0;n<source_files_count;n++) { % sourcefile_t& sf = source_files[n]; % if(!sf.name) { /* the beginning or the end of the directory */ % if(sf.dir) { /* the beginning */ <li class="dir"><% sf.dir %>/<ul class="dir"> % }else{ /* the end */ </ul></li> % } % }else{ <li class="file"><a href="/view/<% sf.dir %>/<% sf.name %>" title="<% sf.desc %>" target="insert"><% sf.name %></a></li> % } % } </ul> <%code> string rfile = sitecing::normalize_path( sitecing::strip_prefix(__CGI->get_meta("PATH_INFO"),"/sources.chtml"), sitecing::restrict_dotdot|sitecing::strip_leading_slash ); diff --git a/htdocs/view.chtml b/htdocs/view.chtml index d885330..f729465 100644 --- a/htdocs/view.chtml +++ b/htdocs/view.chtml @@ -1,35 +1,36 @@ -% html(); return; /* vim:set ft=sitecing: */ +% /* vim:set ft=sitecing: */ %%derive page = "/ancestry/page.chtml"; %%derive sources = "/ancestry/sources.chtml"; +%%pragma main=page <%impl> #include <iostream> #include <fstream> using namespace std; #include <sitecing/util.h> #include <sitecing/sitecing_util.h> #include <konforka/exception.h> #include "acconfig.h" </%impl> <%codemethod string title() %> return "introduction"; </%codemethod> <%method void body() %> <%code> string rfile = sitecing::normalize_path( sitecing::strip_prefix(__CGI->get_meta("PATH_INFO"),"/view.chtml"), sitecing::restrict_dotdot|sitecing::strip_leading_slash ); sourcefile_t *sof = 0; for(int n=0;n<source_files_count;n++) { sof = &source_files[n]; if(sof->name && sof->dir) { if(sitecing::normalize_path(sitecing::combine_path(sof->dir,sof->name,0),sitecing::strip_leading_slash)==rfile) break; } sof = 0; } if(!sof) throw konforka::exception(CODEPOINT,"no access to the file allowed"); string afile = sitecing::combine_path(WEB_ROOT,rfile,0); </%code> <div class="source"> <h1><% rfile %></h1> |