On Friday, January 16, 2015 at 6:03:51 PM UTC+1, RichShumaker wrote: > > I understand now a bit better about loopback and express and understand > the difficulty of using them. > Also I understand that using them might be counter-productive. >
Not conter-productive, but different. > I had a feeling that the things express and loopback did overlapped with > what TW5 already does. > That's right. And the "tiddlywiki --server" command overlaps with express. > Meaning you need to gut TW to add them in, which is the opposite of what I > wanted to do. > The tiddlywiki command line interface (CLI) is a wrapper for a lot of commands. An express project can include tiddlywiki functionality and use it as a requirement. It's kind of a plugin there. So not express needs to be included into TW. It can / should be the other way around. With the TW CLI you can: - create a file tiddlywiki that can be uploaded to tiddlywiki.com - create all the translations that are at http://tiddlywiki.com/#Languages - all of them are single file TWs - create a static file version of tw . com eg: http://tiddlywiki.com/static/HelloThere - run a test server based on the native node http library - .... So I guess the question becomes how can you add something to Node.js TW to > make it more Social(email, tweet, comment) > Is there a widget that does all the things node.js TW does not do, meaning > connect to the world? > There is no "socialize plugin" atm. Because it's a project on its own and imo not just one plugin. > TiddlyWeb seems like a good option but I get the feeling from reading > things that there are some 'issues' in the TiddlyWeb world right now. > Chris has been extremely helpful at the TiddlyWeb group and helped me a > lot with it. > The issue is human resources. We would need a potent sponsor, that can afford to employ several people, full time to drive the development. For standalone TW5 lets reverse this and ask, how would you connect to the > outside world with the freestanding version? > If you start from a local file TW, you can't connect to a server, because all major browser vendors locked down this possibility. Because of the same origin policy <http://en.wikipedia.org/wiki/Same-origin_policy> for web applications (browsers). .... It's a security problem. > Since TW5 HTML is a rendered file you could not get continual updates and > as such only outgoing communication is possible. > That's not true. WebSockets <http://en.wikipedia.org/wiki/WebSocket> give the possibility to have "push notifications". TiddlySpace has an active WebSocket service. TiddlyWeb has one too. Nodejs could have one, if someone would create it. > So what could be done to communicate to the world with TW5 HTML? > Throw human resources at the problems :) -mario -- 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.
