Search Forums
Kiwitrees on Twitter

    special character, dropbox. token, translate, sanity checker, Export/Import, spouse, individual resource, re-order, bug reporting, tree, errors, media_links, CREM, mobile, 3.0.0 widgets, inactive, login, menu, white screen, check, HTML block, duplicates, custom modules, future, css, events of close relatives, FAQ, IE11, mystyle, cookie, pages, sidebar, fancy tree view, GEDCOM errors, edit interface, news module, gettext, blank screem, responsive menus, fatal error, autocomplete, repo, Favourites 3.0.0, language, 3.0.0, support, not married, advent, age, kiwitrees, blank, fancy image bar, roadmap, logs, clippings cart, editor, image, person, release, click


    1636 posts

    One thing I should mention here is that it has always been my aim to move this module into a replacement series of tools for the current “Reports” (which barely work and are ugly in the extreme).

    This module is really a far better alternative to the “Ancestors” report.

    But I have yet to decide quite how to incorporate all this module’s options (and maybe more) into a set of reporting tools, or if they can / should stand alone in admin. I guess it depends how many such tools will require extensive config options.

    My general thought is to create ‘reports’ that work and look good online, but CAN be printed if required. That’s the opposite of the current reports which exist only for printing, but can (almost) be displayed online (badly).

    I’m also firmly of the view that modern browsers have no need of a specific “PDF” print option within kiwitrees. Its a native element to all browsers now, I believe.

    My personal kiwitrees site is