[TYPO3-core] RFC: "type" fields for flexforms

[Dmitry Dulepov]

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

Hi!

Bernhard Kraft wrote:
> Why you just don't add the name of the field to the "normal" type's field
> of the table dynamically/statically however your extension requires.

You probably mean 'requestUpdate' in that table (tt_content)? I did not
try it, yes. In fact, I even did not even have idea to try it because it
looks logically wrong for me. I will explain why.

All information about flexform fields is kept in a single place: in the
flexform xml. Logically, reload flag is a property of flexform field. It
should be in the same place as field properties: in the flexform. But
logical problem is not the worst problem, there is another one (much worse).

What if two flexforms in different extensions have a field with the same
name (say, "mode")? Than one extension will be affected by another. One
extension will define that it wants to reload form if "mode" field
changes. Since it is a global setting (in ext_tables.php probably), it
will affect "mode" field in another extension too! This is bad. My
solution isolates form reload property in the flexform, thus other
extensions are not affected.

There is no naming conventions for flexform fields, so using
"requestUpdate" is bad for for flexforms.

> Another thing is: displayCond can currently only have ONE display condition per
> element. I maded a patch by which it is possible to combine several conditions
> using && and || like in Wolfgang Klingers patch for matchcondition.

This does solve a problem of refreshing flexform when flexform's field
is changed. But this patch is good! I missed it once.

Dmitry.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFECaHCRVcYnKJ8N6kRAv3uAJ9LdMv+LOnYyrV/0K4voPC6YQgYwgCgkx4j
+kzR67F7bIlHMFdFqaYG0Pc=
=CvL4
-----END PGP SIGNATURE-----