On Friday, February 20, 2015 at 6:52:54 PM UTC+1, Tobias Beer wrote: > > * is designed to work with TiddlySpace rather than a generic TiddlyWeb >> server >> > > You see, there are only a few people who really understand what that means > precisely. >
That's true and it's scaring. ... > * it's difficult to make it dynamically choose a desired recipe to use as >> a source for content >> > > I take it, you mean to expose the available recipe's on the TiddlyWeb end > and then assign them in the TW5 front-end. I guess, the point to start is > that TiddlyWeb API for anyone to retrieve recipes or perhaps just bags, for > starters. > IMO you need to start with recipes. Otherwise you will have big trouble in the future. And client side code wise, there is no difference. > TiddlyWeb can provide (given correct setup) but doesn't make it easy >> enough: >> > > That is fine, so long as the setup is doable on the server-side. At some > point there may be some TW5 Admin console to some TiddlyWeb backend, > I do have a very basic admin GUI for the backend. tweb-config [1] but you need to be able to access the server with ssh. I thought, I have a video, how it works, but it seems I don't :) IMO creating new recipes and bags isn't exposed to the web api, due to security concerns. > but let's just start with the basics of getting collaboration up and > running... with requirements as to some srver-smarts in terms of setting > things like recipes and bags up properly. > And here we have to do some standardisation work to do and TiddlySpace isn't the best example. eg: TiddlySpace defines some default recipe/bag names that make the client side code very complex (in TWc). .. It's mainly naming conventions and the resulting client side UI. TW5 has some advantages here, because of the very powerful filter syntax. ... IMO this topic needs its own thread. > * content change notifications either through websockets or fairly >> efficient support for being polled for "all changes since last time I >> checked" >> > > Not precisely sure what that means in terms of what TiddlyWeb actually > provides in terms of an API and how the communication details sort out. > Again, I would think there is some codebase on the TWc end in TiddlySpace, > isn't there? > Yes. TiddlyWeb doesn't have real time features out of the box. socket.io is used on the server and the client. ... But here the client side software is much simpler than, what's needed on the server. You see. Adding a "simple" feature adds more moving parts, server side and client side. > * comprehensive authentication (are you who you say you are) and >> authorization (can you access this thing to do action X) controls via >> challengers and polices >> > > That is perhaps one of the bigger issues why I think we all need a guy > like you at least for supervision, even if others dare pick up on the > coding challenges. > FND made a low level tiddlyweb console [2]. That can be used to assign recipe/bag policies. It works for TS and TiddlyWeb. .... BUT ... I broke mine today, doing some configuration changes. ... I hope it's fixed, when you read this post. * scales from little personal installations to huge enterprisey >> installations >> > > Again, let's start with the basics. If people want enterprisey stuff > someone will luckily cater for it with that required paycheck involved. > For enterprise usage, imo you need a "real" database as a storage backend. ... -> even more moving parts :) have fun! mario [1] https://github.com/pmario/tweb-config [2] https://dev.tweb.at/console.html -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
