aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/SledjHamr/WebSite.txt121
-rw-r--r--docs/index.html2
2 files changed, 122 insertions, 1 deletions
diff --git a/docs/SledjHamr/WebSite.txt b/docs/SledjHamr/WebSite.txt
new file mode 100644
index 0000000..7b3a579
--- /dev/null
+++ b/docs/SledjHamr/WebSite.txt
@@ -0,0 +1,121 @@
1Now that we have a web site, I should turn this into a real web site, huh?
2
3What is a real web site though? Well, the ideal would be to have it
4driven by C and Lua as part of SledjHamr. A default web site for the
5small default home, that supports the basics. It should look something
6like the IG site, but with user selectable colour, and a hell of a lot
7simpler to drive at the back end. That's gonna take a long time to
8write though, and likely depends on wasm becoming popular.
9
10An alternative is to take the IG web site, based on Drupal (Apache +
11PHP), cut it down to the basics, and present that as a working example.
12Then the user needs a LAMP or WAMP stack, plus it's slow.
13
14Middle ground might be to have a basic HTML backend for GuiLua in the C
15part, plus a simple web server. Matrix-RAD had that.
16
17
18
19What is a real web site though? Same question, but this time focused on
20the content. What content / functionality should the web site contain?
21There's several goals here.
22
23An important goal is that eventually it's all just part of the system,
24can be used in world via the usual GuiLua stuff, from a normal bloated
25web browser via wasm, or from a cut down web browser using plain HTML.
26
27Users control of their own world servers.
28
29Communications without starting up a proper extantz client. IM, forum,
30wiki, email (gulp), and the like.
31
32Actual SledjHamr.org site, for users and developers. So add source
33code, bug / feature trackers, support, etc.
34
35
36
37The rest is currently random thoughts while I get organised.
38
39The IG site redesign aimed to boil out some common stuff and simplify
40stuff. Mostly coz I noticed that it doesn't matter how easy to use your
41support system is, users will ask for support anywhere and everywhere
42that they can, with the possible exception of your actual support system.
43So, people spray stuff everywhere, why not just have a single place,
44then organise it later? So no forums or anything, it's all just one
45thing, call them convos. Then tag them later to sort things out. A tag
46cloud, and user creatable tags should round things out. So that takes
47care of forums, wiki, bug / feature trackers, and support.
48
49The only difference between an IM and a convo is that IM is real time, a
50convo is logged, though IMs can be logged as well, and convos can be
51almost real time. So bugger all really.
52
53Should be able to group the convos, to limit them to one or more groups,
54which takes care of the normal OS/SL group IM stuff.
55
56Convos and mailing lists should be two views of the same thing. Email
57is tricky to get right though, even for experts. An alternative to
58email is to pass email type messages between SledjHamr servers. So the
59convos become more mobile.
60
61Sooo, the users small builtin web server includes the world control, and
62convos stuff. This will work via plain ordinary HTML to start with, as
63well as Lua in the viewer, then Lua in the browser eventually. No
64email, that's too hard, but maybe later. Any account system should
65default to world owner created accounts only, no need to deal with
66spammers.
67
68The actual SledjHamr.org web site adds email integration, proper spam
69protection, random stranger created accounts, and source code.
70
71
72
73Soooo, what's it look like under the hood?
74
75
76The basic thing is the convo. Any user can start one, either public, or
77private to one or more individuals, and/or private to one or more
78groups. They can add whatever tags they want, if not it automatically
79gets "off topic" or something. They can allow others to edit the first
80post, thus it becomes a wiki with the "Talk" page simply comments
81following the initial post.
82
83Maybe an option to switch between "IM style" and "forum style"?
84
85The default view of these convos is a list of tags, sorted by
86popularity, looking like a more traditional forum. Should also be a
87"unread convos", also sorted by tags.
88
89All the usual style, colour, image, list, table, etc support should be
90allowed. Sigs are allowed, but only shown on the first post of that
91person on each convo.
92
93The world owner gets to bypass all privacy, just like everywhere else.
94Convo creators get to control privacy for their convos. Group owned
95convos should be possible, they would get one "chat room" convo for free
96according to OS/SL convention. Group owners get to control privacy of
97group owned convos.
98
99This should all run under Jabber / XMMP style protocols, as well as the
100web front end, in world front end, and probably RSS streams and such.
101Email, as mentioned, is left as optional, coz too hard.
102
103world server - Lua and C running server side, running plain HTML widgets, pumping them out a built in simple web server - simple web browser - plain HTML widgets.
104
105world server - ECMAScript web browser (no wams) - Lua.VM.js running DOM (or plain HTML?) widgets.
106
107world server - wams web browser - Lua and C running DOM widgets.
108 Probably don't want to be pushing the entire EFL down peoples networks for each web page. lol
109 On the other hand, likely this will be a single download to get GuiLua onto the browser, then it's all internal skang traffic.
110
111world server - extantz client - Lua and C running native EFL widgets.
112
113I think this is what the NAWS layer should morph into, it's NAWS at the
114top, but under the hood, gets converted to EFL, DOM, plain HTML, what
115ever.
116
117------------------------------------------------------------------------
118
119So, lots of work either way. How about we start with github stuff,
120since the source is there anyway, and work our way through the above at
121our leisure? Second step might be to port and simplify the IG webiste.
diff --git a/docs/index.html b/docs/index.html
index b8997c3..65eb173 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -62,6 +62,6 @@ Welcome to the home of SledjHamr!
62<li><a href="/source/AUTHORS">Authors</a>.</li> 62<li><a href="/source/AUTHORS">Authors</a>.</li>
63</ul> 63</ul>
64<p>We have a code repo on github now - <a href="https://github.com/onefang/SledjHamr">https://github.com/onefang/SledjHamr</a> with just a small README that points to this page. The experimental branch has all the actual code and stuff. We can finally start writing code. A local copy of <a href="/source/">the source</a> can be found here.</p> 64<p>We have a code repo on github now - <a href="https://github.com/onefang/SledjHamr">https://github.com/onefang/SledjHamr</a> with just a small README that points to this page. The experimental branch has all the actual code and stuff. We can finally start writing code. A local copy of <a href="/source/">the source</a> can be found here.</p>
65<p>Now that we have a web site, I should turn this into a real web site, huh?</p> 65<p>Now that we have a web site, I should turn this into a <a href="SledjHamr/WebSite.txt">real web site</a>, huh? Until then, use the <a href="https://github.com/onefang/SledjHamr">https://github.com/onefang/SledjHamr</a> stuff.</p>
66</body> 66</body>
67</html> 67</html>