Implement a small library of ActivityPub objects

These objects allow, and will allow us, to move HTML rendering out of
the archive parser and into separate classes. Each of the derived
classes specialise HTML rendering for their specific requirements.
Furthermore, these ActivityPub objects will be able to be expanded upon
and have support to be written to disk, in a database, for instance.

Separating ActivityPub object retrieving from rendering allows us to
implement other retrieving sources and methods, such as downloading
posts from a configured remote instance.

1 files changed, 21 insertions, 0 deletions

diff --git a/src/activitypub/apbase.cpp b/src/activitypub/apbase.cpp
new file mode 100644
index 0000000..52c995d
--- /dev/null
+++ b/src/activitypub/apbase.cpp
@@ -0,0 +1,21 @@
+#include "apbase.h"
+#include <QHash>
+#include <QFile>
+#include <QDebug>
+
+const QString APBase::get_html_template(const QString& template_name) {
+    static QHash<QString, QString>* templates = new QHash<QString, QString>;
+
+    if (not templates->contains(template_name)) {
+        QFile file("src/templates/"+ template_name +".html");
+        if (!file.open(QIODevice::ReadOnly | QIODevice::Text)) {
+            templates->insert(template_name, "<i>Error loading status_info template.</i>");
+            return templates->value(template_name);
+        }
+
+        templates->insert(template_name, file.readAll());
+        qDebug() << "Loaded HTML template:" << template_name << "Total loaded:" << templates->size(); // print size to make sure that everything is loaded by the same function
+    }
+
+    return templates->value(template_name);
+}