Hi Mario In my view -- 16 branches at each level would be sufficient -- it should be advantageous to structure categories in the TOC in depth, rather than having long lists in parallel. The current TOC at tiddlywiki.com has 12 branches at root level and no more than 20 branches in the second level (which could easily be organised to <16.)
At a maximum, 2 x hex (256) branches should be more than sufficient for any user (and this is likely necessary only in the first couple of layers.) Perhaps it would be better to use the full range of ascii characters -- this would give about 95 possibilities (case sensitive) at each level whilst using only 1 character per level. regards On Wednesday, May 27, 2015 at 9:37:48 AM UTC+2, PMario wrote: > > On Wednesday, May 27, 2015 at 7:13:45 AM UTC+2, Matabele wrote: >> >> This could be implemented if each tiddler were allocated a hex string as >> an ID which marked it's position in the TOC -- 16 branches at each level (I >> suppose two hex characters might be used for the first level -- allowing >> 256 branches at the root level.) >> > > What if I have 257 elements in the the root? We need to expand to 3 bytes > aka 4096 possibilities. .... but what if we need 4097 elements in one > hierarchy level. ........ > IMO Murphy's law [1] applies here. > > Murphy's law is an adage or epigram that is typically stated as: *Anything >> that can go wrong, will go wrong.* >> > > -m > > [1] http://en.wikipedia.org/wiki/Murphy%27s_law > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/b8251e5d-c056-4d90-bfa5-66705abbe9ba%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
