[TYPO3-core] Discussion #27247 [BUGFIX] Bring back recStatInfoHooks hook in Page Tree

[Georg Ringer]

Hi,

Am 07.06.2011 22:04, schrieb Jigal van Hemert:
> It was just a general remark. I personally find newsgroups/mailinglists
> easier for discussions than bugtrackers/etc.

+1 on that.


> - the hook will be called/evaluated for every item in the pagetree; its
> impact on speed should be looked at

of course true. but not having an extension using it is just a check in
a is_array() which is not a problem.

> - the pagetree was redesigned by the usability team; I would at least
> consult them about changes which make it possible for extensions to make
> modifications to it

I don't understand that. any extension can use an xclass to achieve
that. If there would be fear that something is changed, GPL is the wrong
license.

>>> To me this is voting for your own patch.
>> sorry I just wanted to state that it is a nobrainer for me.
> 
> Sorry, that wasn't clear to me. I removed the -2.

thanks

>>> To me this is voting for your own patch.
>> sorry I just wanted to state that it is a nobrainer for me.
>
> Sorry, that wasn't clear to me. I removed the -2.

thanks

> I haven't used it in a while, but a year or two ago l10nmgr did a
> marvellous job at this.

Guess what: the l10nmgr uses the hook I want to get into the core again.
This extension brought me to the hook and it can't work with 4-5+ anymore.

> It was for a site where localization editors
> would do the translations with Trados and the necessary files could
> easily be exported and imported. There were also possibilities to do the
> translations online or with Excel files.

Yeah I know all that as I am developing something better - only
regarding the displaying of changes.
l10nmgr uses a custom index to tell you if something changed which can
be very difficult sometimes because there need to be extra code to
change the index which doesn't happen for 100%. And there are many other
things which the core can't currently too (e.g. if you use DAM or any
other MM relation, it fails to create a helpful diff for you).

My extension will generate the information on the fly

> It seems you want to build an alternative way. That's fine. I was just
> wondering if the core should provide methods to clutter the pagetree
> with additional information.

Again: I don't understand that.
1st: The core provides those methods already (XCLASS, GPL, ...) and it
is just about makeing it easier or harder.
2nd: How can the UX-Team decide if an extension will clutter the page
tree or not?
3rd: I always try to give things back, don't make it harder ;)

Georg