Task #2398

Rethink Lexicon/Index units logic

Added by Sebastien Jacquot over 1 year ago. Updated 10 months ago.

Status:New Start date:04/05/2017
Priority:Normal Due date:
Assignee:- % Done:


Category:Development Spent time: -
Target version:TXM 0.8.1


There is a problem with the interaction between these classes leading to some code visibility, code comprehension and useless duplicate code problems. We need to rethink them and maybe also the IndexEditor and DictionnayEditor (at least rename the last one).
I think Lexicon should extend Index. It's only an Index with a specific query [].
Then the class will benefit from all new features involved in the restructuration (eg. @Parameter annotation).


  • Lexicon extends Index
  • remove lexicon member and lexicon mode from Index class
  • stop to use the Line class
  • for an index on partition, a lexicon could be created and recycled or not for each part (as a child result of each part)
  • etc.


Task #2217: TXMResult and TXMEditor hierarchy, modify Lexicon related...New

Task #2180: Lexicon, extract and move messages to plug-insFeedback

Task #2156: Reorganize Lexicon functions into plug-in projectsNew


#1 Updated by Sebastien Jacquot about 1 year ago

  • Description updated (diff)
  • Target version changed from TXM 0.7.8 to TXM 0.8.0

#2 Updated by Serge Heiden about 1 year ago

What a DictionnayEditor manages actually, is more a general (not TXM) lexicon than a dictionary (the entries are word forms, not lemma, and there are no definitions).

Thus it could be renamed -> LexiconEditor

#3 Updated by Sebastien Jacquot about 1 year ago

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

#4 Updated by Sebastien Jacquot 10 months ago

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

Also available in: Atom PDF