Feature #24672
Epic #55575: Streamline JavaScript Code in the TYPO3 Backend
Refactor the pagetree javascript files to be usable by other trees
| Status: | Rejected | Start date: | 2011-01-20 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | - | Spent time: | - | |
| Target version: | - | |||
| PHP Version: | 5.3 | Sprint Focus: | ||
| Complexity: |
Description
Problem:
The pagetree javascript files are currently very specific for the needs of the pagetree. This would require other tree implementations to always recreate their own components. It's an important requirement before any other tree components are created.
Solution:
The pagetree files needs to be refactored to be more generic. Mainly this is the context menu implementation, the tree implementation and their related components like the node user interface, the tree editor and the state provider. The same would be needed for the top panel and the deletion drop zone, but they need much more changes to be really generic.
I don't will do that for 4.5 anymore and it will be a task for 4.6 as the changes are much to huge. The goal for 4.5 was to create a stable pagetree. Sorry!
(issue imported from #M17154)
History
#1 Updated by Stefan Galinski over 3 years ago
- Assigned To deleted (
Stefan Galinski)
#2 Updated by Daniel Siepmann over 1 year ago
- Target version deleted (
0) - Parent task set to #55575
#3 Updated by Benjamin Mack 16 days ago
- Status changed from Accepted to Rejected
as we are in the process of kicking ExtJS out of the Core, and we streamlined all other trees, we won't fix this in the future.