[TYPO3-core] RFC #16408: Support for Custom Navigation Components

[Stefan Galinski]

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

-- 
Stefan Galinski
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 16408_v1.diff
Type: text/x-patch
Size: 13927 bytes
Desc: not available
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20101115/6b1cbacb/attachment-0001.bin>