Task #2398

Rethink Lexicon/Index units logic

Added by Sebastien Jacquot over 2 years ago. Updated about 1 year ago.

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

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

Description

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 DictionnaryEditor (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).

Solution

  • Lexicon extends Index
  • remove lexicon member and lexicon mode from Index class

Subtasks

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

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

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

History

#1 Updated by Sebastien Jacquot over 2 years ago

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

#2 Updated by Serge Heiden over 2 years 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 over 2 years ago

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

#4 Updated by Sebastien Jacquot about 2 years ago

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

#5 Updated by Sebastien Jacquot about 1 year ago

  • Description updated (diff)
  • Status changed from New to Closed
  • Target version changed from TXM 0.8.2 to TXM 0.8.1

Also available in: Atom PDF