[Typo3-dev] Hooks...

[Christian Jul Jensen]

Hi Rob, list

Robert Lemke <robert at typo3.org> writes:

> Generally it is a good idea to user the getUserObj way if you have more than
> one function you need to provide for the hook, because you only have to
> specify your class name once and all functions of that hook will be used
> automatically.

Makes sense. I didn't think of that situation. That justifies the use
of different ways.


> I prefer the getUserObj way where it makes sense, but sometimes the
> callUserFunction way is quite more flexible.

I think the other is cleaner in some ways. But it's not a big thing. I
just didn't see the point you mention above

> I think it is good to have both ways, maybe we have to give better
> explanations how both work for the implementor of a hook. 

Your article is pretty good, maybe just outline the differences of the
two ways of doing it.

> I didn't think much about an abstraction function, but at the first
> glance I can't imagine how that function would look like. Do you?

I have a few ideas, but I think I can come up with 20 ideas that makes
more sense to use resources on before this.

--
- julle