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

[Andy Staudacher]

Please don't send HTML mails, it's a pain to add the quotation ">" after
converting it to text only.

Martin Seebach wrote: 
>Andy Staudacher wrote: 
>>As I wrote at the end of my mail, the tikipro dev managed to integrate
>>phpbb with very few changes. It's possible, given the right tools from
>>the CMS.
>I looked into the way phpBB integrates in tikipro - it simply
>imports the 'frame' of the page (menus, layout etc), and lets the
>phpBB template engine handle that as the page header and footer.
>Functional, definately, yes, but from a technicians point of view,
>not very pretty.
>There are serveral ways to handle these things, spanning from titkipros
>very simple "i'll draw a menu for you" to Typo3s all-embracing
philosophy.
>The first is probably well fit for a large number of purposes, but when
>you want to do caching, indexed search etc, it's just not a good idea.

Phpbb, G2, etc. have their own templating engine, their own caching
system, etc.
When you want to let these application make use of the CMS' templating
engine etc., you'll need to change a lot of files. I'd call this a fork.
As the first phpbb integration in typo3 has shown, this is a quite
difficult task too, introducing a lot of bugs.
However, as I stated, I want a minimal invasive integration, changing 0
code in the CMS and only a few lines in phpbb. But phpbb is a bad
example anyway, because it isn't "open minded", not designed to
integrate with other apps. But still, with variant "use both user tables
in parallel" it's possible.

>>I'm asking to keep the tables in sync by calling events whenever they
>>get out of sync, exactly in the moment when it happens. So, the moment
>>they are out of sync is extremely short. As we talk of data as
"language
>>choice, address, real name, ...", I can't imagine a scenario this
>>instant of loss of data integrity would do much harm. 
>Just because it can work doesn't make it a good idea. ;) I made phpBB
run,
>and quite well, too. I just fear the day something stops working. If
you
>try to keep heavily updated tables in sync, maybe even across serveral
>mirroring database servers, something is bound to go wrong. A users
default
>language set wrong today, a credit card transaction run twice tomorrow
..
Please, you're exaggerating. 

To some point this is on topic, but it's far too phpbb-specific. I'd
prefer if this discussion went into a more generic direction.

Thanks - Andy Staudacher