[Typo3-dev] Event System in the core / Ease the integration of 3rdparty apps

[Leendert Brouwer [Netcreators]]

"Martin T. Kutschker" <Martin.no5pam.Kutschker at blackbox.n0spam.net> wrote in
message news:mailman.1.1094203035.16401.typo3-dev at lists.netfielders.de...
> Leendert Brouwer [Netcreators] wrote:
> >
> > I've touched upon the topic of user management in relation to
integrating
> > 3rd party apps with TYPO3 through extensions before. I think the real
> > problem lies in the design of the user management code in TYPO3. It's
badly
> > factored, and thus it is hard to override.
>
> And so is in many, many other projects. :-(

Indeed, but if we're talking about integration with TYPO3, all that matters
is the design of TYPO3 in that regard. Link handling etc., is the
responsibility of the third party app, and often a factor that causes
trouble. In the case of osCommerce for example (I played around with a very
simple integration of that with TYPO3 through output buffering), it was
fairly easy, as in osCommerce, link handling happens through a single
function which I just modified directly. Nasty, but working fine. But user
management was still in parrallel next to TYPO3, so that sucked.

>
> And if you've managed users you realize that the "rendering engine" (aka
> templates) is incompatible.

Yeah, although I personally don't really consider that as _that_ big a
problem. It's not that hard to modify a design usually, and once you have
that done, you could simply fetch the application's output through e.g.
output buffering to have it show up in your TYPO3 pages.

>
> Or the database access is different, either because of direct calls to
> mysql_* functions (or PostgreSQL, Oracle,.. ) or the projects uses jus
> another abstraction layer.

That's a problem you're not likely to get rid of :)

> PS:
>
> I'm still dreaming of bare-bone discussion forum, shop sytstem, ...
> These system wouldn't have any user managment nor would they output
> anything. Just pure API access.

Me too sir. In fact, I think a lot of applications should have that
architecture. No view, just an API. I'd even like to see TYPO3 like that.
But I'm afraid that's hardly possible without forking it.

>
> But who would spend hours of programming on such projects?
>

I suppose one could start 'The Big Forking Project' if there was enough
interest from all kinds of areas (not even just TYPO3), since programmers
are usually too stubborn to change their project to fit into the ideas of
some other dudes. But I guess I'm dreaming, just like you say you are ;)