This thread was very helpful as I have aimed to understand how to have
different layouts for different kinds of tiddlers, ones which superceded
the amount of flexibility afforded by the ordering of tiddlers tagged as a
view template, which include different positions for the text field itself
I have not played much with this yet, but I keep coming back to this
thread. Now that I'm getting over the hangover from discovering what
filters can now do, this is the Next Big Thing as far as I'm concerned.
I hope to find time to test-drive this soon.
Cheers,
Chris
On Monday, May 25, 2020
Hi everyone,
Let me explain the method I am using to do these custom templates. I am not
changing the existing $:/tags/ViewTemplate or $:/tags/EditTemplate
architecture at all. The $list widget that builds each tiddler in the
story-river still does exactly that. What I have done is gone into
Here is a json of all the tiddlers necessary to test this out, both the
changed sysetem tiddlers, and the custom templates and settings tiddlers I
have been using to test this new system. If you drag everything into a
fresh wiki, and then open the "Adat 1" tiddler, you should see that the
Yeah, this is probably my favorite hack I've ever come up with. Its so easy
to customize pieces of the Tiddler-in-the-Story-River.
Right now I just got a tabbed editor working on all [tag[Glosary]]
tiddlers, that auto-hides the Fields section in an accordian $reveal
widget, and has the default
>
> So it externalises the determination of the view template "pieces" to use
> given provided conditions?
>
>
Exactly
> I would like to use this to replace the edit mode field handling with a
> customised one on particular tiddlers.
>
>
I've been doing exactly this using one small part of
Saq,
Thanks,
So it externalises the determination of the view template "pieces" to use
given provided conditions?
This seems like a very helpful hack, Using import variable on such
templates we would also be able to reduce the global macros needed for
specific macros for a given template.
Post script,
A Hide-body variable/macro that would override the hide-body field if it is
set, allowing one template to turn it off or on programmatically as
required.
Regards
Tony
On Monday, May 25, 2020 at 10:29:09 PM UTC+10, TonyM wrote:
>
> Joshua,
>
> Can you share what the implications
@TonyM in short this allows you to completely override and replace any part
of the ViewTemplate that you want to.
Look at Joshua's example for $:/config/ViewTemplate/Body from above.
[tag[$:/tags/Macro]then[$:/plugins/joshuafontany/core/ui/ViewTemplate/body/
macro]]
Joshua,
Can you share what the implications are in your mind?
I now have Timimi on Chrome, and read the forum in chrome. I found a nice
workflow.
- Download the json files to a my scratch folder, but they sit in the
browser footer tray
- Go to Tiddlywiki.com drag the json files from
I think I have a solution for this one. The ability to hide/replace the
default text field is a bit cumbersome atm. You can hide the text-body by
setting the `hide-body` field to "yes". And we can add new "sections" with
`$/tags/ViewTemplate`, but unless we dig around and copy the $reveal code
Odin
Where you want text to appear in a html template you can use
<$transclude mode=block/>
Which defaults to currenTiddler and the text field.
Not sure if this solves your problem but it is another way.
Tony
On Wednesday, January 8, 2020 at 7:45:05 AM UTC+11, Odin Jorna wrote:
>
> Hi Eric!
>
Hi Eric!
Thank you for the explanation of how the view tiddler is made of and how
the ordering works. That clarified a lot.
After trying out the list-before field, the text does change to after the
template. But what I was looking for was getting it inside the template.
Inside, there are some
On Tuesday, January 7, 2020 at 11:49:41 AM UTC-8, Odin Jorna wrote:
>
> The problem I am running into is that I don't have control of where the
> contents of the text field are placed into the template. I want to use the
> normal text box to put down my notes, thoughts and any other information
14 matches
Mail list logo
