[TYPO3-hci] Less ways to do it...

[Tapio Markula]

Kasper Skårhøj wrote:

> I think they are rare. Spacer could potentially be used by some as a  
> menu-division element.

I have used them for some customers - usable and needed

> Recyclers - in fact they represent a concept that never materialized;  
> deletion of elements should be moved to closest recycler in tree was  my 
> original idea 7 years ago... :-)

but existing way implementent confusing because the functionality is 
missing. They confused me - why to have page type 'recycler', which
doesn't actually work as expected.
I understand you however - but IMO you should have done 'reclycler'
as "sleeping" page type - not listed before it really works but
the possibility enabled.

>> Features that are never used bloat the interface and make maintainance
>> harder. I'd be really interested in how many people have ever used  moint
>> points

Mount points are very seldom used - *but* there are cases where they are 
important. I had one customer, whom I could not solve otherwise the menu

SUBMENU 1
	ITEM1 ITEM2 ITEM3 ... ITEM8

SUBMENU 2
	ITEM1 ITEM2 ITEM3 ... ITEM8

ITEM3-ITEM8 should be the same and some of ITEM3 ... ITEM8 have subpages.

Shoutcuts didn't worked because they link to *other* branch.
Menu result should look like menu items ITEM3 ... ITEM8
of SUBMENU1 really belongs to SUBMENU2

Content from another page didn't work because subpages are missing.

The *only* solution was combine 'content from page x* + mountpoints, 
which took the subpages.

Disadvantage is that needs extra parameters and address row looks worse.

, spacer and recycler (and would miss them for other reasons  than
>> legacy...).


Michael, IMO you have not thought this thoroghly. If you remove seldom
used features, people get trobles. Seldom used features are *important*
in exceptional cases.