feature request #8474
closed
Make TermCollection.orderRelevant usable for TermTrees
Added by Andreas Müller over 4 years ago.
Updated almost 3 years ago.
Description
Dazu müsste es:
editierbar seinDer TermTree müsste unterschiedlich sortiert angezeigt werden, je nach Zustand des Flags, also mal in der explizit definierten Reihenfolge, mal alphabetisch (nicht unbedingt notwendig, aber sinnvoll)- Beim Anlegen eines Baumes wäre es sinnvoll, dass man gleich zwischen sortierten und unsortierten Bäumen unterscheiden kann (nicht notwendig, aber sinnvoll) => #9643
Unsortierte Bäume müssen sich beim Drag&Drop wie unsortierte Bäume verhaltenMögliche Add Methoden sollten sich ebenfalls wie unsortierte Bäume verhalten, also ein hinzufügen an einer bestimmten Stelle ist nicht möglichBeim Ändern des Flag Wertes muss ein Refresh der Baumansicht stattfindenAls default sollten wir wohl einen sortierten Baum anlegen bei NewTree
Strongly related to #8476 and #8477
- Related to bug #8465: Term nodes order in term trees is ignored in term tree editor added
- Related to feature request #8477: Implement support for TermCollection.allowDuplicates in TaxEditor added
- Description updated (diff)
- Target version changed from Release 5.10 to Release 5.11
- Target version changed from Release 5.11 to Release 5.12
- Status changed from New to In Progress
- Description updated (diff)
- Status changed from In Progress to Resolved
- Assignee changed from Patrick Plitzner to Andreas Müller
- % Done changed from 0 to 20
- Status changed from Resolved to In Progress
- Assignee changed from Andreas Müller to Katja Luther
Only editing the flag is implemented until now so I put it back to InProgress
- Related to bug #8776: Open issues for TermCollection.allowDuplicates handling in TaxEditor added
- Related to bug #8774: Reimplement term tree editors to implement the general save strategy added
Note: saving often does not work due to issues to be solved in #8774
- Target version changed from Release 5.12 to Release 5.13
- Target version changed from Release 5.13 to Release 5.14
- Target version changed from Release 5.14 to Release 5.15
- Target version changed from Release 5.15 to Release 5.18
- Target version changed from Release 5.18 to Release 5.19
- Target version changed from Release 5.19 to Release 5.25
- Description updated (diff)
most of the topics are already fixed in the meanwhile.
- Description updated (diff)
- Status changed from In Progress to Closed
- Target version changed from Release 5.25 to Release 5.24
- % Done changed from 20 to 100
This seems to be completely fixed. Maybe you can find out when the last relevant commit was and attache the ticket to the according version. Otherwise we keep it here.
- Target version changed from Release 5.24 to Release 5.12
Also available in: Atom
PDF