Hi May > >> We try to use text references in shortcut syntaxes but now prefer separate >> title/field/index attributes for widgets. > > Is this a real preference or a compromise? Are separate attributes better > than to have one textreference?
Yes, because of the point I made above: if an attribute specifies a text reference then it is impossible to refer to a tiddler with !! or ## in its title. That might not matter for end users, but for TW5 itself its a deal-breaker: we really don’t want to have the situation where typing certain characters into a tiddler title causes other things to fail. > We do, after all, use the compact textreference format sometimes in current > TW. Yes, this is a matter of layering: Top: shortcut syntax Middle: macros Bottom: widgets We have text references at the top layer because they are, after all, a convenient shortcut. But they don’t belong at the bottom layer. As you say, we do have old widgets that accept text references as an attribute but we now offer separate tiddler/field/index attributes alongside. > The point with my proposal was to avoid unnecessary parameters when possible. > I also think there is a nice aesthetic, and an opportunity, to treat > textreferences as a gradually more fine grained address. A kind of name space. The shortcomings of text references mean that they are not universal, they can only be a shortcut. > The ## used for data tiddler indices is only valid within a text reference. > Otherwise it would clash with the use of # for numbered lists. > > So, both the fact that browsers apparently force us to use ##, at least atm, (It’s not browsers that do that, it’s TW5 that requires the second # — see https://github.com/Jermolene/TiddlyWiki5/issues/3811 <https://github.com/Jermolene/TiddlyWiki5/issues/3811> > and that TWX ought to feature hashtagging speaks for coming up with something > else for numbered lists. > > Side note: One idea could be to use asterisks (*) for all those typed kinds > of lists of lists, but specify how it should appear e.g in the first element. > I think bullet lists are under used, and we can do much more with them (eg > <http://listtree.tiddlyspot.com/> , eg <http://familytree.tiddlyspot.com/>), > particularly considering the role lists play in TW. The plan for TWX is that anyone will be able to add/change their own wikitext rules, without using JS. > >> I think this means that any part of a tiddler could be designed to be >> addressable. Even in the url. > Ah, are you suggesting that {{HelloThere##mylink}} should return the text of > the anchor labelled “mylink”? The problem with that is that you probably > don’t want the text of the anchor (because there often won’t be any), you’ll > probably want the text from the link up to some landmark (e.g. the next > heading). That kind of thing is far too complex to be a low level primitive. > > But, we're already doing that with tiddlers (by providing the title), and > fields and indices - ??? Because they are directly addressable, while pulling out an anchor requires parsing the text (which is slow). > Why could we not (hypothetically) do it with segments marked out by > arbitrarily placed markers? It would be a kind of encapsulation. Other than > to use it as an address for navigation, it could be used for styling (I > guess, basically converting it to div tags). A more tiddleresque idea is to > use it for "auto-excision"to automatically split out such segments that > evidently deserve to be separate tiddlers. Plus there’s the issue I mentioned above that link anchors identify a location within a document, they do not define a run of text. > (Side note: I read somewhere that browsers will soon introduce something so > that you can give an url to a specific point on a webpage.) Every anchor already has a URL. I believe the new proposal is for addressing DOM elements that don’t have an anchor. Best wishes Jeremy. > > <:-) > > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWikiDev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/tiddlywikidev > <https://groups.google.com/group/tiddlywikidev>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywikidev/37c39f26-48c4-41c5-981a-56b07944a8bd%40googlegroups.com > > <https://groups.google.com/d/msgid/tiddlywikidev/37c39f26-48c4-41c5-981a-56b07944a8bd%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/76C16670-683D-437B-AF08-C0352C1FB584%40gmail.com. For more options, visit https://groups.google.com/d/optout.
