add ba_log entry 2019-10-09

2 files changed, 40 insertions, 0 deletions

diff --git a/root/articles/mmmfs/ba_log/2019-10-08/text$markdown.md b/root/articles/mmmfs/ba_log/2019-10-08/text$markdown.md
index 7d69a3a..058cc84 100644
--- a/root/articles/mmmfs/ba_log/2019-10-08/text$markdown.md
+++ b/root/articles/mmmfs/ba_log/2019-10-08/text$markdown.md
@@ -8,10 +8,41 @@ Instead the path, facet-name and type are now all part of the URI:
 | `/fileder/facet: type/subtype -> wrapped/type` | `/path/to/fileder` | `facet`         | `type/subtype -> wrapped/type` |
 | `/fileder/: some/type`                         | `/fileder`         | (default facet) | `some/type`                    |
 | `/fileder/alternate:`                          | `/fileder`         | `alternate`     | `text/html` (default type)     |
+| `/path`                                        | `/path`            | (default facet) | `text/html` (default type)     |
 | `/`                                            | `/`                | (default facet) | `text/html` (default type)     |
 
 The fileder-index metadata was moved to a `?index` 'pseudofacet' (e.g. `/fileder/?index`).
 
+**EDIT 2019-10-09:**
+> I will take this chance to show and hopefully explain the point of this all again:
+> With the system running it is now possible to demonstrate the type-coercion that powers the system.
+>
+> In the system, every piece of data (the *facet*s) is stored together with it's *type*.
+> When requesting data, it can of course be loaded with that *type*, yielding the data unmodified,
+> but it is also possible to demand a different *type* that may be more useful to the receiving application.
+>
+> as an example we can take for example this article about one of the internal libraries for writing HTML documents:
+> [`/meta/mmm.dom/`](/meta/mmm.dom/).
+>
+> The path `/meta/mmm.dom/` corresponds, according to the table above, to the default facet of the `/meta/mmm.dom` fileder,
+> and since no type was specified, it is assumed that the browser wants a `text/html` document.
+> The follwing path gives the same result, but makes this explicit:  
+> [`/meta/mmm.dom/:text/html`](/meta/mmm.dom/:text/html)
+>
+> now, instead of asking for the rendered HTML document, we can also ask for the source, which is of the type
+> `text/moonscript -> mmm/dom` (a Moonscript-script file that evaluates to a website-fragment):  
+> [`meta/mmm.dom/:text/moonscript -> mmm/dom`](/meta/mmm.dom/:text/moonscript%20-%3E%20mmm/dom)
+>
+> or, we could ask for the generated html fragment, but without the full HTML layout around it -
+> that would be the type `text/html+frag`, as mentioned in the last post:  
+> [`meta/mmm.dom/:text/html+frag`](/meta/mmm.dom/:text/html+frag)
+>
+> lastly, we could also ask the system to generate a link to this content, in the `text/html` format (`URL -> text/html`):  
+> [`meta/mmm.dom/:URL -> text/html`](/meta/mmm.dom/:URL%20-%3E%20text/html)  
+> this might seem somewhat redundant, since we need a link to access this link,
+> but it can be useful when a component cannot work with binary data directly, e.g. when mentioning or embedding an image
+> or a video file.
+
 I also added support to the server for serving static assets (e.g. the CSS stylesheet) from the `static` directory.
 These files are accessible through the `/.static/` route (e.g. `/.static/main.css`), where they shouldn't interfere
 with the mmmfs contents.
diff --git a/root/articles/mmmfs/ba_log/2019-10-09/text$markdown.md b/root/articles/mmmfs/ba_log/2019-10-09/text$markdown.md
new file mode 100644
index 0000000..9fec148
--- /dev/null
+++ b/root/articles/mmmfs/ba_log/2019-10-09/text$markdown.md
@@ -0,0 +1,9 @@
+I added another driver/store that loads files straight from disk \[[`86bbe80`][86bbe80]\],
+and made the server load the fileder tree when it receives a request for content, rather than loading the whole tree up front.
+This means that I can work on the content again and see changes in the browser without restarting the server every time  \[[`97bc4a0`][97bc4a0]\],
+This feature should be made unnecessary by the in-page editing feature, but until then it's important for my workflow.
+
+I also started cleaning up the mmmfs article a bit, and integrating this project log in a way that will make it available online soon5f78953becd422126a528b2c31dd611cb0b29ef6
+
+[86bbe80]: https://git.s-ol.nu/mmm/commit/86bbe805a7ec49a8b891412713ea43d6e46d0d73/
+[97bc4a0]: https://git.s-ol.nu/mmm/commit/97bc4a0d8d866026905eac6f0ba08b75f166219a/