Yes, the last one worked perfectly! Though it's a bit more difficult to
understand then the first one.
Which is the input set, the output set, where the variable is assigned to
individual item and where the variable is assigned to the whole set, so
on...
I mean the main question is not exactly
On Monday, July 20, 2020 at 9:03:52 AM UTC-7, Jake wrote:
>
> <$list filter="[tag[Comedy]!sort[releasedate]]" variable="title">
> <$list filter="[get[releasedate]compare:integer:gteq[20200701]then
> ]">
>
> <$link/> <$transclude tiddler={{{
> [get[rating]addsuffix[-icon]]
> }}} /> (<$view fiel
> Try this:
> <$list filter="[tag[Comedy]!sort[releasedate]]" variable="title">
><$list filter="[
> get[releasedate]compare:integer:lteq[20200701]then]">
> <$link/> |
>
>
>
> The outer $list gets the titles of the tiddlers with the desired tag,
> sorted in descending order by re
On Monday, July 20, 2020 at 7:18:57 AM UTC-7, Jake wrote:
>
>
> guys... guys... and to put it inside a $list?.. and to combine it with...
> a tag thing... and a sort thing...
>
ps. btw, if i use only MMDD format for dates - can I use just "integer"
> then as comparison type?
Try this:
<$li
On Monday, July 20, 2020 at 7:05:00 AM UTC-7, Mat wrote:
>
> 2) If you are comparing against a date value like {{!!modified}}, you need
>> to specify the full 17-digit value
>>
>
> Are you sure? This seems to work: {{{
> [[20220701]compare:date:gt{!!modified}] }}}
>
OK... I guess that does work
>
> Jake wrote:
>>
>> guys... guys... and to put it inside a $list?.. and to combine it with...
>> a tag thing... and a sort thing...
>>
>> ps. btw, if i use only MMDD format for dates - can I use just
>> "integer" then as comparison type?
>>
>
> Did you at all *test *it before asking others
Jake wrote:
>
> guys... guys... and to put it inside a $list?.. and to combine it with...
> a tag thing... and a sort thing...
>
> ps. btw, if i use only MMDD format for dates - can I use just
> "integer" then as comparison type?
>
Did you at all *test *it before asking others?
<:-)
--
Y
[image: og_og_1485180781287968971[1].jpg]
guys... guys... and to put it inside a $list?.. and to combine it with... a
tag thing... and a sort thing...
ps. btw, if i use only MMDD format for dates - can I use just "integer"
then as comparison type?
--
You received this message because you
Eric Shulman wrote:
>
> 1) The "greater than" compare suffix mode is "gt"... not "gr" !!!
>
Doh!
> 2) If you are comparing against a date value like {{!!modified}}, you need
> to specify the full 17-digit value
>
Are you sure? This seems to work: {{{
[[20220701]compare:date:gt{!!modified}] }
On Monday, July 20, 2020 at 6:17:11 AM UTC-7, Mat wrote:
>
> After some testing I can only say I agree. Why on earth doesn't that
> work??? I also tried
>
> <$vars date={{!!modified}}>
> {{{ [[20220701]compare:date:gr] }}}
>
>
Three things:
1) The "greater than" compare suffix mode is "gt"... no
Jake wrote:
>
> Hmmm... I think I get... some of that... me thinks :) I also just
> thought that "define" is possible only as part of marco (
> https://tiddlywiki.com/#Pragma) and only one define per macro is possible
> (the one that starts at the very beginning of tiddler), but that's not t
>
> That last solution of mine did *not *have any macro. A macro is a
> separate "codelet" that starts with "\definition".
>
>
>> OK, first, I agree that it *ought *to be possible to directly insert the
>> color into the span thing. Again, my last solution did kind of do this. But
>> there a
>
>
> B-but... why it needs a macro inside?
>
That last solution of mine did *not *have any macro. A macro is a separate
"codelet" that starts with "\definition".
> why it can't be just:
>
> <$list filter="[{!!rating}compare:integer:gt[70]then[green]]
> ~[{!!rating}compare:integer:gt[50
> Hmmm s... do I get it right, that in order not to type all that
>> "list" thing each time I need to make 2 macros?
>>
>
> No, it could all be in one code if it weren't for the fact
> that "background-color:" can't take <<...>> as an argument but it *can *take
> $(...)$ as an argume
Jake wrote:
>
> Can it be done via some "var" thingy?
>
A bit unclear what you mean. There is a variable created and named in my
proposed code, i.e the "variable=color" bit. This variable gets the value
that comes out from the filter. Something like $vars would do a similar
thing if you use it
>
> Maybe I answered in an incomplete way: If you want the outer code, i.e the
> listwidget, to be a macro then you would do as you correctly propose. But
> the reason so split it up into two macros is only because that css bit
> can't handle <<...>> as an argument.
>
Can it be done via some "
Maybe I answered in an incomplete way: If you want the outer code, i.e the
listwidget, to be a macro then you would do as you correctly propose. But
the reason so split it up into two macros is only because that css bit
can't handle <<...>> as an argument.
<:-)
--
You received this message be
> Hmmm s... do I get it right, that in order not to type all that
> "list" thing each time I need to make 2 macros?
>
No, it could all be in one code if it weren't for the fact
that "background-color:" can't take <<...>> as an argument but it *can *take
$(...)$ as an argument. I'm no
>
> Fun little task.
> You might want some additional style tweaking but here's how you can do it:
>
> \define rating() Rating {{!!
> rating}}
>
> <$list filter="[{!!rating}compare:integer:gt[70]then[green]]
> ~[{!!rating}compare:integer:gt[50]then[grey]] ~[[red]]" variable=color>
> <>
>
>
>
Hmm
Fun little task.
You might want some additional style tweaking but here's how you can do it:
\define rating() Rating {{!!rating
}}
<$list filter="[{!!rating}compare:integer:gt[70]then[green]]
~[{!!rating}compare:integer:gt[50]then[grey]] ~[[red]]" variable=color>
<>
<:-)
--
You received this
20 matches
Mail list logo
