[TYPO3-core] Fixing no-brainers?

[Dmitry Dulepov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!

Martin Kutschker wrote:
> But if the UI overhaul is moved from 4.5 to 5.0 we might end up not
> only with 4.1 (as asked by myself) but perhaps an 4.2.

It depends what exactly we mean by this new UI. typo3.org does not
really say what it is.

Ideally I imagine ajax-driven non-frame interface with tabs + XMLRPC
access to BE functions.

> Not that I
> would worry about that. In fact as 5.0 will require PHP5 I ask for a
> long-lived 4.x branch after 5.0 as not everyone will do the jump into
> a refactored Core with new requirements and changed setup (we do plan
> to remove deprectaed stuff, don't we?).

I think dropping PHP4 is the biggest problem that we can expect. Many
people will have to update live (!) servers to PHP5. It may break many
[non-typo3] sites in that live environment. So many hosters will decide
not to upgrade. So (so many "so") many people will stay with last
PHP4-compatible version...

> PS: How about requiring Mysql 4.0 or even 4.1 to take advantage of if
> it's more standard-SQL-like features? 

This is less problematic than PHP, though I just had huge problems
importing non-latin1 data from 3.23 to 4.1.x - non-latin chars were
totally messed up :( I had to force db and mysql to latin1 to put older
utf-8 content to it. "set names", etc not helped.

If we decide to do such a major change, we need to experiment and
provide detailed import/export instructions. And we can require mysql 5
because it supports views, stored procedures, etc. It will give major
performance increase. But this should be evaluated from DBAL view also.

Dmitry.
- --
"It is our choices, that show what we truly are,
far more than our abilities." (A.P.W.B.D.)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)

iD8DBQFEOkRARVcYnKJ8N6kRAjgcAKCHvD/r3IM05/oMXAfIFsPGfNNsTACgoDn4
hAngj77il3yWLVCfDqKL7FM=
=AAx4
-----END PGP SIGNATURE-----