What you describe sounds like a node.js solution and from what I understand, that requires a "per tiddler" gentlemen's agreement.
What I'm thinking feels a little bit more manageable in the sense that it requires a "per TiddlyWiki instance" gentlemen's agreement. Sniffs to me like much less work managing that agreement, at the cost of the supervisor's TiddlyWiki being a bit slow with those "iframe" tiddlers that displays each team member's TiddlyWiki info. (That would probably not be very practical for large teams...) Mind you, a supervisor probably only needs a snapshot of "everything" only once in a while, and can surely preoccupy herself/himself with something while waiting for her/his TiddlyWiki "team info" tiddler to open with all of them other tiddlers. On Thursday, February 4, 2021 at 12:10:24 PM UTC-4 [email protected] wrote: > Interesting idea. > > I would love to be able to handle this type of inter-wiki communication > through canonical_URIs and import mechanism. If another Tiddlywiki is > embedded as an external resource in this way, its tiddlers would be > included/imported on parent Tiddlywiki startup (or when triggered by a > reload manually later) under some unique prefix to avoid parent tiddler > conflicts and be available for regular filtering. > > I have no idea how to implement this though. It would also require some > thinking on what happens if the other Tiddlywiki links back to the parent > in the same way and edits a copy of the parent tiddler. Some sort of > automated/semi-automated/manual tiddler edit merging would be needed. > > /Mike > > On Thursday, February 4, 2021 at 10:33:52 AM UTC-4 [email protected] > wrote: > >> In the midst of enjoying my day's first cup o' coffee, a thought: >> >> For team collaboration re task management, I'd setup multiple tiddlywiki >> instances, with each team member the only person allowed to edit his/her >> tiddlywiki. >> >> There would be also one tiddlywiki for the team's supervisor, either >> maintained by the supervisor or "ownership" delegated to a team member. >> >> Say each team member has one tiddler that summarizes the list of tasks >> he/she has on his/her list. >> >> The supervisor's tiddlywiki would have a tiddler with an iframe section >> for each team member, and each iframe displays, for that particular team >> member, that team member's list of tasks from that team member's tiddlywiki >> instance. We could call this a kind of dashboard. And the supervisor >> could have as many dashboards as needed, >> >> Sure, each dashboard would be a little bit slow, because each iframe is >> loading an entire tiddlywiki to each then just show a particular tiddler >> for each team member. >> >> A node.js setup would fix the speed issue, but then would make it easier >> for folk to mess with each other's tiddlers. I think. I've only read a >> little bit about TiddlyWiki used with node.js. >> >> -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/c5ca434d-c99e-4452-a5ed-65c755de5bc3n%40googlegroups.com.
