This is for the long term, but it would be very nice if KeyBase could support inline editing of keys, so people don't have to download a key and then upload the edited key in order to edit a key.
I envisage something similar as Lucid Phoenix has, displaying the key as an indented key and having the ability to edit leads, add and delete couplets and add and delete items (taxa) and sending the edited key back as a Javascript object. A Javascript library like DynaTree (now FancyTree I think) could handle that.
Before this can be done we need to find a different way to deal with reticulations in keys (#9), as reticulations break the tree graph (and hence the indented key). Lucid Phoenix, by the way, can not handle reticulations in keys and will break an uploaded key with reticulations in it without reporting an error.
After a phone call from Kevin last week, I realised that, if we are going to have inline editing of keys, we'll also need to be able to deal with unfinished keys. Unfinished keys bring:
Leads with multiple assigned items
Leads that lead to a node, as well as assigned items.
This is for the long term, but it would be very nice if KeyBase could support inline editing of keys, so people don't have to download a key and then upload the edited key in order to edit a key.
I envisage something similar as Lucid Phoenix has, displaying the key as an indented key and having the ability to edit leads, add and delete couplets and add and delete items (taxa) and sending the edited key back as a Javascript object. A Javascript library like DynaTree (now FancyTree I think) could handle that.
Before this can be done we need to find a different way to deal with reticulations in keys (#9), as reticulations break the tree graph (and hence the indented key). Lucid Phoenix, by the way, can not handle reticulations in keys and will break an uploaded key with reticulations in it without reporting an error.