Bernhard B.

WOW, that looks AWESOME - really hope that you continue working on it. Looks great! Just out of interest: Does the code live on github? :) > and I might...

Cool, many thanks for sharing! Please let me know when you update the repo and/or move it to github. Would love to follow your progress :) regarding the slash/underline in...

> eventually some sort of partial match or wildcard search would let us find all the blends by a search for a component agreed, that would be awesome. But as...

the graph arrow can now also be used in the search :)

> how it could work - "car" becomes "car" (for simple matching), or perhaps ".\bcar\b." (for regex) That's an interesting idea. I'll check in the backend...maybe that's already easily possible....

> it could be an "advanced task" to just organise the polys people already made I _think_ that's probably the best idea. In my opinion Web UIs are really bad...

Many thanks for sharing! At the moment, I am seeing two rather big problems: * the database schema wasn't designed to support more than one hierarchy level. That was a...

aaah okay, so if I understood you correctly you mean that we store the label as it is (e.g: `0.man.right_arm`) in the database and parse the expression (either in the...

> you mentioned that there's "one parent level" - is this the way you implement "head/dog" as "dog.has='head'" ? jep, right. `head/dog` and `dog.has='head'" are basically equal - one is...

Using the properties system for that...that's an awesome idea. Really like that! I guess we could add a hidden property which serves as index to the properties list. Just thinking...