Alex, I saw you post before about the idea of a tiddlyzine, it sounds interesting but I personally do not have a depth of understanding on this, could you outline the idea of a TiddlyZine?
The trick I think is to collect contributors or lift content from Google Groups and post in a dedicated blog, with a periodical subscription to posts available. This requires a small team to avoid tiying one person to a millstone. Tell use more, about your vision. Tony On Monday, 11 December 2017 00:00:14 UTC+11, AlexHough wrote: > > Hi, > > a suggestion made elsewhere on this group (by me) > > Build on top of the latest pre-release. Document your play. Then when the > pre-release is released collect the play and documentation into an > accompanying TiddlyZine. > > > > best > > Alex > > On 10 December 2017 at 01:42, TonyM <[email protected] <javascript:>> > wrote: > >> Thanks for your contribution Josiah, >> >> On your response to item 1 I agree in principal but if no one starts to >> act and say 5 of us worked together in a side Forum posting end product >> here I see no problem there. >> >> On 2 we can start work on side doco now and petition to have it >> referenced from tiddlywiki.com >> >> On 3 I read almost anything here in last 3 months and more as a results >> of specific searches and I am building my own reference materials and often >> link to relavent discussions. I harvest info from the forum and will use >> this info for any doco I contribute to, however the more I learn the easier >> it is to curate and I often see short cuts to learning tiddlywiki. >> >> Also >> >> In addition to specific details we need peer reviewed conceptual >> outlines. What follows is part of draft work in progress to illustrate my >> point. >> >> If you stop to think about it, in tiddlywiki, everthing references almost >> everything and any change is reflected almost everywhere and >> instantaniously. These updates occur with any change at all, at least >> anything you can see, any new item you look at will update when you open >> it. keep in mind a simple click can be enough to make a change stored >> behind the sceens. >> >> since tiddlywiki is always upto date, you could say it does everthing >> just in time (for you to look at it). its just in time for every relavant >> context as well. until everything is rendered for you to see it, you can >> not do anything. this is why sometimes you just have to wait. its the price >> we pay for everything to be up todate. this just in time method in someways >> prohibits batch processes, you could say its not procedural but contextual >> and just in time. >> >> With few exceptions if any. all changes come from the user, and when they >> do everything that must be changed is and rendered in the new context. this >> seems to be the essence of event driven processes that keep all objects and >> their attributes upto date just in time. >> >> Of course there are differences when you actualy change something vs just >> changing your view or context. >> >> The above account in someways explains why i did not initialy understand >> why you need buttons and similar to trigger any action because tiddlywiki >> waits until you change something including pressing a button before it >> acts, reevaluates the context, updates everythin it must and renders it >> just in time. >> >> this model will not nessasarily be a supprise to anyone who is a >> webdevloper, object and event driven coder, and strangly anyone who coded >> online transaction based mainframes. it can however take someone with >> advanced proceedural languages and batch programming time to grasp, >> >> this structure also sheds light on tiddlywiki not responding naturaly to >> multi user updates, though fine with multiuser read only. >> >> End of example conceptual outline. >> >> -- >> 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] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> 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/f3726758-6a72-4612-9fe7-d36717f6bfcd%40googlegroups.com >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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/f7646649-1be9-4b06-b624-b000f21ca005%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
