zk_html/diary/2002-08-09-20:22:13.html

46 lines
3.2 KiB
HTML

<!doctype html>
<html>
<head>
<title>Zk | Concerning the Content Manager.</title>
<link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Gentium+Plus:ital,wght@0,400;0,700;1,400;1,700&family=Lato&family=Ubuntu+Monodisplay=swap" />
<link rel="stylesheet" type="text/css" href="/style.css" />
<meta name="viewport" content="width=device-width" />
<meta charset="utf-8" />
</head>
<body>
<main>
<header>
<h1>Zk | Concerning the Content Manager.</h1>
</header>
<article class="content">
<p><span class="tag">diary</span> <span class="tag">livejournal</span> <span class="tag">fossils</span></p>
<p>First of all, it needs a good name. I don&rsquo;t want to just call it &lsquo;RF!P Manager&rsquo; or anything, and I&rsquo;ve pretty much exhausted adding &lsquo;Fox&rsquo; to the front of my project names.. Oh well. If anyone has any suggestions, feel free to let me know.</p>
<p>The actual content managing program would be pretty short; all it would have to do is read in a file containing a list of extensions and the plugin associated with them, then read in the extension file and eval it with either the name of the file or a filehandle passed to it (perhaps open to a scalar filehandle, so you have the filename, too, and don&rsquo;t have to access <code>$ENV{&lsquo;PATH_INFO&rsquo;}</code> all the time) along with the CGI handler (add <code>$ENV{&lsquo;PATH_INFO&rsquo;}</code> args to CGI params).</p>
<p>An example url would be ranna.bolognia.net/man/addtable.atm, which is just an html file that requires the user to be logged in to access (Admin::HTML). The atm file has a form who&rsquo;s action url is /man/addtable.adm, where adm is aliased to the function Admin::Admin which requires a password. The addtable would create an SQL file with the suffix .asql and link to it. The extension .asql is aliased to Admin::SQL, which would decide whether to <code>$dbh-&gt;do()</code> or <code>$sth = $dbh-&gt;prepare(); &hellip;</code> it, and require a password in the process.</p>
<p>/man alone would have a default action to parse (<code>$action = $ENV{&lsquo;PATH_INFO&rsquo;} || &ldquo;/index.html&rdquo;;</code>). /man/.ext would dump information about the extension &lsquo;ext&rsquo; (a third field in the config file? <code>extension subroutine info-file</code>)</p>
<p>An idea for a configuration file:
<code># Admin types:
.ah?tml? Admin::HTML ahtml.nfo
.adm Admin::Admin admin.nfo
.asql Admin::SQL asql.nfo</p>
<h1 id="syntax-highlighting">Syntax highlighting:</h1>
<p>.(pl|c|cc|tex|java) Syntax syntax.nfo</p>
<h1 id="livejournal">LiveJournal:</h1>
<p>.lj LiveJournal lj.nfo</p>
<h1 id="info-and-pod-files">Info and POD files:</h1>
<p>.(nfo|pod) POD2HTML nfopod.nfo&lt;/code</p>
</article>
<footer>
<p>Page generated on 2002-08-09 20:22:13</p>
</footer>
</main>
<script type="text/javascript">
document.querySelectorAll('.tag').forEach(tag => {
let text = tag.innerText;
tag.innerText = '';
tag.innerHTML = `<a href="/tags.html#${text}">${text}</a>`;
});
</script>
</body>
</html>