Hi Rich,
I did create a TiddlyWiki, TiddlySpot, TiddlyWeb, TiddlySpace schema 
drawing some time ago. It is intended to create a visual overview about the 
different possibilities and concepts. 

I did an update today and included the nodejs server [1].

On the top of the diagram you have the server side. 
 - The server side has a visible and an invisible area

At the bottom, there is the client side eg: user device PC or tablet, phone 
..

>From left to right, it starts with a simple file based download of an 
empty.html. 

ltr: File TW, TidlySpot, hoster [3], TiddlySpace, localhost:8080 (nodejs 
tiddlywiki) 


As you can see, TiddlyWeb / TiddlySpace design (left side of the diagram) 
is much more flexible, since every thing is a plugin on the server side. 

The nodejs server is intended to be a local / private test server. So it 
doesn't provide strict "seperations of concerns" [2] at the moment.


   - It only provides a very basic TiddlyWeb API. 
   - It can create and serve an index.html file, that contains all tiddlers 
   at startup and can be downloaded with the download button.This mechanism is 
   one way. 
   - If you start the nodejs server with the tiddlywiki --server command, 
   your server can be seen at http://localhost:8080
   - If you use localhost, you can edit tiddlers on a per tiddler basis.
      - Editing a single tiddler is directly written to the server 
      File_Store
      - If the File_Store changes, there is no mechanism atm, that tells 
      the TW on the client. 
      - ...
   
As you can see from the structure. The nodejs server program uses 
tiddlywiki as a requirement. It has the ability to create a TW that can be 
downloaded with the browser save mechanism. See "TW core + all tiddlers 
box". 

The tiddlywiki --server command is just a wrapper for a nodejs program, 
that exposes a very basic TiddlyWeb API see with localhost:8080

In your original post you requested to make express or / and loopback part 
of TiddlyWiki. 

That's is not necessary! (And would have the potential to start a religious 
war btw ;) .... but ....

You / Everyone can create an express project and make tiddlywiki part of 
this project. If you want to have a different store eg a database, you need 
to write an adaptor, that uses tiddlywiki core an knows the interface how 
to connect to the database. If you need loopback for this purpose. I don't 
know. ... 

So you basically would replace the "TiddlyWiki Core with file adaptor" box 
and replace it with your "connect to database xyz box" 

IMO for the client TW we will need a full blown TiddlyWeb plugin. But imo 
Jeremy wants to be TiddlyWeb compatible, but there isn't a commitment, that 
TW5 should support the full TiddlyWeb API. But this is a different topic. 

I hope this makes it clearer a little bit but I'm sure there are still a 
lot of questions. 

have fun!
mario
[1] http://community-img.tiddlyspace.com/TheTiddlySchema_BSD.svg
[2] http://en.wikipedia.org/wiki/Separation_of_concerns
[3] https://tank.peermore.com/

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" 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 http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.

Reply via email to