> Can you have more than one custom field?

You can have as many custom fields as you like.

Here's an example of a complete custom tiddler 'type' for storing
information about CD's:

   http://www.TiddlyTools.com/#CDSample
   http://www.TiddlyTools.com/#TaggedTemplateTweak
   http://www.TiddlyTools.com/#CDViewTemplate
   http://www.TiddlyTools.com/#CDEditTemplate
   http://www.TiddlyTools.com/#ListboxPlugin

* [[CDSample]] is tagged with "CD".
* When you display that tiddler, TaggedTemplateTweak (TTT) applies the
CDViewTemplate.
* When you edit that tiddler, TTT applies the CDEditTemplate.
* The CDEditTemplate fields use the <<select>> macro defined by
ListboxPlugin to offer a configurable droplist of genres to choose
from.

> How about a couple fields called 'parent' and 'grandparent'? If the
> 'parent' is deleted, the 'grandparent' becomes the 'parent' and the
> 'grandparent' field gets filled from the parent field of the original
> 'grandparent'.

> I'm not a programmer, so I don't know if its even possible, but it
> looks like it should be.

Almost anything is possible with enough time, effort, and coding
skills.  The only caveat is that there are always unexpected issues
that add complexity to an otherwise straighforward idea.

For example, while the sort of 'family adoption' handling that you
suggest seems to be reasonable, why should the 'grandparent' adopt the
'orphaned' tiddler?  Why not be adopted by an 'aunt/uncle' tiddler?

Also, what is the appropriate handling if you import tiddlers from
other documents that may have some of the same tiddler names, but
without the same parent/grandparent information?  Do you merge the
existing parent/grandparent data with the new tiddler content?  Or
completely replace the existing tiddler and break the hierarchy by
discarding the parent/grandparent?

I can probably think of many more questions of a similar nature... for
which the answers are always dependent upon the specific use-case,
which is why any such grandparent/parent/child linkage would have to
be implemented as a plugin, rather than be a built-in feature of the
core.

-e

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/tiddlywiki?hl=en.

Reply via email to