Task #2398

Rethink Lexicon/Index units logic

Ajouté par Sebastien Jacquot il y a 5 mois. Mis à jour il y a 19 jours.

Statut:New Début:05/04/2017
Priorité:Normal Echéance:
Assigné à:- % réalisé:

53%

Catégorie:Development Temps passé: -
Version cible:TXM 0.8.0a (split/restructuration)

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

Solution

  • 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.

Sous-tâches

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

Historique

#1 Mis à jour par Sebastien Jacquot il y a 2 mois

  • Description mis à jour (diff)
  • Version cible changé de TXM 0.7.8 à TXM 0.8.0

#2 Mis à jour par Serge Heiden il y a 2 mois

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 Mis à jour par Sebastien Jacquot il y a 19 jours

  • Version cible changé de TXM 0.8.0 à TXM 0.8.0a (split/restructuration)

Formats disponibles : Atom PDF