Such a suggestion is already possible and I have done similar things. However I usually reserve the text field for notes and deliver the transclusions etc via the view template.
I am not exadurating saying almost anything is possible in tiddlywiki, that is why it is my obsession.
Tony
eg: Let's say parent-1 and parent-2 have different last-names. The child will be transcluded into both parents and would therefore have 3 different last-names.
I think we probably want to stick with amoeba style inheritance, and assume only one parent at a time.
If you create children from a parent or parents you can ensure they inherit. Starting with their parents names. If you wish a child could have a field containg not a value but a treansluded text reference. Its value will thus be inherited. Replacing this reference with a value breaks inheritance.
Genealogical trees are already possible, the designer just needs to add logic, Bimlases kin operator is powerful support for this as is Mario's tocp.
One of the keys to such structures is to ensure you also know how to handle missing values.
I know that most of the longest contributors to tiddlywiki also write plugins or propose core changes however I am avoiding this and developing my expertise in the tiddlywiki wikitext and macros rhelm I am confident I can build almost any structure and relationship.
I know I am not always taken seriously or I am criticised for my suggestions of what I perceive to be necessary but would urge you all to consider my somewhat unique perspective, an experienced IT DESIGNER who is mostly not reverting to JavaScript code.
Please consider me a resource for solving problems in the wiki text and macros space and identifying limitations therein because that is my playground. Every time I see a possible limitation I find a workaround, I have 100s of design hacks in my library for systems I want to build in the future. I figure unless I spell this out how would you know?
I already have solutions for some of the limitations I have identified and many will be published in time.
diverse communities are strong communities, embrace diversity.
Tony
Some thoughts
With two parents in genealogy it is recognised there is a patralinial and matralinial tree and when exploring relationships one chooses which tree to follow with, towards ancestors or descendants. In either case or when wanting to investigate both trees it is wise to limit how deep you go. Perhaps 3 back 3 forward and then allow selection of any member in the tree and regenerate 3 back and 3 forward for the selected member.
in active directory, file systems and edirectory inheritance is a litte different, its part of what I alluded to before dealing with missing values. Basicaly you look for a value locally then walk back up the tree until you find the value you are after. This allows the minimum data to be provided because it effectively trickles down unless overridden.
I have built a method to produce what I call a branch, Basicaly you iterate the whole tree but store a strait line of ancestors for each item in the tree e.g. grand, father, son, grandson in a patralinial branch.
You can then use the branch to search for an inherited attribute/value.
If you did this for both matralinial and patralinial branches you could get conflicting results and this needs to be resolved. Evolution effectively does this randomly with exceptions. When this is resolved the result needs to be stored so that subsequent decendants inherit the result.
All this can already be done with a little work.
There is one exception to inheritance flowing down the tree that my father likes to remind me.
"madness is inheritable, you can catch it from your children"
Regards
Tony
With two parents in genealogy it is recognised there is a patralinial and matralinial tree and when exploring relationships one chooses which tree to follow with, towards ancestors or descendants.
Thanks for reitterating. Appreciate your knowledge here.
There is the concept of inheritance for trickle down attribute values and security which is fortunately simpler in many respects. For all types of inheritance its worth collecting tools an methods for designers. What ever the way html list work its a fact any relationship can be represented in tiddlywiki.
I challenge anyone to describe a relationship the don't thing tiddly wiki can represent if not present diagramaticaly.
Regards
Tony