Feature #1670

Task #1471: RCP: improve the editors linkage system and the views/editors synchronization

Feature #996: Link Progression chart with other command editors (synchronous and asynchronous)

Progression chart, link selection with concordance (synchronous editor)

Added by Sebastien Jacquot over 7 years ago. Updated over 4 years ago.

Status:Feedback Start date:02/11/2016
Priority:Normal Due date:
Assignee:- % Done:

80%

Category:Charts Spent time: -
Target version:TXM X.X

Description

Link points selection of progression chart with concordance editor and table (synchronous editor).

Behaviors

  • 1) on point selection:
    • if a linked Concordance editor already exists for the selected token, move to the right page and select the table row of the selected token
    • in case of extended selection, it is the last selected point that is used to update the Concordance editor
  • 2) on double click:
    • open a Concordance editor using the query of the selected token line, compute and display the page of the selected token according to current sorting order and select the table row of the selected token
      • split the editor area so the Progression chart and the new Concordance are visible
    • a new editor is opened for each query (for each line of the chart)
      • if the area already contains a linked Concordance, split the Concordance editor area so all the linked Concordances are visible

Validation tests

The functionality is a few tricky to fully test, feel free to do/add complementary tests. The tests are also linked to the multiple items of chart selection system.

Unique progression query

  • create a progression chart with one query on a relatively large corpora (so the future concordance table will have more than one page)
  • click on some points, check that the display label matches the specifications
  • double click on a point
    • a concordance editor must open below the chart by horizontally splitting the chart area
    • the selected row in table must match the selected progression point
  • click on some other points in the chart and check each time that the selected row in table matches the selected chart point
    • purpose here is to test that the system manage well the page change in the concordance editor
  • sort the concordance table on right context or other column
    • click on some points and check that the system selects well the good row in the table despite of the table sorting order
  • mix these tests with the keyboard chart entities selection system
    • click on a chart point
    • move the selection with the left and right arrow keys
    • check the selected concordance tables rows match well the chart point, auto change the page if needed (with default table sorting order and user sorting order)
  • close the concordance editor
  • click on a point, it mustn't reopen the closed concordance editor
  • double-click on a point, an new concordance must open

Multiple progression queries

  • close all editors
  • create a progression chart with more than one query
  • double click on a point of a curve
    • a concordance editor must open below the chart by horizontally splitting the chart area
    • the selected row in table must match the selected progression point
  • click on a point of another curve
    • a new concordance editor must open by vertically splitting the area of the first concordance editor
  • click, double-click, and/or use keyboard selection in chart and check that the behaviors are the expected behaviors (with default table sorting order and user sorting order and with/without extend selection modifier SHIFT key)
    • for example, a new editor must never be created for a query if one already exists for this query (despite of clicking, double clicking or using arrow keys).

Results

SJ: OK, Win 7 x64 and XP x86
BP: OK, Ubuntu

History

#1 Updated by Sebastien Jacquot over 7 years ago

  • Description updated (diff)
  • % Done changed from 0 to 70

#2 Updated by Sebastien Jacquot over 7 years ago

  • Description updated (diff)

#3 Updated by Sebastien Jacquot over 7 years ago

Defines the behavior when user changes the query of a linked concordance editor.

First proposals

Solution 1

  • disable the query input text and the "Search" button and/or hide/remove them from the editor ? It'd fix the problem and plus it may be more clear for the user that the linked editor is not a "normal" editor
  • Move the "edit" button in an other area. Anyway, even if we do not hide the search functionalities, this button is related to the view but not to the search ? We may move this button near the sorting widgets rather than the search related widgets

Solution 2

  • update the progression chart according to the new concordance query
  • potential problems with the multiple queries progression case since more than one linked concordance editor can be open

#4 Updated by Matthieu Decorde over 7 years ago

  • Subject changed from Progression chart, link selection with concordance (synchronous editor) to Progression chart, link selection with concordance (synchronous editor) V1
  • Description updated (diff)

#5 Updated by Sebastien Jacquot over 7 years ago

  • Subject changed from Progression chart, link selection with concordance (synchronous editor) V1 to Progression chart, link selection with concordance (synchronous editor)
  • Description updated (diff)
  • Status changed from New to Feedback
  • % Done changed from 70 to 80

#6 Updated by Sebastien Jacquot over 7 years ago

  • Description updated (diff)

#7 Updated by Sebastien Jacquot over 7 years ago

  • Description updated (diff)

#8 Updated by Sebastien Jacquot over 6 years ago

  • Target version changed from TXM 0.7.8 to TXM 0.8.0a (split/restructuration)

Moved to 0.7.9, still need to define the behavior when user changes the query of a linked concordance editor.

#9 Updated by Sebastien Jacquot about 5 years ago

  • Target version changed from TXM 0.8.0a (split/restructuration) to TXM 0.8.0

#10 Updated by Sebastien Jacquot over 4 years ago

  • Target version changed from TXM 0.8.0 to TXM X.X

Also available in: Atom PDF