The headers are sorted depending on their status, priority, and whatnot
Before this project can even convert markdown to PDF files in sub-ten seconds, I have been using tables as substitute for columns. This is as the Commonmark Markdown specification does not support such feature.
However, there is a simple problem with tables in markdown: it does not support multi-line cells
Time and time again, I have searched for ways to be able to write multi-line cells in a kind of markdown way. All of them are ugly implementations. None of them can satisfy me.
And then I came across MultiMarkdown's table documentation which makes an interesting observation:
If you need complex tables you will need to create them by hand or with a tool specifically designed for your output format. At some point, however, you should consider whether a table is really the best approach if you find MultiMarkdown tables too limiting.
And I think that that is true.
However, I have thought of a solution. That is to parse markdown inside HTML tags. Such as that the following markdown...
<table>
<tr>
<th>Header</th>
</tr>
<tr>
<td>
- Lorem ipsum dolor sit amet
- Consectetur adipiscing elit
- Integer molestie lorem at massa
</td>
</tr>
</table>...will be converted to HTML like the following:
<table>
<tr>
<th>Header</th>
</tr>
<tr>
<td>
<ul>
<li>Lorem ipsum dolor sit amet</li>
<li>Consectetur adipiscing elit</li>
<li>Integer molestie lorem at massa</li>
</ul>
</td>
</tr>
</table>But, I think that the best solution would be to just make my own implementation of columns.
A solution I am considering at the time of writing is using a custom HTML tag called cols (stands for columns) that wraps col (stands for column) tags, which in turn wraps content in a column. Such as that the following markdown leads to 3 columns.
<cols>
<col>
Column #1
</col>
<col>
Column #2
</col>
<col>
Column #3
</col>
</cols>And yes, the content inside each col tags will be interpreted as markdown.
Despite the talk about the tables above, there is still a legitimate reason to use multi-line tables, such as shitty homeworks that requires such. And more often than not, these tables are multi-line.
And as such, I have thought to actually implement interpreting content inside table cells as markdown, as discussed above. The rationale for this is that while it strays from the actual purpose of using HTML inside of markdown, this can ease up using multi-line tables.
And yes, an option to turn this shitty feature off.
I hate that I have to do these because of school works. No, this is the point of this whole damn thing: to make writing my home works more efficient. But I hate going to school. I barely have time to talk to my girlfriend. But what am I saying right here? Considering that nobody will be able to read this far in this nest of documentation, I doubt that someone will see this. But I digress.
I have a really grand plan: to parameterize common CSS rulesets.
I do not have proper plans for the GUI of this project yet. But boredom does wonders.
I was once subjected to the horrors of national achievement test and mock exams for 4 days. And we are not allowed to use our phones for 4-5 hours straight a day, for 4 days. And so, I scribbled to a scratch paper that I had. And what do you know, I have this graph.
A week later, I graphed the thing in mermaid.js, and here it is:
sequenceDiagram
participant A as core.py
participant B as main.js
participant C as renderer.js
Note over A,C: Initialize
B -) C: Run
note left of C: show loading screen
B -) A: Run
alt log path is `None`
A ->> B: request Electron.js App Directory
note left of B: get Electron.js App Directory
B --) A: Electron.js App Directory
end
A ->> B: log path
C ->> B: ready
B ->> C: tx log path
note left of C: console.log(log path)
C ->> B: ack
B ->> A: tx ack
A ->> B: cfg
note left of B: process cfg
B ->> C: tx cfg
note left of C: remove loading screen
Note over A,C: Nominal Operation
alt log
B -) A: log
note right of A: log
end
alt log
C -)+ B: log
B -)- A: tx log
note right of A: log
end
alt mod cfg
B -) A: mod cfg
note right of A: rewrite cfg
end
alt mod cfg
C -)+ B: mod cfg
B -)- A: tx mod cfg
note right of A: rewrite cfg
end
alt ctl
B -) A: ctl
note right of A: process
alt res
A --) B: res
alt tx res
B --) C: tx res
end
end
end
alt ctl
C -) B: ctl
B -) A: tx ctl
note right of A: process
alt res
A --) B: res
alt tx res
B --) C: tx res
end
end
end
Hereunder this heading are implemented features.
Now, why have not I put the implement features under this header? As it will break the link to other documents.Implemented in 0.0
There is no plain markdown way to add pagebreak in a markdown file. However, I came across this stackoverflow answer that mentions that the answer-er uses <<<<>>>> to denote pagebreak in their documents. And I liked that! And as such, I think I will implement just that in later versions of this program.