scriptorium 0.6.1 → 0.7.2

data/doc/imported/0019-custom-exceptions-via-metaprogramming/source.lt3

@@ -0,0 +1,101 @@
+.h1 Custom exceptions via metaprogramming
+
+.set post.num = 0019
+.set post.slug = custom-exceptions-via-metaprogramming
+.set post.date = 2020-02-17
+.set post.title = Custom exceptions via metaprogramming
+.set post.tags = 
+.set post.views = computing computing
+.set post.published = yes
+.set post.deployed = no
+
+Suppose you want a large number of custom exceptions. And suppose you're not afraid of metaprogramming.
+A few months back, I found myself wanting to be "more specific" with the exceptions
+I raised in my ongoing RuneBlog project (which is used to create this blog). I
+wanted to raise specific exceptions with custom parameterized messages (without
+repeating myself too much).
+
+Here's an example of the "usual" way to do this:
+
+class MyException < StandardError
+
+def initialize(file, dir)
+    msg = "Could not find #{file} under #{dir}"
+    super(msg)
+  end
+
+end
+
+raise MyException.new("stuff.txt", "/home/willard")
+
+# Output:
+# exc.rb:10:in `<main>': Could not find stuff.txt under /home/willard (MyException)
+
+Now there is nothing particularly wrong with that. But as it happens, I wanted a 
+large number of exceptions with fairly descriptive names. I didn't want to type
+(or even paste) this stuff over and over.
+
+Here comes the "not afraid of metaprogramming" part. This is what I did:
+
+def make_exception(sym, str, target_class = Object)
+  return if target_class.constants.include?(sym)
+  target_class.const_set(sym, StandardError.dup)
+  define_method(sym) do |*args|
+    msg = str.dup
+    args.each.with_index {|arg, i| msg.sub!("%#{i+1}", arg) }
+    target_class.class_eval(sym.to_s).new(msg)
+  end
+end
+
+Now, what does this do? The method takes two parameters (or three if you count the
+target class which defaults to Object). You specify a symbol (for the
+name of the exception) and a string (for the exception message). It then does
+two things: It creates an exception class (named after the symbol); and it creates
+a method of the same name.
+
+Here are examples of calling make_exception:
+
+make_exception(:NotImplemented, "Feature not yet implemented")
+make_exception(:CantOpen,       "Can't open '%1'")
+make_exception(:InternalError,  "Internal error: Method %1 got arg '%2'")
+
+And here are examples of raising these exceptions:
+
+raise NotImplemented
+raise CantOpen(somefile)
+raise InternalError(__method__, arg)
+
+You might ask: Why define a method returning an exception object? The answer
+is that I don't want to write these this way:
+
+raise NotImplemented.new("Feature not yet implemented")
+raise CantOpen.new("Can't open '#{somefile}'")
+raise InternalError.new("Internal error: Method #{__method__} got arg '#{arg}'")
+
+I perceive four advantages doing it the first way: I don't have to specify the 
+message string each time; I still get to have a descriptive, unique class name
+without the message making it seem redundantly; I don't have to interpolate
+values into the message string explicitly; and I don't have to say .new 
+every time.
+
+Some of you may have two questions: Can you (or should you) really have a 
+capitalized method name? Can a method have the same name as a class without
+confusing the interpreter?
+
+I'll answer both those questions with an example from the Ruby core: There
+is an Integer class and an Integer method (naturally related to each other).
+Ruby distinguishes between these by context. It's not impossible, and I argue
+it's not a bad practice.
+
+As for the parameters, it's intuitive how they work. A % sign signals a 
+numbered replaceable piece of text, and these are replaced with the parameters
+specified when the method is called.
+
+That part of the code is not really robust, by the way. As it is written now,you could easily confuse it-- make it misbehave or crash. But you get the idea.
+
+So far, I have defined 23 custom exceptions in this project. Each definition
+occupies a single line. If I want to change the behavior of all of them in
+some way, I will go and change the make_exception method (which itself is
+only 9 lines).
+
+Like it, hate it? Comments welcome.

data/doc/imported/0020-fffff/metadata.txt

@@ -0,0 +1,7 @@
+    num  0020
+  title  fffff
+   date  2020-01-21
+pubdate  2020-01-21
+  views  computing computing
+   tags  
+ pinned  

data/doc/imported/0020-fffff/post.html

@@ -0,0 +1,24 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta charset="utf-8">
+  <title>fffff</title>
+  <meta name="generator" content="Scriptorium Import">
+  <meta property="og:title" content="fffff">
+  <meta property="og:locale" content="en_US">
+  <meta property="og:type" content="article">
+  <meta property="article:published_time" content="2020-01-21">
+</head>
+<body>
+  <article>
+    <header>
+      <h1>fffff</h1>
+      <time datetime="2020-01-21">January 21, 2020</time>
+    </header>
+    
+    <div class="content">
+      <p>
+    </div>
+  </article>
+</body>
+</html>

data/doc/imported/0020-fffff/source.lt3

@@ -0,0 +1,12 @@
+.h1 fffff
+
+.set post.num = 0020
+.set post.slug = fffff
+.set post.date = 2020-01-21
+.set post.title = fffff
+.set post.tags = 
+.set post.views = computing computing
+.set post.published = yes
+.set post.deployed = no
+
+

data/doc/imported/0021-trying-ror-yet-again/metadata.txt

@@ -0,0 +1,7 @@
+    num  0021
+  title  Trying ROR yet again
+   date  2020-06-15
+pubdate  2020-06-15
+  views  computing
+   tags  
+ pinned  

data/doc/imported/0021-trying-ror-yet-again/post.html

@@ -0,0 +1,26 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta charset="utf-8">
+  <title>Trying ROR yet again</title>
+  <meta name="generator" content="Scriptorium Import">
+  <meta property="og:title" content="Trying ROR yet again">
+  <meta property="og:locale" content="en_US">
+  <meta property="og:type" content="article">
+  <meta property="article:published_time" content="2020-06-15">
+</head>
+<body>
+  <article>
+    <header>
+      <h1>Trying ROR yet again</h1>
+      <time datetime="2020-06-15">June 15, 2020</time>
+    </header>
+    
+    <div class="content">
+      <p>
+
+Those who know me know I'm not a Rails guy.
+    </div>
+  </article>
+</body>
+</html>

data/doc/imported/0021-trying-ror-yet-again/source.lt3

@@ -0,0 +1,12 @@
+.h1 Trying ROR yet again
+
+.set post.num = 0021
+.set post.slug = trying-ror-yet-again
+.set post.date = 2020-06-15
+.set post.title = Trying ROR yet again
+.set post.tags = 
+.set post.views = computing
+.set post.published = yes
+.set post.deployed = no
+
+Those who know me know I'm not a Rails guy.

data/doc/imported/0023-doctor-sleep/metadata.txt

@@ -0,0 +1,7 @@
+    num  0023
+  title  Doctor Sleep
+   date  2020-11-07
+pubdate  2020-11-07
+  views  chiller
+   tags  
+ pinned  

data/doc/imported/0023-doctor-sleep/post.html

@@ -0,0 +1,63 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta charset="utf-8">
+  <title>Doctor Sleep</title>
+  <meta name="generator" content="Scriptorium Import">
+  <meta property="og:title" content="Doctor Sleep">
+  <meta property="og:locale" content="en_US">
+  <meta property="og:type" content="article">
+  <meta property="article:published_time" content="2020-11-07">
+</head>
+<body>
+  <article>
+    <header>
+      <h1>Doctor Sleep</h1>
+      <time datetime="2020-11-07">November 07, 2020</time>
+    </header>
+    
+    <div class="content">
+      <p>
+If you didn't know, this is the sequel to <i>The Shining</i>.
+
+I have to say: It was well done. It's not a Kubrick movie (and there will
+never be another one), but in its own way, it's faithful enough to the
+original.
+
+<p>
+What do you get with a Stephen King story? Well, let's be honest. He is a
+little too good for the stuff he writes. He himself said, "I am the literary
+equivalent of a burger and fries." And he isn't wrong.
+
+<p>
+But on the other hand, his characters are wonderfully three-dimensional.
+(To be honest, I'm quoting someone who taught a writing seminar I was in
+years ago. But it's spot on.) He is a master of characterization and dialogue,
+of plotting and pacing, and his use of language sometimes rises to the realm
+of the sublime.
+
+<p>
+Of course, even a well-written book doesn't always mean a good movie. I have
+seen some movies apparently based on his works that made me think: As an
+author, he must be crying and hiding his face... all the way to the bank.
+
+<p>
+And though I have seen more King movies than I have read King novels, I
+thought I could see his work shining through here. (Pun totally not intended.)
+Add to that a few wonderful and innovative bits of CG, some interesting
+camera angles, and yes, some really decent acting here and there. What you
+then get is not exactly a masterpiece, but something well worth watching.
+
+<p>
+There are arguably some downsides here. Some of the effects might be a little
+cheesy, some of the tropes a little timeworn, some of the acting a little off.
+But so what? It's better than 90% of the stuff I've streamed lately.
+
+<p>
+I don't like "stars" for reviews. I'm trying to figure out what other kind of
+little icon or widget or thingy I can use. But until then: <i>Doctor Sleep</i>
+gets five stars.
+    </div>
+  </article>
+</body>
+</html>

data/doc/imported/0023-doctor-sleep/source.lt3

@@ -0,0 +1,44 @@
+.h1 Doctor Sleep
+
+.set post.num = 0023
+.set post.slug = doctor-sleep
+.set post.date = 2020-11-07
+.set post.title = Doctor Sleep
+.set post.tags = 
+.set post.views = chiller
+.set post.published = yes
+.set post.deployed = no
+
+If you didn't know, this is the sequel to The Shining.
+
+I have to say: It was well done. It's not a Kubrick movie (and there will
+never be another one), but in its own way, it's faithful enough to the
+original.
+
+What do you get with a Stephen King story? Well, let's be honest. He is a
+little too good for the stuff he writes. He himself said, "I am the literary
+equivalent of a burger and fries." And he isn't wrong.
+
+But on the other hand, his characters are wonderfully three-dimensional.
+(To be honest, I'm quoting someone who taught a writing seminar I was in
+years ago. But it's spot on.) He is a master of characterization and dialogue,
+of plotting and pacing, and his use of language sometimes rises to the realm
+of the sublime.
+
+Of course, even a well-written book doesn't always mean a good movie. I have
+seen some movies apparently based on his works that made me think: As an
+author, he must be crying and hiding his face... all the way to the bank.
+
+And though I have seen more King movies than I have read King novels, I
+thought I could see his work shining through here. (Pun totally not intended.)
+Add to that a few wonderful and innovative bits of CG, some interesting
+camera angles, and yes, some really decent acting here and there. What you
+then get is not exactly a masterpiece, but something well worth watching.
+
+There are arguably some downsides here. Some of the effects might be a little
+cheesy, some of the tropes a little timeworn, some of the acting a little off.
+But so what? It's better than 90% of the stuff I've streamed lately.
+
+I don't like "stars" for reviews. I'm trying to figure out what other kind of
+little icon or widget or thingy I can use. But until then: Doctor Sleep
+gets five stars.

data/doc/imported/0024-just-a-test/metadata.txt

@@ -0,0 +1,7 @@
+    num  0024
+  title  Just a test...
+   date  2024-01-30
+pubdate  2024-01-30
+  views  chiller
+   tags  
+ pinned  

data/doc/imported/0024-just-a-test/post.html

@@ -0,0 +1,24 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta charset="utf-8">
+  <title>Just a test...</title>
+  <meta name="generator" content="Scriptorium Import">
+  <meta property="og:title" content="Just a test...">
+  <meta property="og:locale" content="en_US">
+  <meta property="og:type" content="article">
+  <meta property="article:published_time" content="2024-01-30">
+</head>
+<body>
+  <article>
+    <header>
+      <h1>Just a test...</h1>
+      <time datetime="2024-01-30">January 30, 2024</time>
+    </header>
+    
+    <div class="content">
+      [Content not available - this appears to be an incomplete post]
+    </div>
+  </article>
+</body>
+</html>

data/doc/imported/0024-just-a-test/source.lt3

@@ -0,0 +1,12 @@
+.h1 Just a test...
+
+.set post.num = 0024
+.set post.slug = just-a-test
+.set post.date = 2024-01-30
+.set post.title = Just a test...
+.set post.tags = 
+.set post.views = chiller
+.set post.published = yes
+.set post.deployed = no
+
+[Content not available - this appears to be an incomplete post]

data/doc/imported/import_summary.txt

@@ -0,0 +1,98 @@
+Runeblog Import Summary
+Generated: 2025-08-30 04:42:50
+==================================================
+
+✅ 0001 | 2014-07-29 | Elixir Conf 2014
+     Views: computing austin
+     Content: Available
+
+✅ 0002 | 2014-09-17 | Programmers and word processing
+     Views: computing writing
+     Content: Available
+
+✅ 0003 | 2015-07-17 | How to turn your brain sideways
+     Views: computing
+     Content: Available
+
+✅ 0004 | 2015-07-20 | Upcoming Lone Star Ruby Conference...
+     Views: computing austin
+     Content: Available
+
+✅ 0005 | 2015-07-22 | Elixir Conf 2015 announced
+     Views: computing
+     Content: Available
+
+✅ 0006 | 2015-07-23 | Ruby for Dinosaurs...
+     Views: computing
+     Content: Available
+
+✅ 0007 | 2015-07-27 | Phoenix isn't Rails
+     Views: computing
+     Content: Available
+
+✅ 0008 | 2015-08-10 | Concerning the term "monkeypatching"
+     Views: computing
+     Content: Available
+
+✅ 0009 | 2015-08-11 | Announcement coming soon...
+     Views: computing
+     Content: Available
+
+✅ 0010 | 2015-08-25 | Immutable data (ditching the wax tablet)
+     Views: computing
+     Content: Available
+
+✅ 0011 | 2015-09-17 | Computer science as a lost art
+     Views: computing
+     Content: Available
+
+✅ 0012 | 2015-11-10 | Ruby Day in Turin, Italy
+     Views: computing
+     Content: Available
+
+✅ 0013 | 2015-11-23 | RubyDay was a success
+     Views: computing
+     Content: Available
+
+✅ 0014 | 2016-04-14 | Working on the blogging software
+     Views: computing
+     Content: Available
+
+✅ 0015 | 2018-07-31 | OK, it's not really a lost art
+     Views: computing
+     Content: Available
+
+✅ 0016 | 2019-11-13 | An 'in' operator for Ruby
+     Views: computing
+     Content: Available
+
+✅ 0017 | 2019-12-25 | The Forgotten Mathematician
+     Views: computing
+     Content: Available
+
+✅ 0018 | 2020-01-21 | Ruby puns
+     Views: computing computing
+     Content: Available
+
+✅ 0020 | 2020-01-21 | fffff
+     Views: computing computing
+     Content: Available
+
+✅ 0019 | 2020-02-17 | Custom exceptions via metaprogramming
+     Views: computing computing
+     Content: Available
+
+✅ 0021 | 2020-06-15 | Trying ROR yet again
+     Views: computing
+     Content: Available
+
+✅ 0023 | 2020-11-07 | Doctor Sleep
+     Views: chiller
+     Content: Available
+
+⚠️ 0024 | 2024-01-30 | Just a test...
+     Views: chiller
+     Content: Placeholder only
+
+Total posts imported: 23
+Date range: 2014-07-29 to 2024-01-30

data/doc/livetext-informal-spec.txt

@@ -0,0 +1,65 @@
+Markup guidelines
+-----------------
+ 1. A line with no special content is rendered as-is. This includes
+    a blank line.
+ 2. The four "marker" characters are * _ ` ~ (bold, italic, code,
+    and strikethrough). These behave essentially the same way.
+    Let's use _ as a generic example.
+ 3. In general: A marker following a space or SOL marks a string 
+    terminated by a space or EOL.
+ 4. A marker is never terminated by the same marker (as in markdown)
+ 5. A single marker is a prefix that applies to a single token (with
+    no embedded spaces)
+ 6. Examples:
+      This is *bold
+      This is _italic
+      This is `code
+      This is ~strikethrough
+ 7. A special case is the "doubled" marker; this is for tokens (still
+    with no embedded spaces) that end in a period or comma. 
+    Examples:
+      Three variables are ``num, ``count, and ``max.
+      I am __hungry, I must say.
+      COBOL is just **wrong.
+ 8. When we need embedded spaces or greater control, we can use brackets
+    to delimit. Examples:
+      This is _[four words in italics].
+      You should run `[sblog web start] to start the server.
+ 9. A variable starts with a $; the identifier itself starts with a 
+    letter (uppercase or lower); other characters may be letters, digits,
+    or underscores; period is legal, but only as a separator. 
+      - No two periods in a row
+      - No period at beginning or end
+10. Variable examples:  $foo $foo.bar $web_server  $prep44
+11. Functions are named like variables, but start with $$.
+    Examples: $$max $$last.value $$this_line
+12. A function may be parameterless (as above)
+13. We may pass a single parameter (a string with no embedded spaces)
+    via a colon. Example: Please visit $$link:google.com soon.
+14. We may pass a longer parameter with brackets. 
+    Example: Learn $$index[functional programming] today!
+15. If a bracket is not closed, EOL closes it.
+16. A one-line comment starts with ". " (dot-space) at beginning of line.
+17. A dot command is a dot+identifier at SOL. These may or may not have 
+    parameters.
+    Examples:
+      .nopara
+      .index functional programming
+      .banner This is just a banner!
+18. As a special case, a dot command may be indented (preceded only by
+    spaces) with a $.
+    Examples:
+      .banner Not indented
+          $.banner Indented
+              $.index indentation
+19. Some dot commands can have bodies (a block of text terminated by .end).
+20. In general, a body can contain formatting, variables, and functions.
+21. A body cannot have dot commands inside it.
+22. Some dot commands DO NOT process their bodies (formatting, variables,
+    and functions. Notably .comment (block comment) does not. Also the 
+    special .raw (terminated not by .end but by __RAW__) does not.
+23. Dotcmds .def and .func have Ruby code in their bodies.
+24. .code lang - this has language "lang" in its body.
+
+
+

data/doc/myuserdoc/ch-0.lt3

@@ -0,0 +1,31 @@
+.comment
+  xx. Core Concepts
+      What is Scriptorium?
+        - Static files
+        - What are views? and why?
+        - What is a repository?
+        - How does deployment work?
+      What is Livetext?
+        - Why Livetext?
+        - Syntax in brief (1-2 paragraphs)
+.end
+ 
+.chapter Core Concepts
+
+ 
+.sec       What is Scriptorium?
+ 
+.sec         - Static files
+ 
+.sec         - What are views? and why?
+ 
+.sec         - What is a repository?
+ 
+.sec         - How does deployment work?
+ 
+.sec       What is Livetext?
+ 
+.sec         - Why Livetext?
+ 
+.sec         - Syntax in brief (1-2 paragraphs)
+ 

data/doc/myuserdoc/ch-1.lt3

@@ -0,0 +1,37 @@
+.comment
+  xx. Getting Started
+      Quick installation (gem install)
+      Interactive setup
+        - create repo
+        - create first view
+        - other commands
+        - the sample view
+        - first blog post
+      Basic Configuration
+      Checking dependencies
+      The "standard" theme (only one for now)
+.end
+ 
+.chapter Getting Started
+
+ 
+.sec       Quick installation (gem install)
+ 
+.sec       Interactive setup
+ 
+.subsec         - create repo
+ 
+.subsec         - create first view
+ 
+.subsec         - other commands
+ 
+.subsec         - the sample view
+ 
+.subsec         - first blog post
+ 
+.sec       Basic Configuration
+ 
+.sec       Checking dependencies
+ 
+.sec       The "standard" theme (only one for now)
+ 

data/doc/myuserdoc/ch-10.lt3

@@ -0,0 +1,22 @@
+.comment
+  xx. Reference
+      Command Reference
+      Configuration Files
+      LiveText Reference
+      API Reference
+      View Tree Structure
+.end
+ 
+.chapter Reference
+
+ 
+.sec       Command Reference
+ 
+.sec       Configuration Files
+ 
+.sec       LiveText Reference
+ 
+.sec       API Reference
+ 
+.sec       View Tree Structure
+ 

data/doc/myuserdoc/ch-2.lt3

@@ -0,0 +1,37 @@
+.comment
+  xx. The Front Page
+        - containers and their uses
+        - configuring header
+           - banner
+           - navbar
+        - configuring a sidebar
+        - the main container: post index
+      Widgets
+        - Links
+        - Pages
+        - Featured Posts
+.end
+ 
+.chapter The Front Page
+
+ 
+.sec         - containers and their uses
+ 
+.sec         - configuring header
+ 
+.sec            - banner
+ 
+.sec            - navbar
+ 
+.sec         - configuring a sidebar
+ 
+.sec         - the main container: post index
+ 
+.sec       Widgets
+ 
+.sec         - Links
+ 
+.sec         - Pages
+ 
+.sec         - Featured Posts
+ 

data/doc/myuserdoc/ch-3.lt3

@@ -0,0 +1,19 @@
+.comment
+  xx. Deployment & Hosting
+      Local Development
+      Server Deployment
+      Domain Configuration
+      SSL Setup
+.end
+ 
+.chapter Deployment & Hosting
+
+ 
+.sec       Local Development
+ 
+.sec       Server Deployment
+ 
+.sec       Domain Configuration
+ 
+.sec       SSL Setup
+