1
0
Fork 0
mirror of https://github.com/sbrl/Pepperminty-Wiki.git synced 2024-11-23 04:43:00 +00:00
Commit graph

6 commits

Author SHA1 Message Date
be8595bc44
Start Integrating the BkTree into the main Pepperminty Wiki codebase, but there's a long way to go.
There's also a bug in the deletion logic in that if the root node is 
deleted (if it doesn't crash first), then it's all over and it's broken.
2020-03-14 17:49:26 +00:00
6480d72323
BkTree: Bugfix node deletion.
I think it's working now!
2020-03-09 21:32:06 +00:00
296139049a
BkTree: Add trace, improve shell, and bugfix delete.
The shell has given me an idea.....

We could have a CLI module to Pepperminty Wiki that allow admins to run 
longer-running tasks without them getting killed 1/2 way through because 
of a timeout.
2020-03-09 21:27:20 +00:00
2f901642fe
BkTree: Implement (untested) remove() method 2020-03-09 01:14:31 +00:00
d099be8e16
BkTree: Add graphviz .dot file generation 2020-03-05 01:20:51 +00:00
593f16dfb9
Commit BkTree & Nilsimsa experiments. It's about time!
....I was gettign increasinly nervous about not committing these to git. 
Hopefully at some point soon I'll be able to integrate the BkTree into 
Pepperminty Wiki properly - but I still need to implement word removal 
first before I can do that.

Also, feature-search is getting big. It's refactoring time to be sure, 
but Im uncertain  at this stage precisely _how_ I want to go about that. 
I've got 2 ideas:

1. Refactor the engine and the storage box into separate "library 
modules"
2. Refactor them into their own repository/ies or something, and include 
them as extra data
3. Extend the  extra data system to support local files and include them 
in the main Pepperminty Wiki repository

Thought is required. If anyone actually reads this message, do get in 
touch with your thoughts!
2020-03-04 01:57:13 +00:00