Actually,
On further consideration of the idea having view, update and edit modes,
just imagine having another set of "templates" that describes an update
mode for a tiddler, view would be totally read only, update would enable
specified fields to be active for edit and edit is the current
Mario,
I understand where you are coming from but its a "view all" only, or "edit
all only". I think when using tiddlywiki users and for matter, when acting
as an application or website, this all or nothing edit approach forces the
need for total acceptance of the idea of a tiddler. When for
On Friday, February 2, 2018 at 8:10:42 AM UTC+1, TonyM wrote:
>
> In any given tiddler have a field called field-view or field-edit which
> lists field names that are to be displayed or edited in the view template
>
IMO it's named ViewTemplate for a reason. If you need to edit it,
EditTemplate
My Idea, for the display or edit of fields?
In any given tiddler have a field called field-view or field-edit which
lists field names that are to be displayed or edited in the view template
Ideally for each field there will be a matching field-name tiddler with a
field-caption that sets the
I agree that this would be an optimized way of using fields. Speaking of
fields UI optimization..
I have an extra sugestion.
make it fast to make a field visible!
in current UI you have to edit the view template (for all tiddlers or for a
subset ) to make a new field visible or add*
Reluctantly, perhaps, I have to admit that Fields are really better than
slices, because you can do filter manipulations on them, and not worry
about strange regexp behaviors.
What you can do is create an input template with a drop-down list of
tiddlers to filter. Then each field can be
On Wednesday, January 31, 2018 at 2:35:57 PM UTC-6, Diego Mesa wrote:
>
>
> Personally, I think the most transparent mechanism would just be another
> text area, perhaps the same size as the text edit area for a normal
> tiddler, where everything you type in there (as per the format above)
Thanks all for your comments.
Tony Im looking forward to your work!
Mark, thanks for pointing me to Thomas' extract. Ill take a look. Also, I
need to take a look at "slicing" in TW classic.
Coda thats an interesting idea of actually using a data tiddler to define
fields and their
Diego,
I share your desire to make fields more usable and accessible.
I am working one making fields first class citizens, I have posted on this
previously.
Just as a tag can have a tiddler, I allow a field to have a tiddler, and I
call it a field tiddler.
the intention is to define fields
This was called "Slicing" in the old TWC. It was a much-loved feature that
didn't make it into TW5.
I believe Thomas Elmiger has an extract macro which can be used in a
similar fashion. See the thread:
Hi Diego
Yes, I've done this, so yes, I like the idea ;) I took it to another level
of abstraction by prefixing the field-names with a standard piece of text
that suited my purposes (perhaps you could use "custom-" as a prefix or
"recipe-" if they are recipe related fields and so on).
To
11 matches
Mail list logo
