[TYPO3-project-4-3] Global categorization

[Patrick Gaumond]

ben van 't ende [netcreators] wrote:

> So TYPO3-lobbyist is what we are called? Nice ;-) 

At least it suite me better than "TYPO3 Cheerleader". ;)

And lobbying is really what I'm doing in this case.


> I was fighting with 
> this subject in some projects as well. It is mostly government related 
> institutes that ask for this. We have been discussing this at 
> Netcreators too and what we would need is that this is integrated into 
> the most important extensions there are. 

Sure category is not a subject for 50 pages sites projects... And to be 
successful, Core AND almost-core extensions need this. It's also very 
logical to have this centrally accessible.

> We decided to first check out 
> if we can do this with tt_news. I also discussed this with Rupert and he 
> made some interesting points:
> 
>> IMO the tt_news (3.0) category handling currently offers far more 
>> flexibility/features than tx_categories so the question should better 
>> be: What does it cost to integrate the tt_news category handling to 
>> tx_categories and then extend other exts to use this  ;-)

Well, for me I don't care which system I end up using, being 
tx_categories or the one originating from tt_news. The main goals remain 
the same:

1. Central categorization system
2. Flexible
3. Available at Core level
4. Promoted to ext devs thus fully embraced by Core Team
5. Start small but realistic with expansion in mind


>> another point is, that I consider the way how the virtual category 
>> field is added to all tables as a kind of a hack - It will make a huge 
>> amount of work to integrate this seemlessly to the TYPO3 DB handling. 
>> Since such "virtual" fields are not supported by the core itself, a 
>> lot of functions in tcemain, tceforms, transferdata and so on have to 
>> be extended to support this feature in permissions, workspaces, 
>> language overlays....
>> But besides such big things like workspaces and translations there are 
>> also many, many small functions in the TYPO3 Backend which rely on the 
>> fact that each relation has an actual existing field in the database.
>> Unfortunately I have no Idea how to solve the problem to add a global 
>> category field to each db table in another way.

Maybe category are not needed for everything then modification could be 
concentrated on pages, tt_content for the Core then giving advices and 
method for Ext developers.

> It seems inevitable to me that at one point we would really need to 
> integrate this global categorisation. Any remarks from the techies?

We're on the same frequency !

Patrick