Jeremy,
I cat yet respond to all your questions because I remain somewhat confused
but respond to a few below;
On Thursday, March 12, 2020 at 10:07:06 PM UTC+11, Jeremy Ruston wrote:
>
> Hi Tony
>
> The following is an outline of how I see this for a "view from a different
> mind", for you to keep in mind going forward.
>
> In all your examples of using wikify you tend to use it in the body of the
> wikitext, just in time, wrapping its own output.
>
>
> The results of the wikify widget are indeed only available within the
> content of the widget.
>
> Can you show a counter example to help me understand what you mean?
>
I will later
>
> I tend to run into difficulty using it any other way, such as a local or
> global macro, and when in your example there are "variables" in the source
> eg if your set included {{!!fieldname}} or $tooltip$ etc... in what is to
> be wikified.
>
>
> You’re saying that you can’t use the wikify widget within a macro? I’m not
> sure what you’re getting at here. Perhaps some examples would help?
>
Will show later but see buttons below
>
> It is clear we need to fill out the documentation Pragma
> <https://tiddlywiki.com/#Pragma> and Wikify Widget
> <https://tiddlywiki.com/#WikifyWidget>, sometimes so people know this
> does not promise things it may "on the surface"
>
>
> Any help with that is welcome.
>
Will do
>
> - Is using \import filter more efficient than global macros or the new
> view only macros tag
>
> They’re all the same mechanism under the hood: the importvariables widget.
>
I understand this, but the other mechanisms are often applied to every
tiddler, where as \import variables may apply them only when specifically
named, so in some cases I imagine it more efficient?
>
>
> - Where are the rules documented? Are they a one for one match with
> these names $:/core/ui/ControlPanel/Parsing
>
> The pragmas are documented here:
>
> https://tiddlywiki.com/#Pragma
>
This mentions \rules and not much more. Is there more doco somewhere? That
is why I ask are the rules what we see here $:/core/ui/ControlPanel/Parsing
<file:///C:/Data/TW5/TiddlyDesktop/TiddlyDesktopWiki.html#%24%3A%2Fcore%2Fui%2FControlPanel%2FParsing>
?
*\rules for adjusting the set of rules used to parse the text*
No rules names, *except* not mentioned etc..?
>
> I found the "undocumented "[wikiparserrules[]]" filter operator
>
>
> That’s a filter operator, which are nothing to do with pragmas.
>
Well surely it does relate to the rules pragma, I thought this is a way to
access all the defined rules, which are not documented in the \rules pragma
or anywhere else.
\rules except table
Where table is in the wikiparserrules output and also found listed here
Block Parse Rules <$:/core/ui/ControlPanel/Parsing>
Is there an include parameter or just by naming the rule?
>
> Wikify
>
> - With the Wikify widget is there a way for us to apply the pragma
> rules to the result?
>
> That’s exactly what my example in my previous post showed.
>
Opps Yes, Use an additional set widget to pre-pend the define, even pragma,
to the text before wikifiction.
> - The Wikify Widget <https://tiddlywiki.com/#WikifyWidget> would
> benefit from examples and ideally through the various templates available
> already in the core, so people can generate and store tiddlers in
> alternate
> formats that already operate under export, save and other options.
>
> What do you mean by “templates” here? What’s the connection between
> templates and the wikify widget? Reusing the existing export filters
> doesn’t have anything obvious to do with the wikify widget.
>
I remain awfully confused here, I think I will present another thread in
time. I have tried to use the $:/core/templates tiddlers to render a
tiddler and save the result as a tiddler, copy to clipboard or file.
>
>
> - Storing the result of a wikify operation in the current wiki is also
> of substantial value (I would detail if asked)
>
> As you know, changes can only be made to the wiki via action widgets, are
> you experiencing difficulties doing that? Again, perhaps an illustration
> would help.
>
I would be happy to make a button to do this, But I seem to be missing
something. They often instead include the code unwikified. I will start a
new thread when I have worked through the details.
But I would have thought the below buttons would work, when json-here
returns the formated tiddler.
\define json-here()
<$wikify name=output text="""{{||$:/core/templates/json-tiddler}}""">
<$macrocall $name="copy-to-clipboard" src=<<output>>/>
</$wikify>
\end
<<json-here>>
<$button>
<$action-createtiddler $basetitle="Test" text=<<json-here>>/>
Go1
</$button>
<$button>
<$action-createtiddler $basetitle="Test" text={{||$:/core/templates/json-
tiddler}}/>
Go2
</$button>
>
> Parsing is of substantial interest to many, so I hope eventually we can
> open this to users, especially to add our own markup.
>
>
> Beyond your desire to add custom markup without having to use JavaScript,
> what else is needed to open parsing to users?
>
> I and mario have being looking at this with the leading dotparagraph and
> trailing spacespace. Of course such markup will not be universal when
> tiddlers are transferred but they can be made to "fail gracefully" when
> not defined.
>
> Good stuff,
I just wonder if there would be a way to specify our own markup that that
results in a block or inline html tag being applied at render time?
Primarily to allow us to utilise other html tags that are not yet included
in the wikitext standard, and without making the text harder to follow with
html embedded in it. For example we need a plugin to use the html details
tag, when an additional markup similar to ; and : `<dl><dt>` tags would do
the same. There are plenty of special characters available.
Perhaps even a generic way to to feed block and inline content into a named
html tag pair would open up html features, without needing to wait for a
widget to be written. The advantage of markup is it keeps the text simple,
shorthand.
Imagin with the dot paragraph Idea I could have indicated that a line was
to be wrapped in `<p></p>` and we would not need to incorporate it into
wikitext.
Thanks
Tony
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/531f651e-be94-44f2-a3b2-977b41208a32%40googlegroups.com.
