[TYPO3-hci] Combine page and list module into one module

[Franz Koch]

Dmitry Dulepov [typo3] wrote:
> Hi!
> 
> Andreas Balzer wrote:
>> But does this make sense? If offers you a not so user friendly view on 
>> pages for simple page content elements.
> 
> It does because what how it should be by definition in List module. It 
> *lists* _all_ records for the current page.
> 
> This module is supposed to be technical, not used friendly.

If it's only technical, why isn't it admin-only then ;)

> The other 
> problem is that it is used for making news and other records, which 
> should have their own managing modules... But this is truly another 
> problem.

It isn't. Why should every extension provide it's own way of managing 
records? This is the worst you can do and truly doesn't reflect the 
sense of a content management system. The CMS itself has to provide a 
default, easy to use way for managing records. In TYPO3 the only way to 
do this is the list module. Unless there won't be provided a better 
solution by default - this module should be enhanced to be userfriendly.

>>> Sorry, no go. There are use cases when content element must be in 
>>> sysfolders to be selected randomly (or with certain logic) to be 
>>> presented on pages.

Who said that is has to be hardcoded? Provide a TS option to configure 
it and everybody is happy.

>>  > I see no any real reason for this as well. "Do not implement a feature
>>> just because you can" principle.
>> Developper is speaking, right?
>> Not everything that can be implemented or is implemented is actually 
>> good in terms of usuability. And you wouldn't care if you have used T3 
>> with such a restriction for some days.
> 
> Not developer... User, actually. Making changes just because you (me, 
> John Doe, ...) can is bad. When users are used to something, changes 
> should be made extremely carefully.

sorry - I can't agree here by any means. Only because you got used to 
something it doesn't mean that you like the way it is, nor that you 
won't be much happier if it would work in a different, better way.

And it should not be implemented, just because we can. It should be done 
in terms of usability - which if I might remember you is the goal for 
the 4.x branch. And the decision whether it's useful or not should not 
be done by geek-devs. Surely devs know how to use this - but not the 
average editor - and that's the reason why there has to be done 
something. If everybody would be a geek - we wouldn't need a CMS.

You said yourself in the blog entry topic, that you agree with what is 
said in the blog entry, which is about usability. So why are you that 
much against this usability improvement?

>> They just remove the flexibility to create contents everywhere and 
>> limit the places to those that are useful.
> 
> Dno't use this feature if you do not want to. Hide it with TSConfig. But 
> don't remove it for users who want to use it.

How about a simple pageTS setting to restrict which db-tables are 
allowed to be seen in list module on a certain branch of the pagetree?

Btw - there seems to be a bug in list module - tt_content records get 
listed, although they are only allowed to be edited (for page module) 
and not allowed to be listed in the user-group settings of the editors. 
Is this the desired way?

-- 
kind regards,
Franz Koch