Matt
Very useful thoughts for someone like me.
One thing missing, at least I can't find one, is a CRIB sheet of existing syntax ... something along the lines of those that Tobias did for Filters and WikiText examples.
My single biggest issue as an idiot is that I forget what all the variant brackets mean so have to go fish around and look them up repeatedly. I've found it hard to consolidate what I know in a way that becomes intuitive. Crib sheets help people like me get out fog.
The rest of your points I think I understand, but, before one starts changing fundamentals, I'm wondering is just gathering all the syntax on one "page" with simple examples might not do what is needed.
Best wishes
Josiah
Mat wrote:I just want to bounce this thought to hear if it makes sense:The idea is about how to simplify the syntax, or at least make it easier to learn.
--
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 tiddlywikide...@googlegroups.com.
To post to this group, send email to tiddly...@googlegroups.com.
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/9ed2811c-906c-4e8b-a3ec-1615fc74c71a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
unify tiddlers and variables.
Pulling back up to your original question, the issue we'd now have is how to name those tiddlers that are acting as variables. Simple names like "currentTiddler” wouldn't be great because we'd be stomping all over the users tiddler name space. One solution would be to use a prefix for variables, such as "$:/variable/currentTiddler".
Then the difference between {{Foo}} and <<Foo>> would be that the latter would be equivalent to {{$:/variable/Foo}}.
On 7 Aug 2017, at 16:55, Mat <matia...@gmail.com> wrote:Jeremy Ruston wrote:unify tiddlers and variables.Whoaaa! That sounds conceptually huge!Pulling back up to your original question, the issue we'd now have is how to name those tiddlers that are acting as variables. Simple names like "currentTiddler” wouldn't be great because we'd be stomping all over the users tiddler name space. One solution would be to use a prefix for variables, such as "$:/variable/currentTiddler".A few thoughts, probably based on misunderstanding from my side:a) Is there anything within the $:/ name space that would not be a variable? Shouldn't just "$:/" suffice?
b) ...because wasn't a main point with the shadow tid cascade analogy that overwriting tids use the exact same title as the shadow tid?
I.e that we should not have to name the tiddlers that act as variables in any particular way but that they instead are always treated as variables but with a fallback to a constant value (i.e the tiddler itself... or maybe tiddler content).
c) Are you saying there must exist a tiddler in order for it to be a variable?
If yes, in the case of a currentTiddler variable, maybe the fallback physical tid would be a default tiddler?
Can it not simply be a missing tiddler? Or just a dummy tiddler. Or the way it is currently; the historylist with a "variable field" for current... but maybe that breaks the concept…?
Then the difference between {{Foo}} and <<Foo>> would be that the latter would be equivalent to {{$:/variable/Foo}}.Couldn't e.g {{Foo}} cover everything? -
The system checks to see if Foo is a variable, in which case you get that value. Not variable - go up the tiddler store stack to check if there is a macro named so... get evaluated macro. Last fallback, tidder : transclusion.
I.e only one kind of brackets and one name.
System vars/macros/tids treated the same way but always have prefix $ or similar.
...?<:-)
--
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 tiddlywikide...@googlegroups.com.
To post to this group, send email to tiddly...@googlegroups.com.
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/3bc01743-00d3-4ff8-9530-40c4d74af7de%40googlegroups.com.
Err under this proposal, “variables” are just tiddlers whose value is different across the widget tree. We haven’t turned every tiddler into a variable, we’ve turned variables into a special type of tiddler.
The idea of a naming convention is so that users can easily distinguish between tiddlers intended to be used as variables, and those intended for ordinary use.
Then the difference between {{Foo}} and <<Foo>> would be that the latter would be equivalent to {{$:/variable/Foo}}.Couldn't e.g {{Foo}} cover everything? -Yes, that’s exactly it; I was proposing the angle brackets syntax as a shortcut for transcluding tiddlers with a particular prefix to their title. The idea is to allow us to use long tiddler titles for variables (that won’t clash with the users tiddler titles) while being able to refer to them without typing the entire name.