On 24 Jan., 20:53, Yakov <[email protected]> wrote: > Ah, ok, I can see the problem with 76 q, t, u. Fair enouth, that's needed > at least for some backward compability, currently ":" in the end is taken > to the slicename, this is to be fixed. right
> On the other hand, I don't know why 76 o is problematic? Adding spaces to > slice names is somewhat useful for more human-readable tables, especially > those generated by the GridPlugin (from TiddlyTools). Does anyone know any > background, reason for this restriction? Any core functions relying on > this? Of'course I can just forbid spaces, but that's a major restriction.. I think it is because of output = slices["foo bar"] is valid. At least js can handle it. output = slices.foo bar ... won't work. I think anybody creating plugins, that deal with slices, should use the 1st notation. It is more obvious, that there is something special going on. So +1 from me to accept spaces in slices, if they really work. (I didn't test it). I think there is no backwards compatibility problem. Because, TW just didn't work if slices did contain spaces. So users did change them to get it working. Slices that have spaces but are not used aren't problems anyway. what do others think? -m -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
