var type_index = $.inArray(rel_info.type, rel_types);
var source_found = get_ellipse( rel_info.source_id );
var target_found = get_ellipse( rel_info.target_id );
+ var emphasis = rel_info.is_significant;
if( type_index != -1 && source_found.size() && target_found.size() ) {
- var relation = relation_manager.create( rel_info.source_id, rel_info.target_id, type_index );
+ var relation = relation_manager.create( rel_info.source_id, rel_info.target_id, type_index, emphasis );
// Save the relationship data too.
$.each( rel_info, function( k, v ) {
relation.data( k, v );
temporary = null;
}
}
- this.create = function( source_node_id, target_node_id, color_index ) {
+ this.create = function( source_node_id, target_node_id, color_index, emphasis ) {
//TODO: Protect from (color_)index out of bound..
var relation_color = self.relation_colors[ color_index ];
- var relation = draw_relation( source_node_id, target_node_id, relation_color );
+ var relation = draw_relation( source_node_id, target_node_id, relation_color, emphasis );
get_node_obj( source_node_id ).update_elements();
get_node_obj( target_node_id ).update_elements();
return relation;
return srctotarg.split('-...-');
}
-function draw_relation( source_id, target_id, relation_color ) {
+function draw_relation( source_id, target_id, relation_color, emphasis ) {
var source_ellipse = get_ellipse( source_id );
var target_ellipse = get_ellipse( target_id );
var relation_id = get_relation_id( source_id, target_id );
var ey = parseInt( target_ellipse.attr('cy') );
var relation = svg.group( $("#svgenlargement svg g"), { 'class':'relation', 'id':relation_id } );
svg.title( relation, source_id + '->' + target_id );
- svg.path( relation, path.move( sx, sy ).curveC( sx + (2*rx), sy, ex + (2*rx), ey, ex, ey ), {fill: 'none', stroke: relation_color, strokeWidth: 4});
+ var stroke_width = emphasis === "yes" ? 6 : emphasis === "maybe" ? 4 : 2;
+ svg.path( relation, path.move( sx, sy ).curveC( sx + (2*rx), sy, ex + (2*rx), ey, ex, ey ), {fill: 'none', stroke: relation_color, strokeWidth: stroke_width });
var relation_element = $('#svgenlargement .relation').filter( ':last' );
relation_element.insertBefore( $('#svgenlargement g g').filter(':first') );
return relation_element;
$( '#dialog-form' ).dialog( {
autoOpen: false,
height: 350,
- width: 330,
+ width: 340,
modal: true,
buttons: {
'Merge readings': function( evt ) {
var target_found = get_ellipse( source_target[1] );
var relation_found = $.inArray( source_target[2], $( '#keymap' ).data( 'relations' ) );
if( source_found.size() && target_found.size() && relation_found > -1 ) {
- var relation = relation_manager.create( source_target[0], source_target[1], relation_found );
+ var emphasis = $('#is_significant option:selected').attr('value');
+ var relation = relation_manager.create( source_target[0], source_target[1], relation_found, emphasis );
relation_manager.toggle_active( relation.attr('id') );
$.each( $('#collapse_node_form').serializeArray(), function( i, k ) {
relation.data( k.name, k.value );
<p>Fill in the details of the relationship as indicated in the dialog:</p>
<img src="[% c.uri_for( '/images/02_relationdialog.png' ) %]">
-<p><em>Type</em> can be any one of the types that appears in the key to the right of the screen.</p>
+ <p><em>Type</em> can be any one of the types that appears in the key to the right of the screen.</p>
<p><em>Scope</em> can be one of:</p>
<ul>
<li>Local - the relationship applies only at this point in the text</li>
<li>Document - the relationship applies throughout the text</li>
<li>Global - the relationship applies throughout all texts of this language</li>
</ul>
- <p><em>NOTE:</em> at the moment, "global" scope is treated as "document" scope, i.e. only applies throughout the individual text.</p>
+ <p><em>n.b.</em> At the moment, "global" scope is treated as "document" scope, i.e. the setting only applies throughout the individual text and not throughout all the user's texts.</p>
- <p>The relationships are displayed as colored paths between readings. While in 'edit' mode, clicking on a relationship path will display the information associated with it, and give the user an option to delete it. Deletion of a 'global' relationship will remove that relationship throughout the graph.</p>
+ <p>The remaining options concern the stemmatic significance of the reading, as judged by the philologist. It is possible to answer the following questions:
+ <ul>
+ <li>Is this likely to be a stemmatically significant instance of variance?</li>
+ <li>Would a scribe, seeing the first reading, consciously alter ('correct') it to the second?</li>
+ <li>Would the scribe correct the second to the first?</li>
+ <li>Is this variation reasonably likely to occur in multiple witnesses by chance?</li>
+ </ul>
+
+ <p>The relationships are displayed as colored paths between readings. Relationships marked 'stemmatically significant' will appear with much thicker lines than those that are not; relationships that might be significant will be somewhat thicker than those that are not. While in 'edit' mode, hovering the mouse over a relationship path will display the information associated with it, and give the user an option to delete it. Deletion of a 'global' relationship will remove that relationship throughout the graph.</p>
<img src="[% c.uri_for( '/images/03_infodelete.png' ) %]">
<p>When you are ready to move elsewhere in the graph, click the 'hand' icon to return to select mode.<p>
projects / scpubgit/stemmaweb.git / commitdiff
