Mat,
I think this a worthy project, it was already on my to do list. Along with
a basic way to manage multiple users.
Here is some of my thinking
Lets answer your questions first
1) what would be a good collective/informative name for all these thingies?
*None
- It would be a category error (if you want to include NoteSelf)*
2) which more than the ones mentioned should be included? *All of them*
* The whole ecosystem so that you can take account of the items I raise
below*
I assume you have looked at the system tiddlers prefixed $:/info ? Most of
the below can be determined from there, to be thorough, I imagine, all you
need would be to identify the *saver* in use.
Some terms arising?
- File wikis
- Folder Wikis
- Served
- Securely served https
- Locally Hosted
- Hosted
- Savers
- Http
- File
- Tiddler (eg NoteSelf into PouchDB or CouchDB)
- Computer Platforms
- Server Platforms
- Desktop application server package
Here are some thoughts that may be useful, they apply to normal operation,
because most hosted/Served TiddlyWikis can be Saved with a *file saver*.
- I would consider any tiddlywiki opened in a browser as being "served"
if its address is HTTP/S
- *Of note here the browser is not handling the disk writes*
- If that address begins 127.0.0.1 I would call it "locally hosted,
but this could also occur if browsing on a server
- If it was any other address we could say it was "hosted" including
the dat version for the Beaker Browser
- Any TiddlyWiki opened with a path including file:// is clearly a
single file wiki
- *Of note here the browser is handling the disk writes even if it is
through a plugin/add on*
- Note when a single file wiki is *Served via a Server *it is *hosted*
.
- To me a *server* includes the The beaker Browser, node JS, and
TiddlyServer, TiddlyDesktop, Jeds Multi-access Bob thingy are perhaps*
server platforms* (TiddlyWiki Servers) that use NodeJS below (the
server) that come with another layer or support, especially savers.
- Perhaps these server platforms, given they have plugins the above
also have *savers* which interestingly file savers are also savers.
- So some savers are file savers and some are http savers, or http
server/saver combinations.
- Of note is some servers support serving *single file tiddlywikis*
- and or Serve* Folder based tiddlywikis *(eg I do not think beaker
browser does not serve folder based TiddlyWikis)
- Of course *servers* can run on multiple *Computer Platforms*
- *TiddlySpot *is a* Hosted TiddlyWiki Server*
- And different *browsers* can also run on on different *Computer
Platforms*
- Of note the beaker browser can only access "beaker browser served"
single File Wikis.
- Different browsers can use different *file savers*.
- Now of course TiddlyDesk top also has a Desktop application to *Serve
and browse*, *Both Folder and File wikis*. the saver is built into
tiddlywiki, and comes with a browser. It is a *Desktop application
server platform, and browser* or a *Desktop application server package*
- NoteSelf gets messy because it is a *saver*, not a server. It can
save locally in the browser (not in the file system) or remotely to a
database. Because we have the *NoteSelf Saver* we can call PouchDB a
*TiddlyWiki
Server*, or perhaps only a *tiddler server.*
- CounchDB is also a *tiddler Server,* but session bound in the
browser. It has a Saver in addition to or combined with the PouchDB Saver.
So in closing we need a *Browser* (even if inbuilt) and a *Saver.* Some
savers are *file savers*, some are *Http savers,* Some savers save Files,
Some save tiddlers, some save TiddlyWiki Files (tiddlySpot) some do this
over http. To access tiddlywiki over Http a *Server *must exist, *Servers
can Serve* "locally hosted" and "Hosted" TiddlyWIkis.
I hope this help
Tony
On Friday, May 11, 2018 at 2:02:22 AM UTC+10, Mat wrote:
>
> Thanks everyone. Yeah, "platforms" might be the term!
>
> Jeremy Ruston wrote:
>>
>> Might this list be starting to get rather similar to the information
>> found in GettingStarted? Perhaps best to extend and improve what we’ve got,
>> rather than making something new.
>>
>
> I agree that would make sense - eventually.
>
> At the moment I want to experiment with the format for this though. For
> example, I have a (vague!) idea about a step-by-step guide/wizard that asks
> "Do you have access to a public server - Y/N?" , "Do you want to access
> your TW from multiple computers (owned by you)?" etc. Actually, the
> specific questions will be formulated much depending on what the actual
> platforms do feature and enable.
>
> Plus, I expect it to be some work to actually gather the data for the
> different alternatives because I need to ask around.
>
> <:-)
>
>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/f997d13f-8c63-46a2-b4c2-e2d52c1fad89%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
