Hi bimlas,
Regarding your example:
> For example, if I want to use a custom macro instead of "<>", which
> can open all tiddlers, I simply replace the template in the "tags" field
> definition with a macro I want.
>
I once made a plugin to get my own template working with tags ... took me 8
Hi Bimlas
> I think that besides being able to read these settings, they should be
> adjustable. For example, if I want to use a custom macro instead of
> "<>", which can open all tiddlers, I simply replace the template in the
> "tags" field definition with a macro I want.
It sounds like
>
>
> I think that besides being able to read these settings, they should be
> adjustable. For example, if I want to use a custom macro instead of
> "<>", which can open all tiddlers, I simply replace the template in
> the "tags" field definition with a macro I want.
>
Bimlas,
Actually
Jeremy,
We could perhaps ameliorate the problem by exposing that JS configuration
> information for wikitext to access.
>
I think that besides being able to read these settings, they should be
adjustable. For example, if I want to use a custom macro instead of
"<>", which can open all
Hi Bimlas
As pmario points out, the special behaviour of the fields modified, created,
tags, list and color is defined within the JavaScript core of TW5, and isn’t
directly accessible from wikitext. It was clear some time ago that this
approach isn’t optimal, but by then it was too late to
I'm developing a plugin that lists the values of the fields. As I was
writing it, I had to realize that fields can be very useful, but I feel
like they're hanging in the air because there is no definition for them (so
I implemented most of the following ideas in the plugin).
For example, from
6 matches
Mail list logo
