Search Forums
Forums
Kiwitrees on Twitter
    Tags

    F.A.B., CHR, 3.1.1, batch update, server, library, I18N, version, 3.3.1, statistics, sanity, shared notes, message contactform, husband, charts, googlemaps, menus, contacts, 3.0.0. setup, not married, pop-ups, image, transifex, 3.0.0 widgets, kiwitrees, privacy, googlemap. modified, index, GEDCOM, responsive menus, menu, Require visitor authentication, release, duplicates, 3.2.0, family facts, ckeditor, relationships, census, json, illegitimate, fixing errors, family, timeout, lists, cookie, style, permissions, address, login upgrade, birth, error, add, Histo, mystyle, danish, reports, login failure, beta, tags

    #4996
    kiwi
    kiwi
    Keymaster

    1533 posts

    Some initial thoughts (not meant to appear negative – the proposal does have considerable merit):

    1. The “other facts” do come with issues. Take “immigration” for example, do you use the tag IMIG or EMIG, or both if you know about departure and arrival? I know my own data is inconsistent in this regard. It may be true of many other tags as well (such as BAP/CHR). Then there are cultural differences (Bar Mitzvah vs baptism??) But perhaps we can simply provide an input box where you could enter your own comma delimited list of additional facts?
    2. Then there’s the challenge of the text to include for linking the facts into sensible sentences, and ensuring it is readily translatable by all the languages that need a completely different sentence structure.
    3. It’s easy to say “try as much as possible to imitate the formatting of the story” but that’s not an option. Everything MUST be formatted to a prices definition and all the html for a “story” is part of the data stored. . So if you have formatted your own story page for the Stories tab, the tree View cannot change that. So, for example, if you were to incorporate a table that fills the width of the tab, it might well overflow the width of tree view, or your printed output. At the very least you would need to consider multiple displays when creating the Story in the first place. But, on the other hand, that’s not necessarily a bad thing, just perhaps beyond some people!

    As a slight aside – are there things about the Tree View that you would change (rather than add to? I, for example, don’t see the need for the “Descendants of…” before each menu item and would remove it.

    In the past this module was created for webtrees. But it was a simple exercise to port it over to kiwitrees, and rely on it’s original creator to maintain it. Now with it’s latest changes webtrees has moved so far from it’s original structure that is no longer possible. So I will need to maintain this module myself in kiwitrees now. Hence I am better able to consider improvements to it just for kiwitrees.

    Nigel
    My personal kiwitrees site is www.our-families.info