TT
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
TonyM wrote:
>
> 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.
>
I get where you are coming from. I just thought it worth re-iterating what
Mohammad,
I understands its complexity comes from its power, test it against a copy
of tiddlywiki.com and using items in the toc,
The Kin operator is like a toc only it returns the list of descendants and
or ancestors as a list from a filter.
Where it gets powerful is you can exclude one kin
Thanks Mark,
I think one parent is simpler to understand and follow and more usable in
Tiddlywiki than two parents!
As you said the parser needs to support inheritance if not I have to go
with macros!
@TonyM
I will have a look at kin plugin by bimlas! At the announce time I found it
rather
Mark
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
Doing this where {{!!field}} returns the inherited value would probably
require a rewrite of the parser.
But you could do something like this with macros.
Each tiddler would have a field, say lparent (for logical parent).
You would invoke like <>
The macro would look to see if there was a
Parents beget children
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
Post edited! See the original!
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit
Thank you all for your reply!
1. At first we need simple inheritance like making different styles for
a div or table elements all inherited some features
2. There is one parent, grand parent and grand grand parent
3. We need to have children inherit properties from their parent BUT
Modeling kinship would not necessarily depend on the underlying software
having features of multi-parent inheritance. You can have parent and child
tiddlers, but their relationship would not be expressed via transclusion
but via some other mechanism such as role fields, tags, etc.
On Friday,
Mark S. wrote:
>
> I think we probably want to stick with amoeba style inheritance, and
> assume only one parent at a time.
>
I am not an amoeba, I am a human being.
https://www.youtube.com/watch?v=Ud-eiDxeJj4
Inheritance from two parents--apart from being biologically sound--I found
very
You've kind of skipped to an advanced computer science topic -- two parent
inheritance.
C++ offers two-parent inheritance, but most modern systems, like Java
don't. It's just too messy and complicated.
In biological inheritance, nature tosses a coin and various features are
selected from each
Ciao PMario & Mohammad
TBH, I think it would be well worth having some concrete, fairly detailed,
examples of this & different strategies.
While the official docs are good, the more formal compact presentation
doesn't always illustrate well.
I'm very interested in tools and methods for
On Friday, December 6, 2019 at 12:39:50 PM UTC+1, PMario wrote:
>
> 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.
>
Text edited in first post.
-m
--
You received this
Hi Mohamad,
I think your example doesn't work, since the "inheritence" in this case
won't hold. The "child" always needs its own last-name.
eg: Let's say parent-1 and parent-2 are not married. The child will be
transcluded into both parents and would therefore have 3 different
last-names.
15 matches
Mail list logo
