Hi On Sunday, July 27, 2014 4:16:15 PM UTC+2, David Gifford wrote:
> > First of all, I want to say thank you for introducing me to the amazing > slider table of contents on that Anki site. Wow, that would be cool on a > TW...every time a link is clicked it not only takes you to the location but > also takes you to the place in the TOC, too. And as you scroll up and down > the story river, the TOC adjusts automatically...wow... > Uses bootstrap, several jquery libraries and 'id' 's on header elements -- don't think that'll be coming to TW any time soon :-) I would maybe split your three categories into four...Knowledge management > I would split into two categories, one is knowledge management for self, > and the other is sharing / publishing for others. > The material at 'cyborganize' outlines the process by which information: - enters the system via a number of scratchpads - gets stripped of actionable items (these are transferred to the task management system) - gets transferred to a journal (chronological blog) - gets separated into a few separate story threads (parallel chronological blogs) - gets tagged and split into snippets to form a wiki - is then re-assembled in the wiki into a coherent publishable articles TW seems to fullfill the rolls of scratchpad and wiki -- however, it needs tools for processing the information into a journal and chronological blogs (to mimic wordpress) and for re-assembling the fragments into publishable articles (here yWriter and I think Scrivener do the job.) 'TiddlyWiki for Academics' does a fair job of tagging bibliographic entries, notes and references in order to attach them to an article. The problem I see here is that the information has to be entered into the hierarchal structure via forms. I would prefer a completely random brain dump of information into 'scratchpad' tiddlers that could then be dropped into various 'blog' stories, then pulled out again and tagged into wikis. Thereafter, the process gets a little hazy -- what is needed is a 'TOC' into which the fragments (individual tiddlers) could be placed by tagging appropriately. This process of producing a finished article works best with a versioning system to record the incremental changes as fragments are massaged and re-arranged. I'm not sure that TW is up to this? > I would add photo galleries as a usecase for TW. You can do masonry type > galleries of online images or images in a folder. I once showed Jeremy an > example I have of almost 1600 images linked to from a TW, in over 200 > masonry galleries. > That could form part of the system, rather than a specialised TW, especially during the collection stage. A presentation mode for graphics (slideshow) type version might be useful. I use TWC as a database for our seminary's library. > http://www.giffmex.org/bibliotecaSTRM.html Would be great to have an out > of the box version for TW5 for personal libraries with fields, etc. > Fields could be used for database type applications -- here I dream of a Restful backend such as CouchDb -- not for hosting the whole wiki as in the node.js version, but where certain tiddlers could be posted and 'attached' to the standalone wiki. TW is ideal for organizing recipes. Would be great to have an out of the > box version for recipes. > There is a good case for a separate standalone version for recipes -- it would be popular and recipes are clearly identifiable as recipes from the outset. regards -- 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.
