One Markup Idea: The Arrow.
I have a feeling this would work best in conjunction with the reverse interlinears but even so one of the most used markups in my paper bible is the old "Circle to arrow" markup. (see the image).
It's not a very good example of how I would use the markup, but it demonstrates the markup.
Problem is there would need to be a way to mark "origin" and then "destination". This would definitely be a two step markup procedure.
- Highlight "not"
- Click Markup (or ctrl+k if last used)
- Highlight "Double tongued"
- Click something else or perhaps Ctrl+k to finish the markup.
- Repeat for each additional arrow destination(?).
C
Sarcasm is my love language. Obviously I love you.
Comments
-
I have a feeling this would work best in conjunction with the reverse interlinears but even so one of the most used markups in my paper bible is the old "Circle to arrow" markup. (see the image).
It's not a very good example of how I would use the markup, but it demonstrates the markup.
Problem is there would need to be a way to mark "origin" and then "destination". This would definitely be a two step markup procedure.
- Highlight "not"
- Click Markup (or ctrl+k if last used)
- Highlight "Double tongued"
- Click something else or perhaps Ctrl+k to finish the markup.
- Repeat for each additional arrow destination(?).
C
Yes please, Logos as users we are actually capable of doing this. My work around for this sort of markup has been to use sentence diagrammer in a very crude fashion...but oh that's right Logos determined we don't need sentence diagrammer at the moment.
0 -
Problem is there would need to be a way to mark "origin" and then "destination". This would definitely be a two step markup procedure.
I like this, but it creates some difficult UI problems.
It's "modal". Once you select the origin, you're in a "mode" where the next highlight is destination. How do you know you're in the mode? How do you get out of it if you want to cancel? How do we represent the origin if you haven't picked a destination? How do you use the same origin three times, as in your example -- by repeatedly selecting destination? Do we need to have a standard markup key, but when your markup was a "two-parter", use a different markup key for a destination?
What if you do two arrows from your origin, then come back tomorrow and want to add a third destination. How do you reselect the origin?
These aren't unsolvable problems, but they are complicated and do need answers. We can work on them, but I'd also love to hear your suggestions....
0 -
but oh that's right Logos determined we don't need sentence diagrammer at the moment.
Andrew,
This isn't really a constructive comment.
0 -
I like this, but it creates some difficult UI problems.
I agree, but I think a workable sollution can be had. I do not have a problem with it being Modal. In know that you're trying to get away from that in L4 but this makes great sense to me.
Here's a possible non-modal setup (for a related example see how Jing draws arrows).
- Select the circle and arrow markup from the list
- Click the first word which should have the circle around it (The circle appears and the pointer changes to an arrow)
- Drag (stay clicked) the arrow to it's destination word. The arrow should "snap" to each word it contacts so that it's easy to lock it in by simply releasing the drag.
That solution is not modal but has a few faults:
- It's limited to ONE word, not a phrase, and sometimes I'm going to want phrases - on one or both sides of the link.
- if the areas I want to connect are not in the same screen, I have to be able to scroll - that's not easy. It can work with a wheel mouse, but what about a touchpad?
- There is no cancel, it's just like every other markup. You can highlight it and remove it though, just like any other markup.
- It's also limited to only one arrow per markup. So multiple arrows as my other example shows would require doing this three times. IMHO that's not really a burden for me.
A modal solution could solve some of those faults but potentially introduces some additional complexity from the user's standpoint.
- Select the circle and arrow markup from the list
- Click the first word and drag to highlight the word or phrase that should be circled.
- The UI will "fade" or an overlay would appear, perhaps a tooltip that says, "click on arrow destination or ESC to quit"
- ESC would cancel the process.
- now you can scroll as far as you want (gen to rev if you care to) to locate the next phrase. Note that when hovering over any text the arrow should appear to follow your progress as the above modeless method indicates.
- Click and drag over the destination word/phrase to anchor the arrow.
- the UI remains faded and says, "point to more text and ESC when finished." and continues to show another arrow. In this manner you can perform a link like the one I've shown with three arrows.
Some observations to the modal method:
- It's modal and L4 isn't really like that. (But I think it's clear enough for even aunt Gertrude).
- It works with touchpads.
- um... I wish I could think of something else to say - but don't worry someone will.
Further suggestions:
- The arrows should have a slight curve which "tries" to stay out of the way of other text.
- The arrows should have some translucence so they don't block text.
- I'm not concerned perhaps about varying line widths but the addition of a few colors would be great, red, yellow, green, puce (ok, well maybe not puce).
- If this was tied to interlinear data than the same arrows would appear in every version with interlinear data (ESV, NA27, NASB etc.) That would be useful.
I can "see" both of these examples in my head and like them both, I wish I could figure out how to do a video mockup, but alas I'm left hoping my description is clear enough.
Sarcasm is my love language. Obviously I love you.
0 -
but oh that's right Logos determined we don't need sentence diagrammer at the moment.
Andrew,
This isn't really a constructive comment.
I am not sure what you mean. Its a comment about the direction of the software. Its a comment about what L4 final release is going to offer. I don't see how its inapprorpiate to comment on ways we have done things in the past as workarounds and now can not do so. It is providing feedback to Logos that they can not get through simple usages statistics.
0 -
but oh that's right Logos determined we don't need sentence diagrammer at the moment.
Andrew,
This isn't really a constructive comment.
I am not sure what you mean. Its a comment about the direction of the software. Its a comment about what L4 final release is going to offer. I don't see how its inapprorpiate to comment on ways we have done things in the past as workarounds and now can not do so. It is providing feedback to Logos that they can not get through simple usages statistics.
Maybe you didn't intend it, but I took "but oh that's right Logos determine" as a condescending tone as well. FWIW
0