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, 35 insertions, 0 deletions

diff --git a/src/activitypub/apactor.cpp b/src/activitypub/apactor.cpp
new file mode 100644
index 0000000..6731dd3
--- /dev/null
+++ b/src/activitypub/apactor.cpp
@@ -0,0 +1,35 @@
+#include "apactor.h"
+
+APActor::APActor() {}
+
+APActor::APActor(const QString url) {
+    object_url = url;
+}
+
+const QString APActor::get_url() {
+    return object_url;
+}
+
+QString APActor::get_html_render(HtmlRenderDetails render_info) {
+    // TODO: could be made nicer with profile images
+    return object_url;
+}
+
+const QString APActor::get_plain_render() {
+    return object_url;
+}
+
+QString APActorList::get_html_render(HtmlRenderDetails render_info) {
+    // have something basic for the moment
+    QString text;
+
+    for (APActor elem : *this)
+        text.append(elem.get_plain_render() + ", ");
+
+    if (text.isEmpty())
+        text = "<em>(empty)</em>";
+    else
+        text.chop(2); // remove leftover ", "
+
+    return text;
+}