0.4.1

What's Changed

• feat(view): side panel: checkboxe as sibling toggle by @TheBestTvarynka in #53
• feat: add grafily file menu options; by @TheBestTvarynka in #54
• feat: quadratic layout; by @TheBestTvarynka in #55
• refactor: remove tree implementation. use graph for all use cases; by @TheBestTvarynka in #56
• feat(ui): side panel: add ability to change positioning algorithm of the graph by @TheBestTvarynka in #57
• feat: stateful plugin tab: load the same graph after Obsidian app restart by @TheBestTvarynka in #58
• fix: plugin graph interactivity in a new Obsidian window; by @TheBestTvarynka in #59
• chore: update docs and readme.md; by @TheBestTvarynka in #60
• fix(ui): side panel: now side panel background does not stop pointer events; by @TheBestTvarynka in #61
• feat: scan report; by @TheBestTvarynka in #62
• feat: person creation helper; by @TheBestTvarynka in #63
• feat: implement keyboard navigation and interactivity; by @TheBestTvarynka in #64
• chore: 0.4.1; by @TheBestTvarynka in #65

Full Changelog: 0.3.6...0.4.1

0.3.6

What's Changed

• chore: update docs; by @TheBestTvarynka in #38
• fix(ui): do not render marriage node button if marriage has no children; by @TheBestTvarynka in #39
• fix(layout): full graph: children node inserting; by @TheBestTvarynka in #40
• fix(parsing): consistent spouses order inside marriage; by @TheBestTvarynka in #41
• fix(layout): full graph: parent nodes order; by @TheBestTvarynka in #42
• chore: AI_POLICY.md, CODE_OF_CONDUCT.md and CONTRIBUTING.md; by @TheBestTvarynka in #44
• feat: reorder buttons on SidePanel; by @TheBestTvarynka in #45
• feat: autoselect and automatically center the starting node; by @TheBestTvarynka in #46
• feat: improve edges styling; by @TheBestTvarynka in #47
• feat: now the user can open the person from side panel; by @TheBestTvarynka in #48
• feat: implement buttons for opening the plugin for specific person; by @TheBestTvarynka in #49
• fix(ui): now background pattern present on each grafily tab by @TheBestTvarynka in #50
• feat(ui): dynamic tab title; by @TheBestTvarynka in #51
• chore: v.0.3.6; by @TheBestTvarynka in #52

Full Changelog: 0.3.5...0.3.6

0.3.5

• Now the user is able to show/hide any children nodes of the marriage separately: #34
• Refactored the code, so now developers do not need to silence ESLint: #35
• Added unsaved data detection: now, when the user tries to go to the start-up menu when there is unsaved data, the plugin will ask for confirmation: #36

0.3.4

What's Changed

• Downgraded to React 18: #28
• Fixed start-up menu: show the menu even when the index is empty: #29
• Added artifact-attestations: #30

0.3.3

0.3.3

0.3.2

Fixed the plugin description in manifest.json:

0.3.1

• Updated the README.md.
• Fixed the manifest.json.

0.3.0

Publish a new release, because Obsidian requires the release title to match the version in manifest.json. No new improvements.

v.0.3.0

This release includes numerous changes. Finally, after months of work, this plugin is usable. Below is the short list of new features from most to least significant (in my honest opinion).

^{_{All persons in demo screenshots below are generated using AI. If you find any coincidences with real people, please contact me, and I will fix them.}}

Visualization algorithms

Reingold-Tilford

It finally works as intended. I rewrote the implementation and added nodes collapsing/expanding, node rearrangement, etc. Demo:

This algorithm can render the children's tree as well as the parents' tree.

PRs:

• feat: generic Reingold-Tilford tree implementation
• feat: implement nodes rearrangement (move left, right, and swap);

Brandes-Köpf

A new layout type. It is suitable for family graphs of any complexity. The user can expand/collapse any nodes they want. The nodes are not perfectly centered, but still pretty enough.

PRs:

• feat(layout): Brandes-Köpf
• feat(layout): Reingold-Tilford: tree manipulations support and refactoring;
• feat: implement nodes rearrangement (move left, right, and swap);

Persistance

Now the user can save generated graphs and reopen them in the next session. It allows the user to have a favorite graph collection.

PRs:

• feat: implement graph saving and loading;
• feat: reproducible persistence

Start-up menu

The start-up menu shows when the user opens the plugin. It allows the user to either load a saved graph or generate a new one.

PRs:

• feat: start-up menu

Side panel

The side panel is a panel of 8 buttons:

1. Move the node left among its siblings.
2. Move the node right among its siblings.
3. Swap the selected person's place with their spouse.
4. Show the current node: the viewpoint will move so the selected node will be in the center of the screen.
5. Return to the start-up menu.
6. Reload persons' data. This button will not update relationships. But it will update a person's data, such as names, images, and dates.
7. Save the current graph.
8. Delete the current graph.

Data directory configuring

Now the user can configure the directory that the plugin will scan for people's data.

PRs:

• feat: implement dir path configuring;

Other fixes and small improvements:

View

• feat(rendering): fixed view during graph re-rendering;
• feat: move rendering options from model to node data
• feat(ui): highlight gender and add buttons for node rearrangement;
• feat: implement refresh button;

Docs

• refactor(layout): doc comments;
• chore: update readme.md;
• chore: update readme.md
• chore(docs): update readme.md;
• chore: v.0.3.0;

CI

• ci: add release.yml and update lint.yml;

v.0.2.0

This is the second release of the Grafily plugin. Now it is closer to what I want, but still far from the end goal.

Nevertheless, the list of new features is impressive.

The V2 of the nodes positioning algorithm

Actually, it is not a second version, but rather a complete rewrite with additional features.

Now it supports siblings and their spouses' positioning. Even more, it supports rendering sibling' spouse ancestors (parallel family tree).

Parents collapse

Now the user can hide/show persons' descendants.

Better styling

Do not render the unneeded edge handles. Do not render needed buttons. More consistent styling.

Showcase

(I did not have the time and energy to create fake data, so I just blurred sensitive information)