if it helps a few thoughts;
I like to think of objects - they have a definition and instances of them.
All you need is a way to indicate a tiddler is an object eg a tag or custom
field object-type="book".
next you have a tiddler in the view template that responds to the existence
of the
Very nice Anders, thank you. Is the standardtext field necessary? Why not
just have a tiddler $:/view/book which can be transcluded via a
ViewTemplate onto any tiddler with tiddlertype=book?
On Friday, 16 April 2021 at 13:20:51 UTC+1 Anjar wrote:
> Hi Si,
>
> Thank you for clarification;
Hi Si,
Thank you for clarification; however, I think the approach is still valid
and demonstrated how it works, and with minor adjustments you can have
field templates across source types;
(1) Make tiddlers with
- title starting with "$:/template",
- a field tiddlertype, for example
@Anders The disadvantage of your approach is that you have to manually
create a form for every type of source, many of which will share fields
with one another. The reason I asked about the best way to associate
source-types with their required fields is to avoid this problem. If you
know
Hei Sjaak,
I think a similar approach can be useful;
(1) Make tiddlers with
- title starting with "$:/template",
- a field tiddlertype, for example tiddlertype: book, and
- a field standardtext, for example standardtext: {{||$:/view/book}}
(2) This time, the template contains the form you want
Hi Si,
I have been thinking about an approach like yours but have not implemented
anything yet. It seems important to me that some fields may be of a
different kind than just text to be entered. Like choosing from a list of
options (with f.i. the select widget or radio widget).
My 2 cts.
Hi Si,
Have a look at this post:
https://groups.google.com/g/tiddlywiki/c/Q3vU6tnPffI/m/WNguU1p6BwAJ
It's about using premade templates to create new tiddlers; you can of
course add a form if you prefer that, instead of editing the new tiddler
directly
Best,
Anders
torsdag 15. april 2021
@Springer Thanks for your reply.
>>> The lovely thing is that you can filter on a tag (or any other filter
condition), to see a column for each of the fields you care about for that
tag (or filter condition), with a row for each tiddler that fits the
condition (and the ability to "clone" new
Si, I highly recommend checking out all the RefNotes resources (active here
recently, contributed by Mohammad).
My own approach is to use a DYNAMIC TABLE (Mohammad's Shiraz) for each
reference-type. The lovely thing is that you can filter on a tag (or any
other filter condition), to see a
9 matches
Mail list logo
