[TYPO3-core] Reminder: "type" field for flexforms

[Dmitry Dulepov]

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

Hi!

Bernhard Kraft wrote:
> Again I must say I don't know why to introduce a new property. Look at the
> following piece of code from an application of me:

Two reasons:
- - possible conflict
- - keep all information about flexform fields in the flexform
  (no need to change two files if flexform changes)

> Oh. I think I just get it now. What you mean by "different extensions" have conflicts
> is that they will conflict if they have fields with the same name. You set requestUpdate for
> one field of the one flexform and also get it for the same named field of the other extension.

Yes, this is what I thought. I have a number of extensions and many of
them use "mode" field. But not all of them need to reload when this
field changes. If "requestUpdate" is used, one extension can force all
other flexforms (not even necessarily flexforms from extensions!) to
reload if the have "mode" field. Keeping reload information in flexforms
makes it local to this exact flexform. It is even not good to keep it
local to extension because there can be a number of modules in extension
with a number of flexforms. Thus flexform is the only best place.

> don't forget to send documentation changes !

Yes, thanks for reminding. This must be written down, of course.

> "Freiheit ist immer auch die Freiheit des Andersdenkenden"
> Rosa Luxemburg, 1871 - 1919

Btw, how does this translate? :)

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)

iD8DBQFEDWgURVcYnKJ8N6kRAk+cAJ46SiXUAqYS9M0NPRaFxiAx6+X2AwCfd2rF
nJpaJf7r+qPmKfpXrDtyKXM=
=2BVf
-----END PGP SIGNATURE-----