runeblog 0.1.61 → 0.1.62
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.lt3 +36 -0
- data/README.md +94 -12
- data/lib/liveblog.rb +20 -0
- data/lib/runeblog_version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: e021bb5ab60b228bcc7dd8b0e088af60487f684b6c64abc619f09cbbdd843c8a
|
4
|
+
data.tar.gz: 572d365ddb2687da51026203f2ab4d88aeead5d84e891df5aeec6270f6e446c0
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 2917038cd8e6cadb31ee669027c19c7e2e35f96223a0beeb7df7da360af86042cb2d26403ed2df0a8cf3f4a3eef6936124d601771ff52742ed2fb284ea4d534b
|
7
|
+
data.tar.gz: 12c24806b6a78b9661ee51df1736591bdc7cd37fb311a20d9f1377213e53b53aa997a8ddb657058fed76fffc4d226f990f8f89d5468c3fdc2d9ef68b6ec6df59
|
data/README.lt3
CHANGED
@@ -102,5 +102,41 @@ The next thing you should do is to create at least one view of your own. Use the
|
|
102
102
|
|
103
103
|
*[To be continued]
|
104
104
|
|
105
|
+
.h2 Changing the default templates
|
106
|
+
|
107
|
+
*TBD
|
108
|
+
|
109
|
+
.h2 Basics of Livetext
|
110
|
+
|
111
|
+
*TBD
|
112
|
+
|
113
|
+
(bold, italics, etc.)
|
114
|
+
|
115
|
+
(common dot commands)
|
116
|
+
|
117
|
+
(predefined functions and variables)
|
118
|
+
|
119
|
+
.h2 Runeblog-specific features (Liveblog)
|
120
|
+
|
121
|
+
*TBD
|
122
|
+
|
123
|
+
(dot commands)
|
124
|
+
|
125
|
+
(variables and functions)
|
126
|
+
|
127
|
+
.h2 Defining your own features
|
128
|
+
|
129
|
+
(dot commands)
|
130
|
+
|
131
|
+
(variables and functions)
|
132
|
+
|
133
|
+
*TBD
|
134
|
+
|
135
|
+
.h2
|
136
|
+
|
137
|
+
*TBD
|
138
|
+
|
105
139
|
.h2 More later...
|
106
140
|
|
141
|
+
*TBD
|
142
|
+
|
data/README.md
CHANGED
@@ -7,13 +7,16 @@ Runeblog is a blogging tool written in Ruby. It has these basic characteristics:
|
|
7
7
|
* So far, yes, like Jekyll
|
8
8
|
* It's based on Livetext (highly extensible Ruby-based markup)
|
9
9
|
* It has the concept of multiple "views" for a blog
|
10
|
+
The multiple views are in effect multiple blogs managed with the same backend.
|
11
|
+
<p>
|
12
|
+
|
10
13
|
## What is Livetext?
|
11
14
|
Livetext is a markup format that is a throwback to the old, old days of text
|
12
|
-
formatters such as nroff
|
15
|
+
formatters such as <font size=+1><tt>nroff</tt></font>. It's very flexible, and it is extensible <i>in Ruby</i>.
|
13
16
|
<p>
|
14
17
|
|
15
|
-
It
|
16
|
-
with some custom definitions, to try to ease the formatting of a blog entry.
|
18
|
+
It is far from mature or full-featured, but it is usable. Runeblog uses Livetext,
|
19
|
+
along with some custom definitions, to try to ease the formatting of a blog entry.
|
17
20
|
<p>
|
18
21
|
|
19
22
|
## What are "views"?
|
@@ -32,8 +35,13 @@ But the important points are these:
|
|
32
35
|
* Any post can easily be included in a single view, in more than one, or in all of them.
|
33
36
|
* Each view can have its own look and feel, and it can be linked/published separately from the others.
|
34
37
|
* Each view can be hosted in a different location and/or a different server and domain
|
38
|
+
* Any post can be in more than one view
|
35
39
|
## The `blog environment
|
36
|
-
There is a command-line tool called <tt>blog</tt> which is a REPL (read-eval-print loop).
|
40
|
+
There is a command-line tool called <font size=+1><tt>blog</tt></font> which is a REPL (read-eval-print loop).
|
41
|
+
Note that this tool is a curses-based environment (mainly so it can display menus
|
42
|
+
and such to the user).
|
43
|
+
<p>
|
44
|
+
|
37
45
|
The help message looks like this:
|
38
46
|
<p>
|
39
47
|
|
@@ -43,7 +51,7 @@ The help message looks like this:
|
|
43
51
|
h, help This message
|
44
52
|
q, quit Exit the program
|
45
53
|
|
46
|
-
change view
|
54
|
+
change view _view Change current view
|
47
55
|
new view Create a new view
|
48
56
|
list views List all views available
|
49
57
|
lsv Same as: list views
|
@@ -53,19 +61,93 @@ The help message looks like this:
|
|
53
61
|
lsp, list posts List posts in current view
|
54
62
|
lsd, list drafts List all posts regardless of view
|
55
63
|
|
56
|
-
rm
|
57
|
-
edit
|
64
|
+
rm _id Remove a post
|
65
|
+
edit _id Edit a post
|
58
66
|
|
59
|
-
|
60
|
-
|
67
|
+
preview Look at current (local) view in browser
|
68
|
+
browse Look at current (deployed) view in browser
|
61
69
|
|
62
|
-
relink Regenerate index for all views
|
63
|
-
rebuild Regenerate all posts and relink
|
70
|
+
relink Regenerate index for all views (MAY CHANGE)
|
71
|
+
rebuild Regenerate all posts and relink (MAY CHANGE)
|
64
72
|
deploy Deploy (current view)
|
65
73
|
</pre>
|
66
|
-
##
|
74
|
+
## Getting started
|
75
|
+
But when you first run the REPL, it checks for an existing blog under the <font size=+1><tt>.blog</tt></font>
|
76
|
+
directory. If it doesn't find one, it asks whether you want to create a new blog.
|
77
|
+
If you enter <font size=+1><tt>y</tt></font> for yes, it creates a sort of "skeleton" with a single view
|
78
|
+
called <font size=+1><tt>test_view</tt></font>.
|
79
|
+
<p>
|
80
|
+
|
81
|
+
The next thing you should do is to create at least one view of your own. Use the
|
82
|
+
<font size=+1><tt>new view</tt></font> command for this.
|
83
|
+
<p>
|
84
|
+
|
85
|
+
(new view)
|
86
|
+
<p>
|
87
|
+
|
88
|
+
(new post)
|
89
|
+
<p>
|
90
|
+
|
91
|
+
(preview)
|
92
|
+
<p>
|
93
|
+
|
94
|
+
(publishing one-time setup - server, ssh keys, etc.)
|
95
|
+
<p>
|
96
|
+
|
97
|
+
(publish)
|
98
|
+
<p>
|
99
|
+
|
100
|
+
(browse)
|
101
|
+
<p>
|
102
|
+
|
103
|
+
(and so on...)
|
104
|
+
<p>
|
105
|
+
|
67
106
|
<b>To be continued</b>
|
68
107
|
<p>
|
69
108
|
|
109
|
+
## Changing the default templates
|
110
|
+
<b>TBD</b>
|
111
|
+
<p>
|
112
|
+
|
113
|
+
## Basics of Livetext
|
114
|
+
<b>TBD</b>
|
115
|
+
<p>
|
116
|
+
|
117
|
+
(bold, italics, etc.)
|
118
|
+
<p>
|
119
|
+
|
120
|
+
(common dot commands)
|
121
|
+
<p>
|
122
|
+
|
123
|
+
(predefined functions and variables)
|
124
|
+
<p>
|
125
|
+
|
126
|
+
## Runeblog-specific features (Liveblog)
|
127
|
+
<b>TBD</b>
|
128
|
+
<p>
|
129
|
+
|
130
|
+
(dot commands)
|
131
|
+
<p>
|
132
|
+
|
133
|
+
(variables and functions)
|
134
|
+
<p>
|
135
|
+
|
136
|
+
## Defining your own features
|
137
|
+
(dot commands)
|
138
|
+
<p>
|
139
|
+
|
140
|
+
(variables and functions)
|
141
|
+
<p>
|
142
|
+
|
143
|
+
<b>TBD</b>
|
144
|
+
<p>
|
145
|
+
|
146
|
+
##
|
147
|
+
<b>TBD</b>
|
148
|
+
<p>
|
149
|
+
|
150
|
+
## More later...
|
151
|
+
<b>TBD</b>
|
70
152
|
<p>
|
71
153
|
|
data/lib/liveblog.rb
CHANGED
@@ -222,3 +222,23 @@ def finalize
|
|
222
222
|
@meta
|
223
223
|
end
|
224
224
|
|
225
|
+
Dot = self # Clunky! for dot commands called from Functions class
|
226
|
+
|
227
|
+
# Find a better way to do this?
|
228
|
+
|
229
|
+
class LiveText::Functions
|
230
|
+
|
231
|
+
def br
|
232
|
+
# Thought: Maybe make a way for functions to "simply" call the
|
233
|
+
# dot command of the same name?? Is this trivial??
|
234
|
+
# Also: Should probably pass as a "real" function parameter?
|
235
|
+
n = self.class.param
|
236
|
+
n = n.empty? ? 1 : n.to_i
|
237
|
+
"<br>"*n
|
238
|
+
end
|
239
|
+
|
240
|
+
def hr
|
241
|
+
Dot.hr
|
242
|
+
end
|
243
|
+
|
244
|
+
end
|
data/lib/runeblog_version.rb
CHANGED
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: runeblog
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.1.
|
4
|
+
version: 0.1.62
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Hal Fulton
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2019-04-
|
11
|
+
date: 2019-04-18 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: livetext
|