Mat!
Great suggestion!
I believe there is not good resources on "best practice" coding in TW.
I hope Jeremy accept and I support you!
Mohammad
On Wednesday, August 8, 2018 at 2:57:15 AM UTC+4:30, Mat wrote:
>
> @Jeremy,
>
> Could tiddlywiki.com feature a number of best practice examples such as
I agree Mat, it’s been a real masterclass experience. Jeremy has shown us
insight that I have picked up on other google threads.
--
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,
@Jeremy,
Could tiddlywiki.com feature a number of best practice examples such as the
one given, ideally including less than optimal examples with annotations
and and pitfalls such as my own attempt here above? I cannot think of a
better way to learn good TW code than from seeing comparisons of
Hi Stuart
Here’s a refactored version that works:
\define image(tiddler)
<$set name="state" value={{{ [<__tiddler__>addprefix[$:/popupstatus/]] }}}>
<$button class="tc-btn-invisible tc-thumbnail-image" popup=<>>
<$tiddler tiddler=<<__tiddler__>>>
<$image source={{!!title}}
Could you check it without class="tc-drop-down" and see what will be the
result?
On Tuesday, August 7, 2018 at 9:54:28 PM UTC+4:30, Stuart Amor wrote:
>
> Thank you guys, this has been a real education. I have taken Jeremy's
> code and have tried to expand it to create a button that when
Thank you guys, this has been a real education. I have taken Jeremy's code
and have tried to expand it to create a button that when clicked brings up
an enlarged image, however the image in the popup is very narrow?
\define image(tiddler)
<$button class="tc-btn-invisible tc-thumbnail-image"
I hadn't thought to think of the underscores as brackets, but that might be
useful.
Best wishes
Jeremy
--
Jeremy Ruston
jer...@jermolene.com
https://jermolene.com
> On 7 Aug 2018, at 15:00, @TiddlyTweeter wrote:
>
> Thank you Jeremy
>
> Would it be OK to call __underscore brackets__
Thank you Jeremy
Would it be OK to call __underscore brackets__ "sub-bracketing?"
What I mean is that it needs the "<" "<<" contexts to function, so its a
subsidiary construct?
Best wishes
Josiah
On Tuesday, 7 August 2018 15:24:57 UTC+2, Jeremy Ruston wrote:
>
> The one thing that I'd like to
> The one thing that I'd like to know is whether, in all contexts, you need
> __underscore brackets__ to be "bracketed", i.e. does this construct always
> have to have "<<" or "<" etc. around it?
Yes, a construction involving either << or < is needed to use any variable.
The parameter name
Ciao Jeremy
The one thing that I'd like to know is whether, in all contexts, you need
__underscore
brackets__ to be "bracketed", i.e. does this construct always have to have
"<<" or "<" etc. around it?
Jeremy Ruston wrote:
> The feature was new in 5.1.16:
>
>
>
> ... I wouldn't blink if it said
>
> <<$tiddler$>>
>
I take that back. There is no previously defined such variable or macro so
this wouldn't make sense.
<:-)
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this
Hi Mat
> On 7 Aug 2018, at 12:26, Mat wrote:
>
>
> Your code does work but what on earth is this??
>
> That is just totally new to me. What is it called? Are there any docs on it?
> Actually, what does it do? I wouldn't blink if it said
The feature was new in 5.1.16:
@Jeremy - that was valuable to say the least! Thank you!
But...
<<__tiddler__>>
>
Your code does work but what on earth is this??
That is just totally new to me. What is it called? Are there any docs on
it? Actually, what does it do? I wouldn't blink if it said
<<$tiddler$>>
Thank
Hi Mat
> I'm unsure why you have two separate macro calls in your example. Regardless,
> maybe this works:
>
>
> \define image-inner() [img width=80 [$(caption)$|$(tiddler)$]]
>
> \define image(tiddler)
> <$vars caption={{$tiddler$!!caption}} tiddler='$tiddler$' >
> <>
>
> \end
>
> <:-)
14 matches
Mail list logo
