Open smurp opened 7 years ago
This functionality has already been implemented. Should we close the issue? Or are there any added features that still need to be added? (e.g. #72)
Reformat the EDIT so it says "beta" afterward to warn users that it is a work in progress
Please change "Edit" to "Contribute" and include "beta" afterwards as above.
@wolfmaul @smurp
Thanks!
[x] changed to Contribute (beta)
Perfect, cheers. Do you want to take a look at the original ticket here @smurp and see if this is closeable/reassignable?
Shifted this to "In Progress" since there is still non-mexico stuff to do here.
title | video | experiment |
---|---|---|
mind mapping demos | https://www.youtube.com/results?search_query=mindmapping+demo | |
MindMeister | https://youtu.be/jfIAqr6cBX4 | https://www.mindmeister.com/1250796566 |
Free Mind | https://youtu.be/b8eef06V1us | |
Popplet | https://youtu.be/j-ZPpRPcFc8 | |
XMind | https://youtu.be/6qxfpkO0_cU | |
OmniGraffle | https://youtu.be/TjB2N_xypfk |
If the user has the right to edit in the current context then...
Expose a toggle (perhaps in the upper left) that looks something like this:![edit_mode_2](https://cloud.githubusercontent.com/assets/774119/19197692/71a917cc-8c78-11e6-958d-7c2cbc1835dc.png)
The View mode continues to expose the current behaviour.
When the Edit mode is engaged then a wide single line form is revealed off to the right of the toggle. The form contains three fields:
Subject
,Predicate
andObject
.Behaviour
Save
button becomes clickablesubject
andobject
nodes would be highlighted and lablled during this period too (similar to when an edge is being hovered over). Until the predicate is established the edge is grey.subject
in the form and while one is dragging a new grey line will be visible to represent the new edge being created. The tail of the line will remain at the subject node and its head will follow the cursor, latching when close enough to the possible object node.object
predicate
field is set and is set to a predicate which has a range which is a string, date or number datatype then three things happen:object
field changes to an appropriate widget for that datatypesubject
of the tripleClear
button is pressed or thepredicate
is changed to an ObjectPropertysubject
while any label becomes the value of theobject
; the value of the label becomes theobject
and the appropriate predicate is shown. If there are multiple triples which are recognized as being labels then the subject-predicate-object-save-cancel-delete section is multiplied, one per triple.auto
under the predicate which would cause Save to happen as soon as a successful drop happens -- whereupon thesubject
andobject
would be cleared but thepredicate
would retain its value. This auto-save behaviour could only be engaged while thepredicate
field had a value and would only be sensible if thepredicate
were an ObjectProperty -- meaning that the object must be a resource rather than a literal data value such as a number, date or string.