Hi Chris, Implicit in this should be read my apologies for not being able to do it > myself due to employment constraints.
This is totally understandable and should be ringing one or two bells with me, too. However, while you may not be equiped with the time-resources to do it all yourself, I think you could perhaps keep an eye on vision / implementation... being the most knowledgeable on the perhaps more critical TiddlyWeb end. Let's face it, who else really has the background to guide through that process? So, do you think it would be possible for you to open up some TiddlyWeb5 repo to which other's could make pull request where you, however, would be sketching out the basic issues, lead the conversation so to speak, where you are able, and possibly throw in the occasional doodle of the details of any of this... * 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. > * 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. * it doesn't have smarts for how to fruitfully deal with edit conflicts > (TiddlyWeb will return a response code indicating when one happens) > There are some smarts in TiddlySpace that could be referenced at some "action-item" so that there would be at least something to start looking for solutions other than a blank canvas. 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, 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. * 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? > * 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. * 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. > If anybody wants to know more about these issues or features please ask > and I can try to provide more info. > If I was more of a thorough developer or had all the time of the world at my disposal I might pick up on that offer but — for the time being — my needs are more on the "go look for that next paycheck, Tobi"-front... so, let us know what the Missus says, all non-bindingly. Best wishes, Tobias. -- 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.
