Feature #996
Task #1471: RCP: improve the editors linkage system and the views/editors synchronization
Link Progression chart with other command editors (synchronous and asynchronous)
Status: | New | Start date: | 09/30/2015 | ||
---|---|---|---|---|---|
Priority: | Normal | Due date: | |||
Assignee: | - | % Done: | 57% |
||
Category: | Charts | Spent time: | - | ||
Target version: | TXM X.X |
Description
Progression => Concordance¶
- on point selection:
- display a label area containing:
- the 'ref' property if exists otherwise the 'text:id' property
- the global position in corpora and the total count of all tokens of the corpora
- the number of the selected token and the frequency in corpora of the selected token
- 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
- display a label area containing:
- 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
- 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
- manage a way to open a Concordance editor based on more than one line of the Progression chart:
- we may used contextual menu to do this, something as "Compute the concordance of the selected lines"
- we also may offer a way to compute the Concordance only for the selected points? Can it be useful?
Progression => Edition¶
- on CTRL/CMD + double click:
- open an Edition editor using the queries of all the lines of the chart to highlight the token, highlight "more" the token of the line that has triggered the event and move to the page of the selected token
Concordance => Progression¶
- on table row selection:
- proceed to the "on point selection" event of the Progression chart (display label)
Hyperlinks (asynchronous editors)¶
See subtasks issues.
----------------
Old specifications on the french Wiki: https://groupes.renater.fr/wiki/txm-info/public/specs_charts_progression_repartition
Subtasks
History
#1 Updated by Sebastien Jacquot almost 9 years ago
- Target version changed from TXM 0.7.7 to TXM 0.7.8
Implement a global interfaces system for editors communications and updating data/state of an editor from another one ?
First ideas:
- store a list of linked editors in the source editors (e.g.: getLinkedEditor(int i))
- define and implement a method as doSomething(Object param) which specify something to do and use it on some events.
- in some events loop through all the linked editors and call doSomething(Event event) or other param type
e.g. for linking Progression and Concordance editors:
- on double-click on a Progression point, test if there is already a linked editor with result object of type "Concordance" (see getSource() of TXM CustomizableEditor class). If no, create a Concordance editor and add the Progression editor as linked editor to it. Also add the Concordance editor as linked editor to the Progression editor.
Loop through all the linked editors and call doSomething()
- on double-click on a Concordance row, call in the event listener all the doSomething(Object param) methods of all the linked editors
This system should permit, for a same kind of editor, an easy use of this editor without links, with one link and with multiple links
(NOTE: ATM the current Concordance/Edition communications is hard coded which make it not really easy to add links)
[Edit] These questions/proposals have now their own issue: http://forge.cbp.ens-lyon.fr/redmine/issues/1471
#2 Updated by Serge Heiden almost 9 years ago
Hypertext Infrastructure¶
For a general hypertext infrastructure, we must link to related portal and desktop tickets:- Portal: Feature #667 (Resolved): GWT: x.x, HTML pages, hyperlinks (external, internal, command)
- and his descendants
- Desktop: Bug #229 (In Progress): RCP: 0.7.2, improve Index to Concordance link
- etc.
Link Transitivity¶
If a command result may link to several commands, a particular link may also herit some command parameters from the link it come from: for example a double-clic on a concordance line can have a different behavior depending on the link we come from to build the concordance.
#3 Updated by Sebastien Jacquot about 8 years ago
- Parent task set to #1471
#4 Updated by Sebastien Jacquot about 8 years ago
- Subject changed from RCP: 0.7.6, link Progression chart with Concordance to RCP: 0.7.6, link Progression chart with other command editors
#5 Updated by Sebastien Jacquot about 8 years ago
- Subject changed from RCP: 0.7.6, link Progression chart with other command editors to RCP: 0.7.6, link Progression chart with Concordance
- Description updated (diff)
- Parent task deleted (
#1471)
#6 Updated by Sebastien Jacquot about 8 years ago
- Parent task set to #1471
#7 Updated by Sebastien Jacquot about 8 years ago
- Subject changed from RCP: 0.7.6, link Progression chart with Concordance to RCP: 0.7.6, link Progression chart with other command editors
#8 Updated by Matthieu Decorde about 8 years ago
- Target version changed from TXM 0.7.8 to TXM 0.8.0a (split/restructuration)
#9 Updated by Sebastien Jacquot about 8 years ago
- Subject changed from RCP: 0.7.6, link Progression chart with other command editors to Link Progression chart with other command editors
- Description updated (diff)
#10 Updated by Sebastien Jacquot about 8 years ago
- Description updated (diff)
#11 Updated by Sebastien Jacquot about 8 years ago
- Description updated (diff)
#12 Updated by Sebastien Jacquot about 8 years ago
- Description updated (diff)
#13 Updated by Sebastien Jacquot about 8 years ago
- Description updated (diff)
#14 Updated by Sebastien Jacquot about 8 years ago
There is no RCP API to programatically split the editor area in Eclipse 3.x. It is possible to do that in Eclipse 4.x through the Model service but we don't use 4.x model, we use the 3.x model.
Here is a 3.x workaround by generating fake drag event: http://git.eclipse.org/c/platform/eclipse.platform.ui.git/tree/tests/org.eclipse.ui.tests/Eclipse%20UI%20Tests/org/eclipse/ui/tests/session/Bug95357Test.java
I didn't manage to implement this example, it seems to use another bundle version of org.eclipse.ui than we use, e.g. PartSite doesn't have method getPane() in our version.
#15 Updated by Sebastien Jacquot about 8 years ago
- Description updated (diff)
#16 Updated by Sebastien Jacquot about 8 years ago
- Subject changed from Link Progression chart with other command editors to Link Progression chart with other command editors (synchronous and asynchronous)
- % Done changed from 0 to 50
#17 Updated by Sebastien Jacquot about 8 years ago
- Description updated (diff)
#18 Updated by Sebastien Jacquot over 7 years ago
- Target version changed from TXM 0.8.0a (split/restructuration) to TXM 0.7.8
#19 Updated by Sebastien Jacquot over 7 years ago
- Target version changed from TXM 0.7.8 to TXM 0.8.0a (split/restructuration)
#20 Updated by Sebastien Jacquot over 6 years ago
The split is now effective. But the new opened Concordance editor should hide the settings. (tested on Win XP)
#21 Updated by Sebastien Jacquot over 6 years ago
The context menu of a linked Edition is not the same that when opening an Edition "normally" and the "Send to concordance" command does nothing. The system may use the old Edition code and should use now the Synoptic edition (is it now the default edition?). [SJ: december 2018: fixed]
#22 Updated by Sebastien Jacquot over 5 years ago
- Target version changed from TXM 0.8.0a (split/restructuration) to TXM 0.8.0
#23 Updated by Matthieu Decorde over 4 years ago
- Target version changed from TXM 0.8.0 to TXM 0.8.2
#24 Updated by Sebastien Jacquot almost 4 years ago
- Target version changed from TXM 0.8.2 to TXM X.X