Project

General

Profile

Actions

Feature #24071

closed

Support for Custom Navigation Components

Added by Stefan Galinski over 13 years ago. Updated almost 13 years ago.

Status:
Closed
Priority:
Should have
Category:
-
Target version:
-
Start date:
2010-11-15
Due date:
% Done:

0%

Estimated time:
PHP Version:
5.3
Tags:
Complexity:
Sprint Focus:

Description

Problem:
Currently there is no way to integrate custom navigation components that are not based on an iframe.

Solution:
I implemented a solution that is based on a simple registering for each backend module and an expected directory layout. The components are loaded on demand to improve the overall performance. It's directly bound to the new module menu and is always used as a first option.

Example:
1. Register an navigation component

t3lib_extMgm::addNavigationComponent('tools_txpagetreeM1', 'typo3-pagetree', array(
TYPO3.Components.PageTree'
));

Parameter 1: Module name
Parameter 2: Name of the navigation component
Parameter 3: ExtDirect Providers

2. Create the directory layout

- myExt |- components |- pagetree |- css |- javascript

All files inside the css and javascript folders are automatically loaded together with the TYPO3 backend. The component name must not contain the prefix "typo3-".

I will add this documentation to the pending documentation page after the commit.

How to Test:
Use the attached test extension inside the bugtracker to evaluate the new functionality. Also the latest developements of the pagetree are already based on this implementation.

(issue imported from #M16408)


Files

T3X_customnavdemo-1_0_0-z-201011152213.t3x (8.89 KB) T3X_customnavdemo-1_0_0-z-201011152213.t3x Administrator Admin, 2010-11-15 22:14
16408_v1.diff (13.6 KB) 16408_v1.diff Administrator Admin, 2010-11-15 22:14
Actions #1

Updated by Steffen Kamper over 13 years ago

Committed to trunk rev 9395

Actions #2

Updated by Susanne Moog almost 13 years ago

  • Target version deleted (4.5.0)
Actions

Also available in: Atom PDF